{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I recently got a new Nexus One and loaded up 2.3 on it. The process is extremely simple, and doesn't require unlocking. Here's how to do it:
Download SuperOneClick to your PC. The only thing is to note is that the instructions have an extra step that should be skipped:
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF <- Don't do this part
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
From the Android Market, install Root Checker on your phone and make sure you have root access. If so, congrats, you're rooted!
Download MicroMod's Gingerbread ROM (or any ROM of your choosing) to your microSD card.
- Note: If you're not installing a new ROM and just want to use a new recovery, you need to remove two files before installing the Recovery. See this post for more info.
From the Android Market, install ROM Manager. (Thread link for more info: Amon_RA's RA Recovery)
- Select "Flash ClockworkMod Recovery" and wait for it to finish
- Select "Flash Alternate Recovery" and wait for it to finish -> this will install the latest version of RA recovery.
Click to expand...
Click to collapse
Reboot into Recovery.
- Backup/Restore -> Nand backup
- Wipe -> Wipe ALL data/factory reset
- Flash zip from sdcard -> Choose zip from sdcard -> Choose the zip of the downloaded ROM
- Reboot system now
Congrats! Enjoy Gingerbread! (And future ROM'ing!)
If you're feeling generous and you like my guides, feel free to donate.
One click doesn't work for my nexus one running 2.2.2 it gets stuck on waiting for device I turn off the phone and on while plug in to the comp and still doesn't work. am I doing something wrong?
Manual root guide...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
Why do you make people install clockworkmod first and RA then? I think CWM is just fine, it's up to the user. In any case, why not downloading RA one directly?
elegos said:
Why do you make people install clockworkmod first and RA then? I think CWM is just fine, it's up to the user. In any case, why not downloading RA one directly?
Click to expand...
Click to collapse
Because that's what the instructions say in the thread from Amon_RA himself; you know, the actual creator of the recovery. Notice it's a quote, directly from him.
Even this "Easy method" adds steps. You can skip half of your method by paying for Rom Manager and using it to flash Clockwork and a rom of your choosing.
The steps would then be to simply root (however you can), PAY for Rom Manager because it is just awesome, then install Clockwork and the latest CM7 Gingerbread nightly directly from within Rom Manager.
Clockwork and RA are very similar. I used to use RA and had no problems with it, but Rom Manager needs Clockwork to be really useful. I highly suggest paying for Rom manager and letting it do all the work.
Gaining root is the hard part. Flashing alternative roms is not. Once you root, it is smooth sailing.
Paul22000 said:
Because that's what the instructions say in the thread from Amon_RA himself; you know, the actual creator of the recovery. Notice it's a quote, directly from him.
Click to expand...
Click to collapse
Also, using flash_img in a terminal can be a little messy. CWM gives the whole process a nice GUI, even if you end up on Amon_RA.
CWM has toggles for signature and assert checks, which is a feature RA doesn't have (if it has, it's been implemented from CWM). BTW I think they're really the same thing, this is why I asked
EDIT: BTW Amon_RA created nothing but a fork of the original recovery, so he's not the creator, but a (heavy) modder
josemedina1983 said:
One click doesn't work for my nexus one running 2.2.2 it gets stuck on waiting for device I turn off the phone and on while plug in to the comp and still doesn't work. am I doing something wrong?
Click to expand...
Click to collapse
Try this: turn your phone OFF, load up SOC, then click "root" and wait till it says "waiting for device". THEN plug up your phone and power it on. That's what works for me. If that fails, download pda net on your N1 and PC and connect it. It'll install the correct/missing drivers, then use SOC as I mentioned above. That's how I rooted on 2.2.2
Sent via Tapatalk
elegos said:
CWM has toggles for signature and assert checks, which is a feature RA doesn't have (if it has, it's been implemented from CWM). BTW I think they're really the same thing, this is why I asked
EDIT: BTW Amon_RA created nothing but a fork of the original recovery, so he's not the creator, but a (heavy) modder
Click to expand...
Click to collapse
RA has signature toggles now
sitinon327 said:
Try this: turn your phone OFF, load up SOC, then click "root" and wait till it says "waiting for device". THEN plug up your phone and power it on. That's what works for me. If that fails, download pda net on your N1 and PC and connect it. It'll install the correct/missing drivers, then use SOC as I mentioned above. That's how I rooted on 2.2.2
Sent via Tapatalk
Click to expand...
Click to collapse
Thanks alot it worked like a charm.
Got my N1 from repair today with gingerbread and hboot 35. The guide isnot working for me. Please assisst
its just stuck on waiting for device. I tried doing it switched off then on but no luck. Win 7 if it makes a difference
edit: got further with installing pdanet but now on soc im stuck on
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1209 KB/s (585731 bytes in 0.473s)
OK
chmod psneuter...
OK
Running psneuter...
Click to expand...
Click to collapse
i tried toggling usb debugging but no luck
This is driving me nuts, I was trying all night yesterday and still can't root
Only gingerbread root options are unlock the bootloader or try and downgrade and root.
Rusty! said:
Only gingerbread root options are unlock the bootloader or try and downgrade and root.
Click to expand...
Click to collapse
Then why was this thread made? And how do you downgrade?
This thread was made before Gingerbread was released...
To downgrade, you follow the "Unroot/restore" guide from the wiki, using the passimg method and the FRG33 image. It works for most people, but for some reason there's a few people it just refuses to work for...
it worked for me, thanks
Thanks it worked super for me
to use Gingerbreak babe it 's more simpler..
editing-because i rooted my nexus one
this worked like charm
Related
[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice for you to localize everything, ATT users will be grateful.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.
Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?
Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604
Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.
Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
theres the moto-fastboot file i was looking for!
much appreciated.
Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.
humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.
humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.
SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight
after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way
The procedure is quite simple.
Step 1.
Download the following tools:
Cyanogen Mod 7.1 for Xperia X8 (code named Shakira)
FlashTool
FXP030 kernel (2.6.29)
Step 2.
Step 2.1
Follow the guide located here to unlock your bootloader, do this before continuing with the rest of this guide it is important to have your stock firmware rooted for this step.
Step 2.2
Unzip flashtool to its own folder e.g. /Flashtool/.
Unzip FXP030 kernel to the Flashtool/firmwares/ folder - the directory should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 3.
Step 3.1
Open Flashtool and click on the 'Flash' button, select the FXP firmware from the list on the left hand side and click OK.
Step 3.2
Follow the on screen instructions.
Step 4.
Copy the update-cm-7.1.0-X8-signed.zip to the root of your MicroSD Card as shown below. (Please note that you can do this using a MicroSD Card reader OR your USB cable.
If you do not have a card reader then switch your phone on after flashing the FXP kernel and when you see the FreeXperia logo, repeatedly press the Back button until CWM loads. Once CWM has loaded scroll down to the Mounts and Storage menu. Once on the mounts and Storage menu scoll down to mount USB Storage and copy the update-cm-7.1.0-X8-signed.zip file to the root of the SD card.
Step 5.
Load CWM via the method described in Step 4 and select 'Install Zip from SD card.' then select 'Choose Zip from sdcard' and select the update-cm-7.1.0-X8-signed.zip that you copied over to the root of the SDCard in the previous step, Select the yes option using the volume buttons and let CWM work its witchcraft.
Step 6.
Go back to the main menu of CWM and select 'wipe data/factory reset'.
Next from the main menu of CWM select 'wipe cache partition'.
Finally from the main menu of CWM select 'Advanced' and 'wipe dalvik cache.
Optional
If you want the google apps installed you can download them here. To install them perform Step 4 through to Step 5 and instead of copying 'update-cm-7.1.0-X8-signed.zip' to the root of your sdcard, copy gapps-gb-20110613-signed.zip instead. All instructions in Step 4 and Step 5 that state you should use 'update-cm-7.1.0-X8-signed.zip' should use the file 'gapps-gb-20110613-signed.zip' instead.
Notes:
I'm having issues with the networking with this custom firmware, specifically the network (3G or WiFi) seems to 'drop' after any amount of small usage. If I use a Browser or the Market place for a short amount of time, they simply end up unable to load any pages whilst android reports that wifi/3g signal strengths are full. I tested the connectivity using ping commands from terminal and pings are succesfull. I'm unsure where the issue lies. I suspect however the issue is in the FXP Kernel, some people have reported using FXP 028 Kernel resolves the issues but I've been unable to find them.
Anyway I hope this helps people who are confused as to how to install this.
Credits:
Thanks to Paschalis for correcting an error in my wording.
Thanks go to dbts25 for pointing out mistakes and un-neccessary steps in the guide, sincethen the guide has been edited to be easier to follow and less convoluted.
Thanks go to rav3n_pl for the revised bootloader bundled with the kernel.
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Paschalis said:
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Click to expand...
Click to collapse
Ah Yes, I mean stock. It's 2:34am... That's my excuse haha, between university and sleep deprivation the mistakes keep mounting hehe. Thanks for pointing that out anyways.
And yes, it seems this kernel has issues with data connectivity, and call volume as well for some odd reason. It boggles the mind as to why it's been labelled 'stable'. Stable usually means it's solid and won't fall over and die, plus data connectivity on an android handset is really a critical feature, if it is buggy the custom firmware should not be labelled as stable.
It really need custom kernel?
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
EL_BELLACO said:
It really need custom kernel?
Click to expand...
Click to collapse
Yes, if you don't use a custom firmware it will get stuck in a boot loop and be unable to boot.
Paschalis said:
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
Click to expand...
Click to collapse
If I come across it I will, I'll edit my guide to feature it as a work around for connectivity issues for people in the meantime, if it works correctly.
I've got to admit though, issues aside - it is amazing what the open source community is capable of creating. CM 7.1 looks absolutely fantastic, I love the boot animation.
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
termin8tor said:
.
Step 5.
Turn your phone on and repeatedly press the back button until you are displayed with the CWM menu. On this menu select 'install zip from sdcard' and then choose the 'choose zip from sdcard' select the cyanogenmod file you downloaded and let it do its thing.
Click to expand...
Click to collapse
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
poisike said:
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
Click to expand...
Click to collapse
Can you please share the FXP028 kernel?
has any of you tried the dx kernel yet? with cynanogen mod 7.1
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
dbts25 said:
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
Click to expand...
Click to collapse
I've edited the guide to eliminate that pointless step in the original guide version, thankyou for pointing it out!
Additionally the google apps step has been added to the end of the tutorial.
tonks22 said:
has any of you tried the dx kernel yet? with cynanogen mod 7.1
Click to expand...
Click to collapse
Unfortunately the rom will not boot with the DX kernel, I tried it myself and it gets stuck in a boot loop.
rav3n_pl said:
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
Click to expand...
Click to collapse
I have included the correct kernel for the official cyanogenmod 7.1 rom and slipstreamed your edited loader into the kernel package for peoples convenience. Thanks for linking me to your post!
Hope this helps people!
It seems that this Rom and kernel [cm7] doesn't work.When i flash the kernel my SD is not recognized.And if i uninstall the kernel and try to flash the rom...i get a biiiiigg eror
i hope that they will also make a ROM that is compatible with stock kernel so that it will be easy to install... im having second thought of unlocking my bootloader because of this:
Before I start I must emphasise the fact that meddling with the bootloader is highly dangerous and will result in a hard brick if you don't follow proper instructions. Then, you will have to go and repair your phone by sending it to SE . I am not responsible if your phone dies on you because you didn't follow instructions or you screwed up somehow. I must also mention that this will probably void your warranty (rooting already probably voided it though) and that there is NO WAY to relock bootloader as of now.
Click to expand...
Click to collapse
i know they can make one because they are great programmer...
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Paschalis said:
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
mikel_0004 said:
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
Click to expand...
Click to collapse
There:
http://forum.xda-developers.com/showpost.php?p=17656148&postcount=1
Can it be installed WITHOUT unlocking the bootloader?
Thanks
thu001 said:
Can it be installed WITHOUT unlocking the bootloader?
Click to expand...
Click to collapse
I`m not 100% sure that cm71 rom will work on stock kernel...
When I flashed it under installed CM7 it stuck on bootanimation. Mybe full wipe? Not tried.
Hello
I installed on my Xperia X8 CM7.1 (I had version 2.1 of Android root), but it does not work the WiFi network and the 3G connection is disconnected, it did not work properly Market (having installed the GAPPS). My question, is there any way to get back to my terminal to android 2.1? I did a Back up of my system, but in trying to restore from CWM mistake I make, I guess it is for the kernel.
I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.
sdavidson0316 said:
I've spent quite a while tonight FINALLY getting this MyTouch 4g (Glacier) to root and now I'm stuck in a bind.
Everything seemed to be going well and I got the Cyanogenmod 7 flashed onto the phone via Clockwork ROM Manager. Then the first time I rebooted it got to the Android logo with the spinning arrow and went into a constant loop. After about 20 minutes of this I pulled the battery and tried to restore the phone via the recovery image I created with clockwork. Here is the current status of the phone:
1. CAN get into HBOOT and HBOOT USB (but I dont think ADB can see it, or at least I haven't been able to get it to)
2. CANNOT get into recovery, phone just reboots itself to the red exclamation
3. PD15IMG.zip tries to restore the phone but fails.
What can I do to get the phone back into some sort of usable condition. I dont care where, I can start over as long as I have something to work with.
Click to expand...
Click to collapse
does bootloader show Fail-PU when flashing PD15IMG.zip?
saranhai said:
does bootloader show Fail-PU when flashing PD15IMG.zip?
Click to expand...
Click to collapse
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sdavidson0316 said:
Nope, looks to me like the equivalent of what you're asking is that it says "Fail UZ"
I've attached a few screen shots for reference.
Click to expand...
Click to collapse
It failed to unzip the update. Try redownloading the pd15img. This time verify the MD5SUM and try it again.
ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!
sdavidson0316 said:
ALrighty.....this is my st00pid face. I guess in my lack of sleep last night I forgot to check the MD5SUM.
That worked....now let's see if I can break it again!!
Click to expand...
Click to collapse
Cool Glad it worked for you.
New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!
sdavidson0316 said:
New question, essentially the same topic:
This whole thing started because I tried to flash CyanogenMod 7 onto the phone and it messed up. The phone reboots into Cyanogen and the little android on the skateboard with the arrow just goes into a repeating cycle. It will come on for 10ish seconds at a time and then just cycle back and do the same thing. I've let it go for >20 minutes and nothing changes.
Does anyone have any suggestions on how to get this ROM working? It took me so long to get it rooted with S-off that I'll be darned if I'm stopping now!
Thanks in advance!
Click to expand...
Click to collapse
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension
neidlinger said:
Verify the MD5SUM of the ROM as well. You may of gotten a bad download.
What i personally do when i download and install a new OS is
Download OS to computer
push the OS to the SD card
verify the MD5SUM
reboot into recovery
nandroid backup
factory reset
flash new OS
flash g/apps (if needed)
reboot system
to check the MD5SUM while it's on the SDcard just use the line command from either the terminal emulator or CMD prompt.
Code:
# md5sum /mnt/sdcard/<file_name>.extension
Click to expand...
Click to collapse
+1
You can also check the md5 sum when its on the SDcard using the free mand5 app from the market.
Sent from my HTC Glacier Sense 3.0 using xda premium
Thanks to everyone for helping out, I finally got it working last night when I had time to sit back down with it.
I was trying to use the ROM Manager version of the Cyanogen instructions and it ended up that that was the problem. I switched over to the recovery version based on your suggestions and it worked great.
Thanks again!
General feeling around here is that the only thing ROM Manager is good for is flashing ClockworkMod recovery. There are folks who won't even do that with it.
Sent from my HTC Glacier using XDA App
ROM manager ruined my recovery I had to completely re push recovery thru adb
Sent from my PG86100 using xda premium
Hello Friends,
The best way i found to root / install recovery for my S4 are below
Please do the steps at your own risk i m not responsible for anything that may happen to your device
Before flasing this make sure you have all drivers req on the PC best way is install kies ( make sure all kies applications are closed else u myte hvae issue flashing)
Note:all this i m sharing here is not my work but just trying to help more numbers of XDA users i m not a developer but a user
For Rooting (download the file from original thread below )
Click Me
Odin from Attached Files
How to install
put the device into download mode poweroff / press volume down+home+power key and connect
Open Odin
CF-Auto-Root-ja3g-ja3gxx-gti9500.tar.md5 start flashing
Do not select/tick anything else in odin
All thanks to Chainfire the Genius thank him in his thread please
For Recovery CWM "Phil3759"
Click Here
Download Recovery from above link
Unzip it, flash as PDA in Odin
Click the PDA button, and select recovery-clockwork-X.X.X-i9500.tar.md5
All thanks to "Phil3759" thank him in his thread please
All done u will have Root & Recovery both
Thanks to Chainfire :good:
Thanks to Phil3759:good:
Thanks to Odin:good:
Hope this helps
Thanks for this, but can you please tell me how come your method does not use "Cofface’s ClockworkMod Recovery"? I was reading a couple of posts on the net and saw
you have to flash the Cofface’s ClockworkMod Recovery on your device before you can root it, there’s no way around it, and is a strict requirement if you wish to root your Galaxy S4
Click to expand...
Click to collapse
.
Saw it here: http://www.redmondpie.com/root-galaxy-s4-gt-i9500-on-android-4.2.2-how-to-tutorial/
and here http://gs4.wonderhowto.com/how-to/root-your-samsung-galaxy-s4-gt-i9500-0146685/
Can someone advice?
Thanks
Paparasee said:
Thanks for this, but can you please tell me how come your method does not use "Cofface’s ClockworkMod Recovery"? I was reading a couple of posts on the net and saw .
Saw it here: http://www.redmondpie.com/root-galaxy-s4-gt-i9500-on-android-4.2.2-how-to-tutorial/
and here http://gs4.wonderhowto.com/how-to/root-your-samsung-galaxy-s4-gt-i9500-0146685/
Can someone advice?
Thanks
Click to expand...
Click to collapse
I had tried using that method on my i9500 and it does not root the device even after flasing the file i cant enter recovery and it stays on stock recovery so what i did is root the cell with adam kernal and the use the Cofface recovery to have CWM
This is what i found easy for me and created a thread which could help others also
So, do we need to flash "Cofface recovery" after rooting with your method?
If yes, can you also please add "how to flash "Cofface recovery" to your original post so we can have full steps here?
Thanks
Paparasee said:
So, do we need to flash "Cofface recovery" after rooting with your method?
If yes, can you also please add "how to flash "Cofface recovery" to your original post so we can have full steps here?
Thanks
Click to expand...
Click to collapse
Yes thats the way we can do
in while i will do the changes in the thread and add recovery method also
..
I am getting this error, what does it mean ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
huzefa_from_kuwait said:
I am getting this error, what does it mean ?
Click to expand...
Click to collapse
Preferences, unselect "Run Samsung Kies automatically when a device is connected
Make sure u have kies application not running on backgroud should be close
Also try a different usb port on the computer
And if that doesn't work try a different cable
I dont have Kies installed.
I installed the drivers from "Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe"
I have tried a different USB port, now I will try on another computer.
huzefa_from_kuwait said:
I dont have Kies installed.
I installed the drivers from "Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe"
I have tried a different USB port, now I will try on another computer.
Click to expand...
Click to collapse
Possibly there cud be some driver issue install kies but keep the preferences for kies uncheck while using and try should work
On another computer the drivers are not working at all.
I have removed all drivers and installed Kies. Now its updating.
After that I will try again.
huzefa_from_kuwait said:
On another computer the drivers are not working at all.
I have removed all drivers and installed Kies. Now its updating.
After that I will try again.
Click to expand...
Click to collapse
in the main while try also flashing root method by chainfire this also works well and see whats the result
http://forum.xda-developers.com/showthread.php?t=2292615
Tried that also, same thing..
Stops at SetpConnection
Its a clear indication something is wrong either with the cable or my computer ( I can't understand what )
Mine is Windows 7 - 64 bit, however I shall format my computer and install Windows XP on it and try
huzefa_from_kuwait said:
Tried that also, same thing..
Stops at SetpConnection
Its a clear indication something is wrong either with the cable or my computer ( I can't understand what )
Mine is Windows 7 - 64 bit, however I shall format my computer and install Windows XP on it and try
Click to expand...
Click to collapse
I think windows 7 is just fine no need to go with xp
even i cant understant whats the issue, BTW u have USB debugging on rite ?
1) Disconnect your phone from the Computer
2)Open Device Manager
a)Go to Start Devices and Printer.(Windows 7)
b)Then right-click Device Manager.(Windows 7)
3)Look Down at Universal Service...
4)Expand it and look at USB Composite Device.Right-Click on it and Uninstall.
or
5)Uninstall everything in there.
6)Connect Device Open Odin and see if it works
7, Try changing USB ports that could be the main issue
Note u have to connect device in download mode
I tried CF-Auto-Root, earlier it gave me the same message but after I changed from Windows 7 to Windows 2003, things went normal.
huzefa_from_kuwait said:
I tried CF-Auto-Root, earlier it gave me the same message but after I changed from Windows 7 to Windows 2003, things went normal.
Click to expand...
Click to collapse
Oh thats nice finally
123hiten said:
I had tried using that method on my i9500 and it does not root the device even after flasing the file i cant enter recovery and it stays on stock recovery so what i did is root the cell with adam kernal and the use the Cofface recovery to have CWM
This is what i found easy for me and created a thread which could help others also
Click to expand...
Click to collapse
i did it worked perfectly! (btw at first i downloaded old version it didnt work new one works awesome!) btw this one is easiest! i rooted using other method coz the downlaod link was banned here and also i liek to ahve the CWM reovery! backups and stuff
kamranhaghighi said:
i did it worked perfectly! (btw at first i downloaded old version it didnt work new one works awesome!) btw this one is easiest! i rooted using other method coz the downlaod link was banned here and also i liek to ahve the CWM reovery! backups and stuff
Click to expand...
Click to collapse
You can have CWM that also is posted at 1st
Sent from my GT-I9500 using xda premium
NIce thread buddy. :good:
BTW i have tried rooting through Cofface recovery & got success. Also add latest ODIN 3.07 V from here.
Same thing happened with me when I was using Galaxy S3 ODIN V3.07 for rooting my S4.
So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.
anybody? pretty please? any ideas at all?
Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?
I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!
Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.
Step 9 Fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.
ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
WOO-FREAKIN-HOOOO!!!
at the setup wizard now.
Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?
Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!