Database Info

[Q] HELP!!!

Ok, I think I totaly screwed up my captivate. I was trying to update to froyo 2.2 using the Odin one click method, but that didn't work, so instead I tried to instal it by following this guide on youtube (can't post link - new user)
after I did the adb reboot recovery my phone went to the recovery screen. heres what all it says:
update media, please wait...
update media, finished
#MANUA MODE#
--applying muti-csc...
installing muti0csc
mps_dat val:SER
copy_multi_carrier from: SER
multicsc : can not acces to /system/csc/SER/system/
copy_common_data
I tried to select any of the options in recovery mode, update, fatory reset, etc, but I can't select it. I know you're suposed to use the power button to select, but it does nothing. I think its because of the firmware shown on that website, where you would typically use a home key to select.
Please help! I've been working on this thing for hours and I'm completely lost! Is there anything I can do to fix it, or is it totally bricked?

ok my phones now restarted, and its running froyo 2.2, however its turning the wrong orentation and I'm note sure if I can use restart recovery. I just want to put this thing back to factory software!

use the odin 1 click for stock firmware and to update you dont go into recovery you go into download mode

Thanks! I got it back up and running now. In the progress of restoring my backups. Man after this mess, I'm just going to wait for froyo 2.2 to come out...

is my nexus S bricked? please help. :(

Hi guys,
I was trying to unroot my nexus S using the guide found here (http://forum.xda-developers.com/showthread.php?t=1088494&highlight=unroot)
After clicking start on odin, it started to do its thing and then it failed all of a sudden. and now im stuck on the yellow triangle Downloading screen. I press and hold power nothing happens. i dunoo what to do. I am a complete noob. someone please help. I am attaching the image of the what the screen looks like (http://postimage.org/image/3dhtlidg/)
and here what odin looks like now (http://postimage.org/image/3eqh3vpg/)

ok guys, i took out the battery and put it back on and turned it on again and it powered on but now i have no signal or empty bars. it shows aeroplane now.. i tried different sims no difference.. i get no service.. i think this odin fail at radio damaged my radio somehow..someone please advise me.. please .. i did volume up button + power and tried to go to recovery but i get triangle with exclamation mark. so i took out the battery and reboot it to normal. no signal. just the aeroplane icon. Also when i put the phone in USB mode, i see folders like clockworkmod and im able to see my back up that i made before doing all this. However not able to access it in the phone. I also see that all my apps and everything is gone, but i still some apps folders in the usb mode. what should i do?

First, your link goes to a NxS 4G guide, but you state you got a NxS (non-4G). Which one you got?
Following is for the __NxS only__ (as I have no experience with the 4G):
If a little Droid is holding the "triangle with exclamation mark" then that is normal as you're accessing the stock recovery, press vol up + power again to see the recovery.
Once done that go here and get a full rom flashable zip for your device. Get a "signed" version if available as those are flashable via stock recovery. (*) Put the zip on your sdcard, reboot into recovery again, wipe everything the options allow you to, install zip from sdcard, reboot. You're done with an unrooted, stock phone.
If there's no "signed" you gotta flash the cwm recovery via fastboot first (USB drivers seem to be working and your phone is recognized). Go mount and storage and choose "Mount USB storage" Then continue after the (*) and leave out the reboot after putting the zip on your sdcard.

yeh crap i just realized.. i used the guide for nexus s 4g.. i have the gsm model (non-4g). from here in canada. damn i feeel so stupid... fml..
ok so behind the battery the sticker says my phone model is I9020A and then I went to the page yu asked.. and i found the following two of interest.
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
My phone before all this mess occured was on GRJ22 build. So can i use the 2nd one here since its official and signed whereas the first one is unsigned. and like u suggested i should try to find a signed rom.
next question, how do i "wipe everything the options allow you to" ..
also when i do vol up + power and scroll to recovery and press power.. google logo comes up and then the droid with white triangle that has exclamation mark. I just cannot load into recovery :$
sorry for being so noob at this :$ But thanks for helping...

Breathe.
No, you cannot use the second flash "Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader" This is not for the I9020A variant.
I can tell you how to get everything back to stock. Are you willing to unlock the bootloader? There is no full signed rom for the I9020A.

You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.

Oh okay. yes please I am willing to do anything to get this phone working to normal. and by the way, when i do volume up+power, i see locked stated - unlocked. doesn't that mean my bootloader is already unlocked. I also see the lock icon along with google when i turn on the phone.

cool6324 said:
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Click to expand...
Click to collapse
okay so basically i start following the guide from the point it says Installing the ClockworkMod Recovery Image since my bootloader is already unlocked.
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
also for flashing cyanogen mod, i would choose the "method via recovery" right since my phone is not really rooted right now. I don't have the ROM manager app. Thanks a lot cool6324

The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
Click to expand...
Click to collapse
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.

rentaric said:
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
Click to expand...
Click to collapse
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand. Also, when i go to download the CWM recovery. it says NS4G, so is this again for the sprint 4G model? or it also works on non-4g model which is what i have. I am just confirming this since I don't want to make the same mistake as above. :$

forpulse said:
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand.
Click to expand...
Click to collapse
The linked guide's result is equal to mine if you don't flash the CyanogenMod, but the rom cool6324 linked. Just make sure you get a full rom for _your_ device this time

rentaric said:
Copy the rom on your sdcard (needs to be in the top folder). C
Click to expand...
Click to collapse
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...

forpulse said:
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
Click to expand...
Click to collapse
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App

rentaric said:
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Good Morning,
Alrighty, I think I have understood everything now, although, I'm at work right now so I will begin the process 8 hours later today and get back to you with the results... thanks for being so patient...

Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..

forpulse said:
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
Click to expand...
Click to collapse
Glad to hear it worked out for you to some degree. Sadly I have no solution to the not workign sensor part. See, I'm not pro myself, I'd just try widgetsoid app first. It got an rotate on/off function in its widget, if that wouldn't work for me I'd prolly flash another rom to see if it's the sensor trying to bully me. In the end hardware failures are still a possibility even on teh NxS.

sounds good.. no worries... i have a feeling this phone might have a defective sensor since it did not work also before with the older ROM which was GRJ22 xxkd1 ... but anyway i'll search/ask around if anyone knows anything... thanks again man...

2.3.4 Rolling Out Now

Just pulled the 2.3.4 update on my girlfriend's Thunderbolt, will report back with version numbers when done. Gonna compare to my phone which has the leak.

Just pulled it, working like a champ.

Does it break root?

Question: I'm not near a charger, noticed the update & swapped batteries, now my phone shows no update. Anything I can do?

2.11.605.3 which was leaked is the OTA according to Verizon press release and no VM is not fixed yet, I guess Verizon believes in nightly builds too LOL
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

Yes, OTA do not come rooted, download my Rom Vigor lookalike or XDAbolt in development if u want new leak and keep root.
A62335 said:
Does it break root?
Click to expand...
Click to collapse
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

Can anyone help?

googlemyahoo said:
Can anyone help?
Click to expand...
Click to collapse
Go to settings and press software update just have to wait. If it said there is an update it means it already downloaded to your phone. So its already there. Do software update if that don't work reboot phone.
Sent from my Synergized BOLT VIA XDA app
"If i helped you please thank me"

googlemyahoo said:
Can anyone help?
Click to expand...
Click to collapse
Did you already try going to Settings/about phone and then looking around in there for "updates" or something to that extant?

Yeah I've rebooted multiple times and have went to settings, that's how I found the update, it didn't just pop up on the phone.

I firmly believe that this is the same as the latest leaked build (2.11.605.3). I say this because while you got the update, I'm running the latest leak and I manually checked for the update (even did it with that 1X trick). I got no new software available. They could be rolling out the update by region, but either way I still believe the leak is the OTA.
Sent from my ADR6400L using XDA App

I'm a moron
Rooted and a noob - apparently a dangerous combination. I'm hopeful someone will take pity on me and help me out.
I immediately went to force the OTA, w/o returning to stock or reading any past advise/posts on this site about *not* updating while rooted.
The update downloaded, the phone rebooted automatically, and now it's in a cycle of rebooting, taking me to ClockworkMod Recovery.
Like the fool I am, I have no recovery file (rooted the other week and never downloaded a ROM, so never made one). Please help. This is what I see when I'm taken to ClockworkMod Recovery:
-----
ClockworkMid Recovery v5.0.2.1
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
-----
Am I going to have to do a wipe/factory reset or is there some way to recover from this?
Many thanks in advance for any help.
-Alex

stateofdesign said:
Rooted and a noob - apparently a dangerous combination. I'm hopeful someone will take pity on me and help me out.
I immediately went to force the OTA, w/o returning to stock or reading any past advise/posts on this site about *not* updating while rooted.
The update downloaded, the phone rebooted automatically, and now it's in a cycle of rebooting, taking me to ClockworkMod Recovery.
Like the fool I am, I have no recovery file (rooted the other week and never downloaded a ROM, so never made one). Please help. This is what I see when I'm taken to ClockworkMod Recovery:
-----
ClockworkMid Recovery v5.0.2.1
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
-----
Am I going to have to do a wipe/factory reset or is there some way to recover from this?
Many thanks in advance for any help.
-Alex
Click to expand...
Click to collapse
There was a huge heap of people that did the same thing back when 1.70 came out. I don't remember what the fix is... have to delete some files or something. The answer is out there, but I don't remember where exactly.

stateofdesign said:
Rooted and a noob - apparently a dangerous combination. I'm hopeful someone will take pity on me and help me out.
I immediately went to force the OTA, w/o returning to stock or reading any past advise/posts on this site about *not* updating while rooted.
The update downloaded, the phone rebooted automatically, and now it's in a cycle of rebooting, taking me to ClockworkMod Recovery.
Like the fool I am, I have no recovery file (rooted the other week and never downloaded a ROM, so never made one). Please help. This is what I see when I'm taken to ClockworkMod Recovery:
-----
ClockworkMid Recovery v5.0.2.1
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
-----
Am I going to have to do a wipe/factory reset or is there some way to recover from this?
Many thanks in advance for any help.
-Alex
Click to expand...
Click to collapse
I did exactly the same thing! Any advice MUCH appreciated!

rachbu said:
I did exactly the same thing! Any advice MUCH appreciated!
Click to expand...
Click to collapse
I could have sworn I just said the answer was out there. Ya know, I'm gonna do the EXACT same thing to bring you the answer that you'd be doing; using the SEARCH feature. But....... unlike you I don't really care because it's not my problem so I'm not going to search for the solution. Sorry.

Thank you for the quick response. Maybe b/c it's late on the east coast and I'm stressed, I just can't find this posting. I'll continue the search again when the sun rises.
If I were to flash the full RUU and Radio I found on Android Police, would it fix my phone? I realize it'll wipe it, but it'll at least be working, right?
Thanks again for the help!

Yes you can DL the ROM from android police but this needs to be flashed in HBOOT not CWR and doing this will remove CWR.
Sent from my ADR6400L using XDA App

stateofdesign said:
Thank you for the quick response. Maybe b/c it's late on the east coast and I'm stressed, I just can't find this posting. I'll continue the search again when the sun rises.
If I were to flash the full RUU and Radio I found on Android Police, would it fix my phone? I realize it'll wipe it, but it'll at least be working, right?
Thanks again for the help!
Click to expand...
Click to collapse
I don't think so because the downloaded update is stored in an area that isn't copied over or wiped during an RUU update. Besides, depending on how your rooted, you may or many not have S-off and you'll certainly loose your custom recovery.
I know I've seen this issue addressed. If nobody finds it by tomorrow I'll hunt it up and post it. I should probably put it in my QandA anyways for reference purposes.
---------- Post added at 03:35 AM ---------- Previous post was at 03:28 AM ----------
Ok... I lied. I found it and here it is. LINK Let me know if this works.

Thank you all for the responses. I stumbled upon this info just as I was ready to give up searching. Sorry I can't post the link. Method #1 worked for me. I didn't lose any data either...
Method 1: (thanks to sonicbuffalo for posting this method)
1) Once you are in ClockWorkMod Recovery, scroll down to "Wipe cache partition".
2) Select "Wipe cache partition" using the home key or power button.
3) Now, scroll down to "Yes - wipe cache".
4) Press the home key or power button to perform the wipe.
5) When done, restart your phone.
6) Your ThunderBolt will boot into the Android operating system and will say that the UPDATE FAILED.
7) Choose Cancel to stop the update.
8) Restart your phone one last time and you'll see that the "Powering Off" loop is gone.
Method 2: This will delete your data
1) Once you are in ClockworkMod Recovery, select "wipe data/factory reset" using volume keys.
2) Press home key or power button to select.
3) Answer Yes, by scrolling with vol keys and home or power key to select.
4) When phone reboots, the powering off loop should be gone.
Method 3: This only works if you have a Nandroid Backup from prior to accepting the update.
1) Once in clockwork select "backup and restore" using vol keys.
2) Select using the home key or power button
3) From next menu select "restore"
4) Choose your backup from list and select.
5) Answer yes to restore backup
6) When phone reboots the "powering off" loop is gone.
Method 4: This is a last ditch effort if all other methods fail.
1) Download the Leaked Rooted Update from HERE.
2) Following instructions in THIS post load the rooted leak.
3) When your phone reboots, the powering off loop should be gone and you should be running the latest software and still rooted.

