• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [How To] Root 2.3.4/downgrade and Get S-off

Status
Not open for further replies.
wifi errors are typically from module/kernel mismatches. not sure exactly how it happend,but flashing a new rom should fix it. might want to upgrade yourself to the GB radio also,while youre at it :)
 
scotty85 said:
...flashing a new rom should fix it....
Click to expand...

Okay, Thanks again for all the amazing information, so I have ROM Manager Premium, and when I select "Check for ROM Updates" I get: "The ROM you are using does not support OTA Updates. The developer of this ROM needs to make the appropriate changes so their ROM support OTA update. Please contact the ROM developer! Please DO NOT contact ROM manager: THIS IS NOT A ROM MANAGER BUG."

So, I guess I would do this through the "Download ROM" and then "Install ROM from SD Card"?

Again, thanks for EVERYONES help!
 
i would actually refrain from using rom manager,at lease until you are savy in manipulating things in recovery manually.

rom manager is an app,in a working rom,and thus will not always be available to you. example: stuck in a bootloop. or stuck in a rom with no marlet or way to side load apps. or a rom that freezes.

the only way to fix issues when you cant boot to a working OS and retrieve rom manager in some way will be in recovery.

recovery(clockwork or amon) is a seperate space in phone memory,and will always be available to you,unless you run an RUU or somehow purposefully remove it.

so my advice would definately be to use amon or clockwork recovery at first. once youre comfortable with that you can use rom manager if you still feel the need to,but i perosonally do not. back when i was using my inc daily,it was nice to have rom manager premium on my phone so it would notify me when a new cm7 nightly was available :D but i never used it for anything else... i would go home and download the rom with my pc,then flash it manually in recovery. nowa days i do not even keep rom manager on my phone at all. :eek:
 
Okay, just tried to root. Everything went smoothly until I got this message:
ClockworkMod Recovery v5.0.2.0
Waiting for SD Card to mout (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
Error verifying extendedcommand.
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Click to expand...

Any help here? I can't get out of ClockworkMod Recovery. I've tried to choose "reboot system now" and "power off" but it just goes to the black screen with the hat.


***EDIT***: okay, I rebooted and installed the newest version of ROM Manager. Everything is okay now (I think). I downloaded Root Check Basic and it confirms I am now rooted.
 
ousuxndallas said:
Okay, just tried to root. Everything went smoothly until I got this message:


Any help here? I can't get out of ClockworkMod Recovery. I've tried to choose "reboot system now" and "power off" but it just goes to the black screen with the hat.


***EDIT***: okay, I rebooted and installed the newest version of ROM Manager. Everything is okay now (I think). I downloaded Root Check Basic and it confirms I am now rooted.
Click to expand...


You press the trackball when in recovery, not the power button (that will take you back or give you the hat).
 
Quick update: was able to finish with rom manager pro using these instructions: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore

that fixed my wifi issues and I love cyanogen mod 7! Everything I wanted and then some!!! only issue I had was with visual vm and used the apk i found on this thread: VZW Visual Voicemail for GB/CM7? - xda-developers

good luck everyone else and thanks for everybody's help. with CM7 I see what all the root hype is about!
 
Ok add another person who has succesfully downgraded rooted and gained S-off,flashed my radio to back to 2.15.10.07.07, and restored my back up to get me back to where I was before I started. Awesome write up!!, worked for me!! now that I have S-off anyone have any suggestions on what custom rom to use or custom recovery?

*also when I restored my backup should I of done a data wipe in clockwork beforhand cause I forgot to, will that cause any issues?
 
im pretty out of the loop when it comes to roms,but for recovery i use amon on all my devices that its available for,including the inc. i personally feel it is safer,more reliable.

i usually do wipe data when restoring,but the restore should do it automatically for you,so you should not have any issues :)

if you like AOSP roms,cm7 is very stable on the inc,definately chek it out :)

im glad the guide was helpful :cool:
 
rkern2 said:
Quick update: was able to finish with rom manager pro using these instructions: [Complete Guide] How To Flash A Custom ROM To Your Android Phone With ROM Manager + Full Backup & Restore

that fixed my wifi issues and I love cyanogen mod 7! Everything I wanted and then some!!! only issue I had was with visual vm and used the apk i found on this thread: VZW Visual Voicemail for GB/CM7? - xda-developers

good luck everyone else and thanks for everybody's help. with CM7 I see what all the root hype is about!
Click to expand...

awsome! im glad youre enjoying your "new" phone ;)

definatley check out my advice above,however,and learn how to wipe,flash and restore in clockwork recovery before continuing to use rom manager,as when an issue pops up(part of rom-ing-youll eventually hit a boot loop or something :eek:) you will need to use clockwork to fix it by reflashing,or restoring a backup,and youll save youreslf a moment of panic by allready being comfortable with what to do :)
 
scotty85 said:
im pretty out of the loop when it comes to roms,but for recovery i use amon on all my devices that its available for,including the inc. i personally feel it is safer,more reliable.

i usually do wipe data when restoring,but the restore should do it automatically for you,so you should not have any issues :)

if you like AOSP roms,cm7 is very stable on the inc,definately chek it out :)

im glad the guide was helpful :cool:
Click to expand...

Ok cool thanks for the response :) Also do you have a link for Amon recovery for the inc? Dont have time to hunt for it, gotta get to work here real soon,

Thanks,
Dan
 
dlahmeyer said:
ok cool ty :0 So as far as CM7 goes whats the difference between Cm7 and the nightly roms?
Click to expand...


