Related
This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bear with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloader or flashing some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading around, downloaded SU Update Fixer from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
** One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery on my phone just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assumed it was since I got the Superuser app.
Another thing that felt kind of wrong is that, when I flashed to yakju, it wiped my phone clean. I expected rooting to do the same thing, but it didn't (I think because my bootloader was already unlocked?). So I'm not sure if that has anything to do with it either.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing files from a directory, etc.
Thank you in advance.
BryMerc said:
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bare with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloaderor or replace some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading downloaded SU Update fixed from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assume it was if I got the Superuser app.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing .img files from a directory, etc.
Thank you in advance.
Click to expand...
Click to collapse
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
JaiaV said:
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the fast response.
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot?
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Thanks.
BryMerc said:
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot
Click to expand...
Click to collapse
Yes.
BryMerc said:
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Click to expand...
Click to collapse
JaiaV said:
OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
They only care that the recovery and /system are stock, and even then (as I said) don't care if you're rooted. Rooting doesn't matter. Having a custom recovery does. They are not the same thing. Also, read through ||Nexus|| response.
IINexusII said:
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, but dont reboot this time, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
Click to expand...
Click to collapse
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
BryMerc said:
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
Click to expand...
Click to collapse
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
IINexusII said:
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
Click to expand...
Click to collapse
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
in clockwork mod recovery there should be a "Wipe Cache" option, and for fixing permissions go to "advanced" and "Fix Permissions"
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
Wait, actually I don't think the JB installed now that I'm staring at the screen properly.
It went Installing update...
assert failed: file .........blah blah
Installation aborted.
Also, the drivers I thought I had for my phone seem to be messing up and in device manager it says "Full" with an exclamation point. I'm not sure why.
Sorry for the late responses as a n00b I'm stuck with 5 minute intervals here.
which country are you from?
IINexusII said:
which country are you from?
Click to expand...
Click to collapse
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
BryMerc said:
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
Click to expand...
Click to collapse
After selecting "Install zip from sdcard" I see an option "apply /sdcard/update.zip". Is that anything maybe I need to do or something?
check your PM
I purchased a Kindle Fire for my wife, I want to root it to allow Google Play to be installed
I dl'd the KFU v0.9.6, got the ADB driver, installed, showing as a android composite device
I run the utility following these instructions
from the liliputing.com
it gets to this point, screen cap attached
and dies, it leaves me at the TWRP screen, I have recovered several times using this site here
rootkindlefire.com hot to /how-to-unrootunbrick-rooted-kindle-fire
I must have read 100 threads today but nothing seems to help
Any suggestions or should I just wait for a utility update?
I'm no expert but I have rooted my phones in the past and installed custom ROMs, I'm no developer by a long shot but I'm not out in the woods clueless either.
Thanks
Hopefully you have the latest FFF installed (blue Kindle Fire logo?). If so, when you see it, hold the power button until you see the boot options appear. Select normal or reset boot mode.
soupmagnet said:
Hopefully you have the latest FFF installed (blue Kindle Fire logo?). If so, when you see it, hold the power button until you see the boot options appear. Select normal or reset boot mode.
Click to expand...
Click to collapse
At the moment I am back to stock, kind of skittish as it seems I am not the only person having a similar issue
Well, looking at screenshot, I see that TWRP was installed successfully. As long as have that, you're good. You can use TWRP to install FFF and a new rom which fixes just about everything. When TWRP first installs it will reboot and leave your device in fastboot mode (stuck at boot logo). To fix it, simply change your bootmode. Using the latest FFF (blue Kindle Fire logo) is the easiest way, but it can also be done via command line.
Being "stuck" at the boot logo is a normal process of modifying the KF, it doesn't mean it's bricked. I suggest you take the time to read up on some Kindle Fire basics before you proceed.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it, not to identify your exact problem like so many do, but to educate yourself on how this thing called Kindle Fire/Android works. If you've already read it, read it again. Doing so will help you and those trying to help you, tremendously.
I got the same screen last night as well. TWRP is installed as I can reboot into Normal/Recovery/Reset Boot..
I can use the KFU to reset the bootloader as well (normal/fastboot, etc)..
but for some reason, KFU doesn't seem to root my device when selecting option 2. I get the blue KF boot logo, can access TWRP, but then what? Do I need to install some other software?
I am soo confused...
I want to root my device so I can install programs. I would also like to install custom ROMs (which I understand that I do not NEED to be rooted to do this), but to install other programs I do.
iRock48 said:
I got the same screen last night as well. TWRP is installed as I can reboot into Normal/Recovery/Reset Boot..
I can use the KFU to reset the bootloader as well (normal/fastboot, etc)..
but for some reason, KFU doesn't seem to root my device when selecting option 2. I get the blue KF boot logo, can access TWRP, but then what? Do I need to install some other software?
I am soo confused...
I want to root my device so I can install programs. I would also like to install custom ROMs (which I understand that I do not NEED to be rooted to do this), but to install other programs I do.
Click to expand...
Click to collapse
Transfer the ROM you want to your sdcard and use TWRP to install it. Be sure to "factory reset" (wipe) before you install the ROM or there will be conflicts. It is usually a good idea to wipe cache and dalvik after the ROM installation. There's no need to root a custom ROM.
soupmagnet said:
Well, looking at screenshot, I see that TWRP was installed successfully. As long as have that, you're good. You can use TWRP to install FFF and a new rom which fixes just about everything. When TWRP first installs it will reboot and leave your device in fastboot mode (stuck at boot logo). To fix it, simply change your bootmode. Using the latest FFF (blue Kindle Fire logo) is the easiest way, but it can also be done via command line.
Being "stuck" at the boot logo is a normal process of modifying the KF, it doesn't mean it's bricked. I suggest you take the time to read up on some Kindle Fire basics before you proceed.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it, not to identify your exact problem like so many do, but to educate yourself on how this thing called Kindle Fire/Android works. If you've already read it, read it again. Doing so will help you and those trying to help you, tremendously.
Click to expand...
Click to collapse
Thanks, I reread it last night and will do so again, will likely get back to this over the weekend
soupmagnet said:
Transfer the ROM you want to your sdcard and use TWRP to install it. Be sure to "factory reset" (wipe) before you install the ROM or there will be conflicts. It is usually a good idea to wipe cache and dalvik after the ROM installation. There's no need to root a custom ROM.
Click to expand...
Click to collapse
Thank you for the reply. I assume to transfer the ROM I want I'd use something like Window Explorer to drag/drop or should I use the command language?
Wiping the cache and dalvik - is that also done through TWRP?
one last thing; it is my understanding that once you install a custom ROM, you have "root" access.. will this access allow me to install the App Store/Android Market and install apps that normally require root, such as Titanium backup?
iRock48 said:
Thank you for the reply. I assume to transfer the ROM I want I'd use something like Window Explorer to drag/drop or should I use the command language?
Click to expand...
Click to collapse
In TWRP you can use "abd push" or there is "mount" function that it comes with that will allow you to mount your sdcard as an external drive, much like with the stock Amazon software.
Wiping the cache and dalvik - is that also done through TWRP?
Click to expand...
Click to collapse
Yes, after you install the ROM, you'll be given the option to.
one last thing; it is my understanding that once you install a custom ROM, you have "root" access.. will this access allow me to install the App Store/Android Market and install apps that normally require root, such as Titanium backup?
Click to expand...
Click to collapse
Yes, but the "Market" (Google Play) must be installed in TWRP as a "gapps" package. Just Google gapps for the version of android you're installing (CM10-JB, CM9-ICS, or CM7-GB).
ye i have the same issue "mv: can't rename '/system/bin/check_rooted': No such file or directory". I'm sitting at TWRP recovery screen, so I'm guessing just download rom of choice use the mount function to transfer the rom, full wipe and install. this should solve my getting no further in rooting process problem?
radici said:
ye i have the same issue "mv: can't rename '/system/bin/check_rooted': No such file or directory". I'm sitting at TWRP recovery screen, so I'm guessing just download rom of choice use the mount function to transfer the rom, full wipe and install. this should solve my getting no further in rooting process problem?
Click to expand...
Click to collapse
If your only error is "mv: can't rename '/system/bin/check_rooted': then chances are, you're already rooted. It just means there was no check_rooted file to rename, so you're good.
Not that it matters anyway because installing a custom ROM gives you "root" anyway.
Managed to instal AT&T v20 stock kitkat and sb told me to:
use towelroot to root the device then install gpro rec.apk and flash rec but do not reboot to rec then install busybox and freegee-i DID THAT-was easy I quess
NOW I DON'T GET THIS:and perform cwm action after this reboot to rec and flash phillz rec and reboot again to rec and full wipe then flash any rom u want.
Help?
kamolinkaaa said:
Managed to instal AT&T v20 stock kitkat and sb told me to:
use towelroot to root the device then install gpro rec.apk and flash rec but do not reboot to rec then install busybox and freegee-i DID THAT-was easy I quess
NOW I DON'T GET THIS:and perform cwm action after this reboot to rec and flash phillz rec and reboot again to rec and full wipe then flash any rom u want.
Help?
Click to expand...
Click to collapse
Okay, first, you may want to try flash the v10g version of the stock ROM because it's the best starting point for flashing the custom ROM on lg ogp device. Follow the instructions in the link below and you should be good. I don't know why someone would tell you to use the towel root with the stock v20 rom because a lot of time it doesn't root properly. The instructions you were originally gave were to root with the towel root and then install the busy box so you can use the freegee. With the freegee you can install either cwm or twrp custom recovery. Once you have the custom recovery, reboot into the recovery and then flash philz custom recovery because it's better than the freegee's. Philz recovery is optional if you don't feel like you need it, it just has more bell and whistle, that is all. You can flash the custom ROM with either custom recovery, philz or freegee. However, I'm more concern with you trying to root with the v20 stock ROM, because you will likely run into many issues. So be sure to read the guide I give you first.
[http://forum.xda-developers.com/showthread.php?t=285432
x
Hey! thanks for the replay! I just got one helper because the rom guy didn;t want to help me so the others.Only 1 guy wanted to give me hints and I managed to install this stock rom.
So you're saying that I have wrong rom installed?
Do I have to really instal other rom or can I do it on mine but in other way to root it and process it so as to install http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779 or not?
I'm all confused,just wanted to install http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779
but whole day passed and nothing was done U.Ux
Read the guide I give you.
Managed to root my phone by iRoot.
Now I tried install busybox but after I hit install: "it looks like the instalation of busy box was not successful try installing to different location that may resolve the issue"....
any tips?
If you can't install the busy box, that usually has something to do with the root. That's the reason I said not to use the v20 stock ROM as the starting point. The only reason you need the busy box is the freegee, you can install the recovery without using freegee, but you have to search around XDA first because freegee opens up the boot loader, which is also the reason you can't just flash the recovery with the lg flash tool. You may have to flash v10g version of the stock ROM.
Ok I'm in philz menu.Someone said that all I need is to install(ANY) rom and kernel-how I do it? I want http://forum.xda-developers.com/optimus-g-pro/development/mar-0-lollipop-g-pro-v1-t3043779
Have you used a custom recovery before? Down load both rom and kernel installing files to a directory that you prefer, usually some where on your external sd disk. Once you get the files, go to philz recovery and press install zip, find the directory where the installing files are located, press on them, and it should install the rom. If you have never done this before, remember to factory or clean install the rom. On philz recovery, there is a function call installing a new rom under factory reset section, use that every time you're installing a new rom.
hawkwind212 said:
Have you used a custom recovery before? Down load both rom and kernel installing files to a directory that you prefer, usually some where on your external sd disk. Once you get the files, go to philz recovery and press install zip, find the directory where the installing files are located, press on them, and it should install the rom. If you have never done this before, remember to factory or clean install the rom. On philz recovery, there is a function call installing a new rom under factory reset section, use that every time you're installing a new rom.
Click to expand...
Click to collapse
PLEASE HELP!
Installed CM12.1 on my e980. And now the wifi isn't working at all. Have searched and tried some fixes but to no end. Any suggestions?
D Sami said:
PLEASE HELP!
Installed CM12.1 on my e980. And now the wifi isn't working at all. Have searched and tried some fixes but to no end. Any suggestions?
Click to expand...
Click to collapse
Have you tried clearing Cache from Recovery?
khan.orak said:
Have you tried clearing Cache from Recovery?
Click to expand...
Click to collapse
Yup, I advanced wiped my phone (TWRP) and cleared cache, dalvik and system
What's Wi-Fi doing? I notice there are issue with the modem on cm12.1 based custom rom. During the boot up, it would spent long time searching for the signal, but I never have problem with the Wi-Fi though, then again, I'm not using cm12.1 but vanir instead. However, somewhere I remember reading that someone else is having a issue with the Wi-Fi on cm12.1, and he fix it temporarily by setting up the Wi-Fi each time.
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!