ROOTER Toutes les Tablette Intel avec SuperSU !

Salut les foufous,
Aujourd’hui la question de root
J’ai mis en place un outil pour vous permettre de Rooter votre tablette efficacement sans avoir a passer par des solutions douteuse.

Vous avez besoin de votre tablette en exécution sous Android, d’un PC et d’un câble USB pour les relier ensemble.

Voici le lien Root-tablette-chinoise.net

– Commencer par extraire le dossier « Root-tablette-chinoise.net » sur votre PC
– Activer le débogage USB de votre tablette, je vous invite a regarder la vidéo explicative

Relier la tablette au PC
– Exécuter « 3 Root-tablette-chinoise.net » et laisser vous guider jusque le reboot automatique de la tablette.

Vous voila ROOTED avec SuperSU vous pouvez mettre a jour le binarie normalement puis rebooter votre tablette !

Vous pouvez vérifier l’état du ROOT avec Root Check

Enjoy…

Retrouver sur notre forum plus d’info & des retours d’expérience en cliquant ici !

LoLaTiOn

PES Le 22 mai 2016 11 h 50 min

Problème rencontré :
Downloading BUSYBOX
–2016-05-22 11:44:03– http://busybox.net/downloads/binaries/latest/busybox-i586
Resolving busybox.net… 140.211.167.224
Connecting to busybox.net|140.211.167.224|:80… connected.
HTTP request sent, awaiting response… 301 Moved Permanently
Location: https://busybox.net/downloads/binaries/latest/busybox-i586 [following]
–2016-05-22 11:44:06– https://busybox.net/downloads/binaries/latest/busybox-i586
Connecting to busybox.net|140.211.167.224|:443… connected.
ERROR: cannot verify busybox.net’s certificate, issued by `/C=US/O=Let’s Encrypt/CN=Let’s Encrypt Authority X3′:
Unable to locally verify the issuer’s authority.
ERROR: certificate common name `bugs.busybox.net’ doesn’t match requested host name `busybox.net’.
To connect to busybox.net insecurely, use `–no-check-certificate’.
Unable to establish SSL connection.
.
.
. Nettoyage du system …
rm: /data/app/eu.chainfire.supersu-2: is a directory
.
.
. Envoi des fichiers …
push: root/system/app/Superuser.apk -> /data/local/tmp/system/app/Superuser.apk
push: root/system/app/install-recovery.sh -> /data/local/tmp/system/app/install-recovery.sh
push: root/system/app/99SuperSUDaemon -> /data/local/tmp/system/app/99SuperSUDaemon
push: root/system/xbin/supolicy -> /data/local/tmp/system/xbin/supolicy
push: root/system/xbin/su -> /data/local/tmp/system/xbin/su
push: root/system/xbin/libsupol.so -> /data/local/tmp/system/xbin/libsupol.so
push: root/system/xbin/chattr.pie -> /data/local/tmp/system/xbin/chattr.pie
push: root/system/xbin/chattr -> /data/local/tmp/system/xbin/chattr
push: root/system/xbin/busybox -> /data/local/tmp/system/xbin/busybox
9 files pushed. 0 files skipped.
3503 KB/s (7374225 bytes in 2.055s)
.
.
. Copie des fichiers dans le system …
cp: /system/xbin/daemonsu: Read-only file system
cp: /system/xbin/su: Read-only file system
cp: /system/bin/.ext/.su: No such file or directory
cp: /system/app/Superuser.apk: Read-only file system
cp: /system/etc/install-recovery.sh: Read-only file system
cp: /system/etc/init.d/99SuperSUDaemon: No such file or directory
cp: /system/xbin/busybox: Read-only file system
touch: /system/etc/.installed_su_daemon: Read-only file system
.
.
. Obtention des droits …
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/xbin/su: No such file or directory
chown: /system/xbin/daemonsu: No such file or directory
chown: /system/etc/install-recovery.sh: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/.installed_su_daemon: No such file or directory
chown: /system/app/Superuser.apk: No such file or directory
chown: /system/xbin/busybox: Read-only file system
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/etc/.installed_su_daemon: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/xbin/busybox: Read-only file system
/system/bin/sh: /system/xbin/su: not found
busybox: /system/xbin/crontab: Read-only file system
busybox: /system/xbin/insmod: Read-only file system
busybox: /system/xbin/modprobe: Read-only file system
busybox: /system/xbin/reboot: Read-only file system
busybox: /system/xbin/rmmod: Read-only file system
busybox: /system/xbin/run-parts: Read-only file system
busybox: /system/xbin/runlevel: Read-only file system
busybox: /system/xbin/start-stop-daemon: Read-only file system
busybox: /system/xbin/su: Read-only file system
busybox: /system/xbin/zcip: Read-only file system
.
.
. Attendez … Nous terminons le processus.
.
.
. Enjoy! vous avez ROOTED la tablette.
. Maintenant, la tablette va rebooter.
Appuyez sur une touche pour continuer…
Tablette non routé…

Réponse

9 commentaires

sombret Le 25 mars 2019 23 h 54 min

le processus s termine comme si tout avait marché,sauf que la tablette n’est toujours pas rootée !!!!!!!!!!

Réponse
PES Le 22 mai 2016 11 h 50 min

