To avoid a novel, I'll just the list the steps I did. I had an ancient version of clockwork and paranoid android rom on my N7, not sure what version and I wanted to get Cyanogenmod 10.2.1 on there along with TWRP.
1. Downloaded TWRP from playstore, installed under paranoid rom, also downloaded CM on SD
2. Used TWRP under paranoid rom to install CM and Gapps
3. TWRP rebooted N7, old version of clockwork showed up instead of TWRP
4. Flashed CM, it worked
5. Installed RomManager, updated to newest stable CM update, installed it, rebooted
6. Once rebooted, playstore and rom manager crashes all the time
7. Hold down Vol Down while booting brought me to fastboot
8. If I select recovery mode, it gets stuck on google screen
9. Tried to push latest CWM via fastboot, it says it pushed it, but I'm still stuck on google screen. It does get back in to the OS still, but playstore crashes.
I don't care if I have to install CWM or TWRP, I just want to get it out of this state. Any ideas?
Nevermind all that, pushed TWRP instead of CMW via fastboot and it worked.
Related
I have an Acer A500, it has the v9 bootloader installed. I also have TWRP 2.6.3 installed as the secondary ROM, the recovery is also completely broken, fastboot and zip will not install on it (TWRP 2.6 is to big), but recovery using 2.4.4.0 does boot. That fine since with secondary and recovery installed I can use TWRP from either, which works great, but if I install a ROM it only boots once, then poof, its as if there is no kernel it will not boot. To boot a new ROM I have to format everything except the external SD (which I have removed) then install the ROM reboot to TWRP install it again, then reboot at which time it will boot about 1 is 3 times, if it fails try again and repeat.
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP, I've tried 2 4.0.3 ROMs but I can not get the Installers to run, I've tried 2 10.1 ROMS boot both booted only once and also a 4.3 ROM (build 5 and 6) boot again both booted only once. I'm out of ideas I'd flash almost anything at this point to reset, but then there is that Windows 8.1 issue in which I can not get ACER driver to work (Duh!), and I do not think the issue is going to be fixed, I can only come up with 2 options 1 the internal storage is going bad, or the entire setup is just toast, since it can work, it just does not do so more than once.
Currently I have 10.2 (build6) running, so long as I do not need to reboot, so for now it is charging.
Any suggestions,
ERIC
egandt said:
Now the ACER is basically useless now as I can not boot safely to anything other than TWRP
ERIC
Click to expand...
Click to collapse
I have same problem with TWRP. Try to replace TWRP with TouchRecovery
I got bored today and decided to pull out the old N7, 2012 version. I update recovery to TWRP 2.8.7.0, installed CM 12.1, realized this tablet crawls with any version of Android other than shipped version, so I went and got CM 10 and GApps for JB, wiped and flashed them back on. I didn't see any errors when flashing them, but when rebooting after, it just boot loops. I see the Google logo with the unlocked icon at bottom, then reboot and back to Google/unlocked again. So I wipe and reflash cm12.1 and it's GApps and all boots and works fine, other than being slow. I'm assuming the recovery is the problem as I've run into something similar before on another device, but in that case, the recovery was too old and needed updated, but it makes sense that a recovery could be too new as well.
Am I correct that the recovery is the problem? If so, what should I run for CM 10 to flash and work?
Try cwm recovery
iwjosi said:
Try cwm recovery
Click to expand...
Click to collapse
I don't' know if it was using CWM or that I also tried CM 10.2 at the same time, but it's working now. On CyanogenMod's own page, there was no MD5 for CM10, but there was for CM10.2, so it's possible my copy of CM10 was a bad download. Either way, it's working now, so thank you good sir, or madam, or person on no specific gender.
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
I just installed Lineage OS and it works fine. Problem is there is no Google apps play store so I need to get Gapps
But in order to get Gapps flashed I need to reboot into custom recovery like CWM or TWRP.
I couldn't figure out how to install CWM or TWRP at the first place so kinda ignore it thinking nothing will happen.
https://forum.xda-developers.com/showthread.php?t=3651542
I flashed LineAge OS with TWRP app downloaded from Play Store, the phone prior to bootloop was rooted.
I used odin on my PC to flash to stock rom and it just gives me bootloop, the samsung logo just fades in and out like on a bootloop
Samsung G903W is the model number
hi did you get it to work?
So i might have ****ed up
I have a Xiaomi MI9 that im not particulary impressed with the miui interface so i figured, lets install a custom OS. That ended up with a device that wont boot to paranoid android, instead sends me to fastboot menu no access to TWRP. This is what i have done:
1. got access to bootloader through xiami webpage
2. Installed twrp
3. through twrp Installed Paranoid android (PA)
4. through twrp installed Gapps
5. rebooted, phone stuck and eventually got into twrp again
6. tried again, same results
7. This is where i think i ****edup, i wiped cache, data, dalvík and system
8. reinstalled PA and gapps
9. now it only boots to fastboot.
Question 1, what did i miss, why didnt it boot paranoid android?
Question 2, can i just re-do the process and install them again (given i didnt miss anything first time)
Question 3, i assumed i didnt have to root it as i was installing custom rom anyway, was that assumption correct?
MormorBoston said:
So i might have ****ed up
I have a Xiaomi MI9 that im not particulary impressed with the miui interface so i figured, lets install a custom OS. That ended up with a device that wont boot to paranoid android, instead sends me to fastboot menu no access to TWRP. This is what i have done:
1. got access to bootloader through xiami webpage
2. Installed twrp
3. through twrp Installed Paranoid android (PA)
4. through twrp installed Gapps
5. rebooted, phone stuck and eventually got into twrp again
6. tried again, same results
7. This is where i think i ****edup, i wiped cache, data, dalvík and system
8. reinstalled PA and gapps
9. now it only boots to fastboot.
Question 1, what did i miss, why didnt it boot paranoid android?
Question 2, can i just re-do the process and install them again (given i didnt miss anything first time)
Question 3, i assumed i didnt have to root it as i was installing custom rom anyway, was that assumption correct?
Click to expand...
Click to collapse
me too, it only boots to fastboot.
Try to format /data
format data,then restart