I have a SM-T800, and I can't seem to get it to boot any custom rom, but it does restore my nandriod backup.
I'm using TWRP. I've tried various things like reformatting, the "quick wipe" option in TWRP, clear davlik/cache, but nothing seems to work. I get stuck at the " "Samsung Galaxy Tab S". Happened with 2 custom roms so far. Nothing during the TWRP install log looks abnormal.
thanks in advance.
Related
Hello,
I flashed my device (recovery only) with Odin, installing TWRP v2.6.3.0. The recovery works properly. After that, I did a complete wipe and I flashed my Galaxy Tab 3 10.1 WiFi with this ROM. Unfortunatelly it boots into recovery every time and I can't install any ROM on my device. Is there any way how to fix it, or am I completely lost? I've installed cynaogen mod in similar way on my I-9000 and everything worked fine, so this accident was a real surprise for me. Please, could anyone help?
Regards,
Max
redbull00 said:
Hello,
I flashed my device (recovery only) with Odin, installing TWRP v2.6.3.0. The recovery works properly. After that, I did a complete wipe and I flashed my Galaxy Tab 3 10.1 WiFi with this ROM. Unfortunatelly it boots into recovery every time and I can't install any ROM on my device. Is there any way how to fix it, or am I completely lost? I've installed cynaogen mod in similar way on my I-9000 and everything worked fine, so this accident was a real surprise for me. Please, could anyone help?
Regards,
Max
Click to expand...
Click to collapse
I am having the same problem with my G Tab 3 7 -ST217 from Sprint. I have root access. At first I could only reboot to recovery ONCE after Odin. Now I can consistently reboot to recovery. Every time I try to install anything from a zip in TWRP then reboot, it didn't install and instead restarts the factory android and goes through the first time startup and update cycle. Can't seem to get a ROM to stick.
When you do the ROM installation with TWRP, do you see a message after installation saying "unable to mount" or something similar? If so, the ROM was not installed and the device would either stop at the boot logo or restart to recovery. You might need to try flashing a different recovery.
Thats one theory. The other is that there was a problem with the ROM. Maybe corrupted during download or something of that sort. In which case re-download and if a md5 is there run the checksum and try again.
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovery and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is behaving this way?
Regards, heinzelrumpel
heinzelrumpel said:
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installaer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovrey and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is beahving this way?
Regards, heinzelrumpel
Click to expand...
Click to collapse
Change the recovery, often Philz 5.15 works best with Aroma installer.
Androidwizzard said:
Change the recovery, often Philz 5.15 works best with Aroma installer.
Click to expand...
Click to collapse
Unfortunately this does not do the trick Still stuck after reboot.
I can't tell you why its happening, but what I've done in the past to get around the issue is to flash a stock rom with Odin, then flash a new recovery before going to another custom rom. If you worry about the Knox warranty bit being set you'll have to find an old 4.1 image somewhere to flash. Since I'm past warranty I don't care anymore.
Good luck!
Wipe data cache dalvik format system etc nstall the new rom reboot and after go again to recovery and factory reset it.
Sent from my GT-N7100 using Tapatalk
I have a real frustrating problem with my Canadian Rogers Note 3. I'm rooted and running CM11, but I was looking for a ROM that might be more stable than the nightly builds. I wanted to try a TW-based ROM so I downloaded BobCat, JediElite, and FireNote ROMs.
I copied the ROMs to the SD card, booted into CWM Recovery and tried flashing one of them (don't remember which). The installation seemed to go fine, no error messages or warnings. But when I finished and rebooted the phone just stopped at the Note 3 boot screen. No boot animation, no loading, nothing.
I went back to CWM Recovery, tried the other two ROMs, and got the exact same results. Then I tried flashing the stock Rogers Note 3 ROM. CWM refused to flash it and spat out some garbage about a corrupt zip file (re-downloaded it with the same results). I eventually gave up and restored the CM11 image I'd backed up.
At this point I began to reason maybe CWM wasn't suited to installing TW ROMs, so I decided I needed TWRP instead. Goog.Im and TWRP manager both refused to install TWRP however. So I dropped the TWRP Recovery zip on my SD card and tried flashing it using CWM.
Here’s where it gets really freaky. When my phone rebooted I got a "recovery booting" message, but the recovery never loaded. The screen just froze at the Note 3 logo. If I pulled the battery the phone would again display "recovery booting" and sit there endlessly. The only way I could break the cycle was booting to Download Mode, then exiting so it enters a normal ROM boot.
I let the phone boot up fully and then opened ROM Manager. It showed TWO recoveries installed, one CWM and one TWRP, apparently side by side. Is this even possible???
So anyway, I went back to playing around between ROM Manger, Goo.Im, and TWRP Manger, trying to re-flash it to either CWM or TWRP, but not both. Nothing worked; every time I tried booting to recovery the system would hang at the “recovery booting” message.
I eventually tired of this and decided to get out Odin. I flashed TWRP Recovery successfully (according to Odin), but it still won’t launch. I then tried flashing CWM Recovery with the same results.
So completely out of options, I tried flashing the stock Samsung Recovery. It boots just fine. So I try again flashing the custom recoveries, but they still refuse to launch. Each time I have to reinstall Samsung Recovery.
And that’s where I am currently: I have a (badly) working CM11 nightly ROM on my phone. I have the stock Samsung Recovery installed. I’m afraid to try flashing any zips using Samsung Recovery because my backup image was created using CWM, and if I can’t get CWM recovery to work I won’t be able to restore the backup.
Have I broken some law of the universe by trying to go from CWM to TWRP? Would TWRP work better with TouchWiz ROMs? And can I even install TouchWiz ROMs after hacking my phone to CM11 nightlies? Lastly, how can I get this $#@& Samsung Recovery off my beautiful phone and install a working custom recovery?
Hi everyone
Sorry in case of repost.
I have a P5210 (Samsung Tab 3 Wifi). Once rooted everything was allright until I entered in recovery mode from the Rom Toolbox app.
I'm now stuck in a recovery loop mode and can't get out (CWM v6.0.4.7)
I've tried everything from factory reset / cache and dalvik cache wipe, to "fix" zips and so on. But nothing changes.
I've tried to reinstall CWM by putting a recovery image into a script and flash it through CWM. Seems to be done correctly, but when I reboot, it's still the same CWM (no update)
Eventually, i've tried to install some custom ROMs to start fresh : Every installation crashes at "WRITING SYSTEM PARTITION". I get black screen and a reboot.
And I've tried every custom Rom compatible with P5210.
Can you help me to get back to a clean configuration ?
N.
nicobee75 said:
Hi everyone
Sorry in case of repost.
I have a P5210 (Samsung Tab 3 Wifi). Once rooted everything was allright until I entered in recovery mode from the Rom Toolbox app.
I'm now stuck in a recovery loop mode and can't get out (CWM v6.0.4.7)
I've tried everything from factory reset / cache and dalvik cache wipe, to "fix" zips and so on. But nothing changes.
I've tried to reinstall CWM by putting a recovery image into a script and flash it through CWM. Seems to be done correctly, but when I reboot, it's still the same CWM (no update)
Eventually, i've tried to install some custom ROMs to start fresh : Every installation crashes at "WRITING SYSTEM PARTITION". I get black screen and a reboot.
And I've tried every custom Rom compatible with P5210.
Can you help me to get back to a clean configuration ?
N.
Click to expand...
Click to collapse
Hi
It seems you were on kitkat rom which may have updated your bootloader to kitkat version. The CWM needs to be updated to work well with kitkat. I had similar problem with my SM-T210, and solved the problem after updating CWM as per this post for T210:
http://forum.xda-developers.com/showthread.php?t=2433853
Your tab is different from mine so i think you need a fresh stock rom install using odin, then find an updated CWM for your tab.
Hi. I've installed in the past the Rocket Tab ROM.
Now I've made a full wipe, to install a new rom. I have the PhilZ recovery.
I can install the rom without a problem. But when I reboot the tab, it enters in the recovery mode again, and not in the new rom. I've tried many roms but no one works. It loads the recovery again and again.
Anyone knows what the problem is? I need the tab so much to read my books
Dulop said:
Hi. I've installed in the past the Rocket Tab ROM.
Now I've made a full wipe, to install a new rom. I have the PhilZ recovery.
I can install the rom without a problem. But when I reboot the tab, it enters in the recovery mode again, and not in the new rom. I've tried many roms but no one works. It loads the recovery again and again.
Anyone knows what the problem is? I need the tab so much to read my books
Click to expand...
Click to collapse
Try to reflash the recovery through the recovery, reboot recovery, wipe system and install Rom again. This should work but no guarantees.