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.
Related
I'm running a 100% stock sensation and the OTA update hasn't hit my phone yet.
Is there an easy way to install it from my sd card? I read somewhere that i'd need to boot into recovery, but I can't get that to work either.
Any help would be greatly appreciated.
download the zip file
rename it to update.zip
put it on the root of your microsd card.
boot into recovery.
either TURN OFF FAST BOOT in the power menu and turn off phone, or pull the battery and put it back in
hold down volume down and power.
you'll get into bootloader.
use the volume buttons to go up/down and select recovery. press power to select.
you'll get triangle with ! on it.
press power then volume up real quick/at the same time
you'll get the stock recovery.
go down to select install update.zip.
Download the OTA to the root of the sd card. Then take batt out. Put batt back in. Then hold- vol down + power. That will take to you the hboot menu. Let it look for the .img and then it will take you to a new menu. From there click on 2nd icon, recovery. It will either start for you or you will get a red triangle. If you get the red triangle. press vol up+ power. then click on update from sd card, then click on the update file. Hope this helps.
Edit- I was too slow typing
Root folder would just be /sdcard if I'm using root explorer, right?
Can't get it to work, I'm sure I'm doing something stupid and not realizing it.
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
RuizGT said:
Root folder would just be /sdcard if I'm using root explorer, right?
Can't get it to work, I'm sure I'm doing something stupid and not realizing it.
Click to expand...
Click to collapse
Yes. If you have custom recovery, it's not going to work. Has to be stock recovery.
mtbaird5687 said:
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
Click to expand...
Click to collapse
Did you rename the zip file to update.zip?
nxt said:
Yes. If you have custom recovery, it's not going to work. Has to be stock recovery.
Click to expand...
Click to collapse
That's what I'm using. Phone is still stock.
Yep I renamed it to update.zip. Below is what shows up right after I click 'install update from sd card'
--Invalid Operation--
success rebooting by reasonem-00
mtbaird5687 said:
Yep I renamed it to update.zip. Below is what shows up right after I click 'install update from sd card'
--Invalid Operation--
success rebooting by reasonem-00
Click to expand...
Click to collapse
Same here.
This is really frustrating, I hope it doesn't affect my ability to get the OTA update.
Does anyone have any idea why we're getting the "Illegal Operation" error?
I didn't rename the OTA. It kept it as it was.... all though one thing that I did notice was that I would continue to get an error until the OTA was at the top of the list... Sounds weird but just keep trying.
Ok, on my phone when it downloaded the update, it put it in the /download/ folder on my microsd card.
You guys should try that maybe.
nxt said:
Ok, on my phone when it downloaded the update, it put it in the /download/ folder on my microsd card.
You guys should try that maybe.
Click to expand...
Click to collapse
I'll try that right now.
nope, same thing.I'll try to re-dl and keep the regular file name.
Double edit; tried the full file name in download folder, same thing again.
nxt said:
download the zip file
rename it to update.zip
put it on the root of your microsd card.
boot into recovery.
either TURN OFF FAST BOOT in the power menu and turn off phone, or pull the battery and put it back in
hold down volume down and power.
you'll get into bootloader.
use the volume buttons to go up/down and select recovery. press power to select.
you'll get triangle with ! on it.
press power then volume up real quick/at the same time
you'll get the stock recovery.
go down to select install update.zip.
Click to expand...
Click to collapse
Do you know which one I would need for Canada's Virgin Mobile and where I can find it? I tried Searching and I couldn't find it.
mtbaird5687 said:
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
Click to expand...
Click to collapse
I am getting the same error.stock ROM never rooted...may be European update don't work for Asian....
Sent from my HTC Sensation Z710e using XDA App
Asian HTC Sensation Z710e
no go for me either. I get a same error message...
I've used OTA file for European and also US T-Mobile phones. It just wont work on my (Asian WWE) HTC Sensation.
It seems like I am destined to wait until end of September before I get my update...
I have purchased my phone at negrielectronics.com
Any other users of this version of Sensation? What's your experience?
I gave up, did s-off, and did a 1.45 based rom instead, heh.
I was lucky enough to get the OTA today and the other errors I had didn't prevent me from getting the update.
Good luck guys!
mtbaird5687 said:
I was lucky enough to get the OTA today and the other errors I had didn't prevent me from getting the update.
Good luck guys!
Click to expand...
Click to collapse
Nice. I work at a tmo retailer, the demo sensation had the ota update symbol in the notification bar when I was unplugging phones this morning, it installed fine, just pissed me off more about mine. :|
Hello there,
I've just got a Nexus S which has ICS installed. I must say I've used Android before but am no expert, especially when it comes to the whole ROM scene. While I am a very technical user, from my online research I haven't yet been able to figure out how to best go about the downgrade to 2.3.6.
My concern being that this is not stock anymore and I would not want to brick it by treating it as stock and simply following the standard downgrade or ROM flash directions.
I am attaching a screenshot for everyone to see exactly what I've got on the device.
Any help with this would be immensely appreciated!
Cheers.
Since you said you're a technical user I assume you know how to use fastboot and stuffs. To downgrade to GingerBread, you only need to install a custom recovery (ClockWorkMod) for your phone model and flash a full OTA package. I guess that's all
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
swaipa said:
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
Not necesarilly, CWM not always remains flashed and have to reflash repeatedly. Try what was recommended here, if not, download Rom manager and reflash.
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Kudos my friend, you're on to a life of flashing.. ;-)
Sent from my Nexus S using xda premium
cant go beyond recovery menu using i9023 with ICS any ideas ?
I able to downgrade from 4.0.3 to 2.3.6
Here is what I did...
http://kishanrathod.blogspot.com/2011/12/downgrade-nexus-s-from-403-to-236.html
hey
http://en.miui.com/a-1.html try this steps and it will work.
At "Downloading flashing tools and ROM pack" instead of ther rom, you should download the official OTA for your model from here http://forum.xda-developers.com/showthread.php?t=1063664.
good luck...
i have a i9023 a put first 2.3.3 and i make de update to 2.3.6.
good luck!
just a question please :
What does "install unlocked boot" or "fast boot" mean , Will it unroot the device ? and after that , If I will install a stock 2.3.6 ROM , will I return 100% factory (including the stock recovery) ?
i`ve check my recovery and it is stock like i had before.
after you finish downgrade LOCK the device using UNLOCK start bat and write LOCK instead of UNLOCK.
euskode said:
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Click to expand...
Click to collapse
im also getting this same issue from installing GB via odin.
cant work out how to fix it.
i dont fully understand swipa's instructions there
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
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
Hi I'm new to this rooting stuff but I've been rooted for nearly a year, and had TWRP on my LG G3 as well (I didn't do much with it to be honest).
For some time now, my phone has been insisting on me updating my G3 to a newer version (OTA update). I found out that this update file is located at cache/fota, a file called dlpkgfile, which I cut and pasted to some other folder, and then switched off the option about looking for updates automatically, so that it wouldn't bother me anymore.
I went to the Update Center and it still said "Update Available" like before, most likely because it hadn't yet detected the absence of the file. I thought that I'd clear this "misconception" by clicking install now, only to find it restarting, and then popping up the TWRP screen.
Now I don't know how to get out of this.
I clicked the Reboot button, which gives four options:
System
Power Off
Recovery
Bootloader
I tried all of them, only to see this same TWRP thing pop up.
Please do help me. Thanks in advance.
Hold power button for 10 seconds the will turn off and then start it again
Sent from my LG-P765 using Tapatalk
I think it is trying to flash a file that does not exist. You need to be pretty careful with OTA updates when you have a custom recovery installed.
If the solution above does not work, try wiping cahe and reset. If not, try to backup and then install this backup.
That's what I would do. Hope it helps!