Develop Bugs

[HOW-TO] Simplified Root + Recovery + Custom ROM

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.

[RECOVERY](Updated 2-8-14) Official ClockworkMod Recovery 6.0.4.7

Here is the official ClockworkMod Recovery 6.0.4.7 non-touch images and touch images for the Nexus 10 enjoy :cyclops:!
Credit goes to Koush for releasing the official ClockworkMod Recovery images
These are safe to flash via fastboot.
Non-Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-manta.img
Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-manta.img
These can be flashed via fastboot using the following commands:
Code:
fastboot flash recovery /path/to/.img
fastboot reboot
Once again enjoy :victory:!
Note: To get the recovery to stick on reboot when Clockworkmod Recovery asks you if you want rename flash-recovery.sh or similar say "Yes", this will allow you to keep Clockworkmod Recovery installed permanently (Unless you flash a different recovery image) when you reboot your phone.

These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/

Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.

Dees_Troy said:
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Click to expand...
Click to collapse
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
Ok that is really bizare, both CWMR and TWRP are not working right and encountering similar issues regarding random reboots and mount issues. Whats odd is other people are experiencing random reboots during regular use even when not in recovery. I'm starting to believe that something Google might have to put out at fix for software wise may be needed.

So I take it no more "booting" the temporary ones posted before for the Nexus 4/Nexus 10? We can go ahead and "flash" these ones right?

zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
i cant even get the sideload to work to get SU installed. Its driving me crazy. I keep trying it over and over again with the same result. As soon as i go over to recovery it unmounts from the computer then the sideload command fails due to computer losing connection with it. "Device not found"
Tried both CWM versions now .5 and .6
Not my first time around the block with rooting :-/
Used heimdall suite to flash my GS2.. any way to get it to push the .zip file for SU over to the phone? Push the recovery img then push the .zip maybe?

So I never even ended up trying to sideload anything, I just flashed the official recovery, then went immediately to recovery from fastboot, and once there I just flashed the SU zip and now I have root. Of course, CWMR doesn't work (i.e. if I use Quick Boot to boot to recovery it just takes me to the stock recovery, and if I try to go to recovery from fastboot manually, I just get the dead android w/red triangle).

Jayrod1980 said:
Finally got it... helped to just get the supersu on the root of the device. I used the fastboot commands to get to cwm touch and then I quickly installed it through the interface. I couldn't sideload. The device won't recognize adb when I'm in fastboot mode at all. I don't know what I was doing wrong in that instance, but using cwm briefly let me install supersu. Thanks for your help! Surprising this is so buggy considering it's a nexus... and it's not the nexus that's excluded from AOSP. Go figure!
Click to expand...
Click to collapse
I had to do it this way in order to get root. Finally.. been working on this for like 5ish hours now.. what a pain. Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon. Good luck to everyone that goes this route.. it takes a lot of trial and error

snunez said:
Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon.
Click to expand...
Click to collapse
I'm sure there will be, probably by the end of the weekend, if not sooner

I took apart CWM touch 6.0.1.6 and fixed reboot after 20 sec
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )

damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.

So,
Am I right in thinking...
cd to the adb tools folder where the sdk is saved.
I need to unlock the boot loader via fastboot oem.
Then copy your file to the same directory on my Mac
Then type in the command line you suggested with the correct filename?
After that I will be rooted
Swype'd at pace from my Galaxy S2

Here's my working tree
The-Kevster said:
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
Click to expand...
Click to collapse
I used this tool to unpack and re-pack the image: https://github.com/huaixzk/unpackbootimg.git
Attached is my current working tree as a tar.gz
Edit: the tool in that git repo is missing a step to gunzip | cpio the ramdisk... I made a shell script to do that for me when unpacking and repacking
Edit2: I added the wrapper scripts I made for posterity

damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?

