I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help
Related
Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
md1008 said:
Yesterday unlocked via HTC dev. The through fast boot flashed twrp. That didn't work so well I couldn't actually flash any ROMs I could make a backup and I could restore. OK so I flashed cwm through Fast boot success however I flashed 2 ROMs one experia all seemed to work but WiFi was of no use I don't pay for service so that was obviously a no go. I flashed the ROM 3 times even re downloading it again. Ok so on to aokp flashed via cwm flashed jb gapps flashed boot.IMG via fast boot. Would boot up to start up then FC and reboot and boot loop at the aokp screen. Repeated numerous times getting various results.
Now I relocked boot loader and ran the ruu.exe and had to leave in the process it looked like it was booting hopefully when I come home it will be back to stock. Far from a dev so I am confused. I just want to try out some roms? Could this but a kernel issue? Recovery or something else?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
first more info will get u more accurate advice ie.... build date of aokp.... last nightly is messed up use stable for best results. also the method of which u applyed these roms would be nice htc s-on is a pain so it requires a little diffrent prosses thin on other phones and diffrent strokes for diffrent roms
for wifi u have to reflash boot.img....
for FC and bootloops factory reset, wipe cache partition, wipe dalvik cache....
download latest nightly and follow this------>
1. download rom and gapps,transfer them to root of SD card
2. extract boot.img(the kernel) from ROM zip,or whichever is compatible and place it in fastboot folder
3. go into bootloader, FIRST flash the boot.img in fastboot.
4. go into recovery, then FULL WIPE-factory reset, erase cache and dalvik cache.
5. then flash the ROM.
6. boot into the rom.then again enter into recovery and then flash gapps.
do the above steps in the same order all over again....it should work...:fingers-crossed:
If I am not mistaking I used the latest stable build of aokp, and I flashed both roms through recovery using both CWM and TWRP and also flashed kernel using fastboot. Although I reflashed TWRP and flashed AOKP and all seems to be right in the world. right now in at the set up screen so far no freeze or boot loop and wifi is working. Consider this problem solved
And yeah S-on sucks!
Can anybody advise me how i can keep my recovery (TRWP), every time i try a new ROM zip it gets wiped and a new type of recovery tool gets installed ie CWM or CM recovery which then makes it impossible to restore a TWRP back up. I then have to set up FlashTool and Fastboot install a .img from a rom with TWRP recovery. Then i can restore. Seems a pain in the but. I have previously rooted other devices ie Kindle Fire hd and never lost or over written recovery sectors when flashing new roms.
[email protected] said:
Can anybody advise me how i can keep my recovery (TRWP), every time i try a new ROM zip it gets wiped and a new type of recovery tool gets installed ie CWM or CM recovery which then makes it impossible to restore a TWRP back up. I then have to set up FlashTool and Fastboot install a .img from a rom with TWRP recovery. Then i can restore. Seems a pain in the but. I have previously rooted other devices ie Kindle Fire hd and never lost or over written recovery sectors when flashing new roms.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/xpe...-recoveries-custom-roms-t3016507/post58515438
The reason this happen is that Xperia smartphones do not have recovery partition. The recovery is part of the kernel (boot.img), so the kernel comes with a recovery. The link above has a recovery with is flashed onto the FOTA (over-the-air) upgrade partition, which is not used if you have an unlocked bootloader.
Works great
Thanks for that. I had previously tried it but used the latest twrp zip file instead of the 2 in lower box and recovery was totally unstable. However now done FOTA-TWRP.zip and flashed 2 different roms retaining twrp recovery everytime.
Hey guys, I just recently got some parts for my old One X to start playing with it again (bored with ios). I was running an older version of ViperXL and wanted to get lollipop so my goal was to put CM12.0 on my phone. My recovery was twrp but a version that was older so I had to update it. The in app update wasn't working so I updated cwm instead. When I did this I tried to boot to recovery and it would attempt to go to recovery but then boot back to the os.
Then I was trying to flash the recovery using fastboot which resulted in the same problem. Somewhere in there I flash the recovery.img as my boot image (sudo fastboot flash boot recovery.img) This made my phone repeatedly try to boot into recovery. I tried flashing new ViperXL boot.img as well as a couple others but none let me get into my os again. Now it is just a bootloop trying to start my phone up.
When I try flashing a .zip I get the error 'FAILED (remote: not allowed)'. Flashing recovery and boot images work though.
I've tried a lot and done a lot of searching but nothing can get me into recovery or even out of any sort of bootloop.
I'm using Ubuntu and my phone is S-On if that means anything.
Thanks!
Try restoring any backups of old roms from the recovery. Make sure Recovery is written properly in recovery partition. If this works fine , the appropriate boot.img shud be automatically flashed , i guess.
If u dont have a backup , try finding another one x user using a custom recovery, create a backup from his mobile and copy it to ur sd card by mounting it thru recovery and restore it.
If it doesnt work , wipe all the partitions - System , cache, boot and recovery.. then try flashing a Recovery and then a Boot.img and a rom.
I havent faced such a situation. Just my suggestions as no experts have responded.
Cheers if u have already sorted it out !!!
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM
Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img