Related
I need help. I am a beginner. I recently rooted my phone and installed Android Revolution 4G, S-off, and everything, then flashed the power notification widget for my phone thru the recovery menu from ROM manager by selecting the zip file. It installed successfully, but when I rebooted the phone, my phone is stuck at the white screen with the HTC logo. Please help. I am able to get into recovery menu after pressing vol down button and power button at the same time when the phone is off. What do I do now? Thanks.
stuck at boot logo
Hey i just had this problem today, and i found a solution.
first press vol down and power button to get into recovery. at first you may not be able to scroll down, wait a couple secs. then scroll down to recovery then push the power button to select. the screen will flash the boot screen then go into clock work mod. now scroll to apply zip from sd card and bush power. scroll to restore then push power. now select choose zip from sd card. then navigate to the rom from clockworkmod -> download/ ->coredroidroms.com/ ->roms/ ->desire_HD/ -> release under this, i had 2 choices, the only difference between them was that 1 said update patch. you want to select the one that ends in .zip NOT THE UPDATE! follow through the process and your phone will be bootable now.
sorry forgot to mention that your case may vary a little depending on what rom you have and the location of it on the sd card. but follow the same general guide lines and you should be in good shape
This happen to me when restore a nanbackup with revolution on it, stuck in blank htc screen, so restore other nanbackup with CM7 and it work's so i don't really know what happen here.
Later change it to RCMiXHD successfully.
I am going to say this because it seems people forget. Before adding anything you flash through the recovery menu, BACKUP!!! I put in a power notifications thing also and my phone just kept rebooting over and over again. But I had made a backup just before doing this, went to recovery and restored my backup. Was right back where I started. (By the way, when I was on my captivate, I didn't follow this rule myself and lived to regret it, had to spend a day and a half getting everything mostly back to where I had it, very sad)
That being said, if you have your ROM on the SD card in your phone you can just reinstall that and it should fix the messed up system image. Depending on the system you should be good with just that, some ROMs will wipe when they are installed though so you may have to reinitialize your applications. If your ROM image isn't on the SD you could download it to your computer and put it on the SD card then install from SD in the recovery options.
Good luck, there are folks online that may be able to help as well, there is an IRC channel mentioned in the root thread and people are there often.
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Perfect!
This zip file worked perfectly on my Rogers Galaxy Rugby. Many thanks!
Happy to hear
Sent from my GT-S5690R using xda premium
Big problem now though....
So the root went swimmingly, but I got a little too excited removing pre-installed apps. I backed up and removed Samsung Home, and removed and NOT backed up SNS 1.0. The phone will now refuse to boot unless I wipe data/factory reset in recovery mode, but after that it just ends up crashing during the Android wizard start up....
This is a brand new phone, what can I do to restore those apps, and get it back to the way I received it earlier today?!
There is a way to boot into safe mode, head Google mod2extreme and I find the forum for our phones (currently the only one) find advise there
Sent from my GT-S5690R using xda premium
Thanks for the name of that forum! I've found the guide someone posted here: http://www.mod2xtreme.com/showthread.php?t=12386 and I've decided to try it.
I'm using the first firmware listed in this thread: http://www.mod2xtreme.com/showthread.php?t=11744 (S5690XXKL1 2.3.6 2011 December S5690OXFKL1) mostly because under Country/Carrier it has nothing, so I'm assuming it's more generic than the others. I'm also keeping in mind this is for the 5690, not the 5690R, so it may not work at all. But, worth a shot since my only other recourse is to break down and cry in front of a Rogers attendant to see if he can give me a new one. "Root? What's root? Like ginger?"
I'm using v.1.83 of Odin3, which is listed as supported the 5690.
Downloaded KIES 2.0 from http://www.samsung.com/my/support/usefulsoftware/KIES/JSP - It gave me two DLL registration (COM) errors during installation on Windows. Uncertain if this will end up screwing me over or not.
Be right back, rebooting now that KIES is installed... will edit this post when there's more to report.
EDIT: Yeah, so I ended up trying both Odin version 1.83 and 1.85, with the Marvell .pit file, and the firmware from that thread. I learned that I had to put the phone into Download Mode, NOT Recovery Mode while trying Odin. Even still, nothing worked. I've given the phone up to Rogers and they will try to replace the original ROM, hopefully they won't notice that I've rooted it and really mucked everything up. They said if it doesn't work they'll send it off to Samsung to get it repaired. Anyone know if they find out I rooted it, I'd have to pay for voiding a warranty or anything?
i have the same device hae you manage to get clockworkmod recovery on it?
Does this method erase all personal data/downloaded apps from phone?
Great it worked perfectly...
did you success in installing different firmware?
Thanks again
Thanks a lot, worked like a charm.
Is there a way I can install Clockwork Mod? Rom manager doesn't recognise the s5690r. It gives me the option of selecting the Epic4G or the GalaxyS i9000. will either of these work?
Also, once I get that figured out, is there any roms compatible with the s5690r? I've scoured the webs with no luck. Not a very popular phone, eh?
Thanks again.
markdexter said:
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Click to expand...
Click to collapse
Good Day, I am also working on the Bell Canada Version of the Rugby. It is the GT-s5690m model. I am now stuck in a bootloop and don't know how to fix it. I have played around with the root and unroot zip files that have been floating around but I am certain that the bootloop is due to not being able to clear the Delvik Cache. As you are aware Clockworkmod recovery is not supported on our devices. I am unsure how to get it to work. Until then I just keep trying different things to hopefully get this phone up and working. It is quite a rugged device and would be great with a custom rom and recovery. Could you explain to me in layman's terms how I might create a flashable clockwork image to flash via Odin or even through stock recovery. I would love to get this phone up and working. Thanks in advance
Sasktel Rugby
Hi there. I am working on the Sasktel version of this phone as well. I tried to change the model from R to M because this phone is the same as the bell model version but it would not install it. I found it on the external SD card but it will not run the zip file from the 3e recovery. Any ideas why this might be happening?
Thanks,
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
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
airplane888 said:
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
Click to expand...
Click to collapse
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Maybe, just maybe you didn't clear cache and dalvik when installing cm. I had this problem and I realised I didn't wipe it. I wiped cache and dalvik cache from cwm and it booted fine.
Sent from my Xperia Mini Pro
ooddiittyy said:
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Click to expand...
Click to collapse
Thanks I will look into TWRP. I am getting my ROM/gapps zips straight from cyanogenmod's wiki for my phone, i get gapps from the link they provide. As for MD5, I do not know what that is other than it was generated when i backed up, and checked when i restored.
i have the same problem
i tried it with my galaxy fit s5670
i tried to flash cm-10.1-20130117-NIGHTLY-beni, some another version named of jelly bean pure rom and also TouchWiz_JB_V5
always the same thing it gets stuck at logo than nothing
i did everithing in order clear data, factory reset, clear cache, clear dalvik cache through cwm recovery
can someone help?
is it because of low int. space?
i found app named s2e to make sd card as int. memory but it didn't work
any suggestions?
thanks in advance
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
what ROM are you coming from?
Sounds to me like the new multi-user stuff
I experienced something similar and determined that the phone wasn't hung at that bootscreen -- it was busy moving my 18 gigs of stuff (i9300) from /storage/sdcard to /storage/sdcard/0. Apparently this is the "home data" folder for the primary user of a 4.2 device and CM10.1 (I'm assuming you're using that because of the problem) appears to be that way. It would have been nice to know beforehand that I should have just waited the 1/2-hour I needed (took about that long to move back what had been moved; very little hadn't)
So look for that 0 folder and move the contents up one -- your old ROM will (hopefully) be the way it was before. If you decide to go CM10.1 again, just wait, *really* long, at first boot -- or clean out your internal sd card to make the transition quicker.
---------- Post added at 11:06 PM ---------- Previous post was at 10:53 PM ----------
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
You won't see it appear as removable storage because it's in download mode -- removable storage (and the later MTP mode) are done by the OS, and the downloader screen is much "dumber" than that.
HOWEVER, all is not lost!
Try get a ROM which you can flash with ODIN. Either something off of www . samfirmware . com (stock firmwares available there) or DarkyROM (darkyrom . com) (Sorry, can't post actual links because I'm apparently not allowed to until I've posted more stuff . I've found the S1 and S3 to be practically unbrickable in this regard -- I assume the S2 to be the same. ODIN can push a completely new ROM onto your device, rescuing it. If you download from samfirmware, there is a pdf with instructions available on their site, but it basically boils down to:
1) Download a ROM. If you are downloading a zip file, extract the .tar.md5 file inside somewhere -- this is the file you need to flash via ODIN
1) ensure you have the samsung drivers installed (they will be if you have Kies installed, otherwise google for them -- or ask, and I'll try to help)
2) put your phone into download mode (vol-down+home+power)
3) plug your phone into your PC
4) fire up ODIN, you should see a message about a connected device on-screen
5) click the "PDA" button, browse to the ROM image (the .tar.md5 file) and select it
6) the default options have always worked for me -- just click "Start". The process will take some time, but there is feedback in ODIN. Your phone should (after 1-5 minutes) reboot into a fresh, clean ROM.
If you installed a stock ROM from samfirmware.com, you'll have to go about rooting and installing Clockwork mod again. Hope this helps.
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