I have a GTN-7100 which has CWM 6.0.4.3 and previously had a rooted stock ROM. I am trying to install CM11. I have downloaded a snapshot of t0lte and copied it to the external SD card. I have wiped data/cache using CWM and installed the zip file via CWM. The installer process doesn't report any errors. When I reboot the phone gets stuck on the logo screen.
I have tried downloading a more recent nightly and also repeated the process and installed gapps via CWM. The MD5 sums of the downloaded files are correct. However, the phone always gets stuck on the logo screen. I have left it for up to four hours, just in case it was taking a long time to start.
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.
NOOB ALERT!
I have a samsung sgh-i747 that is still tied to the AT&T network, although, I do not have a SIM or service anymore. (is not being unlocked my issue?) I have been trying install Cyanogen 11 and 10.1. I currently have TWRP recovery, and the phone is definitely rooted. I have followed multiple guides to install a custom OS and nothing has worked. When trying the first time, I get the status 7 error, then I remove the assert check from the script and it still fails. It will sometimes just fail right after it skips the md5 check and not even return an error. What could I be doing wrong?
Possibly relevant info:
- I have CWM recovery that I installed TWRP over(may not be an issue, idk)
- I have tried installing .zip from sdcard and sideloading.
- phone is on stock 4.4.2
- I factory reset and wipe cache and dalvik cache before trying to install ROM.
- I have tried installing on TWRP and CWM.
Any suggestions would be great. I am new to the whole rooting and flashing thing, so I wanna get this done because I am slowly becoming obsessed.
Thanks guys!
Download the latest tar.md5 version of Philz Touch recovery from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download the latest cm11 for the d2lte from here: https://download.cyanogenmod.org/?device=d2lte. Save cm11 to an external SD card.
Download the Gapps from here: http://wiki.cyanogenmod.org/w/Google_Apps. Save the Gapps file to the external SD card. Place the SD card into the phone.
Boot the phone into download mode, uncheck everything in Odin except f.reset time. Connect the phone and flash Philz. When you see the word "reset" in the status window, remove the USB cable, remove the battery, replace the battery, boot into recovery, wipe data, cache, system, and Dalvik. Flash CM11, flash Gapps, boot phone.
Thank you so much. That worked first try. so was it just that I did not have updated recovery?
Yes, status 7 errors are often due to an outdated recovery.
Glad it worked.
Hey guys,
I just flashed the recovery via odin on my GT-I9195 and installed the latest release from cyanogenmod.org It worked fine, the phone started normally. But when i tried to restart the phone it was stuck on the samsung screen, saying "set warranty bit kernel". I tried to install the ROM again doing factory resets and so on but whenever I start the installation the screen goes black for a second or so and jumps back to the main menu of the recovery... I also tried the cwm-recovery which gives the same result. screen goes black and jumps back into recovery.
Anyone got a solution?
Recovery used:
openrecovery-twrp-3.0.2-1-serranoltexx-STABLE-signed.zip
CyanogenMod:
cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx.zip (snapshot)
jacob00 said:
Hey guys,
I just flashed the recovery via odin on my GT-I9195 and installed the latest release from cyanogenmod.org It worked fine, the phone started normally. But when i tried to restart the phone it was stuck on the samsung screen, saying "set warranty bit kernel". I tried to install the ROM again doing factory resets and so on but whenever I start the installation the screen goes black for a second or so and jumps back to the main menu of the recovery... I also tried the cwm-recovery which gives the same result. screen goes black and jumps back into recovery.
Anyone got a solution?
Recovery used:
openrecovery-twrp-3.0.2-1-serranoltexx-STABLE-signed.zip
CyanogenMod:
cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx.zip (snapshot)
Click to expand...
Click to collapse
Have you install "Gapps" after flashing CM13?
If you backup you custom rom than try fresh installation: copy CM13 & Gapps to Ext SD Card, Wipe everything (Dav cache, Cache, Data, Perload, Internal Storage) Dont wipe your Ext SD Card.
Than flash CM13 & Gapps after flash simply reboot. Don't wipe anything, Don't factory reset.
Hope it could be worked...
Try to go back to stock rom. Hope your phone revives.
Was trying to update the supersu binary by installing the updated zip in recovery. On reboot it was stuck in a boot loop. First off nothing else worked, then fastboot worked and then 10 mins later twrp recovery started working. I tried to restore a backed up image but still got boot loop. Then tried to flash a rom I had on sdcard - still boot loopy. Tried to go the miflash tool root but couldn't get it to find the phone despite it appearing in explorer. Copied stock miui zip onto sc card from pc and installed but still same problem. Standard dalvik/cache wipe before and after each install. Now I'm struggling to get recovery up.
Help - haven't managed to totally brick something despite many years of tinkering. :/
PS. I can still get fastboot up. Now when I try to get recovery up the screen goes black and I have to reboot.