Underworld79 said:
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Click to expand...
Click to collapse
I could probably do it to TWRP as well (later today, it's sleep time for me)... however, I don't know where the latest nexus 10 recovery image is from them (considering it's not in this forum).

so can I permanently flash this now instead of fastboot?

damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Well I just flashed your version of the recovery, and after doing "fastboot-mac reboot" and rebooting, I tried rebooting to recovery via adb, and unfortunately it brought me back to the dead android red triangle screen. In fact, I can't even get to CWMR at all. Anyone else??
And to be clear, I have successfully rooted, so at this point I'm just trying to get a functioning version of CWMR on the tablet, if possible.

Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.

Randomwalker said:
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Click to expand...
Click to collapse
Yeah I know that, but I'm not trying to enter stock recovery, I'm trying to enter the custom recovery (which is the supposed "stable" one by damien) which I've installed. And it only let me access CWMR immediately after flashing it. However anytime afterwards I simply cannot access it again:
1) tried "adb reboot recovery" and it brings me to the dead android w/red triangle
2) tried getting to recovery via the Quick Boot app, and the same thing happens
3) tried getting to recovery via the normal holding buttons down to get to bootloader, then going to recovery manually from there, and a no-go as well.
In the end, all that happens is I have to toggle the buttons once I get to the dead android screen, and the menu for the stock recovery appears, which allows me to reboot. But as for CWMR, it is nowhere to be found. WTF.

Did you reboot after installing CWM? If so, did you remove install.sh, that will restore the stock recovery?

[Q] Where can I get CM11 howto on Ouya

Hello
I own Ouya for the month but most of time I use it as media-box for TV (watching movies, etc)
I have already rooted it and installed play market but i hate the stock UI and obsolate android
I saw a video in youtube with CM11 and ouya (android 4.4) and started to google the solution
I already know that it is based on Eternity Project kernel.
I found the way to install bootloader http://www.eternityproject.eu/topic/1114365-eternityproject-tpl-bootloader-for-ouya/ and it is clear
The next step is to install kernel http://www.eternityproject.eu/topic/1114362-eternityproject-kernel-3437-for-ouya-cpu-2ghz-gpu-650mhz/ but it is unclear for me about fastboot command
The next step as I understand is to install CM11 from the CWM
Is it possible to install KitKat without EP kernel?
So If someone have detailed steps or howto on installing CM11 on ouya please give it to this thread
Thanks in advance

I think this is what you're looking for. I'm not sure the EP boot loader is compatible but I'm sure its mentioned in the thread somewhere. Or in the bootmenu thread anyway.
http://forum.xda-developers.com/showthread.php?p=51332165
Sent from my Nexus 5 using XDA Premium 4 mobile app

This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.

quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.

PHYSC-1 said:
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.
Click to expand...
Click to collapse
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.

quepaso said:
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.
Click to expand...
Click to collapse
Just realized cwm is removed,can't install using oneclickrecovery tool either fails says cannot find img etcetc,yet its all there no problems adb is fine and works.Fastboot driver i can't get running although listed yellow exclamation,any ideas?
Fixed it managed to get fastboot going downloaded the required missing dll files and win_usb.inf set up and used ouyatoolbox 1.0.0.0 to rewrite recovery,found i can no longer add the newer 6.0.4.8 recovery zip in update from zip in 6.0.3.2 recovery though? Used to be able to do that. Any way tmore to the point is can someone tell me the step by step process to add cm11 firmware so i don't have to read a load of [email protected] that doesn't end up giving less than nothing in terms of having a clue how,someone in the thread writes about erasing stuff and what oreder but that doesn't tell you how to install or what erase process is or anything detailed and the net has exactly the same misguided tutorials on how to do it.Tellinng a newbie to erase stuff means they will erase all the wrong stuff in all fairness it's good to have a slightly better idea by reading that but it doesn't go in depth or step by step.
All i have found is sites pointing back to the xda pages that do not explain it,it's like your expected to know everything before you have been taught and fill in the gaps off the top of your head.

quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Exactly what he said, I just did these same steps on a 3rd new ouya yesterday and it went off without a hitch. The cm11 thread is long but honestly all the information you need is in the first few posts. If you were able to connect the ouya to USB and run oneclickroot then you're ready to get started.

[Guidance] SGH-T989 UPDATING ISSUE!

Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.

Did you follow the instructions to flash TWRP using Odin?

olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear

bump

Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1

aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?

N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.

N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.

markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post

aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!

N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.

NEED HELP

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!