Develop Bugs

[Q] rom flashing frustration

Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.

tenpin416 said:
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
Click to expand...
Click to collapse
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?

DMF1977 said:
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
Click to expand...
Click to collapse
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe

tenpin416 said:
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
Click to expand...
Click to collapse
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...

DMF1977 said:
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
Click to expand...
Click to collapse
After doing some reading I think the abort is caused by having the older ics bootlaoder.ive never had to update one before so im a bit hesitant. ..do you know if I update and try to switch back to my original restore or to a different rom (other than cm 10) Will I have to change the bootloader back again or will I run into a greater chance of problems in the future?

[S-ON][Latest TWRP/4Ext] Urgent...

Hello folks,
Those who are using latest TWRP or 4Ext recovery,Please comment below.Also i want to know which custom rom your on? I do flash roms in every 2-3 days and problem took place i guess somewhere from CM11 nightly 06/12 onwards.
So my question is: Anybody has encountered a problem where flashing latest nightly or any latest build beyond 4.4.3 causes reboot into recovery automatically soon after flashed boot.img and reboot system.
I always prefer Clean wipe, Install rom, Appropriate GApps, Inspiremod Patch, flash boot.img via fastboot.
Also i would like to add,that when i use Musta's CM11 nightly after successfully flashing it and rebooting the device. But nothing comes after typical htc logo and complete blank screen for few seconds and redirects me into TWRP recovery again. Where as If i use any rom made chinese devs like for ex. Mokee Open Source's latest weekly(randomly) it flashes correctly but it stuck at bootanimation.
Yesterday i've tried one more modified version of Musta's 20140622 nightly made by chinese dev, It flashed correctly but hangs up in bootanimation, i couldn't able to see anything beyond that.
Any sort of help will be appreciated.
Thanks.

Cannot install CM11 no matter what

Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.

TF666 said:
Hi guys,
I am getting DESPERATE here. Because of a mistake, I had to reflash stock LG ROM 50020d 4.4.2. From there, I rooted using geohot's towelroot and used Flashify to flash this TWRP 2.8.0.0 After 128754E10th attempt, it worked. I experienced all kinds of recovery loops when I used files for 4.2.2 base (because someone mentioned it's needed to prevent brightness issue) but it caused my recovery to go into some strange loop. So I reflashed the recovery.
Now I can enter TWRP 2.8.0.0 but I cannot, cannot, cannot flash yesterday's CM11 nightly for my device. When I try, log says:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error executing updater binary in zip '/sdcard/cm-11-20141101-NIGHTLY-v500.zip'
Error flashing zip /sdcard/cm-11-20141101-NIGHTLY-v500.zip
Updating partition details
I am truly desperate. I even fixed the name of my device in build.prop to v500 (before it was 'awifi' for some reason) but still no dice.
Please, is there someone to give me some clear instructions? Thanks a lot guys.
Click to expand...
Click to collapse
Have you tried with another build of CM11? Perhaps the latest milestone? Have you wipe:d all the data and cache and stuff? Can you tell me how you got the TWRP on there? Did it work the first time you flashed the 4.4.2 version? Where you on the latest version of android before rooting?

Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood

TF666 said:
Thanks for your effor, djmiek.
I managed to fix it yesterday. Nothing was out of ordinary - TWRP 2.8.0.0 (specifically for v500) was flashed using Flashify. Phone was rooted (see my original post) and I wiped everything properly before flashing CM11. However, for some reason there was no way to install nightly from 11/1. Everytime I tried to install, I got aforementioned error message.
So I got fed up with all that and just went and restored my whole tablet to a backup from april (50010b) which I very wisely did just after rooting the brand new device. This reverted TWRP to 2.6.3.2 and as soon as I booted recovery I could install that nightly without any hassle. No incompatible data, no bull like that - everything went smoothly. I don't know if there's a problem with TWRP 2.8.0.0 and current CM11 nightly combo but I sure as hell will stay away from it.
So, the moral of the story - BACKUP any working installation folks! Do not underestimate the power of word "restore". It feels goooood
Click to expand...
Click to collapse
Is 50010b also 4.4.2 or is it earlier? Did you just flash TWRP with flashify then after rooting?

I think it was 4.4.2.
My initial root after purchase was done according to http://www.youtube.com/watch?v=05T3mYVnYYE
Everything went smoothly then, but I think you'd achieve the same outcome using Flashify.

Warning: CM11 and 12 don't work with the latest versions of TWRP and Philz touch

EDIT: So it turns out the latest version of Philz touch actually does work, at least after reflashing stock.
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.

sorcererofdm said:
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
Click to expand...
Click to collapse
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.

sorcererofdm said:
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
Click to expand...
Click to collapse
Actually, I got CM12 working after flashing CM12 on top of CM11 restored from philz touch after flashing stock. So this is probably more properly called an "upgrade" from CM11 to CM12

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