Develop Bugs

[SOLVED] Unable to install custom rom after modem upgrade

Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!

Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.

Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!

acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!

I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D

Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk

It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D

wipe Dalvik and Cache before trying the rom again. If

[Q] "gapps stopped" loop after CWM restore

Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );

if you can still get to recovery, download latest gapps and flash that

Did you factory reset before or after you restored your back up?

Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:

Try to factory reset again

vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!

I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.

Reboot after booting to recovery

I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".

OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...

So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it

OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.

OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.

mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.

OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.

BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.

Issues flashing ROM

I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue

Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?

audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...

I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...

Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?

audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.

It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.

Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!

Flashing roms doesn't go past flashing "system"

Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?

I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe.
Click to expand...
Click to collapse
That's fine, you need to wipe system to flash a new ROM.
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Click to expand...
Click to collapse
How long does it stay stuck? Most ROMs take a lot of time in flashing system because it involves unpacking and flashing firmware. Depends on the installer, really.
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
Click to expand...
Click to collapse
Can you remember if you also selected System partition when making backups? If you did, try restoring after wiping System, data and cache.

mharis05 said:
That's fine, you need to wipe system to flash a new ROM.
Click to expand...
Click to collapse
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7

Simone98RC said:
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Click to expand...
Click to collapse
That is wrong in any form. There is no rom that needs oos system to be present before flashing. And its not recommended to (dirty flash over a stock rom when switching to a custom rom)
---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------
android_fury said:
Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
Click to expand...
Click to collapse
Did you allow modifications in twrp ? Try to mount system in recovery before flashing / restoring

I ended up fixing it. I went to TWRP to do a regular wipe and saw the option to format partitions. I formatted system and it allowed me to reinstall roms. I flashed CM13 and CM14 with no issues. Thank you all for the suggestions.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app