Ok, so a friend of mine bought 3 of these things from Kohls on Black Friday as Christmas presents for her kids and has asked me to help set them up as kid friendly devices. Unfortunately they don't come with any Gapps installed and I'm having difficulty installing any of them including the Play Store. I'm also running into problems installing simple games like Angry Birds. In fact very few of the APK's that I have backed up from my other Android devices seem to want to install on these tablets. I also can't find any forums on here or anywhere else evening addressing these devices yet. I'm wondering if there's some kind of generic udate.zip I can use for these things that isn't device specific? A little while back I was able to install an update.zip on a Zeki tablet that enabled me to finally install all the Gapps and maximize it's potential. But then again those things come rooted out of the box and the update was Zeki specific, so...
Anyways, please if anyone can help? This could be your chance to be the first to help unlock the potential of these devices.
Rooting PTAB8000
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Thanks.
HD Brian said:
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Click to expand...
Click to collapse
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
I had been thinking about reloading the stock rom and doing the root all again as a refresher for myself, but I have never done a YouTube video before. I will try to find the time to do it and them I will post the link here.
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
TeODH4 said:
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
Click to expand...
Click to collapse
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
Any luck with this script yet? Also, how were you able to flash back to factory?
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
BigT504 said:
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
Click to expand...
Click to collapse
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Dossey said:
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
Click to expand...
Click to collapse
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
I was able to get the play store on with the first upload and then by following a couple of steps from aother tutorial, but I can't seem to get any apps in the Play Store to open or download. I keep getting a "device is not compatible" message. I've tried the DPI play store and also messed around with LCD Density Monitor but haven't had any luck. If someone could help tackle this problem as well as get netflix up and running, I would be extremely grateful. This seems like a pretty awesome tablet, it just needs to be let free.
I feel I should also add, for anyone considering doing this, that once you have the Play Store installed, at least in my experience; if you have it hooked up to a PC via the USB and try to install anything, it goes ape sh** and starts trying to force close and kicks a whole bunch of errors. It doesn't seen to do anything, but it's annoying as hell. I haven't tried it yet with it plugged into the charger, and it doesn't do it nearly as much when you have it unplugged, but it's just another one of those quirks that I'm sure will be fixed in due time.
TeODH4 said:
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
Click to expand...
Click to collapse
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
psctornado said:
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
Click to expand...
Click to collapse
This is a secure release, it probably doesn't like all the files embedded into the exe... I can re-upload it un-packed if you like.
No it's ok I thought I would ask. So the big issue is the play store?
psctornado said:
No it's ok I thought I would ask. So the big issue is the play store?
Click to expand...
Click to collapse
Yes, the protected applications do not show up, or if you try to use the web site, and send an app to your device it will say unsupported, I'm going to take a look at my build.prop in a little bit and see if i cant get the full market working. From what I can tell its google blocking the apps because this is a non google supported device. which is why we needed to load the play store in the first place, if you run AIO 1.2 you will at least get all Googles app's working... Gmail, etc. I will have an update out soon to fix the play store issues, and hopefully fix the crashing gapps service...
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
TeODH4 said:
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
Click to expand...
Click to collapse
rysimpson318 said:
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
Click to expand...
Click to collapse
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
TeODH4 said:
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
Click to expand...
Click to collapse
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
psctornado said:
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
Click to expand...
Click to collapse
Sorry for the late response, but it should fix some of the issues. See the thread below for more info on current bugs...
I will now be posting all project updates and downloads here: http://forum.xda-developers.com/showthread.php?t=2066041
BigT504 said:
Any luck with this script yet? Also, how were you able to flash back to factory?
Click to expand...
Click to collapse
I haven't tried the new version yet since I don't have my laptop with me right now but I'll try it later. To reset back to factory after getting stuck on the black screen follow this sites direction. You will need a micro SD card. southerntelecom dot com / polaroidsupport / firmware /firmware_guide_ptab8000 dot html then download the files for your model and then put them on the SD card and insert the SD card in the tablet. Then to start the factory reset hold down volume down and power at the same time until you see the update screen come up. I believe that is what it said. It should explain it all in the link. If my link won't post since I'm new just Google ptab8000 firmware and click on the link for a southerntelecom firmware site.
Related
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Wreximus said:
Has anyone begun working on rooting and customizing roms yet? I know the device isn't out for a week or so but I would figure I would ask. My vibrant I so much better rooted and I wanted the same experience on this sidekick.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
i wish i knew how to do this, but if i can't figure it out, i'm sure others will soon.
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
abliss said:
Just got mine last night. The usual Samsung trick with rageagainstthecage-arm5.bin works great.
Click to expand...
Click to collapse
Oh really? Cool. So far all I've used is one-click root for the Samsung Epic.... is this similar? I'll check it out, thanks!
Has anyone tried using SuperOneClick yet?? I will probably try in a bit and post back with my results..
Ok... well I didn't try SuperOneClick, but I did root it via the rageagainstthecage exploit...
Want to help me do the exploit on my SK4G to root it man ?
Give me instructions ?!
I got it working on mine too. The basic steps were
1) enable debug USB mode on your phone
2) install Samsung drivers for the phone - right now Samsung's site seems to not have a choice for the Sidekick 4G's model (SGH-T839), but I grabbed the drivers for the Vibrant (at www .samsung.com/us/support/downloads/SGH-T959ZKDTMB) and they worked.
3) get adb shell working on your PC (Google it)
4) download the rageagainstthecage-arm5.bin and Superuser packages from the links in this page: wiki.cyanogenmod.com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide (be sure to unzip the files into the directory where your adb.exe program is unless you've put it in your path)
5) reboot your phone and plug it in
6) adb push rageagainstthecage-arm5.bin /data/local/tmp
7) adb shell
8) cd /data/local/tmp
9) chmod 755 rageagainstthecage-arm5.bin
10) ./rageagainstthecage-arm5.bin
11) wait until you get booted back out to your DOS command prompt
12) adb kill-server
13) adb start-server
14) adb shell
15) you should now be at a # prompt. The first few times I tried, I wasn't - I was at $. Doing this from a fresh boot seemed to be the trick. Reboot your phone and try again if you're getting a $.
16) mount -o remount,rw /dev/block/stl9 /system
17) exit
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/stl9 /system
22) exit
23) reboot the phone then run an app that requests root, such as Root Explorer, to verify
(p.s. sorry for having to mangle the URL's above, XDA won't let me include links since I haven't posted 8 times yet)
josby said:
16) mount -o remount,rw /dev/block/st19 /system
18) adb push su /system/xbin
19) adb shell chmod 4755 /system/xbin/su
20) adb push Superuser.apk /system/app
21) adb shell mount -o remount,ro /dev/block/st19 /system
Click to expand...
Click to collapse
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Also, after step 20, I had to run the following commands for the superuser application to grant root privledges to applications..
adb shell echo "root::0:0:root:/data/local:/system/bin/sh" > /etc/passwd
adb shell echo "root::0:" > /etc/group
Awesome to see it being rooted so fast.
I'm really interesting in getting this phone but I'm not in the US. Does anyone know if the phone will work outside US?
brenix said:
Just to note, on step 16 and 21... it is /dev/block/stl9 rather than st19
Click to expand...
Click to collapse
Dang, good catch, thanks. That's what I get for not copying and pasting from my terminal window...stupid, since I was just chastising two people at work for making the same mistake yesterday. I've edited the original post to prevent problems for people who might start before reading the entire thread.
Interesting about having to create a passwd and group file...I've only run a few root apps so far, but they've worked without me doing this. I wonder if it's app-specific.
Now to start removing some of the damn bloatware this thing comes with!
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
i'm so glad this thing got rooted. i used to be a scene kid with a kick. i dont have this phone, i doubt i'm going to get this phone considering the sensation is droppin soon.... but for nostalgia purposes, i'm glad it got rooted. now you can really hack it!!!
not like the old ones!!
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
fawkReviewz said:
19) adb shell chmod 4755 /system/xbin/su
i get stuck on there it says unable to chmod no such file or directory . there's SU in my android-sdk/tools
Click to expand...
Click to collapse
Double-check your step 18...that's the step that copies the su file from your computer onto the phone. I forget the exact output format, but it shows you a Kb/second number of how fast the file transfer went when it finishes successfully.
droctii said:
Good looking out...I rooted mine earlier today. What version of Clockworkmod Recovery are you all using?
Click to expand...
Click to collapse
I'm not brave enough to try putting the ClockworkMod for one of the Samsung devices on the list onto mine, for fear of bricking it. Don't know enough about that works as far as hardware differences go.
I have removed the APK's listed below from /system/app with no apparent ill-effects. Not that YOU should remove them necessarily - just that they're things I don't have a need for:
AccountAndSync.apk
AmazonMp3.apk
AppPack.apk
DriveSmart.apk
DriveSmartHelper.apk
install_flash_player.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
Memo.apk
MiniDiary.apk
MobileBackup.apk
MyFiles.apk
PhoneSetupWizard.apk
Twitter-2.0.1-121.apk
vvm-signed.apk
Though there must be something I don't fully understand, because even after a reboot, Amazon MP3 and AppPack are still on my phone, and they still work.
FYI, don't remove Settings.apk - I got stuck in a loop where the launcher kept crashing then reloading itself (thank goodness I was able to put it back in place with adb).
Can anyone tell me if Setcpu works for them?
Ace42 said:
Can anyone tell me if Setcpu works for them?
Click to expand...
Click to collapse
Appears to work fine.. no crashes although the Max Hz is 1000. U can still raise the Min Hz.
Sent from my Nexus S using XDA App
Can someone post a full:
ls of / and /dev/block and /efs
Thanks
Will this phone get a proper sub-forum on xda?
Root for ZTE z990g aka ZTE Merit
by jcase - [email protected] - http://twitter.com/TeamAndIRC
June 16 2012 - Copyright 2012 CunningLogic
Do Not Distribute or republish without permission. (Sad that this is needed, but people/blogs like to profit off the work of others without credit)
Want to support my work? Donations are always appreciated, but never required:
Paypal: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LZ62YFU3XCEK8
Amazon Giftcards: [email protected]
Required files:
http://dl.dropbox.com/u/8699733/chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
Code:
adb shell
Set up the dirs, so shell owns them prior to logging. If shell does not own them then we can not control them. If the logs dir already exists, you may have to do a factory reset to remove them. They should not exist unless someone attempted this previously.
Code:
mkdir /data/local/logs
mkdir /data/local/logs/kernel
Open emode's logset activity. First button should be for enabling log set, enable it. Do not exit the activity, but if you do just repeat the below command.
Code:
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.
Code:
ls -l /data/local/logs/kernel/log_kernel.txt
If it exists, delete it and immediately symlink it to /data/local.prop, logset may recreate it, if it does delete and try symlinking again.
Code:
rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.
Code:
ls -l /data/local.prop
Now once /data/local.prop exists, go back to the logset activity and disable logset. If you don't disable it, it will slowly eat away at all the disk space, and possibly overwrite the local.prop before you get root. Now lets set qemu=1 then reboot.
Code:
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
Once you have rebooted, remount, install su.
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Clean up your mess!
Code:
adb shell rm /data/local.prop
adb shell rm -r /data/local/logs
Reboot, install the Superuser app from the market and enjoy
Code:
adb reboot
Might Not Work As Expected
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
bitshifter52 said:
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
Click to expand...
Click to collapse
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
jcase said:
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
Click to expand...
Click to collapse
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
Click to expand...
Click to collapse
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
Click to expand...
Click to collapse
It Worked - But Don't Know Why...
jcase said:
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
Click to expand...
Click to collapse
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
bitshifter52 said:
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
Click to expand...
Click to collapse
Generally you have to run superuser once to get it to work I've found, at least recent builds (or maybe its recent android builds)
Problem.
Hello, i have followed this entirely but at parts it says "Access denied" when im on certain parts when i tryed to check if the Kernel log was there it said "access denied" same with some folders.
root or no root
followed steps, ended up with this...
$ ls -l /system/xbin/su
ls -l /system/xbin/su
-rw-rw-rw- root root 22364 2012-07-15 09:25 su
the superuser app shows all blank under apps and logs, when i try to update it, it says "checking" for a few secs and then nothing... also wondering how to do a factory reset cuz if i didn't screw the phone up yet, i will thx in advance
Has you can see I'm new here. I'm old and retired I would love to root my ZTE Merit 2.3.5 but this is over my head.
I was wondering if there's any accomplished phone rooters in the NC area that would be willing to walk me through this or do this for me
I'd be more than willing to make a donation to make this happen,
custom recovery
I was wondering if someone would make q custom recovery for this phone because the stock recovery is really bad
Not working
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Worked!
omg I've wanted to root my phone. Thank you thank you! I thought I would brick my phone at first.
SIM Carrier unlock a ZTE Merit Z990G Straight Talk
I'm currently a T mobile prepaid customer and received the Merit from a friend of mine for doing some painting. I have looked for a month now and had a few unlock websites fail at attempting to unlock the phone via the IMEI (which the phone does have ). I have attempted to put my tmobile sim in the Merit but there is NO place to enter an unlock code. I really DONT wanna change my service to straight talk and would be willing to pay a decent amount to anyone that is capable of unlocking this phone for use with tmobile. If you think you have what it takes PM me and i will give you the IMEI and we can work out a deal. I challenge ANYONE achieve the impossible and get me the unlock code and a way to input it into the phone.
Cannot get local.prop
I have waited 20 minutes after trying to create the local.prop file and it simply won't create it. Any suggestions?
Can't get SU to upload
Hey I'm new to rooting android. I get to the point of installing SU but windows keeps telling me file not found. Would really like some help in fixing this issue. I have installed SU file to C:\Android\android-sdk\SU. Up to this point everything works fine.
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Any help would be really appreciated.
Thnks
Help getting Started
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Not a Damn thing...
Rather sad....I have everything going as it should....all input correct...still no root after final reboot...I followed every step to a T several times -rw-rw-rw- grrr...ive rooted many devices none this big of a pain in tha butt!
Used updated su binary on root just for fun...same result
Help plz!
im a noob to this but have been messing around with ubuntu for some time now can someone show me step by step on how to root my zte merit plz? is there a video tut on how? i tried all the quick methods but they don't work, this one obviously does on this page, can someone help start me out plz, im learning still and love to learn more!
---------- Post added at 08:59 AM ---------- Previous post was at 08:45 AM ----------
Univarseman said:
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Click to expand...
Click to collapse
help me, whats the first step then i can get the gearz in motion, i have not a clue on how to start this but if i do i can usually figure it out from them sometimes
Start menu
jjflappy said:
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Click to expand...
Click to collapse
Start menu then type CMD hit enter
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
https://play.google.com/store/apps/details?id=com.noshufou.android.su
As usual thanks for all your work for this GREAT community!!! :good:
Thanks for letting me watch you work & getting root for my wife's phone.
Edit: DroidHost of Androidarea51.com has made a OneClick for this phone using Jcase's root. it also installs a recovery & Superuser all at the same time.
androidarea51.com/***-all-things-
root-***-174/
Help Me Please
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
jcase, i pmd you i need help please
TechManPro said:
what do you do when it says permission denied or not permitted when waiting for device, remounting, or pushing su?
Click to expand...
Click to collapse
run adb shell
make sure your prompt is a # not a $. If it is a $ start over, if it is a # make sure you run adb remount.
jbach44 said:
lol now all we need is someone to write different roms :>
cyanogen would be nice :> lol
thank you for rooting this phone :>
Click to expand...
Click to collapse
No problem.
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
iliekandroid said:
You actually left out a step. In order to push su to the phone you have to adb remount -o rw. Otherwise it is a read-only filesystem and it cannot be pushed to the phone. Most people would probably get this, but the novices who end up with bricked phones will be angry.
Great work!
Click to expand...
Click to collapse
Actually no, you are incorrect.
adb remount without the additional parameters is correct, and not possible of bricking a phone with adb remount. No novice would be angry, because there is not possible brick from this guide, as long as it is followed.
I got the LG for my daughter (13 going on 30), and now it works fine. Thanks jcase.
Did not unlock my lgl35g
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
jcase said:
Update: Friday November 2nd 2012
Fixed a bad upload of the su file, must of become corrupt sorry.
Silly permission bug again, but w/e. LG should know better, from what I am told this is a recently released device. This is a long standing known issue. Lg get your sh*t together.
Directions:
unzip su.zip into the current path (directory) you are in.
adb shell
(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device shell
(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
adb wait-for-device remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
Once rebooted install superuser from the market:
Click to expand...
Click to collapse
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
anyone know of a way to SIM unlock this device? I have AT&T and would like to use it om there, i bought it for $30 on clist thinking net 10 would work with an AT&T SIM but was wrong, any help would be appreciated...
Click to expand...
Click to collapse
What is weird about that is i put the sim in a iphone and it worked just fine!!! Best bet would be ebay for unlock...
I have the Net10 one that I put a Straight Talk SIM in with no problems if I can get my hands on a AT&T SIM today I'll check it out.
---------- Post added at 07:39 AM ---------- Previous post was at 07:34 AM ----------
NateDoggTN said:
Yes I am a Noob... nobody likes me
I have exhausted every resource that I could find on this phone. I thought that this post was the answer to my problem, however it did not seem to help at all. Everything seemed as if it was working fine as I went step by step through the process. However, I rebooted my phone and there is no difference then when I started. The "su.zip" file enclosed in this post was not able to extract into the directory of my ADB client. It kept saying root already existed, but I was unable to see it in windows explorer? Is this "su.zip" a modified version of a pre-existing file in the SDK kit? I really need to unlock this phone so that I can clean up the junk. Any help would be greatly appreciated.
:
Click to expand...
Click to collapse
Did you push the su binary file or the whole folder? If you pushed the whole folder you will have to remove the directory & start over.
how to run root
Sorry for sounding like a noob, but I am...when it comes to LG. im trying to root my homies LG optimus logic but im not sure where to run the command from. if some one could help me out on to where the zip should actullay be placed and unziped to that would be a big help, thanks. and if there is a thread already for this please hook up a link.
thanks
thanks mate for this
i appreciate your time.
Anyone know of a rooted ROM
I have looked all over, but it doesn't look like a dev has created a ROM for this device. Has anyone come across one? If I knew programming I would give it a shot, but it's a mystery to me. I know that CyanogenMod 9 for the L3 (e400) works, but there is a problem with the radios, hence no cellular, wifi, or bluetooth.
Source code......
http://www.lg.com/global/support/opensource/opensource-detail.jsp
http://forum.xda-developers.com/showthread.php?p=34104009
This guy had some success with CM9, but no radio. Anyone know how to extract the radio? I've never built a rom, but this is tempting.
How to root Nook HD+ (and Nook HD too, I guess).
(Thanks for some useful ideas to sparkym3: http://forum.xda-developers.com/member.php?u=4411543 )
(tested only on 2.0.0 version (as comes out of the box), also works on 2.0.2
Get one of the attached files: root_win.zip if you are on windows, or root_unix.tgz if you are on Linux or Mac.
unpack the file to some dir and run "makeroot" on Windows or "sh makeroot.sh" on Mac/Linux
After a couple of reboots you should be able to do
adb shell and issue a "su" command in the shell and get the root prompt (#).
Thanks to someone0 for his prior investigations here.
Known bugs:
Superuser.apk does not really install because package manager could not be contacted.
Oh, and I think you'll find this interesting too:
Hai.
Kind of a two-fer, eh?
I noticed that people see their Nook HDs restoring to factory settings after 8 unsuccessful reboots next time you boot after rooting, so possibly there's some extra check somewhere.
Very sneaky on the B&N side, I'd say.
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
roustabout said:
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
Click to expand...
Click to collapse
Do the new HD & HD+ still allow you boot from the external sd card ?
roustabout said:
Hm, the 8 failed boot = wipe and restore has been true since the NC, and is valuable because it helps keep the device from getting bricked, also triggerable if the registration token doesn't match BN's reg token. I learned this early on by restoring a backup made before I'd erased and deregistered. I forget where the token lives, in /data/ somewhere.
I'll take a look at this on 2.0.2 this weekend - mine updated before I got ADB working so it restores to 2.0.2 now...
OK, so this approach does work with the 2.0.2 OS, and restarting the device does put it into a boot cycle. Very nasty.
Before I rebooted, I removed the post_boot_hook file and also got rid of the symlink; I'd say BN is doing some kind of inventory of what's in system and driving a reflash based on that.
My guess is it's not a very careful inventory, but it'll certainly be amenable to study now that we can get, at least temporarily, root.
Hm. Interesting -- my ability to mkdir /data/su is now gone after the restore. I wasn't able to do it the first time I tried, either - I suspect that there's something keeping some level of eye on that.
Oh, very uncool - in addition to resetting the system, they wipe personal data in the process. Losing the apps doesn't surprise me much. Losing the books I'd sideloaded surprises me.
Click to expand...
Click to collapse
if you put your books into /system/media, it will back them up to the cloud
Is it possible to push a new recovery with adb after rooting? The 8 failed boot repair is only possible with the stock recovery. But then again you may end up in an endless bootloop without it there to finish it's task. But maybe you can find and delete the trigger flag that starts the process.
leapinlar said:
Is it possible to push a new recovery with adb after rooting? The 8 failed boot repair is only possible with the stock recovery. But then again you may end up in an endless bootloop without it there to finish it's task. But maybe you can find and delete the trigger flag that starts the process.
Click to expand...
Click to collapse
stuff is best to be not mentioned. /sarcasm.....
recovery is signed, so it's not super easy to replace it with anything that would run.
The unsigned bootloader trick at the moment requires a boot from sdcard.
shouldn't step 8 & 9 be outside the code block?
verygreen:
I just want to thank you for your all your work on the Nook series. I've been using your "size-agnostic method ..." tools and process to run from the SD card on my Nook Color since you created the method, and now I'm excited to use your work on my new Nook HD+ (just received yesterday) !
just got mine and got an update notification. turned off wifi so it didnt complete.any word if it breaks root ir bootloader?
CWM is now possible too.
Something is interesting, eventhough mine originally got automatically updated to 2.0.2, but after the factory reset, it went back to 2.0.0. But for some weird reason I can't get root.
Maybe this will help, the build number is 2.0.0.1031.lithium01.ovation.rldp.s68403 with the manufactured date 10/22/2012
please compare mine to your.
I also rewrote your code into a batch file. You can double check it I guess.
Code:
@echo off
cls
@echo .
@echo wait for it
@echo .
adb devices
@echo .
@echo if you do not see you device listed above hit ctrl+c and exit the script
@echo then check adb on your PC and device then try again.
@echo .
@echo reroute /data/local/tmp
adb wait-for-devices shell rm -r /data/local/tmp
adb shell ln -s /data/ /data/local/tmp
@echo .
@echo Now rebooting
@echo .
adb reboot
@echo .
@echo waiting for reboot to finish and making directory /data/su
adb wait-for-devices shell mkdir /data/su
@echo uploading su
adb push su /data/su/
@echo uploading busybox
adb push busybox /data/su/
@echo uploading boot_complete_hoot
adb push boot_complete_hook.txt /data/boot_complete_hook.sh
adb shell chmod 755 /data/boot_complete_hook.sh /data/su/*
@echo .
@echo Now rebooting again
@echo .
adb reboot
@echo .
@echo waiting for reboot to finish and getting shell
adb wait-for-devices shell
someone0 said:
Something is interesting, eventhough mine originally got automatically updated to 2.0.2, but after the factory reset, it went back to 2.0.0. But for some weird reason I can't get root.
Maybe this will help, the build number is 2.0.0.1031.lithium01.ovation.rldp.s68403 with the manufactured date 10/22/2012
please compare mine to your.
I also rewrote your code into a batch file. You can double check it I guess.
Click to expand...
Click to collapse
so, when you run this, after the final adb shell, what are the permissions on /system/xbin/su?
run su and you should get the root prompt.
I don't get root prompt, su never get copied to /system/xbin/su
here is the list of my finding.
Code:
/data/
-rwxr-xr-x shell shell 167 2012-11-10 05:52 boot_complete_hook.sh
/data/su
-rwxr-xr-x shell shell 586212 2012-11-10 06:07 busybox
-rwxr-xr-x shell shell 22364 2012-11-10 06:07 su
/data/local
lrwxrwxrwx shell shell 2012-11-10 06:20 tmp -> /data/
cat boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
everything is in place and correct, but no dice. either boot_complete_hook.sh didn't get executed or it did but never get launched with root permission.
someone0 said:
I don't get root prompt, su never get copied to /system/xbin/su
here is the list of my finding.
Code:
/data/
-rwxr-xr-x shell shell 167 2012-11-10 05:52 boot_complete_hook.sh
/data/su
-rwxr-xr-x shell shell 586212 2012-11-10 06:07 busybox
-rwxr-xr-x shell shell 22364 2012-11-10 06:07 su
/data/local
lrwxrwxrwx shell shell 2012-11-10 06:20 tmp -> /data/
cat boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
everything is in place and correct, but no dice.
Click to expand...
Click to collapse
well, there should be more stuff in the shell file, you miss the final chown line: chmod 06755 /system/xbin/su
It did, I just didn't copy and paste the output correctly. But regardless, since the foulder /system/xbin don't have the su file, this mean as I suspected earlier, either it wasn't executed or lauched w/ root permission.
someone0 said:
It did, I just didn't copy and paste the output correctly. But regardless, since the foulder /system/xbin don't have the su file, this mean as I suspected earlier, either it wasn't executed or lauched w/ root permission.
Click to expand...
Click to collapse
check if your /system/bin/clrbootcount.sh calls /data/boot_complete_hook.sh
verygreen said:
check if your /system/bin/clrbootcount.sh calls /data/boot_complete_hook.sh
Click to expand...
Click to collapse
This is interesting, it look as if it won't launch the /data/boot_complete_hook.sh
Code:
cat /data/boot_complete_hook.sh
#!/system/bin/sh
/data/su/busybox mount /system -o remount,rw
/data/su/busybox cp /data/su/su /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
[B][email protected]:/data $ /data/boot_complete_hook.sh
/data/boot_complete_hook.sh
/system/bin/sh: /data/boot_complete_hook.sh: No such file or directory
1|[email protected]:/data $
[/B]
Yub it does
Code:
cat clrbootcount.sh
#!/system/bin/sh
################################################################################
##
#
# File clrbootcount.sh
# Description Clear the bootcount variable to 0 on successful boot
#
##
# Run potential hook first.
[B]/data/boot_complete_hook.sh[/B]
# Zero the boot count
cat /system/etc/zerobootcnt > /bootdata/BootCnt
FOR 2016(6th GEN) ON 5.3.1 AND 5.3.1.1 ONLY: Works on HD7, HD8 and HD10
You can downgrade from 5.3.2 by adb sideload the 5.3.1.1 bin file.
DO NOT downgrade from 5.3.2.1!! Hard-brick attention!!
This guide requires some ADB skills, read more from the forum, install it from here
Enable ADB and install apps from other sources in Developer Options
Download Kingoroot PC version at www.kingoapp.com or google mirror
Root your Kindle using Kingoroot, then reboot your device
Download a file explorer apk (ie. ES File Explorer) and sideload install the apk to your kindle
Download SuperSU apk at APKPure, but DON'T install it first
Download the attachment "Kingo.to.SuperSU" below then unzip and paste into your kindle, ie /sdcard/Kingo.to.SuperSU
Run ADB Shell and type
Code:
su
mount -w -o remount /system
Keep the root-accessed ADB shell open, then remove root by using Kingoroot
(If your kindle reboot at this step, you need to re-root it and try the above steps again)
In the ADB shell type
Code:
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
Still keep that root-accessed ADB shell opened, copy the SuperSU apk into your kindle and install it using the file explorer, DO NOT OPEN IT.
In the ADB shell type
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
(1 error with "No such file or directory" is okay I think)
Run SuperSU and update binary, choose the "normal" one, then it should ask you to reboot your kindle
Open up SuperSU and go to setting
Set the "Default Access" as [Grant]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Due to unknown reason, kindle cannot prompt the "Asking for root access", this step is to allow all access for all apps.
Install Root Checker and confirm you have root, run ADB shell to confirm you can su
Remove Kingolink and that Kingo battery app from kindle
Uninstall Kingo from PC via manual unins000.exe inside install directory in programs(x86)
ALL DONE! You may then want to install google play, do all the pm disable for OTA, firelauncher, and other amazon services you don't want.
References:
[Index] Amazon Fire HD 8 and HD 10 (5th Gen/2015)
[Working]Root Kindle Fire HD8 6th Gen
Tips, Tricks, and the Root!
[HOW-TO] Install Google Play Store (Fire OS 5.3.1.1) (No Root/ADB)
[Script] Replace KingoRoot with SuperSU
Credits:
@coltxL2717
@chemie99
@2ig2ag
@smokejumper76
@phpbb88 ME
phpbb88 said:
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
[*]Run SuperSU and update binary then it should ask you to reboot your kindle
[*]Open up SuperSU and go to setting
Click to expand...
Click to collapse
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot
imadiamond said:
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot
Click to expand...
Click to collapse
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Thanks for making this clear and concise guide! Well done.
phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.
Could I also install a customrom after root? with one?
meikschlenther said:
Could I also install a customrom after root? with one?
Click to expand...
Click to collapse
Not at this time... There are no ROMs as of yet, and if I'm not mistaken we would need a custom recovery and our bootloader is still locked.
imadiamond said:
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.
Click to expand...
Click to collapse
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.
phpbb88 said:
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.
Click to expand...
Click to collapse
First problem was even though previously all drivers loaded and I was able to root/re-root and navigate adb.... when booting the device into recovery mode? Tablet not recognized by computer. Extremely frustrating. Read and read and read.... and finally came across something from @smokejumper76 -----answer was in Device Manager, tablet was showing up as KFGIWI with the error that drivers were not installed. Did "manually install drivers" "Search online" does not work) and chose ADB Composite Device, and now tablet is recognized in recovery mode.
Issue NOW is the process gets halfway through installation and then force closes with
E: failed to verify whole-file signature
E: signature verification failed
Man, I am ticked. What now? Been reading for the past hour++. People elsewhere are saying to change the .bin extension to .zip, but I haven't seen that here on the XDA forum.
---------- Post added at 01:48 AM ---------- Previous post was at 01:11 AM ----------
Install from ADB complete: went through. After multiple tries, did 2 things at once so not sure which one it was
1) ran cmd prompt as Administrator
2) deleted all 5.3.1.1 bin files from computer, just in case what was gotten previously was corrupt, and redownloaded fresh file onto the ADB computer, instead of the copy and paste version from another computer
Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.
I hope all you guys are also donating some bux to Kingoroot (I did).
We want to keep those geniuses happy and cranking out rooting updates for the v5.3.2.x builds!
Thanks so much for the guide. It was pretty easy to get through!
I have Nova Launcher running now and it is way better.
However, Auto Rotate screen isn't working quite right. If it is in Portrait, it will flip to landscape if I turn the tablet, but then it gets stuck in landscape which is the wrong landscape that I need for my Fire cover/stand.
Anyone else experiencing this?
Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .
el7145 said:
Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.
Click to expand...
Click to collapse
Thanks for pointing out the mistake, cause I had disable ota update by OpenDNS method before, so I was not aware of this.
imadiamond said:
Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .
Click to expand...
Click to collapse
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.
Need to type exit, exit in shell to save settings?
phpbb88 said:
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.
Click to expand...
Click to collapse
Good question. Thanks for asking phpbb88! Definitely changed the default access. Rebooting here was one of the problems earlier since SuperSU says to reboot, then you must hit "Ok"-- and then logically, you would reboot. But instructions don't say to *ignore* and stay in SuperSU. Previously was rebooting, since Step 13 says "Open up SuperSU"... but SuperSU is already open in Step 12, so no need to open it up.
Only connected to the internet with it once, in December. Saw that everything needed an Amazon account, so have had wireless off/airplane mode ever since. Bought it with sole purpose to root.
The only thing I can think of would be not typing "exit" twice to get out of the shell. First read that instruction at the end of the pm disabling tutorial. If that's important than it needs to be added to the instructions also. Otherwise, when finished people will just power down the device or pull the USB plug. It's got to be written so that someone not knowing anything- first-time Kindle buyer like me , can do it. Here is the log.
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 7590
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU #
C:\Users\COMPUTER\AppData\Local\Android\Sdk\platform-tools>
smokejumper76 said:
I used eu.chainfire.supersu_2.79-SR3-279_minAPI7(nodpi)_apkmirror.com.apk for superSU...that would be another thing to check
Click to expand...
Click to collapse
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .
imadiamond said:
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .
Click to expand...
Click to collapse
Glad to hear that you can finally root your fire.
In fact, I never typed exit twice in adb shell, I just close it...lol
1) After SuperSU updates its binary, I followed the reboot, still success to root my device.
2) I am using the SuperSU apk download from apkpure linked above, why don't you download it in the first try...?
I went to appsapk.com and have a look of the SuperSU, it is totally a different app.
Thanks for the Guide finally got root!
phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
I had the exact same problem over and over finally tried this:
change this: rm /system/bin/install-recovery.sh
To this: rm install-recovery.sh