Installation:
Unlock your phone at www.htcdev.com
Boot phone into fastboot
Perform command fastboot flash recovery recovery-clockwork-touch-6.0.4.8-t6xx.img or the recovery.img file name
Boot into HBOOT and select recovery
Root:
Download SuperSU http://download.chainfire.eu/supersu
Flash it in recovery
Downloads:
8060 China
Touch -
Classic - http://flyhalf205.com/getdownload.php?file=recoveries/recovery-clockwork-6.0.4.5-t6dug.img
Stock - http://flyhalf205.com/getdownload.php?file=recoveries/stock_recovery_t6dug.img
GSM
Download - http://builder.unstableapps.com/#/latest/clockworkmodrecovery/t6
Stock - http://flyhalf205.com/recoveries/stock_recovery_t6ul.img
Sprint
Download - http://builder.unstableapps.com/#/latest/clockworkmodrecovery/t6spr
Verizon
Download - http://builder.unstableapps.com/#/latest/clockworkmodrecovery/t6vzw
Stock - http://flyhalf205.com/recoveries/stock_recovery_t6vzw.img
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
XDA:DevDB Information
ClockworkMod Touch Recovery, Tool/Utility for the HTC One Max
Contributors
Flyhalf205
Version Information
Status: Testing
Created 2013-10-26
Last Updated 2014-09-27
Thank you very much. Love you so much.
I see that this is for Verizon One Max. Do you know that is this same as international version?
seto_613 said:
Thank you very much. Love you so much.
I see that this is for Verizon One Max. Do you know that is this same as international version?
Click to expand...
Click to collapse
Yes. This recovery is built for the International One Max.
Flyhalf205 said:
Yes. This recovery is built for the International One Max.
Click to expand...
Click to collapse
Thank you very much~~
What a wondful job! Thx very much!
thx u very much
Random question here guys. Either on TWRP or CWM. When you turn off the phone and plug it up into charger. Is there a charge animation?
I am using dual SIM version of One Max (China Unicom's 8060, main SIM for WCDMA, sub SIM for GSM). Unfortunately, this recovery does not work. After unlock and flash recovery is done, it cannot enter recovery. It stays at the initial screen with "Entering recovery" and nothing happens. I have to press power button to power off. Is it possible to modify this to fit other model? Highly appreciated.
---------- Post added at 06:04 AM ---------- Previous post was at 05:27 AM ----------
One more question. How can I flash back to stock recovery? Tks.
PD said:
I am using dual SIM version of One Max (China Unicom's 8060, main SIM for WCDMA, sub SIM for GSM). Unfortunately, this recovery does not work. After unlock and flash recovery is done, it cannot enter recovery. It stays at the initial screen with "Entering recovery" and nothing happens. I have to press power button to power off. Is it possible to modify this to fit other model? Highly appreciated.
---------- Post added at 06:04 AM ---------- Previous post was at 05:27 AM ----------
One more question. How can I flash back to stock recovery? Tks.
Click to expand...
Click to collapse
The only way to flash back stock recovery is if you had backed up the stock recovery before flashing CWM.
Can you tell me how to back up the stock recovery? Thanks again.
Hi Flyhalf, will you consider working out a version of the recovery for China Unicom's dual-SIM model (T6/8060)? It uses the same configuration as international version except that it supports dual SIM. I bet many users here (including me) are really looking forward to receiving it. Thank you very much.
PD said:
Hi Flyhalf, will you consider working out a version of the recovery for China Unicom's dual-SIM model (T6/8060)? It uses the same configuration as international version except that it supports dual SIM. I bet many users here (including me) are really looking forward to receiving it. Thank you very much.
Click to expand...
Click to collapse
I need a stock recovery or boot image from your device if you guys can get me one.
Someone who has s-off their device and this recovery will not boot. Please send me a copy of your stock recovery.img or boot.img
Flyhalf205 said:
The only way to flash back stock recovery is if you had backed up the stock recovery before flashing CWM.
Click to expand...
Click to collapse
I have just unlocked my boot-loader and have been trying to backup my stock recovery before flashing CWM. I seem to be lost as no methods (adb/terminal) seem to work. Can you please post a link where i can find instructions to backup my stock recovery?
I also tried fastboot boot <recovery> but the phone hangs in HBoot after this. I have to reset to get it working
Am i missing something? My phone is stock with unlocked BL without root.
Thanks!
---------- Post added at 05:13 AM ---------- Previous post was at 04:20 AM ----------
I searched around and found from the HTC One forums that i may not be able to take a backup of the stock recovery if i don't have an s-off.
I went ahead and flashed CWM and tried to enter recovery. It would not boot and the phone was stuck which showed "Entering recovery ..." and a background HTC Logo.
I hard restarted the device and then entered HBoot to notice TAMPERED at the top of the device - This was weird for me. is this normal ?
I tried to boot into recovery again but it never worked.
I then flashed TWRP recovery which works fine and boots to recovery.
Phone seems to work without any issues though.
pradeepvizz said:
I have just unlocked my boot-loader and have been trying to backup my stock recovery before flashing CWM. I seem to be lost as no methods (adb/terminal) seem to work. Can you please post a link where i can find instructions to backup my stock recovery?
I also tried fastboot boot <recovery> but the phone hangs in HBoot after this. I have to reset to get it working
Am i missing something? My phone is stock with unlocked BL without root.
Thanks!
---------- Post added at 05:13 AM ---------- Previous post was at 04:20 AM ----------
I searched around and found from the HTC One forums that i may not be able to take a backup of the stock recovery if i don't have an s-off.
I went ahead and flashed CWM and tried to enter recovery. It would not boot and the phone was stuck which showed "Entering recovery ..." and a background HTC Logo.
I hard restarted the device and then entered HBoot to notice TAMPERED at the top of the device - This was weird for me. is this normal ?
I tried to boot into recovery again but it never worked.
I then flashed TWRP recovery which works fine and boots to recovery.
Phone seems to work without any issues though.
Click to expand...
Click to collapse
Twrp is the best and it ask if u want to root when rebooting
Sent from my HTC Butterfly s using xda premium
Can I get a Sprint user to test the Sprint version in the OP? Thank you!
whats going on
im s-off and 6.0.4.4 touch is woking for me ... and xxx.4.5 not ??
why ?
Sprint clockwork recovery boots, wipes caches, and dalvik, flashed su. Did not mount usb storage.
Edit: su not properly installed. Can't update binary, no busybox installed. Can't install busybox from market either.
lawnguy said:
Sprint clockwork recovery boots, wipes caches, and dalvik, flashed su. Did not mount usb storage.
Edit: su not properly installed. Can't update binary, no busybox installed. Can't install busybox from market either.
Click to expand...
Click to collapse
Could you hook up your phone and turn on usb debugging and do this command for me?
adb shell cat /proc/emmc
I've left my house I will as soon as I get back. Probably an hour.
Sent from my HTC0P3P7 using Tapatalk
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
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update. The Bootloader Logs screen says "failed to validate system image" followed by "Boot up failed".
All of my important data is backed up. I don't care about preserving any data on the phone; I just want to get it working again.
The attached photo shows what I can see.
After connecting the USB cable, "fastboot devices" returns TA38502SB6 fastboot
Is this something I can fix myself, with appropriate software? Will I need to approach Motorola? Is it beyond help?
Flash the twrp recovery using fastboot, install a rom and the squid kernel. The Rom is pretty stable now..
---------- Post added at 09:05 PM ---------- Previous post was at 08:33 PM ----------
Or else you can download the stock Rom
http://motofirmware.center/files/fi...2_lxi2250-531_cid7_subsidy-default_cfcxmlzip/
And the guide is : http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
rushabshah32 said:
Flash the twrp recovery using fastboot, install a rom and the squid kernel. The Rom is pretty stable now..
---------- Post added at 09:05 PM ---------- Previous post was at 08:33 PM ----------
Or else you can download the stock Rom
http://motofirmware.center/files/fi...2_lxi2250-531_cid7_subsidy-default_cfcxmlzip/
And the guide is : http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
Click to expand...
Click to collapse
Those look very useful, thank you. Gives me something to do this evening!
Loganberry said:
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update.
Click to expand...
Click to collapse
Was it the stock 5.1 update???
Software status: modified
How did you get the OTA update and what did you do previously ?
Recovery log says you had a modified software. So there was no hope to apply patch properly. And it bricked your system
rushabshah32 said:
Was it the stock 5.1 update???
Click to expand...
Click to collapse
Not sure. It was only around 20-30MB or so; can't remember the exact size.
PsyClip-R said:
How did you get the OTA update and what did you do previously ?
Recovery log says you had a modified software. So there was no hope to apply patch properly. And it bricked your system
Click to expand...
Click to collapse
OTA update was advertised through the normal Motorola OTA feature. All I did was to tap on "Yes, I'm in" to accept it when it was offered.
If my phone's ruined, then it's ruined. Irritating, but not the end of the world; a new Moto E2 isn't expensive. I'd just prefer not to have to buy a new one if there's any hope of resurrecting this one. As I indicated in my first post, the important data is safe; I just want a working phone again.
Edit: just re-read your question; realised I might have misunderstood part of it.
My phone had previously been rooted; before accepting the OTA update I went through the steps to unroot the phone before taking the OTA update; looks like something went wrong somewhere along the way.
Loganberry said:
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update. The Bootloader Logs screen says "failed to validate system image" followed by "Boot up failed".
All of my important data is backed up. I don't care about preserving any data on the phone; I just want to get it working again.
The attached photo shows what I can see.
After connecting the USB cable, "fastboot devices" returns TA38502SB6 fastboot
Is this something I can fix myself, with appropriate software? Will I need to approach Motorola? Is it beyond help?
Click to expand...
Click to collapse
i got the update yesterday too on my X1521 but it was working fine.after immediate reboot it was lagging like hell but rebooting solved it
Guys don't panic. What I would do is unlock the bootloader and flash TWRP, after that just download any custom ROM and TWRP lets you get on MTP so you can transfer the ROM to the internal storage.
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Also there's plenty of stock ROMS out there like SuperR's Stock Roms
I have a similar issue, I just accepted the OTA update from Motorola on my XT1511(otus), It was stock/rooted. The phone went into boot loop. Tried these things to remedy
1) tried booting to TWRP from fastboot. I'd get the TWRP splash screen, but no functionality
2)flashed TWRP - now have functioning recovery, but during rom flash get "error, cant mount /data
3)fastboot -w successfully wiped data, but couldn't format partition, still raw
4)From twrp "mount" screen couldn't check the box for mounting data
5)from twrp wipe>format data was able to format the partition
6) I've flashed a couple of twrp recovery images, and a couple of different roms, I don't get error messages, but now when the phone is powered on it always boots into recovery, even when reboot>system or reboot power off is selected. I can still access fast boot.
Any suggestions? I'm going to try returning to stock at this point'
Update: Downloaded stock recovery here:
http://forum.xda-developers.com/devdb/project/dl/?id=11977
Installed with fastboot, phone boots properly now!
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
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel
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.