Nightlies are experimental versions that are built every night (features will be added and removed) until a stable version is released. Basically the night lies are the betas in between stable releases and the final release version.
 
I can't get root to come back on my Dinc. Here's where I'm coming from:


  1. I rooted while on the original 2.2
  2. My root was preventing me from getting the Gingerbread OTA, so I installed the RUU image manually, with the full knowledge that I would (temporarily?) be losing root.
  3. The Gingerbread flash went perfectly.
    • Android version = 2.3.4
    • Baseband version = 2.15.10.07.07
    • Build number = 4.08.605.2
  4. I confirmed in the HBOOT menu that I'm still at S-OFF (I'm a noob at this stuff, but this is really important, right?)


I'm sure I've been running through these instructions correctly, but after three tries I still get no root. There are no problems, and unrevoked finishes with "Done". The final text I see on the phone is this:


ClockworkMod Recovery v5.0.2.0
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
Error verifying extendedcommand.
Error processing ROM Manager script. Please verify you have ROM Manager v4.4.0.0 or higher installed.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
Click to expand...
The phone reboots fine. But when I'm back to the home screen, I still don't have root access.

FYI -- After trying several times, I just rebooted back to HBOOT, and I still have S-OFF.

:confused:
 
Okay, I'm rooted just fine (thanks for the thread!!).

However, when I try to downgrade, I get an error when I get to the sd card. It tells me it can't chmod.

I typed in:
chmod 0755 /data/local/flash_image
Click to expand...

It tells me:
Unable to chmod /: Read-only file system
Click to expand...

I was at the # prompt as well, not the $.

I've read through this thread and didn't find any answers. Sorry if this has already been addressed and I missed it.
 
ousuxndallas said:
Okay, I'm rooted just fine (thanks for the thread!!).

However, when I try to downgrade, I get an error when I get to the sd card. It tells me it can't chmod.

I typed in:


It tells me:


I was at the # prompt as well, not the $.

I've read through this thread and didn't find any answers. Sorry if this has already been addressed and I missed it.
Click to expand...


Did you type the su command and get the prompt on your phone to allow superuser permissions? (Sounds like you are)

And are you typing in the command before the chmod command
Code: 
cd /data/local

Copy and paste your adb session here...you are probably just messing up on something small.
 
sdrawkcab25 said:
Did you type the su command and get the prompt on your phone to allow superuser permissions? (Sounds like you are)
Click to expand...

i feel like this tripped me up once as well... IIRC,the promt will change to "#",but unless you actually allow the superuser prompt on your phone,you wont have root access.

may need to clear data in superuser,and start the adb commands over.

as sdraw said,a copy/paste of your entire cmd window will likely help us figure out what went wrong. :)
 
Thanks so much for the instructions -- tried this last night (using method 2, couldn't root with method 1), got stuck in a bootloop, reflashed 2.3.4....went back and started over this morning, and I'm now successfully back to 2.2 and S-OFF. Unrevoked didn't turn S-OFF but I flashed the tool and that worked.

Now...CM7, I think.
 
I'm trying to -install the drivers as described on unrevoked page but I get an error message "Windows encountered a problem installing the driver software for your device. Windows found driver software for your device but encountered an error while attempting to install it. Android Bootloader Interface. The system cannot find the file specified".
And yes, I did choose "Browse my computer for driver software" and picked the Android USB Driver folder.
I'm running GB 2.3.4 with S-On and I'm trying to downgrade to Froyo so that I can root the phone and gain S-Off in order to install a custom Rom.

Can someone help me please?
 
what am i doing wrong to get "base system device" instead of "android 1" with the devise manager? I am unable to update the drivers any help please!
 
sdrawkcab25 said:
Did you type the su command and get the prompt on your phone to allow superuser permissions? (Sounds like you are)

And are you typing in the command before the chmod command
Code: 
cd /data/local

Copy and paste your adb session here...you are probably just messing up on something small.
Click to expand...

Okay, now I can't even get that far. Here's a shot of where I'm at:

Code: 
c:\mini-adb_inc>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT07EHJ03323    device


c:\mini-adb_inc>md5sums mtd0.img

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
mtd0.img                                       34307be744275f1db1dd16af04c37839

c:\mini-adb_inc>md5sums flash_image

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
flash_image                                    0098a7dd6600b55fac34fc6645be5d7a

c:\mini-adb_inc>adb push flash_image /data/local/
1579 KB/s (76044 bytes in 0.047s)

c:\mini-adb_inc>adb push mtd0.img /sdcard
failed to copy 'mtd0.img' to '/sdcard': Is a directory

c:\mini-adb_inc>
 
ousuxndallas said:
Okay, now I can't even get that far. Here's a shot of where I'm at:
Code: 
c:\mini-adb_inc>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT07EHJ03323    device


c:\mini-adb_inc>md5sums mtd0.img

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
mtd0.img                                       34307be744275f1db1dd16af04c37839

c:\mini-adb_inc>md5sums flash_image

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb_inc\]
flash_image                                    0098a7dd6600b55fac34fc6645be5d7a

c:\mini-adb_inc>adb push flash_image /data/local/
1579 KB/s (76044 bytes in 0.047s)

c:\mini-adb_inc>adb push mtd0.img /sdcard
failed to copy 'mtd0.img' to '/sdcard': Is a directory

c:\mini-adb_inc>
Click to expand...
You are forgetting the / at the end of /sdcard should be
Code: 
adb push mtd0.img /sdcard/
 
Status
Not open for further replies.
Back
Top Bottom