Problème rencontré :
Downloading BUSYBOX
–2016-05-22 11:44:03– http://busybox.net/downloads/binaries/latest/busybox-i586
Resolving busybox.net… 140.211.167.224
Connecting to busybox.net|140.211.167.224|:80… connected.
HTTP request sent, awaiting response… 301 Moved Permanently
Location: https://busybox.net/downloads/binaries/latest/busybox-i586 [following]
–2016-05-22 11:44:06– https://busybox.net/downloads/binaries/latest/busybox-i586
Connecting to busybox.net|140.211.167.224|:443… connected.
ERROR: cannot verify busybox.net’s certificate, issued by `/C=US/O=Let’s Encrypt/CN=Let’s Encrypt Authority X3′:
Unable to locally verify the issuer’s authority.
ERROR: certificate common name `bugs.busybox.net’ doesn’t match requested host name `busybox.net’.
To connect to busybox.net insecurely, use `–no-check-certificate’.
Unable to establish SSL connection.
.
.
. Nettoyage du system …
rm: /data/app/eu.chainfire.supersu-2: is a directory
.
.
. Envoi des fichiers …
push: root/system/app/Superuser.apk -> /data/local/tmp/system/app/Superuser.apk
push: root/system/app/install-recovery.sh -> /data/local/tmp/system/app/install-recovery.sh
push: root/system/app/99SuperSUDaemon -> /data/local/tmp/system/app/99SuperSUDaemon
push: root/system/xbin/supolicy -> /data/local/tmp/system/xbin/supolicy
push: root/system/xbin/su -> /data/local/tmp/system/xbin/su
push: root/system/xbin/libsupol.so -> /data/local/tmp/system/xbin/libsupol.so
push: root/system/xbin/chattr.pie -> /data/local/tmp/system/xbin/chattr.pie
push: root/system/xbin/chattr -> /data/local/tmp/system/xbin/chattr
push: root/system/xbin/busybox -> /data/local/tmp/system/xbin/busybox
9 files pushed. 0 files skipped.
3503 KB/s (7374225 bytes in 2.055s)
.
.
. Copie des fichiers dans le system …
cp: /system/xbin/daemonsu: Read-only file system
cp: /system/xbin/su: Read-only file system
cp: /system/bin/.ext/.su: No such file or directory
cp: /system/app/Superuser.apk: Read-only file system
cp: /system/etc/install-recovery.sh: Read-only file system
cp: /system/etc/init.d/99SuperSUDaemon: No such file or directory
cp: /system/xbin/busybox: Read-only file system
touch: /system/etc/.installed_su_daemon: Read-only file system
.
.
. Obtention des droits …
chown: /system/bin/.ext: No such file or directory
chown: /system/bin/.ext/.su: No such file or directory
chown: /system/xbin/su: No such file or directory
chown: /system/xbin/daemonsu: No such file or directory
chown: /system/etc/install-recovery.sh: No such file or directory
chown: /system/etc/init.d/99SuperSUDaemon: No such file or directory
chown: /system/etc/.installed_su_daemon: No such file or directory
chown: /system/app/Superuser.apk: No such file or directory
chown: /system/xbin/busybox: Read-only file system
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/etc/.installed_su_daemon: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/xbin/busybox: Read-only file system
/system/bin/sh: /system/xbin/su: not found
busybox: /system/xbin/crontab: Read-only file system
busybox: /system/xbin/insmod: Read-only file system
busybox: /system/xbin/modprobe: Read-only file system
busybox: /system/xbin/reboot: Read-only file system
busybox: /system/xbin/rmmod: Read-only file system
busybox: /system/xbin/run-parts: Read-only file system
busybox: /system/xbin/runlevel: Read-only file system
busybox: /system/xbin/start-stop-daemon: Read-only file system
busybox: /system/xbin/su: Read-only file system
busybox: /system/xbin/zcip: Read-only file system
.
.
. Attendez … Nous terminons le processus.
.
.
. Enjoy! vous avez ROOTED la tablette.
. Maintenant, la tablette va rebooter.
Appuyez sur une touche pour continuer…
Tablette non routé…

Réponse
geminisc Le 2 mai 2016 9 h 35 min

hello ,
j’ai essayé la procédure sur un Chuwi HI12 .
toutes les étapes semblent se passer correctement ,jusqu’au reboot de la tablette ,mais aucun changement ,au final . pas de root effectif après avoir utilisé cette méthode .
Quelqu’un à un idée pour rooter la chuwi HI12.
merci

Réponse
MerlinX Le 5 février 2016 17 h 27 min

Bonjour,
quand j’ouvre le lien « root tablette chinoise » google drive l’ouvre, puis quand je veux le télécharger, il y a un message « Désolé, ce fichier est infecté par un virus
Seul le propriétaire est autorisé à télécharger des fichiers infectés »
Je veux rooter ma HI8 et comptais sur ce tuto pour mon niveau de gros débutant.
Que faire? Merci.

Réponse
- Admin Le 3 avril 2016 19 h 40 min
  
  Bonjour,
  
  Normalement ça devrait étre bon
  
  Réponse
Pingback : Chuwi Hi8 – Root & Win 10 Update
cat Le 19 juillet 2015 13 h 53 min

Allo!
J’ai un CHUWI Hi8 et j’ai essaye de le rooter; j’ai recu la meme info que G123 les a recu…
Quoi faire, SVP????

MERCI!

Réponse
g123 Le 24 mai 2015 9 h 12 min

Sur la Chuwi vi10, on a pas le 0/root, on a :
.
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011
(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),
3006(net_bw_stats) context=u:r:shell:s0
.
. If ID above – 0/root, Everything will goes well.
. If otherwise, press CTRL + C to cancel.

Que faire ?

Réponse
jarryel Le 4 mai 2015 9 h 55 min

impec !

Réponse