What fixed it for me:
I had made a backup through TWRP 2.6.3.0, but then upgraded to 2.3.6.1 after. Not sure why it didn't work on 3.1, I flashed back to 2.6.3.0, flashed my backup, and everything works again.
So, I've been having one hell of a battle trying to get MJ9 and ROMs based off it to work in the last couple days. In the end, I have decided to go back to my Liquid ROM that I have a backup of yesterday morning in TWRP. This backup, until now, has served me well and has gotten my phone back to how it was.
Until now.
I wiped everything through TWRP and tried to recover my ROM image... Now when I boot, it's stuck at Samsung Galaxy Note 2 screen, and stays there indefinitely. I can boot to recovery if I pull the battery. How does this happen? I was recovering back to this backup just fine until now.
I've deleted system/cache/internal storage, flashed, then deleted cache, no luck.
I flashed Beans stock deodexed 4.3 image. That booted ok, but when I go back to recovery, my Liquid backup still will just hang at the Note 2 screen.
What can I do from here to get it working? Do I need to ODIN a pit file? I'm at a loss.
Related
I have S-off Hboot 1.4
Was running Cleanrom 1.1 reborn. & Twrp
Flashed over to CM9 Nightly, worked fine.
Decided I wanted to go back to a sense ics rom, so I flashed the latest ICS meanrom.
Phone went into bootloop
Went back into recovery, flashed superwipe, then did factory reset/wipe cache
Flashed ICS Meanrom again, still boot loop.
Restored TWRP backup I have of stock rom, booted fine.
Tried flashing Cleanrom 1.1 reborn, went into boot loop.
Restored my stock rom, booted fine again.
Changed recovery to Ext4... didn't make a backup in ext 4.
Tried flashing both Cleanrom GB, Meanrom, sends me to boot loop on both.
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
http://forum.xda-developers.com/showthread.php?p=26381636#post26381636
j4keg said:
I have S-off Hboot 1.4
Was running Cleanrom 1.1 reborn. & Twrp
Flashed over to CM9 Nightly, worked fine.
Decided I wanted to go back to a sense ics rom, so I flashed the latest ICS meanrom.
Phone went into bootloop
Went back into recovery, flashed superwipe, then did factory reset/wipe cache
Flashed ICS Meanrom again, still boot loop.
Restored TWRP backup I have of stock rom, booted fine.
Tried flashing Cleanrom 1.1 reborn, went into boot loop.
Restored my stock rom, booted fine again.
Changed recovery to Ext4... didn't make a backup in ext 4.
Tried flashing both Cleanrom GB, Meanrom, sends me to boot loop on both.
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
Click to expand...
Click to collapse
maybe Cleanrom 1.1 isnt good......
j4keg said:
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
Click to expand...
Click to collapse
Not that this solves your problem, but you could switch back to twrp to use your nandroid backup.
Sent from my PG86100
coal686 said:
Not that this solves your problem, but you could switch back to twrp to use your nandroid backup.
Sent from my PG86100
Click to expand...
Click to collapse
Sorry took so long to follow up.
Later on that day, I realized that my phone wasn't accepting the flash of zipped files. It go through the flashing process in like 5 seconds.
I did switch over to ext4, this was causing the same problem.
Couldn't boot into any rom, so I had to use fastboot and adb to send twrp to the phone. Finally restored my stock rom and was able to flash fine since.
j4keg said:
Sorry took so long to follow up.
Later on that day, I realized that my phone wasn't accepting the flash of zipped files. It go through the flashing process in like 5 seconds.
I did switch over to ext4, this was causing the same problem.
Couldn't boot into any rom, so I had to use fastboot and adb to send twrp to the phone. Finally restored my stock rom and was able to flash fine since.
Click to expand...
Click to collapse
Glad to hear it. Thanks for the followup.
So up until today I was running this rom: http://forum.xda-developers.com/showthread.php?t=1912596
It was getting really buggy, so I decided to update to the latest CM10.1 nightly. I updated safestrap to the latest version, and I saw that on the changelog for the CM nightlies that the rom could be installed on any slot. For some reason, there was no rom slot 1, even though that's what I had the current rom installed on. I made a backup of the stock rom slot, wiped system/cache/factory reset, and installed CM 10.1 on the stock slot. That didn't boot up. So I tried to restore my backup. My backup of my current rom didn't show up, but the initial stock rom backup that I made when I first rooted the phone showed up, so i wiped everything again and tried to boot from that. On that, the boot animation showed up and went through, but it sat there for a few minutes without booting, so I did a hard reset and went back into recovery. I then made a romslot-1, wiped for precaution, then tried to install the cm nightly. The install went fine, but when I try to boot, the phone just vibrates initially like it's going to boot up, but there is no boot animation or anything on the screen, and it just sits there. Is there anything I can do to get this thing up and running again? I am not at the least opposed to returning it to stock, but I'm not sure if I need to restore to stock ICS or JB, since I'm pretty sure the rom I had running was using the ICS kernel. Here's the link to the rom I just tried to install: http://forum.xda-developers.com/showthread.php?p=39330661&highlight=boot#post39330661
Any help on the matter would be greatly appreciated.
I have an MDK S4 with TWRP 2.6.3.1 and I have been flashing CM-11 nightlies about every week. Currently I'm on the 12/25 KK build and its working fine but I decided to update anyway. I made a backup and then proceeded to flash the 1/1/14 build however my S4 wouldnt go past the Samsung custom screen. I restored my backup and it worked fine. I proceded to flash a stock based ROM wiping everything and still it would not go past the Samsung Custom Boot screen. The only thing that works now is the build I have backed up nothing else boots. I have wiped data and evened ODIN'ed back to 4.2 MDK and rerooted and re TWRP'd and still I cant flash anything besides the one kitkat build I have backed up, any other ROMS dont go past the initial screen it just vibrates and shuts off and loads TWRP again. Any suggestions of what I can do to fix this?
Thanks in advance
I've done everything: cleared all data, tried to restore backups, do a full charge, nothing's working.
I upgraded to 4.4.4 Liquidsmooth, but I decided to restore (with clockworkmod) back to 4.3.
I got the infamous MD5 Mismatch error, so I recreated the nandroid.md5 file, and I successfully booted back into 4.3.
Now 4.3 kept giving me errors so I turned it off and tried to restore BACK to a backup I had once I upgraded to 4.4.4, and nothing happened.
Now I'm in limbo: the phone crashes on the boot screen, and if i restore either the 4.3 or 4.4.4 backup, clockworkmod just crashes while restoring.
At this point I'd be fine with deleting EVERYTHING and starting with a fresh phone, but I don't even know how to do that...
Help would be MUCH appreciated, thanks.
Follow the guide in general forum sticky on how to wipe and flash a stick firmware with Odin. Make sure you factory reset after flashing.
Alright, I know enough to be dangerous. I rooted my Samsung tab a 10.1 by installing twrp and then super su, all went fine. I then began to try and make a nandroid back up. It kept saying unable to mouth data, so I read a little and I changed data format. This caused a boot loop. Went in and changed back data format and used twrp to reset. All was fine again. I then attempted to use titanium backup. I recited a message backup was successful and reboot. I rebooted and now a boot loop. I then tried to reset with twrp and my file is gone. So, I downloaded what I thought was the right firmware to flash with Odin but just made that worse. Does anyone have a download for a rom I can flash with Odin to get this thing going. I have downloaded a couple and the either don't work or are the wrong one. SM-T580.
tlstaggs said:
Alright, I know enough to be dangerous. I rooted my Samsung tab a 10.1 by installing twrp and then super su, all went fine. I then began to try and make a nandroid back up. It kept saying unable to mouth data, so I read a little and I changed data format. This caused a boot loop. Went in and changed back data format and used twrp to reset. All was fine again. I then attempted to use titanium backup. I recited a message backup was successful and reboot. I rebooted and now a boot loop. I then tried to reset with twrp and my file is gone. So, I downloaded what I thought was the right firmware to flash with Odin but just made that worse. Does anyone have a download for a rom I can flash with Odin to get this thing going. I have downloaded a couple and the either don't work or are the wrong one. SM-T580.
Click to expand...
Click to collapse
Alright, I was using an olsee version of odin, got the new one and I was able to flash a rom. It says tab a 6 on boot up bit it is functional. Now my question? Can anyone recommend a custom rom that is nebiew friendly. I'm food at following directions and problem solving but I about had a panic attack, I just got this $300 thing. Sigh off relief for at least getting it functional again.
Hmm
Ok so I have flashed a stock rom, 6.0.1, flashed TWRP, and installed SuperSU. all is working well again. However I am still getting "unable to mount data" message in TWRP when i try to make a backup. If i uncheck data on the list it backs up fine. This is what got me in that boot loop pickle before when i tried to change the data format. What data format? Idk, im scared to jack with it anymore, and im done with titanium backup, it has burned me in the past, though i think what went wrong there was when i backed everything up i then went and change data format and after all that restored and the backup was in a different data format. Idk newbie guess. I am just trying to getting a reliable nandroid backup. Anymore ideas? Perhaps i should just leave it alone and be happy with just having root.