Develop Bugs

Issue with flashing roms with s-on

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

LineageOS-based roms won't boot - Firmware 4.1.0

I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.

do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/

bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong

vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.

Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot

Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM

go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further

indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen

Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!

AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes

indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)

AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now

Can't upgrade TWRP from 2.8.7 to 3.0.2

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

Can't install TWRP

I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.

Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again

pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.

pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.

jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np

It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?

jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.

noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.

jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.

Help flashing back to stock, tried everything.

Hi, i'm having trouble flashing back to stock.
I've got the latest stock firmware from sammobile.
Using twrp to install it says missing META-INF as the firmware zip isn't made the same as custom firmware.
Adding the tar.md5 to ap in odin flashes the boot and recovery but goes extremely slow when it starts flashing system (left it 2 hours and it hadn't even got half way) I'm guessing that's not normal.
I took a backup with twrp before I started flashing in twrp which flashes fine but I get endless boot loop when trying to start it.
I've tried fastboot but it doesn't detect the tablet.
I've tried different usb ports, cables, different versions of odin and different stock firmware. I'm ready to throw it out the window.
One thing to note is the [P600][Touchwiz] Marshmallow Rom 20170622 works great but also boot loops when I turn it off and on again, I have to boot into twrp then choose reboot in there and then it boots ok, that doesn't work with my twrp backup though.
Anything I'm doing wrong?
Thanks.

Well for some reason after installing marshmallow rom again then installing my backup it boots fine, havn't a clue why it failed to boot the other 4 times.

Nope
Back to continuous boot loop after second reboot.
All I did was turned developer options off and it's boot looping again.
Flashed original stock boot.tar.md5 and recovery.tar.md5 then factory reset and wiped cache but still boot loops.

Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?

Mazert said:
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Click to expand...
Click to collapse
I'm not quite sure what your problem is but you should be able to downgrade, I've done it before.
Try this guide first. I've had success with it.
If all goes well you can then try to flash your stock ROM. The one I've flashed successfully in the past is the one in this post.
Good luck!

You may need to repartition your system. Tick the repartition in Odin. **All data will be lost**
Sent from my SM-N915G using Tapatalk

Thanks, I followed the guide in that post and it flashed ok then I finally managed to flash the latest stock!