Database Info

Pipo U2 root Instructions - rk3066 (should work for other devices just as easily)

Tools needed to Root the new Pipo Ultra U2.
http://www.mediafire.com/?0g1tc07kx0tu482
Rar includes;
rkAndroidTool (English)
u2_root.zip
rk drivers
instructions...
This is the easiest way and will give you Super User and CWM recovery.
If you wish to use the Chinese application for rooting; http://www.mediafire.com/?mddj3wn8z2rcb1u
***Use at your own risk - I take no responsibility for bricked / broken devices using this thread / tools***
on a softer note, I am not sure what can go wrong given this method and the standard rockchip way of flashing the rom to restore
I do not take credit for creating CWM; credit to Christian Troy at dragondevs.com for creating a CWM for RK3066 tablets
Update zip is an edit of a script that has been floating around for sometime...
English Stock Firmware available from here;
http://www.mediafire.com/?145py7tcdmuu5aq
http://www.mediafire.com/?1m7nzmzda9vukah
Use at your own risk as usual though (with no guarantee) I do not think these methods will void warranty but its not my problem... (flashing stock firmware using batch tool will remove root & CWM)
Instructions
1. Hard power off your Pipo U2 (Hold power button until it powers off)
2. While holding Volume- (down) button
3. plug use into phone then your PC (update mode)
4. Install missing drivers from driver folder if you have not already
5. Run RKAndroidTool.exe
5. Unselect option 2 (Parameter)
6. Select Flash Rom
Your Pipo U2 should now have booted to Clock Work Mod.
Take a nand backup if you wish.
You can access CWM via the usual Android way...
(Power off Pipo U2, while powering on hold volumne- (volume down) & (holding power button).
Now its time to to get root access...
7. Copy u2_root.zip to the root directory of you SDcard.
8. Hard power off
9. Boot to CWM (Holding volume down as you hold power button until you see Pipo boot)
10. Select Install zip from SDcard
11. Scroll and install u2_root.zip
Will install and say that you are rooted.
12. Reboot device (you will now have Super User installed and working)
If you install Titanium and it doesn't give it root access just reboot again and fresh install TB and you'll be sweet!
Remove any bloatware / unwanted Chinese applications using titanium backup. (or install English firmware prior to root)
ENJOY!!! and please don't forget to hit the thanks button

Please post you responses and your device
This will ensure other user have the tools needed to successfully root their tablets...
I am quite sure this should root most rk3066 devices including the Pipo U1 , U2 , M3 etc and will be intrigued to hear other results as I am quite sure it should do all rk3066 tablets :laugh:

I got CWM installed on the u2. When I install the root.zip in CWM, it says it is installed. However, I do not appear to have root access. I have restarted several times, reinstalled "root.zip" etc. The root checker app confirms that I do not have root. I also don't see Superuser installed in the apps list, etc. Any suggestions?
When I install root.zip:
Installing: /sdcard/root.zip
Finding update package...
Opening update package...
Installing update...
Applying root...
Deleting old binaries and packages...
Unpacking new files...
Setting permissions...
You have been root...
Install from sdcard complete.

new root.zip
Hi mate, appears I may have accidently deleted the wrong root.zip prior to creating these files...
This new one will do the trick
http://www.mediafire.com/?at8fkcqkncjqk1z

Yup, it worked on the first try. Root Checker confirmed, and Titanium Backup works. Future users just need to use CWM from first post, and root that's in second post. (post order may change if Raz fixes the first upload of course)
To other users based on my observations of just 1 tablet:
CWM install:
- If using Win7 64-bit, the rk drivers to install CWM are finicky. If the Win7 driver doesn't work, try the Vista driver (worked for me after a few tries). If that doesn't work, unplug and reboot tablet and try again. If you can't get included drivers to work in Win7, the drivers work flawlessly in WinXP.
I did poke around google/this forum/other forums looking for better drivers, but all RK drivers seem to behave this way in Win7 64-bit.
I *think* the included drivers with Superoneclick *may* work (the ones that Superoneclick forces Windows to use). Install Android SDK, then run Superoneclick and hit "yes/proceed" for the it's driver installation.
Using CWM to install root:
- The volume +/- buttons scroll up/down, and the power button is the enter key. However, for mine the power button is finicky. If it's not "entering" (and instead making the CWM logo bigger), try hitting the "esc" key and/or scrolling up/down.
Other programs I tried:
- While waiting on Raz's response, I went ahead and tried using other RK3066 root programs and none of them worked. I tried "Superoneclick", "Busybox", and even tried the questionable "ZhuoDaShi 2.2.9". None of them worked. Stick with Raz's stuff in this thread. However, YMMV.
Thanks Raz!

Runeswords said:
Yup, it worked on the first try. Root Checker confirmed, and Titanium Backup works. Future users just need to use CWM from first post, and root that's in second post. (post order may change if Raz fixes the first upload of course)
To other users based on my observations of just 1 tablet:
CWM install:
- If using Win7 64-bit, the rk drivers to install CWM are finicky. If the Win7 driver doesn't work, try the Vista driver (worked for me after a few tries). If that doesn't work, unplug and reboot tablet and try again. If you can't get included drivers to work in Win7, the drivers work flawlessly in WinXP.
I did poke around google/this forum/other forums looking for better drivers, but all RK drivers seem to behave this way in Win7 64-bit.
I *think* the included drivers with Superoneclick *may* work (the ones that Superoneclick forces Windows to use). Install Android SDK, then run Superoneclick and hit "yes/proceed" for the it's driver installation.
Using CWM to install root:
- The volume +/- buttons scroll up/down, and the power button is the enter key. However, for mine the power button is finicky. If it's not "entering" (and instead making the CWM logo bigger), try hitting the "esc" key and/or scrolling up/down.
Other programs I tried:
- While waiting on Raz's response, I went ahead and tried using other RK3066 root programs and none of them worked. I tried "Superoneclick", "Busybox", and even tried the questionable "ZhuoDaShi 2.2.9". None of them worked. Stick with Raz's stuff in this thread. However, YMMV.
Thanks Raz!
Click to expand...
Click to collapse
No worries. I have also sourced English stock rom in other thread if you search. Zhoudashi works with English but so does the new script
I am on win764bit, I think the drivers were the reason I couldn't get zhoudashi to work and had to find another way. Enjoy! Make it easier for those scared of Chinese app or can't read root thought its quite clear in English . Haha
BTW, some devs working on updated kernel

BTW, I updated root package file earlier to include new script.

Will this method also work for the Pipo U1pro?

myvisione said:
Will this method also work for the Pipo U1pro?
Click to expand...
Click to collapse
I believe it will. I don't have a Pipo U1 pro to test. Please report back with your results for other U1 owners.
Thanks.

razmattaz said:
I believe it will. I don't have a Pipo U1 pro to test. Please report back with your results for other U1 owners.
Thanks.
Click to expand...
Click to collapse
I'm afraif I bricked my tablet after flashing CWM, every time i reboot it boots into CWM with a lot of errors like:
E:can't mount /cache/recovery/command
etc.
Help me please? :crying:

@myvisione:
I can't post links since I'm new here. Just google "Pipo U1 CWM" and there's a version at slatedroid posted that should work.
If that doesn't work, in your CWM that's giving errors, try going into the "Mounts and Storage" in CWM and mounting that share.
@Raz:
Thanks for the tip on the stock rom, very reassuring that's available if we need it.

myvisione said:
I'm afraif I bricked my tablet after flashing CWM, every time i reboot it boots into CWM with a lot of errors like:
E:can't mount /cache/recovery/command
etc.
Help me please? :crying:
Click to expand...
Click to collapse
Have you got a external SDcard present? I am 99.9% sure this CWM will work on U1. Is CWM working? It appears to be a SDcard issue...
Reinstall stock firmware using rkbatch tool and give it another shot. I don't believe you have bricked device...
I will send you a parameter file for the U1, so leave parameter option ticked when flash CWM. I am away from home until tomorrow, will send then. If you solve issue before then, let me know.

myvisione said:
I'm afraif I bricked my tablet after flashing CWM, every time i reboot it boots into CWM with a lot of errors like:
E:can't mount /cache/recovery/command
etc.
Help me please? :crying:
Click to expand...
Click to collapse
English U1 firmware;
http://www.mediafire.com/?fh6bxfaqd6a099t
http://www.mediafire.com/?7hvbfqd46evppj9
http://www.mediafire.com/?rdcsq1sab7ps1cy
Tool
http://www.mediafire.com/?5rzsadl7tmhg1d1
Power off holding power button. Hold volume down and plug into USB while still holding volume down for approx 15seconds and restore.

I got it work but took me some time and help of anonther user (thanks to him).
I did the instructions as posted in the first posting and don't know what went wrong. After installing CWM and rebooting the U1pro wasn't able to boot properly. With or without SD-Card it came only to boot in CWM. Restoring or backuping wasn't possible.
Solution:
I reflashed the *.img with RKBatchtool. But at first the tablet didn't show up in RKbatchtool. The U1 (or in my case the U1pro) has to be started with Esc + Volume+ button pressed. This was the trick.

myvisione said:
I got it work but took me some time and help of anonther user (thanks to him).
I did the instructions as posted in the first posting and don't know what went wrong. After installing CWM and rebooting the U1pro wasn't able to boot properly. With or without SD-Card it came only to boot in CWM. Restoring or backuping wasn't possible.
Solution:
I reflashed the *.img with RKBatchtool. But at first the tablet didn't show up in RKbatchtool. The U1 (or in my case the U1pro) has to be started with Esc + Volume+ button pressed. This was the trick.
Click to expand...
Click to collapse
Did the root script I provided root your Pipo U1 Pro once you solved CWM?

razmattaz said:
Did the root script I provided root your Pipo U1 Pro once you solved CWM?
Click to expand...
Click to collapse
How to solve the CWM issues? When I'm following the steps it comes to a bootloop in CWM and I have to reflash the original firmware and clockworkmod is gone.

myvisione said:
How to solve the CWM issues? When I'm following the steps it comes to a bootloop in CWM and I have to reflash the original firmware and clockworkmod is gone.
Click to expand...
Click to collapse
I thought you had solved it...
When you connect to flash cwm your device has to be in update mode (same as rk firmware flash), as you said previously volume+ for U1.
Use Google, there are posts on CWM for U1 though there is no difference in this version to U1... they re both rk3066.....

razmattaz said:
I thought you had solved it...
When you connect to flash cwm your device has to be in update mode (same as rk firmware flash), as you said previously volume+ for U1.
Use Google, there are posts on CWM for U1 though there is no difference in this version to U1... they re both rk3066.....
Click to expand...
Click to collapse
Thank you for your fast reply. When i start rkandroidtool which boxes do I have to tick?
Last time it went through but when it comes to CWM (which seems to be fine) there is no firmware installed on the device and so a reboot forces in CWM again and again. Maybe I triy with a different micro-SD inserted.

razmattaz said:
I will send you a parameter file for the U1, so leave parameter option ticked when flash CWM. I am away from home until tomorrow, will send then. If you solve issue before then, let me know.
Click to expand...
Click to collapse
If you could do so, would be awesome. I need the parameters for U1Pro. Thank you so much.

myvisione said:
If you could do so, would be awesome. I need the parameters for U1Pro. Thank you so much.
Click to expand...
Click to collapse
Here you go; http://www.mediafire.com/?kb0g7wzoyew4ymf
Extract to the rom folder of the rkAndroidtool and leave parameter checked when flash CWM.
Leave the default 3 ticked when using the parameter file; options 2,3,6
When you plug in the Pipo, rkAndroidTool should say at the bottom "Found RKAndroid Loader Rock USB".
Post back your results

[GUIDE] How to root a Sprint Samsung Galaxy Tab 3 7" (SM-T217S)

There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.

Thanks Justin! Works great. Someone should sticky this.
Luckily I had a Windows computer I could use for this, but my main machine is a MacBook Pro. I wish someone would do a nice clear walkthrough like this one for using Heimdall on a Mac.

To start I have rooted many phones but am stumped on this tablet. After getting it to start with holding the volume down and power key it stops on the downloading screen. Once I can get it to reboot I held the volume up and power key and got into system recovery. If I am not mistaken I can boot from here also. Right??

Thanks it was very useful!

Will this trigger the Knox 0x1 problem? I just got this tablet and I want to be able to take it in to Sprint for repairs if I need to.

Thanks!!!
Justin Buser said:
There are a couple other guides on here but they are mostly just links to videos or ad infested download links and none of them worked for me so this is how I ended up getting it to work. Everything I used is attached
For the more experienced readers it's simple, flash TWRP using Odin, boot into recovery and TWRP will prompt you to root.
For the only slightly experienced:
Boot into Download Mode (Hold Vol Down +Power to turn on the Device)
Unzip the TWRP Recovery Image after downloading it below.
Connect your tablet to your PC, unzip and run Odin, click the PDA button and select the TWRP md5 file you just unzipped.
Begin holding the Volume Up button on your Tablet and hit the start button in Odin (this will ensure you reboot into the new recovery)
Once in TWRP if you select the reboot option under advanced you should be prompted to root your device if it's not already rooted. If that doesn't happen for some reason you can use adb to sideload the SuperSU zip I've attached, or put it on an sd card and find the flash zip from sdcard option in TWRP to flash it.
Click to expand...
Click to collapse
Thanks for the help! This is my first root I've done myself and it works like a charm. Now my next step is to flash it to any carrier. Does anyone know how to flash the sprint device to a different carrier? If anyone could help me out, that would be greatly appreciated.

Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.

colt223 said:
Thanks for this. I finally got a couple Galaxy Tab 3's (One 210 and one 217) to upgrade my girls from their Kindle Fires.
Really needed this root to remove all the factory loaded crap.
Thanks.
Click to expand...
Click to collapse
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.

slickdealers said:
I just recently got this tablet from a deal sprint had. What version was your tablet on before rooting? Right now mine is on 4.2.2, but there is an update out. I dont want to update if it wont work with this root.
Click to expand...
Click to collapse
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.

colt223 said:
I believe it was on 4.2.2 when I rooted. I will have to double-check that when I get home tonight.
What model number do you have? I had to use a different TWRP download for each one of mine, meaning I had to find a different one for the 210.
Click to expand...
Click to collapse
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?

slickdealers said:
My model number is T217S. I tried to do some extra googling and came up with a post saying that the update after 4.2.2 installed KNOX on their tablet, which made their tablet come up with errors when trying to root. Based on your answer and what I found, I'm assuming I'm alright to give it a try. I do have one other question though. After rooting do you know if it would be possible to unroot incase I have to go back to Sprint with a problem?
Click to expand...
Click to collapse
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.

colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Just tried it and successfully rooted! I got the same message that you described about Knox. It appears when you go to update SuperSu. Thank you for the help!
For anyone else wondering about going back to stock, I found a thread to the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2512172

I found the answer in another thread. Flashing TWRP will trip Knox.

Didn't work for me
I did the TWRP stuff and all it did was trigger that warranty bit. Still no root.

colt223 said:
I am honestly not sure about going back, but I have had no problems. In fact, when I booted after root, something (sorry I dont remember if it was during root, or after) asked me if I wanted to disable Knox. I said yes, and smooth sailing ever since. I think it might have been the super user app itself that disabled it for me.
Click to expand...
Click to collapse
Yeah, same story here. After flashing TWRP then installing SuperSU first via the TWRP option by booting directly to recovery before OS after flashing TWRP through odin.....then once I clicked the SuperSU app after the OS loaded I chose first the "play" option to update SuperSU then the TWRP option to install the binary update. When it next booted it informed me that Knox was installed and asked whether to disable or not..I said yes and haven't had any problems at all...just trying to find a good ROM now^^

awesome thanxs for the info..... now if we could only get cm11 on this puppy

Root Failure, odd case
I have twins - they are both, identically:
Software Version: T217VPUAMH9
Hardware Version: T217S.04
Model Number: SM-T217S
Android Version: 4.2.2
Baseband Version: T217SVPUAMH9
Kernel Version: 3.4.0-1458241
Build Number: JDQ39.T217SVPUAMH9
Jim Trotter III-style, I-DENTICAL!
I successfully rooted one with:
1: Enable debugging
2: Boot into Download Mode (from poweroff, hold Vol Down+Power)
3: terminal: sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
4: poweroff ; boot to TWRP. From TWRP, wipe [factory reset], then install: ./root/SuperSU-v1.93.zip
With the second (apparently evil) twin, at the heimdall command, I get:
...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
On the device, the blue progress bar grows to about 2% and stops.
I even tried using a different cable in case one had gone wonky, to no avail.
I am at a total loss here.

... and SUCCEED, but via strangeways
...
So, mounting frustration.
I tried instead a slightly different version of TWRP:
$ sudo heimdall flash --RECOVERY recovery/T217S.TWRP.2.7.0.0.recovery/recovery.tar.md5
This time the result is different, but still no success:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
... but it stuck at 100% and did not continue. Device also stuck.
^C, hard reboot of device.
Tried again to double check, same result - sticks at 100%, progress bar on device sticks at somewhere around 5%.
Aware of the possible futility, but bored, I tried first one again:
$ sudo heimdall flash --RECOVERY ./T217S.TWRP2.7.0.0.flashable/recovery.img
SUCCEED.
So, apparently it has to be "knocked loose"?
Dunno. I'm in. Hope this helps someone else.

Root NB8
This won't work with NB8 EDIT: I was wrong this does work on NB8

Apparently had to reinstall the drivers a few times to get it to take on Windows. Still no clue what the issue was with Heimdall.

my lg o1 stuck at lg logo, need help

Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate

eran32 said:
Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate
Click to expand...
Click to collapse
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.

shinobisoft said:
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.
Click to expand...
Click to collapse
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?

eran32 said:
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?
Click to expand...
Click to collapse
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.

shinobisoft said:
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.
Click to expand...
Click to collapse
thanks man, now my lg o1 works

Glad to help
Sent from my LG-P769 using Tapatalk

Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
Most of you are stuck on a yellow screen with”Emergency mode!!” or the phone is not responding at all. You guys wanted a custom rom like Optimus Prime-v2 and let me tell you, this time it will work. Optimus One P500 comes with stock android 2.2 – V10a, V10b … and android 2.2.1 – V10n. They might be done for different regions depending upon the phone release and its popularity and definitely bug fixes and enhancements. To have Prime-v2 on your handset you will require V10a or V10b on your handset. Reason, V10n stock cannot be rooted easily. Rooting the handset is must if Prime-v2 is required on the device. Steps to install V10a, V10b series. I am using Windows 7 32-bit, 3 GB RAM laptop:
1. Clean your system first; get rid of LG PC suite and other stuff shown in Uninstall Program with vendor name as LG. Remove MSXML builts from the handset. Remove Nokia and other drivers if they are on system like Ovi suite etc. I also removed a lot of Microsoft runtime environments. Not sure about the reason but it worked for me.
2. LG usb device drivers, download the application B2CAppSetup.exe http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe .
3. In the Menu Bar, click "Options & Help", and click "Country & Language". Select the appropriate Country & Language. I used India and select P500 from the list that popup after you change the country and region. It will download, install and save the drivers somewhere in C:\LGP500\USB_Driver, it will prompt to open the rar files, just click and install the exes seen in them.
4. Reboot the system.
5. Right click on Computer -> Properties -> Device Manager and see for three drivers – LG android usb modem, LGE serial usb port and LG composite USB device. Disable the modem driver and reboot once again.
6. Switch off the phone and press volume up + BACK button + POWER button. Phone should turn yellow with text “Emergency Mode!!” To switch it off you have to remove the battery (I know it hurts, but that’s the only way out here). Switch off and let’s continue with the setup.
7. To do the KDZ of system you will require the KDZ software updater, links keep going off and on internet. Try searching for “KDZ_FW_UPD_EN” or “KDZ_FW_UPD_EN.7z” in Google and download the software. It should be somewhere around 2.3 MB. To use it you will required some good version of WinZip or winrar again Google it and install the 7z archive utility.
8. Install msxml.msi as the manual or readme.txt says to do so.
9. To get the V10x Official ROM, you need to first determine the ROM of your choice. List of all firmware available for LG Optimus One P500 (list of codes) http://csmg.lgmobile.com:9002/csmg/b2c/client/ezlooks_model_list.jsp?model=LGP500 , search for your country (use IE it looks sexy in it), I looked out for IND/INDIA. Download link to the ROM is http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/XXXXX/V10a_00/V10A_00.kdz where XXXX is code from list of codes. In my case it was: AINDBK. Save the file.
10. Prepare the handset by removing the SD card and boot it to emergency mode (some are already stuck on it so reading this post…: D) using the key combination stated above.
11. Connect to the PC and it should say, installing drivers’ blah… blah … your device is ready to use now.
12. Run the KDZ updater downloaded in step 7. Select 3GQCT in Type, DIAG in PhoneMode, and browse for ROM V10a in KDZ file and hit Launch Software update. Wait for somewhere around 5-10 minutes. It should say ===FINISHED=== in the log window of updater.
13. Handset will reboot, if not wait for another 5 minutes. Unplug from USB and try to switch it on.
Click to expand...
Click to collapse
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!

GameX2 said:
Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!
Click to expand...
Click to collapse
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.

shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.
Click to expand...
Click to collapse
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.

GameX2 said:
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.
Click to expand...
Click to collapse
Yep. Sounds like you're good to go

shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
12 - Start the phone again. If you get stuck in a screen with an Android and an exclamation mark ("!") in a triangle, just unplug the USB cable and the battery. Plug the battery again and start the phone. It will take 2 to 5 minutes to reboot for the first time and the boot animation will be the stock LG (your carrier's stock animation is lost for good), but chances are your phone is intact, with all it's apps and configurations working the same as before the incident. When the boot finishes, turn off the phone again and put back the SD Card you took off on the first step.
Click to expand...
Click to collapse
I really don't want to mess anything at this point.

GameX2 said:
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
I really don't want to mess anything at this point.
Click to expand...
Click to collapse
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...

shinobisoft said:
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...
Click to expand...
Click to collapse
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY

GameX2 said:
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY
Click to expand...
Click to collapse
Glad things worked out for ya And helping is what I'm here for

shinobisoft
shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks for helping NOOBS, i appreciate that!

[Q] Help with KitKat + CWM 6.0.4.6

Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!

SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.

LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.

Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime

I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!

I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/

jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.

It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!

kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..

amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.

still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​

shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.

voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)

jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need

Questions about 1st time root SM-J700P w/7.1.1

Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.

J727P
Nupid Stoob said:
Hello. I've never bothered trying to root a phone before, but getting tired of the forceware apps being a buggy PITA you can't even disable/remove, so thought it was time to root for more control.
However, there are so many old posts, old tut videos, updates to software that might be superseded by newer software by the time you get to the last page, etc. that I'm not actually sure what's what or where to start, so figured I'd ask and hopefully get accurate info from you guys/gals that are more in the loop on the most current methods using the latest software.
Phone in question seems to be a 2015 J700PVPU2BQJ2 software version w/ J700P.03 version hardware updated to 7.1.1 and it's through Virgin. I ONLY want to root the phone, and nothing more, while trying to keep the phone as close to factory image as possible., and prefer using a PC to do it. Thought Auto-Root might be way, but it looks like it's not in use anymore?
Again, I'm new to phone rooting and the lingo, so treat me with kid gloves, thank you.
Click to expand...
Click to collapse
ok you have an older phone the J700P you can start by downloading odin an twrp recovery an superSU zip you can get twrp from here !https://twrp.me/devices/samsunggalaxyj72015qcomsprint.html
an odin from here
https://mega.nz/#!nYVDXBAC!_cTWbW4_Ow8sZMWcZvO7bVwEEBFlD1DQsB5NeFhj1EY
An just google latest superSU zip to find that !
good luck !
step 1 enable oem in development settings !
step 2 put phone into download mod an flash twrp then boot into twrp recovery an flash superSU zip !

Thank you for the info. I'm presently confused. Here's what I've done:
I ran Odin and flashed with twrp-3.2.1-0-j7ltespr.img.tar. It went through successfully going off odin's message.
Vol. up + home + power. It'll eventually show a yellow triangle with the white trash can guy on it's side stating "No Command". Power + up gets the Android Recovery screen.
At this point, am I supposed to choose the Wipe Data/factory reset option? I see tuts that seem suggest I should already be in the twrp UI or something. I've tried watching vids and looking at a handful of tuts, but either they are the wrong phone, too old, the button combos show something else entirely, etc.
Thanks!

Anyone? Videos show the buttons vol. up + home + power as booting right into twrp recovery gui. For me, it's going into "Android Recovery" screen. Is there an extra step with Odin or something that I missed? Or am I supposed to wipe/boot in the Android Recovery screen and it'll boot the twrp recovery gui? If bricking something I'm not familiar with wasn't a concern, I'd be courageous with it.

I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?

J700P
Nupid Stoob said:
I tried the twrp-3.1.1-2-j7ltespr.img.tar and same thing. Odin says it's a success. Phone boots up to normal phone screen. Videos show the person's phone booting right into Twrp recovery. Mine acts like nothing changed. Root checker says unrooted. The Twrp app says unrooted. OEM Unlock and Debugging options in phone are selected, and I have it set for manual updates.
Anyone have an idea what's going on here?
Click to expand...
Click to collapse
Ok when flashing twrp with Odin first uncheck auto reboot in options flash twrp pull battery replace battery an boot into twrp an flash superSU zip then reboot system !

Thank you so much Peter! That did the trick THANK YOU :good:
For posterity to anyone else w/limited root knowledge with a SM-J700P Virgin variant running 7.1.1 (and what was most recent factory updates until this point); Flashed the twrp-3.2.1-0-j7ltespr.img.tar again w/o auto reboot in options of Odin, pulled battery once safe (i.e. you get the "Pass" message from Odin confirming everything went as planned) to get out of the downloading screen, replaced battery, booted the recovery (vol up + power + home) and it finally booted into the twrp recovery gui. Selected the "Install" option, then went to where the supersu.zip was stored on the SD (I created a separate "supersu" folder via PC connection for easy locating; internal phone memory card looks to now be unlocked, so can most likely use that if you don't have a SD card). Checked the "reboot once installed option" in the gui box and swiped to install supersu,zip and verified it was rooted via app after phone fully booted back up.
BTW, If anyone gets a hang/crash in Odin immediately after trying to select a twrp tar image in the "AP" box, try downloading the twrp image via PC instead of the through the phone (the legit twrp site that has the repository of past/current .tar), and just put it somewhere like Odin folder on desktop. Somehow, mine were getting corrupted via phone download through the twrp app, and Odin would NOT recognize the file was bad/corrupt when trying to select it via the AP box and hangs instead of giving a warning message. I ran into this earlier on then noticed the file was too small for some reason after viewing it on my PC, hence the Odin hang that needed a task manager kill.

I hate to necro an old thread but I still do not want to create an entire new topic for a single question. If I was to follow this info will it wipe the phone or will it simply root it while keeping all data on the phone? I ask as it is my wife's old phone and she would be pissed if I wiped her apps and everything on accident since she wont be able to remember what she had.
Edit: also when I add the TWRP file to odin it immediately hang/crashes like OP mentions but I am already DLing via pc. any thoughts?