Hi all,
OB software V10b, Android 2.2.2, Gingerbreak v1.2
Trying to root my OB with GingerBreak and the rooting never completes. Several times now I've let it run for an hour and it just does not complete and reboot.
Yes, SD is mounted and USB Debugging is active.
Tried powering OFF/ON and removing the battery and retrying but without any success.
Ideas appreciated.
TIA
Greg
Related
i m on a rooted n1 and after installing the 1.6 kernel (probably noob move from me) my device does not turn on (stuck at cross picture).
i can get into recovery after taking the battery off though
anyone have any suggestions to solve it?
never mind,i did a NANDROID backup and everythings fine
I've actually had this problem twice in the past two different roms (cm & enomther). Both times I had to do a nandroid restore to fix the problem.
The only connection I can make is that both times my phone was plugged into a usb port when rebooting (neither time was this after a fresh install).
Any chance you were plugged in via usb at the time?
I have 1.0.1 and used the correct autonooter and successfully rooted it. Although, after turning on and off the phone, I run into big problems. One time it got stuck in the boot screen and I had to do the 8x reflash thing. Now I'm getting the error "Battery too low to power ON. Please wait 15 minuets and try again" after charging for many hours! *EDIT* Now the reset method ("n" button, power, and +) isn't working. What am I doing wrong? I'm confused about what I'm supposed to do with the sd card. After rooting, do I leave it in for ever or do I take it out? I didn't even get adb working correctly.
Any help? Thanks
Hey everyone, new member and my first post and I need help. I have a SGS I9000 and did the same thing as "michaelg117" did in this thread: http://forum.xda-developers.com/showthread.php?t=890987
I installed OCLF and saw it needed to have a rooted phone. I installed z4Root temporary root and when I ran the OCLF lag fix it rebooted and I now have a phone that is frozen on the blank screen after the S animation.
I notice that while sitting at the blank screen I get one buzz followed by three buzzes. I assume that because of not being rooted it's the OCLF failing then being forced closed and then getting stuck in that loop.
I've been searching for any solution. The phone is only a few weeks old and I can recover my contacts from Outlook but I do have a few pics that will probably be lost if they're not already.
Is it possible to re-root the phone so she'll start "normally" with OCLF so I can then remove it and unroot back to normal? I've tried the Galaxy S OneClick Root for I9000 (by TGA Gunnman) but keep getting the following errors:
E:failed to open /mnt/internal_sd/update.zip (No such file or directory) error.
E:signature verification failed
Installation aborted
Does anyone think that being able to root would cure the problem? What other options are there for forcing a root in this condition?
Thoughts?
Thanks in advance.
Well, I ended up booting into recovery mode using ADB then doing a factory reset. Lost my pics but backed up my contacts. At least the phone still works. I think I'll wait for 2.3 to come out before I try to change anything else.
I did the same on mine but i did a recovery too. You can do the permanent one now + OCLF without any problems.
Sent from my GT-I9000 using XDA App
Hi,
I have the same problem you had: z4root temporal + OCLF = Soft Brick.
It was my fault not to check that I had access to download/recovery mode using the three buttons. But fortunately, I had the debug mode enabled and can use adb to reach recovery mode...
BUT, I was advised in another thread _NOT_ to use factory reset in this situation because then I will lose the debug mode so if things go wrong I would not be able to reach download/recovery mode with adb again. They recommend use first a 3 button combo fix instead. This:
http://forum.xda-developers.com/showthread.php?t=821698
In this way, I would not depend on only debug mode for subsequent manipulation. What do you think?
Hi i rooted my revo with superoneclick and it runs gingervolt2.0. It ran great for about 3 months? and then every time the phone dies and i turn it back on it boots into recovery mode and i have to hit reboot, after that when it reboots i get a vzw update message and when i try to update it tells me theres a problem with the update...can anyone tell me whats going on?
If you need anymore info please lmk, its 2am and im tired.
Your phone has downloaded the ZV8 update and is trying to push it at boot. It will fail every time since you're on root with cwm. Browse the Dev forum for several methods of updating to the most current build.
http://forum.xda-developers.com/showthread.php?t=1583023
http://forum.xda-developers.com/showthread.php?t=1577423
OR:
http://forum.xda-developers.com/showthread.php?t=1621625
Hiya!
Been on the forums for years modding my Nexus One and would like to thank everyone for their humongous contribution! 3 years of constant upgrading and improving of what turned out to be the best phone ever!
Now, I've come to an end where my self-confidence took over caution and preparation and i think i've made a boo-boo.
Long story short, i have a unlocked Nexus One that has been running a CM10 ROM with Blackrose for a good 6 months. Most of the functions were working fine, except for a few glitches, but last night i decided to go back to the roots, and install a stock Gingerbread ROM. I found a unrooted GB ROM, and went straight on to renaming it to PASSIMG, throwing it on card and rebooting. Now that's where the funny things started:
First, all goes well, click Volume Up, get it started, and than a screen with all OKs except for [7] BOOTLOADER - Fail-PU and a message saying 'Only Blackrose can be flashed'
Next, I get 7 OKs, except for BOOTLOADER, and the following: Partition update fail! Update fail! Do you want to reboot? Y/N
Figuring i forgot to uninstall Blackrose and need to do so, i let it restart, it comes up with a clean un-rooted GB ROM, and here's where my troubles start.
1. USB Connection: Plug it in, laptop doesn't recognize it at all. Classifies it as 'Unknown Device' and that's it. Tried fresh drivers, Universal Naked Drivers, SDK drivers, ASUS tablet drivers, nothing. Tried 3 cables, the HTC one, a Blackberry one and a Samsung one. Nothing. Uninstalled all USB hubs/devices, restarted the laptop multiple times. Debugging ON/OFF, no difference. I'm at a loss here, no clue what else to try!
2. Fine, i thought, let's flash a rooted rom! PASSIMG on the card, phone finds it, gets to the line 'Parsing... Passimg.zip' and goes back to the neutral screen. Tried it multiple times, different ROMs, nothing.
3. At this point, figured maybe an earlier ROM will cause an OTA update and fix things up. FROYO PASSIMG on the card, flashed 'succesfully', just like in #1, reboot to clean un-rooted FROYO. Checked USB connection, same again. OTA Update - constantly failed.
Been reading through Wikis and Q&A's here all day today, everything seems to be so easy to fix as long as you get a live ADB connection, and i know i could fix it, but i just can't get the laptop to recognize the bloody phone! Do not have access to another computer just now, so can't check whether it's just my Vaio.
So now, the questions:
1. Any other ideas on the USB issue? The phone does not display the usual 'choose your option/mass storage...' when connected, and nowhere in the menu is there an option for that.
2. When booting into recovery, i get the green droid with the white triangle and the !, and then get into the 3e recovery that has an 'update.zip' option. can i install a custom recovery without the phone being rooted? just of the sdcard? is there an update.zip that can re-stock my HBOOT?
any other ideas will be greatly appreciated, as of right now i am stuck with a FROYO handset that is perfectly capable of running JB, and it's really frustrating!
thanks in advance for all your help, cheers!