stateofdesign said:
Thank you all for the responses. I stumbled upon this info just as I was ready to give up searching. Sorry I can't post the link. Method #1 worked for me. I didn't lose any data either...
Method 1: (thanks to sonicbuffalo for posting this method)
1) Once you are in ClockWorkMod Recovery, scroll down to "Wipe cache partition".
2) Select "Wipe cache partition" using the home key or power button.
3) Now, scroll down to "Yes - wipe cache".
4) Press the home key or power button to perform the wipe.
5) When done, restart your phone.
6) Your ThunderBolt will boot into the Android operating system and will say that the UPDATE FAILED.
7) Choose Cancel to stop the update.
8) Restart your phone one last time and you'll see that the "Powering Off" loop is gone.
Method 2: This will delete your data
1) Once you are in ClockworkMod Recovery, select "wipe data/factory reset" using volume keys.
2) Press home key or power button to select.
3) Answer Yes, by scrolling with vol keys and home or power key to select.
4) When phone reboots, the powering off loop should be gone.
Method 3: This only works if you have a Nandroid Backup from prior to accepting the update.
1) Once in clockwork select "backup and restore" using vol keys.
2) Select using the home key or power button
3) From next menu select "restore"
4) Choose your backup from list and select.
5) Answer yes to restore backup
6) When phone reboots the "powering off" loop is gone.
Method 4: This is a last ditch effort if all other methods fail.
1) Download the Leaked Rooted Update from HERE.
2) Following instructions in THIS post load the rooted leak.
3) When your phone reboots, the powering off loop should be gone and you should be running the latest software and still rooted.
Click to expand...
Click to collapse
Thank you. That's the one I was looking for, but the one I posted has basically the same info as step one.

