Issue flashing roms, reseting - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

I have been having a weird issue. Whenever I flash a rom and it completes, I will reset like normal but it wont boot. It will vibrate twice after the note 4 screen and loop. I have a stock nandroid backup I have reverted back to. Its more annoying then anything trying to figure out whats going on. Any ideas?

What recovery?

TWRP

Flash a stock ROM tar and then do a factory reset in stock recovery. Then reflash twrp and try again.

Related

[Q] Flashed Rom Hangs

So I flashed a new rom, did the usual, clear everything, reset/cache/dalvik and flashed the rom. However, when I rebooted the trinity logo/initial startup just stays on that screen forever. I tried reflashing from recovery and it still hangs forever on that screen. Do I have to go thru download mode/odin and get stock/root to be able to flash again or is there a quicker easier way?
Have you tried to restore a nand backup?
Try a factory reset after you flash the new rom.
Aerowinder said:
Try a factory reset after you flash the new rom.
Click to expand...
Click to collapse
I tried the reset after flash... and I never do NAND backups T_T. But I never do anything that could ruin it. I just thought there would be a quicker way instead of a compete reset to stock. But o wells, now I can set the flash counter back to 0 and not trip it anymore.

[Q] Stuck after ROM flash

I have the Sprint S3 with 4.1.2. Last night I rooted it and it worked fine. I then flashed CWM Recovery and rebooted, all was fine. Tried to put on Liquid Smooth rom and didn't have gapps, attempted to flash gapps but came up with error. Got fed up with it and tried to flash the Synergy Rom. I cleared dalvik and cache, made a backup and flashed. Went through the whole process and auto rebooted afterwards. Went to SAMSUNG on boot and screen went black before finishing and will not go further. I can get into stock recovery but not CWM Recovery. I'd like to have the liquidsmooth rom on there but i also downloaded the stock 4.1.2 rom just in case. How can I get past this to get into either CWM recovery or somehow flash a rom from Odin? I'm stuck.
jsaye2002 said:
I have the Sprint S3 with 4.1.2. Last night I rooted it and it worked fine. I then flashed CWM Recovery and rebooted, all was fine. Tried to put on Liquid Smooth rom and didn't have gapps, attempted to flash gapps but came up with error. Got fed up with it and tried to flash the Synergy Rom. I cleared dalvik and cache, made a backup and flashed. Went through the whole process and auto rebooted afterwards. Went to SAMSUNG on boot and screen went black before finishing and will not go further. I can get into stock recovery but not CWM Recovery. I'd like to have the liquidsmooth rom on there but i also downloaded the stock 4.1.2 rom just in case. How can I get past this to get into either CWM recovery or somehow flash a rom from Odin? I'm stuck.
Click to expand...
Click to collapse
So you were able to get into the custom recovery (CWM) a couple of times before flashing Synergy Rom, but now it's reverted to stock recovery? When you turn your phone off and hold Volume up, menu, and power it boots into the stock recovery? I've never heard of that happening before.
The best way is to re-do your root process through Odin a-la qbking77's tutorial. This will install CWM again and then you can flash away. Make sure you check your md5sums on the Rom files you downloaded before flashing them. That's the most common cause of bad flashes around these parts.
topherk said:
So you were able to get into the custom recovery (CWM) a couple of times before flashing Synergy Rom, but now it's reverted to stock recovery? When you turn your phone off and hold Volume up, menu, and power it boots into the stock recovery? I've never heard of that happening before.
The best way is to re-do your root process through Odin a-la qbking77's tutorial. This will install CWM again and then you can flash away. Make sure you check your md5sums on the Rom files you downloaded before flashing them. That's the most common cause of bad flashes around these parts.
Click to expand...
Click to collapse
I've ended up fixing it but had to flash stock 4.1.1 on it from Odin and then it automatically went to 4.1.2 after reboot. Thanks
But yes, it was going to CWM just fine before I flashed Synergy after Liquidsmooth. Thats how I put on Synergy. But at least it was just a soft-brick.
Did you wipe (everything) between flashes? Even roms of the same version can have issues if you flash one over the other
By everything I mean /system, /data (factory reset), dalvik cache, and cache

Having trouble flashing ROMs

I've got the intergalactic ROM installed on my S3 and I've had it for a while. I want to change ROMs but every time I flash a new one it flashes fine but when the phone boots up it tells me the setup wizard failed and a bunch of other stuff stopped working. any ideas on what it could be?
I'm using CWM.
Also if I just wanted to wipe everything on my phone and go back to stock so that I can re root it and try flashing roms then how would I do that?
You probably just need to factory reset. If you wanted to go back to stock rooted, flash the root66 firmware via odin then boot recovery and factory reset. Note that factory reset from stock recovery will wipe internal sd. From cwm/twrp it will leave internal sd alone unless you "format data".
Sent from my SM-N900T using Tapatalk

HELP!!! Need a PIT file for N4

Some how I have screwed up my partitions. I was able to Odin to stock lollipop and I can get into download and recovery. However I cannot flash anything at all at this point. In TWRP when I try to flash a custom ROM, Kernel or even the lastest TWRP version, all that happens is recovery restarts. This all started when I tried to flash SlimLP ROM. It flashed fine but would only bootloop when I tried to start phone. So I wiped everything and reflashed lollipop AllianceROM. The phone started okay but I got some error message about the UID. I noticed right away that ALL my text messages which should have been wiped were intact. The phone was running really, really slow and I had continual issues installing apps from the Playstore and TiBu. I decided to try another ROM and again wiped everything, flashed and rebooted. Again text messages were intact. I believe it's my system and/or data partition that is messed up but I am not sure. I'm not knowledgable about any of this so I really need some help here.
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
tx_dbs_tx said:
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
Click to expand...
Click to collapse
samep said:
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
Click to expand...
Click to collapse
Thank you both. I did just what you guys suggested and it worked out! Thank you again!

Boot loop after updating rom

So I've been using this phone for a few months and love it. The only issue I have is that when I update a ROM, regardless of which one it is, it bootloops and I have to start fresh.
What happens is that the phone works, I make a nandroid backup, flash rom, gapps, and magisk. When I reboot, it stays on the MI logo and reboots to recovery. The only way to fix it is by using FORMAT DATA, which wipes the phone clean and boots to the last rom that was flashed with it.
Thinking it was an issue with the ROM (crDroid), I reflashed it with Nusantara and it booted just fine. When I went back into recovery, to restore data and apps, it went smooth until reboot. After reboot, it sticks on MI logo and reboots into recovery.
Something in my DATA is causing a recovery bootloop. Has anyone else experienced this? This makes me not want to update my ROM if I have to painstakingly restore apps, from nandroid backup, using the outdated TitaniumBackup.
What am I doing wrong here?
Is there a better way to restore data from the nandroid backup?

Categories

Resources