I flashed CWM 6.0.3.1 with SIII Toolkit, and now after trying to apply the latest cm10.1 nightly the phone indicates it is rebooting into recovery with the little blue text at the top left, but then black screens until i remove the battery or reboot into ODIN mode. Is there any way to fix this through ODIN mode or Recovery reboot?
Edit: I got the OS rebooted properly and after fiddling with the Toolkit with the proper img file, ODIN still crashed on flashing the tar I compiled, so I forked out the $2 for ROM manager to do it for me and everything seems to be fixed.
Related
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?
What I was trying to do: I have a stock 4.4.2 AT&T GS3 that I wanted to root, and then install Cyanogen Mod.
What I did: I flashed Auto-Root with Odin 3.10, restarted and then flashed TWRP 2.8. I then booted to TWRP and attempted to wipe/format the phone but it showed some errors along the way, I think it was something having to do being unable to mount the SD card. I then rebooted into recovery and flashed CM12 and slim Google Apps zip. When it was flashing both I got a string of errors but it said it was successful.
Where I'm at now: When I try turning the phone on (without holding any buttons down) it attempts to boot straight to the TWRP but gets stuck at the blue TeamWin screen. I'm able to get to download mode by holding down the appropriate buttons. I'm wondering if there's anything I can flash from Odin to resolve this.
I also realized I have unbacked up photos on the device, I don't think the format was successful, is there any way to recover those?
Thanks
To recover the pictures, try re-installing TWRP, boot into TWRP, and mount the partitions. Connect the phone to your computer and copy your pictures.
TWRP
I have had this happen before. Try using Odin to flash an older version of TWRP, uncheck reboot after flash and then when it is done, do a battery pull. This has gotten me back into a working TWRP to restore my previous setup. Note: You made need to go back to 2.6. Once you have gotten back up and running flash to the current TWRP with the app.
my tmob s4 is stuck on boot screen i tried to update twrp from twrp manager and it said unsuccessful and ask to reboot into recovery i said yes and it rebooted and now when it goes to boot screen and says on top in little blue words botting recovery it just stays there what can i do?
i tried battery pull and Manually going into recovery nothing seems to work plz help.
UPDATE: odin latest firmware NK2 working great!
The lateat version of twrp is borked. Its what caused your problem.
Any previous version will work fine
I was trying to root my device and was following a guide which instructed to flash TWRP, then rooting kernel and finally a ROM of my choice. After using Odin to flash TWRP the phone booted to the TWRP menu on which I chose to reboot the system and the phone got stuck on the black welcome to galaxy screen and it just kept on flashing that screen. I was able to boot to the load screen by holding power, home, volume up key and using Odin to flash the original image file.
Question is am I following the correct order to root this thing and if I am what could have gone wrong?
re: booting issues
SterlingMace said:
I was trying to root my device and was following a guide which instructed to flash TWRP, then rooting kernel and finally a ROM of my choice. After using Odin to flash TWRP the phone booted to the TWRP menu on which I chose to reboot the system and the phone got stuck on the black welcome to galaxy screen and it just kept on flashing that screen. I was able to boot to the load screen by holding power, home, volume up key and using Odin to flash the original image file.
Question is am I following the correct order to root this thing and if I am what could have gone wrong?
Click to expand...
Click to collapse
After the phone rebooted to the TWRP recovery you should have flashed the rooting kernel before rebooting
the phone in twrp. You need to go back into twrp recovery (you will need to odin flash twrp again).
Here is the xda link for Jovy23's stock rooted G928T kernel: (flash this in twrp recovery)
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3229557
If you flash the wrong kernel the phone will be in a constant bootloop and or it will get stuck on the logo screen.
Good luck,
Have a Happy New Years.
Ok guys im in some really deap ****. This is what happend
I was trying to flash my SGH-T999 with cm-2xxxxxxNIGHTLY-d2lte to get the 4.4.4kitkat upgrade. Rooting with clockworkmod using Odin V1.85 was succesfull. I got into recovery mode, wiped data factory, /cache, and /delvik cache/ and i went on to install zip from sdcard. The installation failed, tried severals times and it still fails. And when i try switching it on, it boots with the SAMSUNG Logo and goes back off, then comes back on again with a "Recovery Booting" written on the top left hand corner of the screen, and then it boots into recovery mode. When i hit Reboot System, it does same thing. I have tried downloading the recovery but my SD-Card slot seems to be damage of which the recovery needs to be put on, and more so i cant detect if the memory card i install is ready or not.
Flash twrp to the phone. Cwm has not been updated for a while.
A few months ago I flashed TWRP 2.8.7.0 using Heimdall just fine, no problems. Now I've been trying to flash the latest TWRP 3.0.2, I can't seem to get it to boot, the flash is successful. Then I reflash the older version, and it's not booting into recovery. I'm not too familiar with Samsung phones, but I've been doing this for a long time on my Moto X 2014 using ADB/Fastboot, without issues.
I was able to return to stock firmware using Odin.