Develop Bugs

Factory Reset after Restore with TWRP

Hello,
I was flashing the latest version of AOKP using TWRP, and the update failed. I verified the MD5 hash before attempting the flash, but figured I'd the file had gotten corrupt somehow. So I went to reboot my phone, and it hung on the boot loader screen. I Pulled the battery and tired again, but same result. So I booted back into TWRP, restored from the backup I took just prior to attempting the flash, and upon booting my phone went directly to the Setup Wizard. I rebooted, tried the restore again, but same result. I went through the wizard, and confirmed my phone had factory reset (Note, I didn't manually wipe anything).
Does anyone know what might cause this, and if I have any way to restore the backup I have? I was going from AOKP JB Builld 3 to 4, so I didn't take a Titanium Backup first. I've been using CWM since I got my GNex in January and have never had an issue (I've switched ROMs several times, and done many backup.restores with CWM. So i'd like to think I know what I'm doing ). This is the first time I've tried out TWRP, and everything seemed to go smoothly (Except for the failed flash).
Any help would be greatly appreciated. I've been searching around and haven't found anyone else reporting this.

Not sure why it factory reset but if you still have cwm back ups flash cwm and restore one of those. Factory reset isn't a bad thing though staying fresh is the best way to start a new ROM. I don't recommend restoring anything.
Sent from my Galaxy Nexus using xda premium

[Q] 4.3 roms will boot but wont reboot

I've tried most of the 4.3 ROMs available. Installed 100% clean with a factory reset and/or wipe system, data, cache & dalvik. After the initial boot if I try to reboot, the phone gets stuck on the first "note2" screen. 4.2.2 ROMs flash boot and reboot fine. I've tried a factory reset after flashing a 4.3 but it still gets stuck. I tried devil kernel... Stuck. I'm using the latest twerp recovery. Please tell me where I fail! Thanks

mrtoast said:
I've tried most of the 4.3 ROMs available. Installed 100% clean with a factory reset and/or wipe system, data, cache & dalvik. After the initial boot if I try to reboot, the phone gets stuck on the first "note2" screen. 4.2.2 ROMs flash boot and reboot fine. I've tried a factory reset after flashing a 4.3 but it still gets stuck. I tried devil kernel... Stuck. I'm using the latest twerp recovery. Please tell me where I fail! Thanks
Click to expand...
Click to collapse
Sorry I made a duplicate thread. I think I've tried more trouble shooting than the other thread. Its your call moderator.

mrtoast said:
Sorry I made a duplicate thread. I think I've tried more trouble shooting than the other thread. Its your call moderator.
Click to expand...
Click to collapse
Maybe try flashing just the rom without any gapps. see if it'll boot for you after a couple reboots. also when u download the files check them again their MD5's so you can confirm that you have a good download.

Clockwordmod superuser app was the key! After the first boot, I ran the app and even though it always wanted to be updated (even after it went through its process) 4.3 ROMs would reboot! I tried probam and pacrom. Each time I flashed new, I had to re update the su or else no reboot. Thanks for your help!

[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] make_extf4fs error

Hello XDA-san,
i've been in a battle of wits with this damn phone the whole evening..
it is a i747m, on 4.3 with Bell
this is what happened:
i flashed a stock, pre rooted firmware (stock) from here
I went into the stock recovery, did a factory reset, wipe cache and got the following error (pic attached)
now every time i boot it i does not get back the sammie logo..
i tried flashing twrp, cwm, flashing a custom rom, getting it back to stock stock, then pre-rooted stock.. nothing..
also, when i try to wip data from any custom recovery it says cannot mount data..
anyway.. this is the situation.. im afraid the internal storage might be corrupt or something.. so if you have insight on this, please do share xda-san
ty

forgot to attach pic

update on my little misadventure above..
i ended up doing a complete wipe via the twrp format data menu in which you need to type in the word 'yes', then reflashed the pre-rooted, de-knoxed stock rom mentioned above.
finally for the #$^#$^ thing to boot properly.
mods, if need be, please close this thread, apologies for my neuroticism

[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.