nooby: can not update from zip file GT-P5110 4.0.4

I'm new with android.
I like to try it and put my Apple days behind me.
Never had a problem with 'rooting' it. But it’s time for something new.
I bought a Samsung TaB2 10.1 GT-P5110
After reading ( a lot ) on forums and google-ing youtube walkthroughs, I wanted to start the rooting process.
First problem ... the tablet is new but already updated to 4.0.4.
I don’t think I can undo that :-/
So I used Odin3-v1.85_3.zip and the file "GT-P5110_ClockworkMod-Recovery_5.5.0.4.tar"
All went fine but then i had to root it.
Getting into "download mode" wasn’t easy.
I think my mistake was that I have to do this immediately after I used ODIN and rebooted the tablet.
But l’ll try that later.
The real problem is that I don’t have the choice in the menu "install zip from" sdcard
im reading the toppic "[How To] ROOT- Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110 & 4.0.4 UPGRADE or OEM".
The menu i get :
Android system recovery <3e>
Volume uo/down to move highlight:
power button to select
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
This is NOT the CWM menu
I can see the external drive and can click on the file CWM-root-gtab2a.zip if i use "apply update from external storage" but it gives an error.
There is a link with "workaround at post 325. " but i dont know what to do.
The "workaround" is not for newbies i gues ?
ok.i read someware that the "Android system recovery <3e>" is not the CWM menu
Originally Posted by notoriousB
Uncheck the option to automatically reboot in odin. Upload the cwm tar file. When the upload is completed and shows green, power off the tablet using the power button. Then immediately reboot into cwm and apply the root zip file. Do not boot into android after loading cwm, you must go right into recovery and install the root package.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Now i can update the "CWM-root-gtab2a.zip" file.
Next step would be => go to CWM => backup BEFORE you chance anything.
I can only go in the CWM menu if i do ALL the steps again.
Gonna try this this evening.
Thanx in advance

