Related
Just created the new thread so that the url does not get lost in the android 2.3.2 thread with all the comments.
Hope the devs can tell us what's its all about.
http://android.clients.google.com/p...cd.signed-soju-GRH78C-from-GRH78.353e2673.zip
Update: Rooting is not affected and can be achieved following instructions from this thread for e.g
http://forum.xda-developers.com/showthread.php?t=895545
Those having stock ROM, with clockwork recovery, follow this excellent guide thanks to distortedloop.
http://forum.xda-developers.com/showpost.php?p=10811723&postcount=29
those having stock recovery, to update:-
-Download the OTA package here
-Rename it to update.zip, and place it on the root of your internal storage
-Shut down your phone, and reboot into the bootloader by holding volume up and powering on
-Choose "recovery" from the list, and select it with the power button
When you see the red triangle press volume up and choose to update
deeren said:
Just created the new thread so that the url does not get lost in the android 2.3.2 thread with all the comments.
Hope the devs can tell us what's its all about.
http://android.clients.google.com/p...cd.signed-soju-GRH78C-from-GRH78.353e2673.zip
Click to expand...
Click to collapse
Nice thanks
thanks!
10 characters
root work after update to 2.3.2 ?
i didnt update it though. I was waiting to see if a dev could enlighten us but nevermind ) i'll try to update and try to root n let u know.
cross fingers.
Thanks. Works fine on non-rooted Nexus S.
Sent from my Nexus S using XDA App
deeren said:
Just created the new thread so that the url does not get lost in the android 2.3.2 thread with all the comments.
Hope the devs can tell us what's its all about.
http://android.clients.google.com/p...cd.signed-soju-GRH78C-from-GRH78.353e2673.zip
Click to expand...
Click to collapse
I posted it over on the other thread just for those following it, gave credit to you.
This one patches everything in the /system/app folder, the /system/frame-works, and a few random files in other sub-dirs.
It also replaces/patches the recovery again and includes the script to re-flash it every time you change it.
Here's the patch script
Just rooted with new update. so everything is fine. i'll get back to the nightlies then.
cheers
Awesome
Thanks deeren.
Updated through stock recovery and everything’s fine, still rooted. I will have to re-flash clockwork again, but that was expected.
Sorry for the noob question, but how do I apply this update? I tried downloading through the browser and the download fails. \do \i donload with PC and put on device manually?
Can you just put this on your SD card and go to Rom Manager and select Install ROM from SD card while you point it to this zip file?
Also does it disable your root, and then you have to root again?
meetagrawal said:
Can you just put this on your SD card and go to Rom Manager and select Install ROM from SD card while you point it to this zip file?
Also does it disable your root, and then you have to root again?
Click to expand...
Click to collapse
Yes, you will have to root again (at least I had to). I used stock recovery because I think that way is safer, i don’t know about Rom Manager.
Jnowak1981 said:
Sorry for the noob question, but how do I apply this update? I tried downloading through the browser and the download fails. \do \i donload with PC and put on device manually?
Click to expand...
Click to collapse
Do as follow if you have stock recovery
BigRick10 said:
Download the OTA package here
Rename it to update.zip, and place it on the root of your internal storage
Shut down your phone, and reboot into the bootloader by holding volume up and powering back on
Choose "recovery" from the list, and select it with the power button
When you see the red triangle press volume up and choose to update*
Click to expand...
Click to collapse
Edit: *When you see the "white" triangle press power button and volume up, then choose apply update from /sdcard.
it's work great one my rooted Nexus S
How do I go from cw to stock recovery without having to do to much
Sent from my Nexus S
i boot into recovery i see the triangle and when i press volume up nothing happens...
i believe once you press vol up to move the cursor onto update, you need to press the power button to select update.
I dont get the option to update. It just stays on the screen with the android and a triangle with a "!"
Jnowak1981 said:
I dont get the option to update. It just stays on the screen with the android and a triangle with a "!"
Click to expand...
Click to collapse
same here
10 char
I am not a computer guy--tried to install latest update and am now stuck in recovery--I tried to install a recovery off an sd card but seemed to fail and now cant get anywhere. Can anyone walk me through a fix??
Thanks
press ctrl+alt+del
not suer
Need more info. Were you on a stock or custom ROM? Are you stuck in stock or custom recovery? What method did you try to install another recovery?
Sent from my SGH-I777 using xda premium
stuck
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
this worked for me...my situation sounds very similar to yours....
http://forum.xda-developers.com/showpost.php?p=23587495&postcount=47
ostism attachable
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
voodoo_dr said:
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
Click to expand...
Click to collapse
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
voodoo_dr said:
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
Click to expand...
Click to collapse
Why you trying a stock ota on a custom rom?
feisty_noodle said:
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Click to expand...
Click to collapse
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
tegezee said:
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
No, this is overkill and won't fix his issue.
This will work period
fone_fanatic said:
Why you trying a stock ota on a custom rom?
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
No, this is overkill and won't fix his issue.
Click to expand...
Click to collapse
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
tegezee said:
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
Click to expand...
Click to collapse
His problem is with it getting stuck in recovery, which is a known issue with Koush's 5.5.0.4, simple fix with adb. No need to reflash the whole rom.
voodoo_dr said:
I am not a computer guy
Thanks
Click to expand...
Click to collapse
Well if he's not good with a computer, my method is the easiest especially if he doesn't have it figured out by now...
Thanks for the help everyone--Ended up using NVflash to load a rom called prime 1.6. 3:30 a.m. and I am as good as new. No ICS but at least it is stable
Good to see you got it back working...
Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod on a stock Epic 4G (SPH-D700) running Gingerbread FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
IMPORTANT NOTE: Be sure to follow the exact procedure below.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- Backup your stock kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
12/08/2013: (Major Addition) Added important note. Added backing up stock kernel.
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Appreciate the effort and updated info.
Mr_You said:
Thanks to alephzain, bbelos/CMTeamEpic, DRockstar, koush, neldar, QBKing77, and toadlife!
See a change log of edits to this post at the bottom. Any corrections or suggestions are welcomed.
This How To will explain how you can root and install ClockworkMod (CWM) on a stock Epic 4G (SPH-D700) running FC09 without a USB cable, Odin, and with or without a computer. My phones USB pins are busted, but otherwise it charges fine and works great. So I spent many determined days figuring out how I may eventually install CyanogenMod. This first requires getting ClockworkMod on the phone.
How will you get files onto your phones external sdcard?
Novice:
- Without a computer: Download files using a browser found in the Google Play Store: Firefox, Dolphin.
- With a computer: Email yourself the files and use your phones email app to save them to your sdcard.
- With a computer: Remove your external sdcard, insert it into an adapter, then insert/connect it to your computer to copy files to the sdcard.
Expert:
- With a computer: Its possible to access "offline files" with Google Drive, but its a bit cumbersome to find the file using a file manager.
- With WiFi and a computer: After gaining root, install the "WiFi ADB" app and download the Android ADB tools for your OS: Windows, Mac OS X, Linux
Transfer the following files to your sdcard (see attachments below):
- Framaroot-1.6.1.apk
- CleanGB_Kernel_0b28e9767b.zip
- cwm-5.0.2.7-epic4g.zip
Get Rooted:
- On your phone go to Settings -> Applications -> Check: Unknown Sources
- Install the Framaroot-1.6.1.apk package.
Install the following apps from the Google Play Store:
- SGS Kernel Flasher
- ROM Manager
Start SGS Kernel Flasher:
- You may backup your kernel, but if you re-flash your stock kernel then you will need to repeat the following procedures.
- Choose Kernel -> Select CleanGB_Kernel_0b28e9767b.zip -> Flash Kernel
- Reboot
Start ROM Manager:
- Select Reboot into Recovery
Recovery Mode:
- Press the Settings icon: You should now be in CWM v3.1.0.1 (use volume up/down, camera to select, home to go back)
- Select: install zip from sdcard -> toggle signature verification -> choose zip from sdcard -> cwm-5.0.2.7-epic4g.zip
- Reboot
Verify CWM Installed:
- Power off phone, wait a few seconds after vibration indicates phone is powered off.
- Hold down: Volume Down, Camera, and Power On.
- Release when the icons light up.
- You should see "CWM-based Recovery v5.0.2.7" and the menu in blue text.
Congratulations you flashed ClockworkMod without USB or Odin!
What now? How about installing CyanogenMod? Well thats my next step and I highly suggest your phone already be activated, the PRL updated, data/contacts synced/backed up, and all services working before installing CyanogenMod stable. Otherwise, as of today (CM v10.1), you will need to temporarily boot into Samsungs FC09 in order to perform these functions.
I hope you find this How To helpful. Feel free to aks any questions, but please Google search for any "inbetween steps" that I have left out of this How To for the purpose of brevity.
Good luck!
Change Log:
11/21/2013: (Minor Addition) Added email method for transferring files to your sdcard. Clean up.
11/20/2013: (Minor Addition) In case their sources disappear I have attached the required files.
11/18/2013: (Minor Correction) Improved links. Clean up.
11/17/2013: (Major Correction) Corrected spelling of Framaroot-1.6.1.apk filename.
11/16/2013: (Minor Correction) After installing CyanogenMod 10.1 (STABLE) I realized the above version CWM is not the latest.
Click to expand...
Click to collapse
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
TheKillah512 said:
This rooting method works, but i have a problem.
The kernel has the su binary installed, nd thats the problem; with a root checker it says no root access. Now i cant do anything else because everytime i do something to fix this issue, it stays the same after a reboot
Please help me
Click to expand...
Click to collapse
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Mr_You said:
The purpose of the CleanGB kernel is to provide CWM v3.1.0.1. You only need to install Framaroot to root the phone.
I'm not exactly sure where you are stuck or what you are trying to achieve. I tried duplicating the process, but it is entirely possible that I made an error so any corrections are helpful.
Click to expand...
Click to collapse
Yes, im sorry that i have to make u go through all this trouble because maybe im doing this wrong..
What i was trying to say is that the kernel also has 'su' in /sbin (im not sure if this is the problem but in my galaxy s3 the 'su' is only located in /system/bin and /system/xbin)
I also read this article where it said that the 'su binary' isnt supposed to be in /sbin because in this case (what i think its saying is) that everytime it boots up the /sbin is part of the booting process. Here is the website link: htt p://a ndro idsu.co m (cant post links yet damn)
" People with the su binary located in /sbin have a much tougher time. I’ve found that these are mostly Samsung users (with the notable exception of the Nexus S). I don’t know why it’s done this way, and if anybody does know, please let me know, but for some reason kernel and ROM devs for these devices put su in /sbin. /sbin is part of the boot.img, and therefore any modifications to that directory will be erased on boot."
What i first did is installed Framaroot nd rooted the phone, then got excited because i had been trying to root it for like 2 years now with no success, so since i thought i knew what i was doing, i trailed off nd tried to install CWMR through Rom Manager then went into recovery nd for some weird reason it just put me in the stock android recovery so i knew something went wrong... Then i got scared nd tried to go back to your method nd installed the kernel flasher so i flashed the kernel, rebooted, nd then went into the superuser app. It said the SU binary needed to be updated (got surprised because it didnt say that before i flashed the kernel) i put continue nd it showed me an option to install it through TWRC/CWMR or install normally,so i chose through CWM nd it actually booted me up into CWM but then it said something about a command not working [it was some couple days ago so i cant remember what it said exactly] so i messed around with CWM and tried to installed CyanogenMod which i had downloaded previously, did the signature verification toggle off, but it still said installation aborted because of the command or something... Then i rebooted the phone nd then the problems started, in the superSU app i tried to install normally but it said installation failed... Got the root checker nd said su found in /sbin /system/bin and /system/xbin but i had no root access so i panicked nd tried to root it again with Framaroot, it said success nd i rebboted but it didnt work. I ran the root checker again nd it was the same. I tried to go back to a backup i did when i only had root without the kernel but(which by the way by the end of the backup it said couldnt make md5 sums)but idk why but it took me to the stock android recovery so i couldnt make a restore. I felt trapped cs i couldnt go back to before i had the kernel. With no root access i couldnt also do the restore to the stock kernel(SGS Kernel Flasher app) because i made a backup of it in case something went wrong.. Unfortunately it did so now with no root access i cant really do nothing anymore... I was thinking of using odin to go back to its original state, but then i remembered that it was impossible because odin never recognized my phone while in download mode... Im short in options on what to do please help, im still a noob
Can you try to do a factory reset from the stock recovery and start over?
Mr_You said:
Can you try to do a factory reset from the stock recovery and start over?
Click to expand...
Click to collapse
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
TheKillah512 said:
Yes, thats exactly what i did two times but it didnt work because once you flash something theres no way to go back unless you have a backup and a way to restore it or is there a way i dont know of?? I also checked right after the factory reset in the settings nd it still had the same kernel, and the root checker still said the su binaries were installed in the 3 places i mentioned earlier nd still without root access
Click to expand...
Click to collapse
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Mr_You said:
EDIT: If you have tried this procedure on a Galaxy S3 then I would suggest this discussion be continued on the appropriate forum.
Click to expand...
Click to collapse
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
TheKillah512 said:
No, lets get this straight. I already rooted my gs3 a long time ago nd i didnt use this procedure with it. I used this procedure with my Epic
Click to expand...
Click to collapse
I assume you've already tried uninstalling any SU-type packages?
Mr_You said:
I assume you've already tried uninstalling any SU-type packages?
Click to expand...
Click to collapse
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
TheKillah512 said:
Yes i did.. In the SuperSU app in the settings section it has an option to Full Unroot, nd i think it works but it has to reboot, and at the time of reboot, the kernel overrides it and gets rid of any modifications like getting unrooted..
Looks like im going to have to bear with this nd just leave it like that, besides i already have a rooted gs3
Click to expand...
Click to collapse
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Mr_You said:
So your are running CleanGB? When you open ROM Manager and select "Boot into Recovery" does it boot into CWM v3 and are you able to flash CWM v5 or do you still get the error?
Click to expand...
Click to collapse
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
TheKillah512 said:
Yes i am running CleanGB nd when i use rom manager and select "Boot into Recovery" it does nothing because i dont have root access and that means it doesnt have permissions to boot into recovery, however i did also try to manually boot into recovery but it took me to the stock recovery.. Is this supposed to happen??
Click to expand...
Click to collapse
Yes that is normal.
I see you say you tried reinstalling Framaroot, but try reinstalling again. But don't reboot. Afterwards go straight into ROM Manager and select "Boot into Recovery" and if rooting was successful I believe it should boot into CleanGBs CWM v3 recovery.
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Sent from my SPH-L710 using XDA Premium 4 mobile app
TheKillah512 said:
It did boot up into CWM v3 nd i tried to flash the CWM v5 but there were these weird things, look ill show u a picture of it.
Click to expand...
Click to collapse
For some reason all the forums posts images are broken for me. It seems to be a 404 error.
Ok lets try this:
Make sure you are rooted (install Framaroot again if you need to, don't reboot) and start SGS Kernel Flasher and flash your backup backed up stock kernel and reboot. Then try following the procedure again from the top as described to try to install CWM. Rebooting your stock kernel may or may not fix these issues. If it doesn't then it may require finding a way to fix it via a Terminal app or other method.
I seem to be rooted in some ways but not in others
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
cdupree said:
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
I would try reinstalling Framaroot (and don't reboot) then: Start ROM Manager->Reboot into Recovery
cdupree said:
I installed Framaroot and it claimed success. However, that doesn't seem to be true according to the Root Checker app. I removed Framaroot, rebooted, reinstalled, and reran it with no difference. But what's weird is the first time it seemed to work, so I went ahead and tried to flash CleanGB and it worked. I'm currently running CleanGB.
The problem now is that when I ask ROM Manager to Boot into Recovery it won't do it, presumably because I don't have root access. What can I do next? Any suggestions are appreciated!
Click to expand...
Click to collapse
Thats exactly what is happening to me too, friend...
Sent from my SPH-L710 using XDA Premium 4 mobile app
TheKillah512 said:
Thats exactly what is happening to me too, friend...
Click to expand...
Click to collapse
Sorry you're mistaken. You just posted a pic of CWM v3. So your "Reboot into Recovery" from ROM Manager worked.
Did you try what I suggested here to fix your errors?
I'm a bit of a newbie with rooting and flashing but have been pretty successful up until now. I installed TWRP 2.3.6.2 and CM 10.2 on my Verizon LG G2 about a month ago.
Since then I've been updating with nightlies with much success.
When the 11.0 build showed up in the CM updates list I downloaded it and installed. It failed and I had to flash an older 10.2 nightly. My device became pretty unstable after this. Most GApps were gone or somehow corrupted. I re-installed a number of them but Google Play still didn't work.
I tried updating again to an 11.0 nightly today and again it failed. I then flashed a recent 10.2 nightly that had worked for me and now my phone is stuck an infinite spinning Cyanogenmod boot screen.
I have tried every combination of holding power and volume down to try to get into TWRP to try flashing another nightly but my device just continues to reboot to LG then Cyanogenmod spinner over and over.
I decided maybe I needed to reinstall TWRP (looks like there's a new version from today). I tried to access my device with it plugged into my computer using fastboot and adb push loki_flash and it returned "device not found."
I'm totally stuck now... no idea what to do next. Would be so grateful for some guidance on how to get my device functional again.
Thanks.
One additional comment: I've tried doing Power + Volume Down during LG logo but it doesn't do anything.
I managed to get into a Hardware Key Control Mode screen by holding Power + Volume Up + Volume Down which had some options about answering calls or turning off alarm using hardware keys.
Cannot seem to do anything to get to TWRP.
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
tophy0 said:
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This screen is what you want to see. Push Power a couple of times. It won't erase your settings. It'll boot into TWRP.
tophy0 said:
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
Click to expand...
Click to collapse
Phew, that worked! Back into TWRP.
Any additional guidance on what I should be doing to try to get back into a stable version of CM? I have many builds of CM 10.2 in internal storage that I could pick from. But before I try another one of those should I attempt to clean things up at all? Seems like my current configuration must have some sort of conflict that's leading to all the instability. I do have Titanium Pro installed so I believe I should be able to get my apps + data back as long as I don't completely clean out everything.
Thanks again for the help.
Also mods: just realized that I should have posted this thread in Q&A not General. Sorry about that! I don't think I can move it over myself or I would.
I think what I would like to do now is update TWRP to 2.6.3.3 and then install 11.0 using this build: http://www.droidforums.net/forum/lg-g2-development/258385-rom-wip-cyanogenmod-11-g2-vzw.html
Not sure how to update TWRP from 2.6.3.2 to 2.6.3.3 though. When I originally set up TWRP I used adb / loki-push but it's a bit of a blur how that worked since I was just following step 1-2-3 instructions.
Sorry for being such a noob with this stuff. Any additional guidance would be awesome.
As I suspected, flashing any CM ROM now leads to an infinite CM spinner so I think I need a plan B to get my device working again. At least I can now get to TWRP thanks to the help above.
Not sure where to go from here.
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Makrilli said:
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
tophy0 said:
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
Click to expand...
Click to collapse
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
madisonjar said:
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
Click to expand...
Click to collapse
Thanks, makes a ton of sense.
I also use Titanium to backup. When I do a fresh install of TWRP and CM 11.0 can I restore my system data in addition to apps + app data? I'm not sure to what restoring extent system data could create conflicts with the CM 11.0 build. For example will all the Google Mobile Services system data from my CM 10.2 build create conflicts?
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
tophy0 said:
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
Click to expand...
Click to collapse
You can safely use TB to restore user apps, their data and trebutchets data if you use that. Backing up sms and contacts with TB, I'm not sure about that as I used other app "super sms backup". And about emails I have no idea. Also it's not a good idea to restore settings, better to set them again
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
WCM3 said:
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
Click to expand...
Click to collapse
You know, I was wondering as well of how to get to TWRP if a rom didn't boot. I got to that screen too and thought it would erase the phone. This is good to know and should be a sticky somewhere.
Hi Guys,
i have spent the last week looking around for information and i cant find a fix, wondering if people could help please!
Im a long time user of custom roms, have had customs on the HTC Hero, S3 and now my S4... and i had the CM12.1 nightlies installed, running TWRP and the CF AUto Root.
It ran perfectly for a few weeks or so, even with the OTA updates you get.
I woke up the other morning to the phone misbehaving so i thought i would check and now i dont have Root access at all. Super SU, TWRP and even root checker all confirm no root access.
I have wiped the phone, reinstalled root, then TWRP and then the latest CM12.1 nightly and whilst it boots into the OS, i still dont have root.
Can anyone assist please? no root seems to cause hell!
You have a big misconception about rooting a custom rom.
CF auto-root is ONLY for stock TW rom. It's should NOT be used with CM or ANY other custom rom.
Root is standard in CM, it's only disabled. It can be enabled trough devoloper options.
- To enable Developer options go in Settings->About device and press "Build number" for 7 consecutive times.
- Then go in Developer options and enable root.
After that you can install SuperSu from the playstore (but it's not required). It would recommend it though.
Lennyz1988 said:
You have a big misconception about rooting a custom rom.
CF auto-root is ONLY for stock TW rom. It's should NOT be used with CM or ANY other custom rom.
Root is standard in CM, it's only disabled. It can be enabled trough devoloper options.
- To enable Developer options go in Settings->About device and press "Build number" for 7 consecutive times.
- Then go in Developer options and enable root.
After that you can install SuperSu from the playstore (but it's not required). It would recommend it though.
Click to expand...
Click to collapse
Hi Lennyz,
rookie mistake from my point eh!
i have just checked root options in dev options and it has 'Root Access' set to Apps and ABD and it still doesnt work?
noodles249uk said:
Hi Lennyz,
rookie mistake from my point eh!
i have just checked root options in dev options and it has 'Root Access' set to Apps and ABD and it still doesnt work?
Click to expand...
Click to collapse
I'ts possible that that is caused by flashing cf auto root.
- Wipe /system (you don't need a full wipe). You can the option somewhere in TWRP.
- Reflash the rom you are on.
- Enable root in developers settings.
- Install supersu from the playstore.
Have you actually tried reinstalling SuperSU? Or force updating the libraries?
I'm having the same issue. But without root, I can't even go into recovery. What should I do to wipe the system and flash the same rom? Please help, thanks.
2080722 said:
I'm having the same issue. But without root, I can't even go into recovery. What should I do to wipe the system and flash the same rom? Please help, thanks.
Click to expand...
Click to collapse
Root is nothing to do with the recovery. Won't stop you from booting into it if you don't have root
Cannot boot into recovery anymore (in CM 12.1)
DSA said:
Root is nothing to do with the recovery. Won't stop you from booting into it if you don't have root
Click to expand...
Click to collapse
Thanks for your help. I'm still quite new to the rooting/flashing ROM thing. The reason I ask that question was I cannot boot into recovery anymore. I tried using the following three ways, 1) holding volume up, center home and power - it still boots back to normal boot; 2) The advanced boot option in CM12.1 used to have the option of booting into recovery, but it's gone now; 3) Using the Cyanogen Update from CM12.1 to run the update within the About Phone section of settings.
Is there another way to boot into recovery? Or, do you think there is something wrong with the CM 12.1? Thanks again.
With the phone switched off, press and hold volume up/power...ignore home button its not needed
Let go when you see blue writing in top left
If that fails, then we can take it from there
DSA said:
With the phone switched off, press and hold volume up/power...ignore home button its not needed
Let go when you see blue writing in top left
If that fails, then we can take it from there
Click to expand...
Click to collapse
I just followed your instruction. I saw the blue writing in top left, then it vibrated once and went back to boot into the regular OS. What should I do next?
Thanks.
2080722 said:
I just followed your instruction. I saw the blue writing in top left, then it vibrated once and went back to boot into the regular OS. What should I do next?
Thanks.
Click to expand...
Click to collapse
hmm... maybe you are holding down the buttons for a little too long...try releasing when you see the samsung logo start appearing
Ok, that worked, thanks. I was back in recovery.
But then when I tried to flash the zip file of the same ROM again, I got an error message saying that the ROM is for certain models: jfltexx, i9505, GT-i9505 etc. and that my device is jfltecan.
My device is a Canadian Rogers Galaxy S4 (SGH-i337M). Initially, I used the CM 12.1 ROM for jfltexx to flash and then the model name in settings became GT-i9505. Also in setting, it's showing the CyanogenMod version as "12.1-20150426-NIGHTLY-jfltexx. So, how can I fix that?