Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
rolltide78 said:
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
Click to expand...
Click to collapse
The saferoot method might be able to be done via terminal emulator, the install.sh seems to be all shells commands. Don't see why you couldn't modify it to run from the phone, or enter the commands manually. Someone correct me if I'm wrong...
Edit:
Nvm. It states it cannot be ran from terminal emulator.
rolltide78 said:
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
Click to expand...
Click to collapse
Perhaps post this in saferoot thread in dev forum. Smart guys hangout there
safestrap enabled, Hyperdrive driven
decaturbob said:
Perhaps post this in saferoot thread in dev forum. Smart guys hangout there
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Unfortunately I haven't had 10 posts yet so it won't let me post anything there.
rolltide78 said:
Unfortunately I haven't had 10 posts yet so it won't let me post anything there.
Click to expand...
Click to collapse
Would obtaining a stock rom and flashing with Odin get me through this or will that flag the counter?
rolltide78 said:
Would obtaining a stock rom and flashing with Odin get me through this or will that flag the counter?
Click to expand...
Click to collapse
A full-wipe stock ROM will clear the custom flag. However, if you can't get USB to work, I'm not sure what you can do.
k1mu said:
A full-wipe stock ROM will clear the custom flag. However, if you can't get USB to work, I'm not sure what you can do.
Click to expand...
Click to collapse
Dang. We'll can you provide me with a link to the stock? The ones I've found lead me not too confident.
rolltide78 said:
Dang. We'll can you provide me with a link to the stock? The ones I've found lead me not too confident.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2578209
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
So this will keep Knox/etc alone? It still baffles me why we can't root without using a PC.
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Also, one other thing to add... it does charge verrrrrryyy slowly when its powered off and connected. It loops and vibrates the charging icon with a grey spinning icon. It does charge though (about a 1/4 over a 4 hour span). So its not completely not working..whichi is odd.
rolltide78 said:
Also, one other thing to add... it does charge verrrrrryyy slowly when its powered off and connected. It loops and vibrates the charging icon with a grey spinning icon. It does charge though (about a 1/4 over a 4 hour span). So its not completely not working..whichi is odd.
Click to expand...
Click to collapse
Are you using the USB cable that came with the phone? Some other USB cables will charge, but won't transfer data. So, it may be the cable and not the USB port. Just a thought!
rolltide78 said:
So this will keep Knox/etc alone? It still baffles me why we can't root without using a PC.
Click to expand...
Click to collapse
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
adb push getroot /data/local/tmp/
adb shell chmod 755 /data/local/tmp/getroot
Click to expand...
Click to collapse
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
[email protected]: / $ chmod 755 /data/local/tmp/getroot
unable to chmod /data/local/tmp/getroot: Operation not permitted
Click to expand...
Click to collapse
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
k1mu said:
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
Click to expand...
Click to collapse
Thank you very much for the explanations. I love it! First...I've tried using multiple USB cables and no go (except for the slooowww charge using the vibrate behavior loop). Any microusb cable used to work fine. I want root but just not on this device as I'm sending it in to Verizon. If I could get rid of the custom boot animation and the SuperSu app I wouldn't be wary but I just feel awkward sending a device back with these two items still visible ont he device. I'll root and load hypervisor on the new device when it arrives. Now, I'm just trying to get it to a state to send back and am trying to figure out my options.
rolltide78 said:
Thank you very much for the explanations. I love it! First...I've tried using multiple USB cables and no go (except for the slooowww charge using the vibrate behavior loop). Any microusb cable used to work fine. I want root but just not on this device as I'm sending it in to Verizon. If I could get rid of the custom boot animation and the SuperSu app I wouldn't be wary but I just feel awkward sending a device back with these two items still visible ont he device. I'll root and load hypervisor on the new device when it arrives. Now, I'm just trying to get it to a state to send back and am trying to figure out my options.
Click to expand...
Click to collapse
Have you used the SuperSU "full unroot" setting to remove it? That'll get rid of SuperSU at the very least;
My Saferoot thread has unrooting info in post 2 - worth trying, especially before killing SuperSU.
k1mu said:
Have you used the SuperSU "full unroot" setting to remove it? That'll get rid of SuperSU at the very least;
My Saferoot thread has unrooting info in post 2 - worth trying, especially before killing SuperSU.
Click to expand...
Click to collapse
See that's just it....I took the MK2 OTA update from MJ7 thinking that is how to unroot and now I no longer have root. I get the binary not found issue when I try to launch supersu. Root checker confirms I no longer have root.
k1mu said:
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
Click to expand...
Click to collapse
I wish the moderators were more helpful so we could have a number of stickies in these forums. We could save so many from screwing their phones up as well as saving us a lot of time in constantly explaining the same stuff over and over again because some new comers don't want to take the necessary time to research the process. As you can tell, I'm getting a bit testy with new posters in some of my replies because its so obvious they put in so little research into what their phones are capable of taking for mods. This explains the background and how and why ADB needs to be understood as well as the ODIN process before you take the plunge. Three thumbs up to you!
rolltide78 said:
See that's just it....I took the MK2 OTA update from MJ7 thinking that is how to unroot and now I no longer have root. I get the binary not found issue when I try to launch supersu. Root checker confirms I no longer have root.
Click to expand...
Click to collapse
I apologize for my lack of experience with rooted with the Android platform. I think my downfall was relying too much on youtube videos by folks like rootjunky and galaxys4root. They are excellent at obtaining root but not so much on removing root and getting rid of the Custom screens, etc. When I tried to come here it was a bit overwhelming with all the variants, versions, and options. I thought I was doing the correct methods. I'm going to look into adb and understand more of the inter-workings now. Hopefully it won't be an issue with Verizon but I just wanted to do as much as I could to get it back to stock given the issues I have with my device and USB.
Am I completely out of luck removing the padlock custom?
rolltide78 said:
Am I completely out of luck removing the padlock custom?
Click to expand...
Click to collapse
If you can't get your device to be recognized over USB, you're kind of stuck.
Typically, you'll at least see the "Verizon Mobile" disk drive show up when you plug it in. If you see that, try running the VZW_Software_upgrade_assistant.exe that appears - that will flash stock and clear the "Custom" flag.
rolltide78 said:
I think my downfall was relying too much on youtube videos...
Click to expand...
Click to collapse
Bingo! Your modifying a $700 device based on YouTube videos. At bare minimum one should take the time to read and understand the complete process. Yes it can be very overwhelming because of all the different information contained here. Stick with reading the most popular threads in the topic you want to learn about. They are generally up to date and contain answers to most questions.
Sent from my SM-T310 using Tapatalk
Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Once you select Option 1, you need to go back to the main windows to uncheck one box (F something) and then click start before it does the rooting. I missed it yesterday also and just keep waiting until I realized there was a step I didn't do.
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Delete the root toolkit, restart your computer and download it again. Same thing happened to me :thumbup:
Sent from my SCH-I545 using xda app-developers app
Help!
I am having the same problem and my phone is sitting there with a large android icon and message reading "Downloading.. Do not turn off target!!" I am afraid to disconnect the phone from the USB. What should I do?
ThugosaurusRex said:
Delete the root toolkit, restart your computer and download it again. Same thing happened to me :thumbup:
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Same here, Verizon Samsung g s4.
I followed the instructions: unchecked the F. reset box, and selected tar and clicked start. The "<OSM> All threads completed. (succeed 0 / failed 0) line showed up, and nothing else.
goldberg96 said:
Hi folks. I am not allowed to post in the developer forums since I am a new user so I figured I'd try here and hopefully some developer will be watching this forum.
I want to root my new Verizon Samsung Galaxy S4. I found the thread regarding the all in one tool for doing the root and installing recovery.
I followed the instructions, downloaded the tool, connected my phone, invoked the tool and selected Option 1 (Root my phone). The cursor skipped down one line and then nothing. I waited 15 minutes to make sure it wasn't doing anything but that's it, nothing.
I am new to Android and therefore new to Rooting so I thought this all in one tool would be perfect for me to get the job done. But I now have no idea why nothing happens when I invoke the tool and select Option 1.
Is there somebody in this forum who can help me please?
Thanks ............ Rob
Click to expand...
Click to collapse
Did you enable USB debugging and third-party? USB debugging can be found by tapping on build number (i think) under about phone like 7 times. Developer options should appear in your settings after that. Third-party sources is under security I believe. Hope that helps!
whichonespink73 said:
Did you enable USB debugging and third-party? USB debugging can be found by tapping on build number (i think) under about phone like 7 times. Developer options should appear in your settings after that. Third-party sources is under security I believe. Hope that helps!
Click to expand...
Click to collapse
I don't mean to hijack any responses here, but seeing as I have the same problem as OP I think it's safe to say that he also enabled USB debugging and third-party sources. Nothing
dabs delicious said:
I don't mean to hijack any responses here, but seeing as I have the same problem as OP I think it's safe to say that he also enabled USB debugging and third-party sources. Nothing
Click to expand...
Click to collapse
I actually found my problem. Even though I had the usb debugging flag set, when I tried to root, a popup window came up in the background asking me to confirm that I wanted to enable usb debugging. Because it was in the background I kept missing it. Once I saw it and replied, everything worked perfectly. Hope this maybe helps someone.
goldberg96 said:
I actually found my problem. Even though I had the usb debugging flag set, when I tried to root, a popup window came up in the background asking me to confirm that I wanted to enable usb debugging. Because it was in the background I kept missing it. Once I saw it and replied, everything worked perfectly. Hope this maybe helps someone.
Click to expand...
Click to collapse
You're talking about the popup window on your phone, right? Because It pops up for me too, and I click "confirm" each time, but to no avail
Does anyone else have any suggestions?
Question about using the 3 in 1 tool
I am wondering a few things. I have the Samsung Galaxy 4 that has not been activated by Verizon yet. I want to use it on Straight Talk which uses GSM. After running this tool with the unlocking and rooting, will I be able to do this?
Super Noob
Hello everyone this is my very first post, I am looking to root my verizon s4 using the one tool kit i dont believe i will have any trouble doing so i have rooted a few phones in my past before, my only question is about unrooting. i didnt want to start a whole new thread for this so figured i would ask here. is the VRUAMDK Factory Image (modified with No-Wipe) that you download from http://forum.xda-developers.com/showthread.php?t=2301259 is that the stock verizon firmware the only thing holding me back from rooting is not being sure that i have the stock firmware to flash, i might mess up and wanna make sure i have that for any situation that might come up. would someone plz confirm that that is the file i want to return to no root stock
missjamie said:
I am wondering a few things. I have the Samsung Galaxy 4 that has not been activated by Verizon yet. I want to use it on Straight Talk which uses GSM. After running this tool with the unlocking and rooting, will I be able to do this?
Click to expand...
Click to collapse
Root just allows you to hack the software on your phone, and the "unlock" refers to the bootloader. It does not unlock the phone for other carriers; this is done (from what I understand) by dialing a specific set of codes, generally provided to you by the original carrier of the phone if you have an account in good standing with them and you tell them you plan on travelling out of the country and need to use GSM. I have never needed to do this and as such only have a minor theoretical knowledge of the subject; I would appreciate it if somebody with more knowledge on this would confirm or deny my suspicion that you are better off trading the phone for an AT&T/T-Mobile one that actually was meant for GSM, or otherwise obtaining one.
JNava420 said:
Hello everyone this is my very first post, I am looking to root my Verizon s4 using the one tool kit i don't believe i will have any trouble doing so i have rooted a few phones in my past before, my only question is about unrooting. I didn't want to start a whole new thread for this so figured i would ask here. is the VRUAMDK Factory Image (modified with No-Wipe) that you download from http://forum.xda-developers.com/showthread.php?t=2301259 is that the stock Verizon firmware the only thing holding me back from rooting is not being sure that i have the stock firmware to flash, i might mess up and wanna make sure i have that for any situation that might come up. would someone plz confirm that that is the file i want to return to no root stock
Click to expand...
Click to collapse
This is the original bootloader; not the stock firmware. You need to flash this after you successfully root, start the phone, start SuperSU, and update the SU binary.
The full stock firmware is rather large and available here:
http://forum.xda-developers.com/showthread.php?t=2289325
might not know as much as i thought
thanks for telling me this first of all, so let me see if i get this right and im hoping you or someone will tell me if im correct or not. The all in one root method does that take care of the whole SuperSu, and update part or do i still need to do that after the root tool does its business? With unrooting do i just need to flash the stock firmware in odin use triangle away and i should be good correct, im not quite understanding the whole thats the original bootloader....the file that downloads is a .tar i thought that was firmware/rom....what do i need the original bootloarder for exactly? I honestly am to the point id be willing to pay someone who has a credible rep to video chat and walk me through it all
If you need assistance. Pm me. If I sm available ill help you.
JNava420 said:
thanks for telling me this first of all, so let me see if i get this right and im hoping you or someone will tell me if im correct or not. The all in one root method does that take care of the whole SuperSu, and update part or do i still need to do that after the root tool does its business? With unrooting do i just need to flash the stock firmware in odin use triangle away and i should be good correct, im not quite understanding the whole thats the original bootloader....the file that downloads is a .tar i thought that was firmware/rom....what do i need the original bootloarder for exactly? I honestly am to the point id be willing to pay someone who has a credible rep to video chat and walk me through it all
Click to expand...
Click to collapse
The original bootloader is locked and doesn't allow for us to use the exploit to install SuperSU and root the phone.
We are installing the unlocked bootloader via Odin...
Then running motochopper to exploit a vulnerability to gain root...
Then MANUALLY (this can't happen automagically) opening SuperSU and updating the SU binary...
Then rebooting the phone to make sure you still have root (personal preference)...
Then re-loading the original bootloader (we don't need the modified one anymore!) via Odin...
Then we are done!
The steps in the how to are very precise and accurate. If you would like to PM me, I am available for another hour or so.
OverkillSD said:
The original bootloader is locked and doesn't allow for us to use the exploit to install SuperSU and root the phone.
We are installing the unlocked bootloader via Odin...
Then running motochopper to exploit a vulnerability to gain root...
Then MANUALLY (this can't happen automagically) opening SuperSU and updating the SU binary...
Then rebooting the phone to make sure you still have root (personal preference)...
Then re-loading the original bootloader (we don't need the modified one anymore!) via Odin...
Then we are done!
The steps in the how to are very precise and accurate. If you would like to PM me, I am available for another hour or so.
Click to expand...
Click to collapse
Well said. Only correction is the bootloader still remains locked. The recoveries included are loki patched. This bypasses the bootloader. All roms and kernels are loki patched so flashing them is safe. This is as close as we're gonna get to an unlocked bootloader for now.
Ah. I was under the impression the bootloader was unlocked. Thanks for the info.
I'm getting an error in Odin: "Cannot open serial port." I have debugger mode enabled and whatnot, any help?
dabs delicious said:
I'm getting an error in Odin: "Cannot open serial port." I have debugger mode enabled and whatnot, any help?
Click to expand...
Click to collapse
I am also coming up with this error. My computer says that device is not responding. I am a first time "rooter" but I read the instructions carefully and now im stuck.....any suggestions?
chrisxstyle1182 said:
I am also coming up with this error. My computer says that device is not responding. I am a first time "rooter" but I read the instructions carefully and now im stuck.....any suggestions?
Click to expand...
Click to collapse
Could be a couple of things first make sure your using the cable that came with your phone. Try switching usb ports. Alsi try rebooting your pc
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
ok
enjid said:
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
Click to expand...
Click to collapse
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
jimyv said:
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
Click to expand...
Click to collapse
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
?
enjid said:
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
Click to expand...
Click to collapse
.
Safestrap was booting?
jimyv said:
.
Safestrap was booting?
Click to expand...
Click to collapse
Yup. Still is.
?
enjid said:
Yup. Still is.
Click to expand...
Click to collapse
What was your original system version? And which safestrap version?
jimyv said:
What was your original system version? And which safestrap version?
Click to expand...
Click to collapse
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
did
enjid said:
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
Click to expand...
Click to collapse
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
jimyv said:
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
Click to expand...
Click to collapse
Well... thank you. I messed up my backup of stock, so I couldn't just roll back. I thought I had tried flashing a bin, but I looked again and it was something I downloaded from a forum (so either a bad d/l or bad file in general).
Anyway, I did as you suggested with a brand new Amo download and it worked. Thank you for your help and patience.
Hi all,
Putting it briefly....
Factory reset of hdx 7" on 4.5.2
Stuck at Kindle Fire logo
Shows in PC as Internal Storage but just empty folders Music, DCIM etc...
Can get ADB connection (good news?)
That's it....now here's the interesting bit.....
If I use Kindle Fire Utility and try to root using Towelroot the device goes straight go lock screen. I slide to open and am confronted with Towelroot app. Click on Make It Rain but nothing happens.
If I try other things like installing SU it returns with permission errors.
I can also get to the devices settings too. No other apps installed just HDXPOSED and TOWELROOT.
Got me baffled... Any ideas how to fix?
You can NOT use Towelroot for 4.5.2! You must use Kingroot. Read about this, I've no experience with it. From what I've read it's possible it requires internet connection, I also read this could be for optional download of some browser or whatever, so try to disable such options, if available. You should avoid internet connection, or have it as short as possible, to avoid OTA upate from Amazon to 4.5.4.
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
myotai said:
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
Click to expand...
Click to collapse
Nothing comes to mind. Generally being stuck at the grey Kindle logo is terminal on a device with stock recovery and a locked bootloader. For future reference HDXPOSED is obsolete and may have contributed to your woes. It was never designed for FireOS v4 and doesn't work well on later versions of FireOS v3.
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
myotai said:
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
Click to expand...
Click to collapse
Assume you tried another factory reset. Being stuck at the orange logo offers some hope but there is no Rx that I know of.
Obtaining root is obviously desirable. You can try installing Kingroot via adb install and hope it executes (like towelroot apparently does) and continues to completion. If successfully you could try to repair the damage that is preventing FireOS from fully booting.
I recall someone saying installing a different launcher (eg: Nova) allowed their Kindle to boot.
Another path is to place the 3.2.8 rollback file into the root of sdcard and hope it takes.
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
myotai said:
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
Click to expand...
Click to collapse
You probably won't find that (not aware of any forum postings). Here's the deal. You are operating in uncharted waters trying to revive an unlocked/unrooted device that got borked for unknown reasons. You are going to have to a bunch of research and take some chances. FireOS can be a bxxch to repair. If the device is under warranty your best course of action is to engage Amazon for an exchange.
Kingroot is a longshot idea which I would not have mentioned if not for your experience with Towelroot. I have no idea if it will work.
Google (or another search engine) is your friend. A couple representative links below that popped up on the first attempt. I have no experience with either site an can not vouch for the content. Just a starting point ...
- Kingroot
- ADB Info
Thanks for your feedback!
I guess nothing ventured n all that!
Its a paper-weight at the moment so can't get much worse.....I'll wander around those un-charted lands and see what I come up with!
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
So you're on 4.5.2 rooted & OTA disabled now? Then try to install Safestrap v4. If it works, backup your stock slot (even if it doesn't work, who knows what it'll be good for), and move it to your PC. As the secondary slots won't work with WLAN atm anyway, you can install one of the Safestrap v4 compatible ROMs, e.g. Nexus, or CM11 in the stock slot, don't create any secondary Slots (yet).
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
To confirm you are now on rooted 4.5.2 but can get beyond the FireOS settings menu. If you install an apk via adb can you retain enough control to launch the app UI? You can do this via an adb shell command; unfortunately, the specifics are beyond my knowledge. Hopefully someone else can jump in or you can research on your own (if needed).
There is no safe way to repair FireOS directly with a locked bootloader. On many Android devices you would simply reflash/reinstall the ROM. Unfortunately, Amazon neutered the stock recovery environment as you discovered. If something goes wrong you are in a world of hurt. I think there is a very good chance your device can be revived. Just need to proceed carefully and not bork things to the point were you don't get past the grey logo. That generally means you own a door stop.
Thoughts (sorry if these are obvious):
- Keep in mind OTA is probably enabled on your device. Stay off wifi if you get that far; best to use a tether for file transfer, etc. until the problem is fixed. You can also rename the OTA apk via adb ... but your focus should be elsewhere at this point.
- It appears the FireOS launcher is hanging during initial setup (as you did a factory reset). You may find joy by installing another launcher (eg: Nova via adb) which often set themselves as the default when installed. Once you regain some control you can then install Safestrap v4 which is the pathway to other roms or repairing 4.5.2. Be aware FireOS will try to reset the default launcher on reboot. If this method works don't mess around trying to fix stuff. Install Safestrap v4 immediately (you also need to open the app and install Safestrap recovery) so you retain some control over your device during further troubleshooting.
- If a different launcher does not work try going for Safestrap v4. You will probably need to get smart around adb shell commands as you have to launch the UI to install the Safestrap recovery environment.
Thanks all taken in - my knowledge of ADB and its various commands are being added to as the hours go by - never really used it before.
Determind though........!
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
myotai said:
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
Click to expand...
Click to collapse
Yep - just flash 4.5.2 rom from here (don't use any other - you'll be rewarded with a brick). I strongly suggest you backup your existing stock slot (containing CM11) and reflash that to a secondary slot that you'll need to create. You won't be able to use wifi on the secondary slot but it will give you a rom to boot into in the event something goes wrong with the FireOS flash. Once you get FireOS working in the stock slot you should be able uninstall Safestrap. The operative word is 'should' as the system and recovery partitions need to be consistent for FireOS to boot properly. From what you have shared there is no reason to believe this is not the case - but the risk can not be dismissed. The other option is to leave Safestrap installed which only adds an annoying splash screen on boot but otherwise does not impact performance. What it does do is give you a pseudo-recovery environment which can be quite handy as you have discovered! It's also the vehicle for installing other roms such as CM11, Nexus v4, etc.
Take note of the cautions in the linked OP, in particular OTA. After flashing 4.5.2 you'll need to root and rename the OTA apk before enabling wifi. Amazon is aggressively pushing 4.5.4 which can not be rooted. Don't ruin your day - block OTA (yea - that was stupid).
Thanks so much. Its worth listing the procedures that got me this far...
I think installing TOWELROOT via ADB despite the fact I knew it wouldn't work was oddly the only thing that got me as far as 'settings' from a stuck Kindle logo. Then I had to resgiter the device in order to go to 'new offers' in the books setting to access the browser.....emails......Kingroot......finally Safestrap....boom!
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!