I downgraded my Fire HD 6 to 4.5.3, rooted it using Kingroot and installed TWRP using Flashify (couldn't flash TWRP because the bootloader/fastboot was locked ("Failed:...locked hw")) . After rooting, I blocked OTA using the adb command lines.
Then I updated to the latest Fire OS using http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449. After step 2A (flash the respective Amazon ROM 4.5.x update (the latest one? [so I tried 5.5.4)), I thought I was home free. But upon rebooting, I found root was gone. Not sure what I missed and when I missed it but that's not the point now. [Upon much reflection, it was probably not issuing the block OTA commands again, duh.]
Now, I have no recovery; TWRP is gone. Stock recovery is gone. I can't flash TWRP using fastboot because bootloader is still locked. Flashify needs root to work. Help greatly appreciated.
I tried to unbrick (even though it's not bricked but I'm at a loss as to how to get a recovery back on it) using Imma Wake's Linux but it just hangs on ./reader.sh . I'm really at a loss but it's not for not trying. I've got to reroot this thing cuz I hate hate hate amazon. Can't do it without a recovery. Well, really, is there no one who can help me?
bleak93 said:
I tried to unbrick (even though it's not bricked but I'm at a loss as to how to get a recovery back on it) using Imma Wake's Linux but it just hangs on ./reader.sh . I'm really at a loss but it's not for not trying. I've got to reroot this thing cuz I hate hate hate amazon. Can't do it without a recovery. Well, really, is there no one who can help me?
Click to expand...
Click to collapse
Why don't you try unlocking the bootloader so you can flash TWRP, bleak?
bleak93 said:
Why don't you try unlocking the bootloader so you can flash TWRP, bleak?
Click to expand...
Click to collapse
Well, that's a damn good idea, bleak. I wish I thought of it.
So I tried using the python/cublock.py method. I'm on Windows 7 so I installed Python. I get the two codes, run cublock.py [XXX] [SSS] and I get a file called "unlock.img" but after that, it hangs when I run adb reboot bootloader / fastboot -i 0x1949 flash unlock unlock.signed. I tried fastboot -i 0x1949 flash unlock unlock.img cuz that's what the file is called but it just says "[WAITING FOR A DEVICE]" or something like that after both of those commands. I think it doesn't reboot into the bootloader after adb reboot bootloader ; it shuts down because there are no signs of it in the device manager.
bleak93 said:
Well, that's a damn good idea, bleak. I wish I thought of it.
So I tried using the python/cublock.py method. I'm on Windows 7 so I installed Python. I get the two codes, run cublock.py [XXX] [SSS] and I get a file called "unlock.img" but after that, it hangs when I run adb reboot bootloader / fastboot -i 0x1949 flash unlock unlock.signed. I tried fastboot -i 0x1949 flash unlock unlock.img cuz that's what the file is called but it just says "[WAITING FOR A DEVICE]" or something like that after both of those commands. I think it doesn't reboot into the bootloader after adb reboot bootloader ; it shuts down because there are no signs of it in the device manager.
Click to expand...
Click to collapse
Did you just reply to yourself? ???
I'm stuck in the same crappy situation
I'm in this situation too...
I'm no expert, but I think I know what happened. For whatever reason, TWRP doesn't play nice with 5.x bootloaders. 4.x is fine but 5.x is a no-go. I'm assuming that when you flashed TWRP you overwrote your stock recovery. This would have been fine, but the wording in the tutorial you were following is a bit misleading. When he said flash the 4.5.x update (the latest one) he meant the latest 4.5.x (eg 4.5.3, 4.5.4, etc) but not anything above 4.5.whatever. When you flashed 5.5.4 you updated the bootloaders to 5.x so TWRP no longer works and you've lost your stock recovery. Not sure what happened to your root though. It's possible it's still there and there's just not a manager app installed? Try installing Kingroot again and using its root check function to see. If it really is gone, then I have no idea how to fix it.
@bibikalka any help please?
---------- Post added at 11:55 PM ---------- Previous post was at 11:49 PM ----------
Killa8;72047553 [user=6680544 said:
@bibikalka[/user] any help please?
Click to expand...
Click to collapse
@powerpoint45
similar situation
I havea fire hd 6 (4th generation) running 5.3.1.0 no recovery but I do have root via kingroot so I have flashify and rashr. I have tried flashing TWRP using flashify and rashr, and no error but it wont boot to twrp. Any way to flash stock recovery or is there another option for 5.3.1.0 as far as recover??
bleak93 said:
I downgraded my Fire HD 6 to 4.5.3, rooted it using Kingroot and installed TWRP using Flashify (couldn't flash TWRP because the bootloader/fastboot was locked ("Failed:...locked hw")) . After rooting, I blocked OTA using the adb command lines.
Then I updated to the latest Fire OS using http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449. After step 2A (flash the respective Amazon ROM 4.5.x update (the latest one? [so I tried 5.5.4)), I thought I was home free. But upon rebooting, I found root was gone. Not sure what I missed and when I missed it but that's not the point now. [Upon much reflection, it was probably not issuing the block OTA commands again, duh.]
Now, I have no recovery; TWRP is gone. Stock recovery is gone. I can't flash TWRP using fastboot because bootloader is still locked. Flashify needs root to work. Help greatly appreciated.
Click to expand...
Click to collapse
Hi I am having the same exact problem and I would just like to know if you have found a fix for this problem yet. I'm stuck on cm11 rom which has a bunch of bugs and I would like to go back to fire os but I have no root and can boot into fast boot or recovery. Any help would be appreciated. Thanks.
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Killa8 said:
I'm stuck in the same crappy situation
Click to expand...
Click to collapse
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Killa8 said:
I'm stuck in the same crappy situation
Click to expand...
Click to collapse
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
kyle12345109876 said:
Hi I am having the same exact problem and I would just like to know if you have found a fix for this problem yet. I'm stuck on cm11 rom which has a bunch of bugs and I would like to go back to fire os but I have no root and can boot into fast boot or recovery. Any help would be appreciated. Thanks.
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
Click to expand...
Click to collapse
Just so I have a clear understanding: you're running cm11 but you have lost root and recovery. Can you get into fastboot? I think you wrote you can boot into fastboot and recovery.
Kindle fire no twrp
Drunkpilot said:
Just so I have a clear understanding: you're running cm11 but you have lost root and recovery. Can you get into fastboot? I think you wrote you can boot into fastboot and recovery.
Click to expand...
Click to collapse
Ok so yes I am on cm 11 and i cannot boot into recovery but I can boot into fast boot using the adb commands so does this mean I can flash twrp using fast boot?
Also I have used kingo root and have now gained root access.
kyle12345109876 said:
Ok so yes I am on cm 11 and i cannot boot into recovery but I can boot into fast boot using the adb commands so does this mean I can flash twrp using fast boot?
Also I have used kingo root and have now gained root access.
Click to expand...
Click to collapse
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Thanks I tried flash fire and it didn't regonize the kingo root, also tried flashify and it just rebooted the tablet and didn't work. So I will try with the fast boot.
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Right now I remember I tried to flash twrp using fast boot and it gave me an error saying :FAILED (remote: flashing not allowed for locked hw).
Does this mean my bootloader is somehow locked? If so how do I unlock it?
kyle12345109876 said:
Thanks I tried flash fire and it didn't regonize the kingo root, also tried flashify and it just rebooted the tablet and didn't work. So I will try with the fast boot.
Click to expand...
Click to collapse
Maybe try flashing a chainfire SuperSU.zip through flashing so that you can replace the kingo SU, then use the SuperSU app to clean up some of the kingo root remnants and have something recognizable when flashing TWRP. I have been doing a lot of Fire flashing work lately as I just used my warranty for a brick I replaced. Then, within a couple hours bricked the replacement due to me not turning off the OTA sufficiently while running 4.5.2 and used the Powerpoint45 technique (which worked brilliantly on the new Fire) and then stupidly lost root and had to revert back to 4.5.3. Needless to say, I have been reading and executing a lot of different actions. Currently, I'm on 4.5.3 with TWRP and finally getting the Google Play store to work.
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
kyle12345109876 said:
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
Click to expand...
Click to collapse
Look at the TWRP thread for our Fire. I think it has the dd commands to install the recovery now that you are rooted once again. It sounds like you didn't install the 5.x.x uboot and recovery zip along with the update and lost recovery. I think you said you used the unbrick method and you just hung on the reading.sh. that method would give you TWRP and nothing else, but from there you could them flash the 5.x files in the thread. I used Flashify to get TWRP yesterday, and I think I had kingroot at the time. I know the is a zip only containing the 4.5.3 bootloader's, but I can't remember where I saw it right now, and if it would work or not. I'm still in learning more as well.
Drunkpilot said:
Look at the TWRP thread for our Fire. I think it has the dd commands to install the recovery now that you are rooted once again. It sounds like you didn't install the 5.x.x uboot and recovery zip along with the update and lost recovery. I think you said you used the unbrick method and you just hung on the reading.sh. that method would give you TWRP and nothing else, but from there you could them flash the 5.x files in the thread. I used Flashify to get TWRP yesterday, and I think I had kingroot at the time. I know the is a zip only containing the 4.5.3 bootloader's, but I can't remember where I saw it right now, and if it would work or not. I'm still in learning more as well.
Click to expand...
Click to collapse
Hi thanks for the help turns out I managed to brick the device once again so I just used powerpoints video to unbrick and now I have twrp again. Question though I tried to install fire os 4.5.3 in twrp but it give me an error sayingI have the Omni Ariel not the full Ariel so I can't flash the file. Anyone know how to fix it?
kyle12345109876 said:
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
Click to expand...
Click to collapse
Hi the process should be fairly simple. Use the tutorial from the unbricking thread to get your device back to normal. It will be long but it works unless you have fire os 5(like me). Otherwise there's literally no other option you can use
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
kyle12345109876 said:
Hi thanks for the help turns out I managed to brick the device once again so I just used powerpoints video to unbrick and now I have twrp again. Question though I tried to install fire os 4.5.3 in twrp but it give me an error sayingI have the Omni Ariel not the full Ariel so I can't flash the file. Anyone know how to fix it?
Click to expand...
Click to collapse
Did you download the correct file? Check again
Related
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
HyperNyan said:
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
Click to expand...
Click to collapse
Can you get into recovery by holding Power and Volume-Up?
DoLooper said:
Can you get into recovery by holding Power and Volume-Up?
Click to expand...
Click to collapse
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
HyperNyan said:
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
Click to expand...
Click to collapse
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you! My Fire tablet is now able to boot and can run normally, but with root access this time Thank you for helping me through this issue
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
You may be able to dd the recovery partition. Someone else will have to help with that.
HyperNyan said:
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
Click to expand...
Click to collapse
Just do this, run the script provided :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
I'll get you TWRP and 4.5.3 bootloaders. Then flash 5.4.1 stuff from TWRP.
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
THANK YOU SO EFFING MUCH! I thought my HD6 was done. I was beginning to panic. I went through a LOT of guides to fix it and nothing worked except what you posted.
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
HyperNyan said:
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
Click to expand...
Click to collapse
The recommendations have not changed since the last time you asked Either install stock recovery via Flashify (dig out the recovery image from this zip : 5.2.0_stock_recovery_only.zip , here : http://forum.xda-developers.com/showpost.php?p=62011272 ), or run the script in post #2, and from TWRP, re-install 5.4.1 bootloaders :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Thank you! My tablet is now working great, TWRP successfully installed. Just about a few minutes ago I had a panic attack when it started boot-looping, but then I shut it off for a while, and booted it into TWRP, and it was fine. Go figure I will now attempt to install cm11! Thank you for all of your help!
Hi,
I was thinking about trying to get TWRP and CM11 on my 2014 Fire HD 6, as I went to do it I couldn't for the life of me get the device into recovery or the bootloader. ADB commands do absolutely nothing and nor do any button combinations. I've even tried adb shell, su, reboot recovery to no avail.
Software I'm running atm is OS 5.1.1.
Any help would be appreciated!
jakestevens96 said:
Hi,
I was thinking about trying to get TWRP and CM11 on my 2014 Fire HD 6, as I went to do it I couldn't for the life of me get the device into recovery or the bootloader. ADB commands do absolutely nothing and nor do any button combinations. I've even tried adb shell, su, reboot recovery to no avail.
Software I'm running atm is OS 5.1.1.
Any help would be appreciated!
Click to expand...
Click to collapse
Easy. Get root (have root already ?). Then, the script in post #2 for TWRP, and do whatever you want from TWRP:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
bibikalka said:
Easy. Get root (have root already ?). Then, the script in post #2 for TWRP, and do whatever you want from TWRP:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you for that, I did have a look around for some stuff but obviously missed that. Thanks again for finding that
Sent from my SM-N910F using XDA-Developers mobile app
I'm running 4.5.5, can I still use that same script to install TWRP?
bibikalka said:
Easy. Get root (have root already ?). Then, the script in post #2 for TWRP, and
do whatever you want from TWRP:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Emerald9 said:
I'm running 4.5.5, can I still use that same script to install TWRP?
Click to expand...
Click to collapse
You need to get root. But with root, the TWRP script will work just fine!
Thanks, bibikalka. I have root and TWRP (thanks to you and doLooper), but no Google store yet. Can I use your guide here to go from 4.5.5 to 5.3.1?
bibikalka said:
You need to get root. But with root, the TWRP script will work just fine!
Click to expand...
Click to collapse
I have been searching in the internet for hours, trying every method i could understand and none of them worked. the main problem is the official bootloader unlock tool provided by asus is not working, it just restarts the phone and it is still locked. one solution is flash a custom recovery without unlocking phone and another way is unlock without the official app or maybe root without custom recovery, i would be happy if someone explains a way to root this phone.
indeed. the official bootloader unlock is not working and just restarting with no changes.
Then i tried to flash TWRP via fastboot it says Ok but no TWRP when I proceed to recovery its only stock recovery.
iamcurseal said:
indeed. the official bootloader unlock is not working and just restarting with no changes.
Then i tried to flash TWRP via fastboot it says Ok but no TWRP when I proceed to recovery its only stock recovery.
Click to expand...
Click to collapse
iamcurseal said:
indeed. the official bootloader unlock is not working and just restarting with no changes. Then i tried to flash TWRP via fastboot it says Ok but no TWRP when I proceed to recovery its only stock recovery.
Click to expand...
Click to collapse
I've managed to root my phone using magisk and looks like my phone is unlocked and unlock tool had no problem because i could flash modified boot.img and install magisk. Also i can't install asus updates anymore.
lostact said:
I've managed to root my phone using magisk and looks like my phone is unlocked and unlock tool had no problem because i could flash modified boot.img and install magisk. Also i can't install asus updates anymore.
Click to expand...
Click to collapse
did you flashed the magisk?
sorry Im only newbie in flashing, can you give me the procedure how to use magisk? if possible, also the rooting procedure.
The consequences like cant update the version is no problem for me.
thanks for the help. :good:
You can try this twrp http://www.stupdroid.com/2018/02/root-twrp-Asus-ZB501KL.html
lostact said:
I've managed to root my phone using magisk and looks like my phone is unlocked and unlock tool had no problem because i could flash modified boot.img and install magisk. Also i can't install asus updates anymore.
Click to expand...
Click to collapse
can you provide a guide on how to do this. A link to a boot.img would be greatly appreciated!
lostact said:
I've managed to root my phone using magisk and looks like my phone is unlocked and unlock tool had no problem because i could flash modified boot.img and install magisk. Also i can't install asus updates anymore.
Click to expand...
Click to collapse
I don't really need to root it, and instead of creating new thread I'd ask here;
The L1 is my wife's phone now, it's unroot, and never need to be,...can somebody tell me the guide of how to get rid the bloatwares on it? With adb on pc perhaps?
Thank you in advance.
Pasarireng said:
I don't really need to root it, and instead of creating new thread I'd ask here;
The L1 is my wife's phone now, it's unroot, and never need to be,...can somebody tell me the guide of how to get rid the bloatwares on it? With adb on pc perhaps?
Thank you in advance.
Click to expand...
Click to collapse
Somebody please?
Help!
can you provide a guide?
lostact said:
I have been searching in the internet for hours, trying every method i could understand and none of them worked. the main problem is the official bootloader unlock tool provided by asus is not working, it just restarts the phone and it is still locked. one solution is flash a custom recovery without unlocking phone and another way is unlock without the official app or maybe root without custom recovery, i would be happy if someone explains a way to root this phone.
Click to expand...
Click to collapse
I suppose that you've already turned developer mode on and enabled the USB debugging.
Did you either reboot the phone by yourself or it did that automatically after flashing twrp? There are some devices that just restart and get the official bootloader back. This auto restart overwrites the bootloader.
Some people say that after flashing twrp you must unplug the device and then reboot directly to bootloader by yourself, holding the power and volume up buttons . Have you tried it?
---------- Post added at 06:16 PM ---------- Previous post was at 06:14 PM ----------
mark332 said:
You can try this twrp http://www.stupdroid.com/2018/02/root-twrp-Asus-ZB501KL.html
Click to expand...
Click to collapse
Thank you guy! But today it returns 404.
I have unlocked the bootloader after that I have installed the twrp and wanted to have the magisk too.
but unfortunately when flashed magisk zip phone got bricked and didnt boot into recovery just go into fastboot (btw the recovery i flashed was also temporary as it has been gone every time i restart and i have to again reflash the recovery) kindly help me how to unbrick my phone????? tried many method found online all in vain.
I was using realme ui 1.0.
So you have unlocked bootloader from ui 1.0 and flash twrp and try to root. Perhaps the magisk is not for ui 1.0. Can you still go into twrp and flash ui 1.0 (c.03) or downgrade? BTY your phone is India version, right?
donkeyman1234 said:
So you have unlocked bootloader from ui 1.0 and flash twrp and try to root. Perhaps the magisk is not for ui 1.0. Can you still go into twrp and flash ui 1.0 (c.03) or downgrade? BTY your phone is India version, right?
Click to expand...
Click to collapse
yeah still i can go to twrp but unable to install the officiAL rom as twrp does not recognizing ozip file so what to do now? i have global version.
So you used stock recovery to flash india version ui 1.0 and unlock the bootloader and flash twrp, that sounds great. Just try to change ozip to zip and see twrp do.
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
Sajidmaibal said:
yeah still i can go to twrp but unable to install the officiAL rom as twrp does not recognizing ozip file so what to do now? i have global version.
Click to expand...
Click to collapse
rename ozip to zip, see if twrp works? And can you show me your phone version?
donkeyman1234 said:
So you have global version then you used stock recovery to flash india version ui 1.0 and unlock the bootloader and flash twrp, that sounds great. Just try to change ozip to zip and see twrp do, because I can't unlock the bootloader for my global version. Maybe you can show us how you unlock the global version steps by steps.
---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------
rename ozip to zip, see if twrp works? And can you show me your phone version?
Click to expand...
Click to collapse
unfortunately i have hard bricked my phone. dont know thinking what i just tried to lock the bootloader and boom. now just boot/recovery destroyed screen appears on the screen. any soln:crying:? or i have to wait till this corona pandemic over nd get it done from service centre??
Sajidmaibal said:
unfortunately i have hard bricked my phone. dont know thinking what i just tried to lock the bootloader and boom. now just boot/recovery destroyed screen appears on the screen. any soln:crying:? or i have to wait till this corona pandemic over nd get it done from service centre??
Click to expand...
Click to collapse
unlocking bootlaoder is easy
1. you need in dept test app latest one
2. submit for review
3. review will get successful in 10/20 mins
4. then just follow the normal procedure for unlocking
kindly follow these vidoes for reference
https://youtu.be/dW4yKt6Xtss
https://youtu.be/V-4ArXEmySM
Sajidmaibal said:
yeah still i can go to twrp but unable to install the officiAL rom as twrp does not recognizing ozip file so what to do now? i have global version.
Click to expand...
Click to collapse
So you hard bricked you phone by locking bootloader.
Maybe you should take it to service center.
Flash twrp 3316 IMG..it will flash ozip
Had boot/recovery destroyed message after attempting to flash a gsi. I followed the unbrick guide. I can access fastboot & boot into recovery, however touch input is not working so I'm unable to do anything. Phone sticks on the realme screen when attempting to let it boot. Any ideas? I live in the US so a service center isn't possible.
XDA seems pretty dead these days. Shame.
J-Mizzle said:
XDA seems pretty dead these days. Shame.
J-Mizzle said:
Had boot/recovery destroyed message after attempting to flash a gsi. I followed the unbrick guide. I can access fastboot & boot into recovery, however touch input is not working so I'm unable to do anything. Phone sticks on the realme screen when attempting to let it boot. Any ideas? I live in the US so a service center isn't possible.
Click to expand...
Click to collapse
it happened to me too. i can help you. first boot into fastboot and use ur computer to flash twrp using command "fastboot flash recovery (attach twrp img here) then boot into recovery which should be twrp and then download orangefox recovery for realme xt. it should be a zip file so just install it using twrp. Then get the official realme xt ozip from their website boom orangefox should install it then wipe data once again.. then start your system. if it goes into recovery again just wipe data again and it should work.
Click to expand...
Click to collapse
any update here guys? bricked my phone on relocking bootloader.