This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
We really did need this excellent thank you very much!
jimyv said:
We really did need this excellent thank you very much!
Click to expand...
Click to collapse
I still don't know whether this works or not. There's no reason it shouldn't work, but you never actually know until you try.
Sent from my Nexus 7 using Tapatalk
Sorry for the dumb question, but when you say try those commands, where do you enter them?
Let's Note. Comback to 4rum.xda....
Big thank for your method, Senior r3pwn
dburns865 said:
Sorry for the dumb question, but when you say try those commands, where do you enter them?
Click to expand...
Click to collapse
I have the same question with you
wow
danhvt said:
I have the same question with you
Click to expand...
Click to collapse
I'm sorry guys but if you really need to ask this then you probably shouldn't have been modifying your devices in the first place http://forum.xda-developers.com/showthread.php?t=2786190
Fix Bricked
Sorry, Im slightly confused, how are we able to fix the device with ADB if it is bricked? Mine will not get past the white "Kindle Fire" page, any ideas?
i will test this tonight. Bricked my kindle hdx but my wife has a working one so hoping if this doesn't fix mine i can somehow use her system files to fix mine.
thanks and will update tonight!
It worked for me
r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
For the 8.9" HDX, they are posted at
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks dude, it worked for me. I mistakenly formated data after wiping system so I stuck in safestrap recovery. I transfered a stock Rom through ADB but It failed while flashing... because there was some kinda problem with Cache partition... so i tried your method and it worked... but i made a little change in last Commands... I gave it "EXIT" command only 1 time and did not give the command "ADB reboot Recovery"... I recommend you guys to manually boot to safestrap recovery after quitting CMD.... Ahhh my device is Kindle Fire HDX 7"
root not required?
Thanks, r3pwn, this works well. Nice, easy instructions that should be instructive to anybody messing with their device.
This helped me after a botched update to newer Amazon firmware. Quick question though: It seems like you don't really need to be root / use su to do these steps. I had lost su in that update but was able to execute the rest of the adb commands without root. I guess that should be the same for anyone who doesn't have root, right?
scaftogy said:
Thanks, r3pwn, this works well. Nice, easy instructions that should be instructive to anybody messing with their device.
This helped me after a botched update to newer Amazon firmware. Quick question though: It seems like you don't really need to be root / use su to do these steps. I had lost su in that update but was able to execute the rest of the adb commands without root. I guess that should be the same for anyone who doesn't have root, right?
Click to expand...
Click to collapse
Do you mean I can use this way to downgrade my firmware?
Thanks. but i have question now.
does it work on 4.5.2? as my friend remove the framework-res, and get it bricked T_T.
r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
hi,
any glue what went wrong with a permission denied? everything in the adb shell session was ok, but adb push says (after several minutes!):
Code:
D:\adb_fastboot>adb push update-kindle-13.3.1.0_user_310079820.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.3.1.0_user_310079820.bin' to '/cache/kindleupdate.bin': Permission denied
sn123py said:
hi,
any glue what went wrong with a permission denied? everything in the adb shell session was ok, but adb push says (after several minutes!):
Code:
D:\adb_fastboot>adb push update-kindle-13.3.1.0_user_310079820.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.3.1.0_user_310079820.bin' to '/cache/kindleupdate.bin': Permission denied
Click to expand...
Click to collapse
No, sorry, I don't even have this device. There are newer, better ways to unbrick now.
I think trying to find eMMC pointer
i have tried this.. but when rebooting it takes me back to recovery menu with 2 options.
1. reboot
2.reset
whichever i chose, still takes me back to boot loop (animated logo)
any ideas?
does this method require TWRP? As i cant get this working..
Ali Ejea Mc said:
Thanks dude, it worked for me. I mistakenly formated data after wiping system so I stuck in safestrap recovery. I transfered a stock Rom through ADB but It failed while flashing... because there was some kinda problem with Cache partition... so i tried your method and it worked... but i made a little change in last Commands... I gave it "EXIT" command only 1 time and did not give the command "ADB reboot Recovery"... I recommend you guys to manually boot to safestrap recovery after quitting CMD.... Ahhh my device is Kindle Fire HDX 7"
Click to expand...
Click to collapse
I was trying to root my Kindle fire HDX 7 for android apps and google apps on it. it was successfully rooted and google play services working on it perfectly. Than suddenly google play stop working on it. but games installed on it working properly. Then i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC and in device manager only shows connectivity as MTP USB device. But no device show in my computer. Snapshot attached. Please assist any solution. I am not familiar with developer language. So please assist step by step.. Thanks
My Kindle fire HDX 7 i think bricked any solution?
I was trying to root my Kindle fire HDX 7 for android apps and google apps on it. it was successfully rooted and google play services working on it perfectly. Than suddenly google play stop working on it. but games installed on it working properly. Then i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC and in device manager only shows connectivity as MTP USB device. But no device show in my computer. Snapshot attached. Please assist any solution. I am not familiar with these developer language. So please assist step by step.. I tried below command but su Permission denied.
Related
VRoot Cleanup Tool - Easily replace VRoot with SuperSU
From your Windows PC
OK everyone, here's the deal. I did the VRoot the toher day on my phone and it worked great. The problem is that it can be tricky to get the old Chinese Superuser app and SU binaries updated to SuperSU. As a result I decided to put this tool together to help update the VRoot files to SuperSU, and get rid of the old VRoot ones. What this means is that you can now clean up the Chinese Super User app and completely install SuperSU with a single click, from your Windows PC.
How to use:
Download Root Cleanup from here: https://www.dropbox.com/s/sto74q58uq4r1bj/root_cleaner.zip
Extract it to a folder on your computer.
Open the new folder and double click the clean_root.bat file.
Follow the directions.
** You will want to make sure that USB debugging is on (which it should be from VROOT) and that VRoot is closed when you run this. **
Also note I only have one phone to test with, and it worked great on the one I have. Please let me know if you have any other issues and I will try my best to help. Also, as always, not responsible for problems . <3
Edit: I just got asked via PM if this is to be run after freezing VRoot, etc. So I wanted to add here in case anyone else wondered. With this tool you do not need to freeze VRoot, delete any files, etc. My script will literally take care of everything for you. So, run VRoot and the phone will reboot. You can immediately close VRoot on your computer and run this to completely replace VRoot with SuperSU, and remove VRoot files.
This is my first time writing something like this, but so far I have a lot of people who told me it works fine. Please let me know if you have issues and Ill do my best to help! I went ahead and created this thread at the request of some people who have had good success with this on the other thread here: http://forum.xda-developers.com/showthread.php?t=2511815&page=29
Update: V4 is up - this version makes sure that ADB is accessible. Thank you @k1mu for helping me with this!
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
fabrilas said:
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
Click to expand...
Click to collapse
My guess would be these lines:
adb shell "su -c 'rm /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm /dev/com.mgyun.shua.su.daemon'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su.daemon'"
The issue is that I cant remember if com.mgyun.shua.su and com.mgyun.shua.su.daemon are directories or files. If you could confirm for me which they are then I will be happy to fix my tool!
Thx
Angie
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Works also with Galaxy S4 Italy Gt-i9505 :good:
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
LilTechPrincess said:
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
Click to expand...
Click to collapse
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
ComputerBro2 said:
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
Click to expand...
Click to collapse
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
k1mu said:
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
Click to expand...
Click to collapse
Thank you very much for the help! Im still a newb! haha Anyhow, I updated my tool with your suggestion.
LilTechPrincess said:
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
Click to expand...
Click to collapse
No the adb won't start on my phone
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Bfitz26 said:
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No it freze on this
rm failed for /sdcard/install-recovery.sh, No such file or directory
when i disconnect the pone say not found for 4 or 5 times and finish
---------- Post added at 08:49 PM ---------- Previous post was at 08:28 PM ----------
I tri 3 times
try to wipe all data.
Next try is to reinstall last firmware update whit odin or it trip my knox 0x0 to 0x1 ?
MexyHKR said:
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Click to expand...
Click to collapse
Thats not a big deal. Basically, I removed the /sdcard/install-recovery.sh from the script earlier and forgot to not try and delete a file that doesnt exist... Ill fix that! haha That doesnt hurt anything at all. Sowwy!
Ok now im freeze on Cleaning Up Files....
Your link is down
Tomsgt said:
Your link is down
Click to expand...
Click to collapse
The link has 2 hh's in the http
eklipz3 said:
The link has 2 hh's in the http
Click to expand...
Click to collapse
thanks did notice that
Finaly dont work on my GS4
PDA: I9505XXUEMJ7
MODEM: I9505XXUEMJ7
CSC: I9505ITVEMJ8
Try 2 times after full wipe and emergency firmware restore.
Freeze on Cleaning etc...
Now need to go sleep 1:06AM in italy
Good night and sorry for bad speak
I speak like a fish trying to speak Russian
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
** THIS WORKED FOR ME, BUT MAY NOT FOR YOU. I'M POSTING THIS FOR INFORMATION **
From reading through logs of my boot looping HDX 7", i have found this method is working to re-flash an update file onto a kindle. needs ADB and ROOT access.
Use your current version or higher update file. This was on STOCK recovery, going from 13.4.5.2 to 13.4.5.3
1. Download update file
2. ADB PUSH <yourupdate>.bin /data/local/tmp/
3. ADB SHELL
3. su
4. echo '--update_package=/data/local/tmp/<yourupdate>.bin' >> /cache/recovery/command
5. reboot recovery
Once recovery starts, it will look at /cache/recovery/command for any tasks, and see that it needs to install the update package.
Thanks
osmorgan said:
** THIS WORKED FOR ME, BUT MAY NOT FOR YOU. I'M POSTING THIS FOR INFORMATION **
From reading through logs of my boot looping HDX 7", i have found this method is working to re-flash an update file onto a kindle. needs working ADB, and possibly root access.
(not sure if latest update is required, this method ?could? be used for downgrade)
1. Download update file
2. ADB PUSH <yourupdate>.bin /data/local/tmp/
3. ADB SHELL
3. su
4. echo '--update_package=/data/local/tmp/<yourupdate>.bin' >> /cache/recovery/command
5. reboot recovery
Once recovery starts, it will look at /cache/recovery/command for any tasks, and see that it needs to install the update package.
Thanks
Click to expand...
Click to collapse
Thanks for the guide, but you should also add from which FW to which FW your recovery was successful (i.e. from 13.4.5.2 to 13.4.5.2). In general is not recommended downgrade from FW 1x.3.2.8 to lower FW because Amazon activated efuse, which is blowed in case of downgrade, and result is HW brick...
jeryll said:
Thanks for the guide, but you should also add from which FW to which FW your recovery was successful (i.e. from 13.4.5.2 to 13.4.5.2). In general is not recommended downgrade from FW 1x.3.2.8 to lower FW because Amazon activated efuse, which is blowed in case of downgrade, and result is HW brick...
Click to expand...
Click to collapse
have edited original post.
root access is necessary to write into /cache
you cannot downgrade (except 3.2.8) and flash same version
you can flash 4.5.3 or 3.2.8
and of course this works until you have adb
with adb access and root always could restore device
Thank you for this!
Unbricked my kindle successfully by rolling back to 3.2.8
Glad I could help
Bricked HDX 8.9 (3rd) [4.5.2], but ADB is available
I bricked my HDX 8.9 (3rd).
It has ROM version: 4.5.2.
Here's exactly that I have done.
I have rooted it with the cve20147911.apk,
Installed RootExplorer
disabled OTA and tried to install gapps with this tutorial
But the gapps package is too big, so I installed Titanium backup to convert some amazon apps (goodread, special offers, market, firefly, and some others) from system apps to user apps to free up some space on the system drive. I also freezed them, as I don't need them at all.
I managed to get about 80 MB free space on the system drive, then created a folder called "x" in the root, then copied the "system" folder to this "x" from the gapps package.
Selected the "system" folder in my "x" temporary folder, then selected Permission option, then set permissions to 644 RECURSIVELY to the "system" folder.
Then selected "system" folder in my "x" folder, then selected "cut" from the options, then pasted the clipboard content to "/" then the folder structure would match, so the system can copy all the files to the right place in a single step.
Root explorer asked about the existing folders, I selected "merge". There were no question about files, so all of them were new, which means I did not overwrite anything.
After finishing this copy, the screen started to blink very quickly in black and grey, then I turned off the tablet.
I tried to turn it on.
It stuck on the gray "Kindle Fire" screen, and couldn't get to the golden "Fire" loading screen.
After about a minute, it restarted itself to Recovery mode.
Tried to restart, but it stuck again the grey kindle fire screen, and restarted itself to recovery.
I made a (now I know) wrong decision at this point.
Restored to Factory defaults. Did not help.
In Windows 7 32bit, it appears as "Android Composite ADB Interface", but I can not see it in adb devices from now.
Rebooted to Linux mint 17.1 (Ubuntu 14.10).
It appears in lsusb for some seconds as:
Code:
Bus 001 Device 003: ID 1949:000d Lab126, Inc.
So I installed ADB and set the /etc/udev/rules.d/51-android.rules file with the following lines:
Code:
# Amazon Kindle Fire HDX 8.9
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="000d", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb",ATTR{idVendor}=="1949",ATTR{idProduct}=="000d",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="1949",ATTR{idProduct}=="000d",SYMLINK+="android_fastboot"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
I know not all of them necessary...
Then ran:
Code:
sudo service udev restart
Now I can see it properly in adb devices.
Code:
List of devices attached
B057070xxxxx device
At this point I thought everything's fine despite the factory reset I still has access ADB.
The truth is that I can pull files (and probably push too) from my device (tried/system/ build.prop) to my computer.
But when I try "adb shell", it throw this error:
Code:
WARNING: linker: could not load library "/vendor/lib/libNimsWrap.so" from LD_PRELOAD for "/system/bin/sh"; caused by could not load library "libc.so" needed by "libNimsWrap.so"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/system/bin/sh"; caused by library "libc.so" not found
(adb logcat give the same error)
At the moment I can not push anything to the "/system" because that is mounted Read Only, but I might be able to push to some RW folders, but have no idea how to move it without shell.
I managed to pull some files from the "/system" so it is readable (at least for some seconds).
Additional info:
There's a "No command." message in the middle of the screen in Recovery Mode
Please, if you have any ideas that we can do with my half-bricked HDX 8.9 (3rd), please share them. I would be very thankful.
Thank you.
The fact that you are in linux might help, but when you reset to factory defaults, you removed root access and your ability to fix the problem. Try to install cve and run it from adb. I do not think it will work, but you could try.
Sent from my KFTHWI using Tapatalk
Broken sh
The cve is only a su hack.
My shell is broken. I will be unable to run su from shell.
Thank you so much for this. After trying literally everything else, this is the only thing that worked, and worked the first time.
Command prompt stuck
I have a Kindle Fire HDX 7 inch soft bricked at the white and gold screen where the animation moves across. I can get to the very end of step 4. After entering that in the command prompt it shows > and will not let me enter any other command to reboot recovery. Anything that is typed just kicks the prompt back to > do you guys have any ideas on how to get to step 5. Anything would help. Thanks.
Just a thought, you could try adding the argument -v to step 4 and see why it is stalling. Also, do you know what you did to get to the softbrick, and what version os/recovery you have?
Command prompt stuck
lekofraggle said:
Just a thought, you could try adding the argument -v to step 4 and see why it is stalling. Also, do you know what you did to get to the softbrick, and what version os/recovery you have?
Click to expand...
Click to collapse
I believe I know what soft bricked it. I downgraded to 3.2.8 and added safe strap and made a backup in case of a mistake. When everything was fine I moved to 4.5.2. I installed google play and got the white screen error. I removed the google play apks. While doing that I deleted the twrp folder with the backup since I moved from 4.5.2 I figured it wouldn't matter, but it seems like I was wrong. I have adb access and root still I'm on 4.5.2 and I have the kindle recovery, or atleast that's what comes up when I use the adb reboot recovery. I think I can still save it if I can get to step 5.
I agree, but unfortunately, I think that no you need to wait for someone with more expertise than me to help I do not know why it won't copy the files. Sorry.
Command prompt stuck
Here is a screen shot
Thanks for the help.
Robo101007 said:
Here is a screen shot
Thanks for the help.
Click to expand...
Click to collapse
Disclaimer: I didn't try these commands, I only look on your posted pictures and compare them with OP...
Your commandline for part 4 is wrong, it should look like this (focus on parts in bold, in part two you are copying myupdate.bin to kindle, so in part 4 you already have file in kindle, no need to add path to myupdate.bin on your PC to the path described in part 4, also there is missing >> in your pictures)
example
2. ADB PUSH myupdate.bin /data/local/tmp/
3. ADB SHELL
3. su
4. echo '--update_package=/data/local/tmp/myupdate.bin' >> /cache/recovery/command
5. reboot recovery
Hopefully if you type it correctly, it will work and you save your kidle, good luck...
jeryll said:
Disclaimer: I didn't try these commands, I only look on your posted pictures and compare them with OP...
Your commandline for part 4 is wrong, it should look like this (focus on parts in bold, in part two you are copying myupdate.bin to kindle, so in part 4 you already have file in kindle, no need to add path to myupdate.bin on your PC to the path described in part 4, also there is missing >> in your pictures)
example
2. ADB PUSH myupdate.bin /data/local/tmp/
3. ADB SHELL
3. su
4. echo '--update_package=/data/local/tmp/myupdate.bin' >> /cache/recovery/command
5. reboot recovery
Hopefully if you type it correctly, it will work and you save your kidle, good luck...
Click to expand...
Click to collapse
Jeryll thank you so much. I really appreciate it. That did install the update and that makes sense as to why I was having issues. Thanks for the response.
osmorgan said:
** THIS WORKED FOR ME, BUT MAY NOT FOR YOU. I'M POSTING THIS FOR INFORMATION **
From reading through logs of my boot looping HDX 7", i have found this method is working to re-flash an update file onto a kindle. needs ADB and ROOT access.
Use your current version or higher update file. This was on STOCK recovery, going from 13.4.5.2 to 13.4.5.3
Click to expand...
Click to collapse
Help my kf hdx7, it's bootloop and only system recovery, I can enter stock recovery but phone don't connect with pc, how to connect it and run adb?
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Aftermath__ said:
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Click to expand...
Click to collapse
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Davey126 said:
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Click to expand...
Click to collapse
Thanks, also he said something about changing device name in build.prop Is it important?
Aftermath__ said:
Thanks, also he said something about changing device name in build.prop Is it important?
Click to expand...
Click to collapse
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Davey126 said:
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Click to expand...
Click to collapse
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Aftermath__ said:
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Click to expand...
Click to collapse
You're done. Recovery is almost impossible.
Davey126 said:
You're done. Recovery is almost impossible.
Click to expand...
Click to collapse
Not necessarily...
@Aftermath__: Can you gain adb access?
EncryptedCurse said:
Not necessarily...
@Aftermath__: Can you gain adb access?
Click to expand...
Click to collapse
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Aftermath__ said:
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Click to expand...
Click to collapse
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
EncryptedCurse said:
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
Click to expand...
Click to collapse
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Aftermath__ said:
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Click to expand...
Click to collapse
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
EncryptedCurse said:
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Aftermath__ said:
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Click to expand...
Click to collapse
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
EncryptedCurse said:
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Click to expand...
Click to collapse
It worked. Thank you so much for your help.
Aftermath__ said:
It worked. Thank you so much for your help.
Click to expand...
Click to collapse
Glad you are able to fix the problem. Props to EncryptedCurse for picking up the ball and pointing you in the right direction. Thanks also to draxie for posting a solution. Not many devices live through a soft brick. Well done.
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Aftermath__ said:
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Click to expand...
Click to collapse
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Davey126 said:
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Click to expand...
Click to collapse
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
- download 3.2.5 here; print upgrade instructions
Click to expand...
Click to collapse
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Aftermath__ said:
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Click to expand...
Click to collapse
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Davey126 said:
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Click to expand...
Click to collapse
I tried and i can't do factory reset because of the same issue as with the upgrade/downgrade. I guess the reason is that I flashed this recovery and I really shouldn't.
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!