rooting help
Okay, Im not an expert, but I've rooted several android devices before. Some steps that i go through to make sure that everything will go smoothly are:
0. Check the forums first with a search to see if the topic hasn't been answered before. READ EVERYTHING CAREFULLY. Most mistakes are usually user error. If you don't understand what you are doing, maybe you shouldn't doing it. Or you need to read up on it more.
1. Make sure that i have the absolutely appropriate packages to do what i intend to.
2. Make sure my Samsung drivers are up to date. You can install them with Kies or install them separately link in a development topic about rooting and so.
3. Download mode is accessed by powering off the tablet and holding volume down and the power button. Connect your tablet after you've set up the basics (pda file is correct for rooting, recovery, etc)
4. Go over everything and look for the right signs fora completed operation (PASS!, GOOD!, etc.)
5. Recovery mode is accessed by powering off the tablet and holding volume up and the power button. If you don't see the gear and top hat, chances are that you don't have the clockworkmod recovery successfully flashed. Try it again and if it still doesn't work, be as clear as you can with your next post why it doesn't.
I've the same model p5110 with 4.0.3 ICS build WALD2 and I've rooted and flash several times from stock to Rom to stock again. It's never easy the first time, but you'll get the hang of it soon.:good:

I am working on this just like you. I have rooted my phone but trying to root my p5113. The menu you are getting is the android stock recovery menu. When you reboot after rooting you cannot allow to boot up all the way or it will overwrite the cwm recover. So while you are rooting and it reboots, quickly unplug it and hold the power and left/volumn down key. That should do the trick

Yep,
Got it working.
Can manualy instal progs.
But im not sure im going keep this tablet yet.
Its a verry good tablet but,... maybe its because im an iphone user, and im used to cydia..
Keeping it for at least 1 month more before i decide.
Strange ,... there is no tomtom or garmin gps program ?
Are you guys using CyanogenMod ?
Dont see the point yet for using it.
Its fun using android do (boys and there toys ;-o )
a while later...
ByBy Iphone...Welkom Nexus

[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