Database Info

[ROM] Stock 2.1 Hero Update zip from RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe

Since some people were interested I've made a stock update zip from the RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe so you can flash via recovery.
This is just for those who want a completely stock rom to work off of or those that can't or don't want to run the RUU. If you want something already tweaked then use DamageControl. I'm not trying to start a custom rom I just did this for a couple people that wanted it.
It does not include the new hboot or radio.img included in the RUU and the system is stock except for adding busybox, patched su and sh.
To use su you need to install Superuser.apk.
Busybox is not installed by default you can do that through a terminal app or adb executing su and running "busybox --install /system/xbin".
You must be rooted and flash via Amon_ra recovery. Recommend nandroid backup and wipe/factory reset before flashing.
Here is a link to my post on how to make an update zip from the RUU.
Download link for the update/rom:
http://dl.dropbox.com/u/6022412/zen-hero_0.1b.zip
The link might be down since dropbox just suspended my public links due to excessive traffic.
Alternate download:
http://www.4shared.com/file/YqMmKAzL/zen-hero_01b.html
This is a link to my google code site where i put up some of the binaries/scripts that I use for rom making. These are linux binaries. If you download them put them in your path so you can execute them from anywhere. Also make sure you chmod them to executable. If you don't know how the google can tell you.
http://code.google.com/p/zen-droid/downloads/list
Due to recent events I just want to say that the devs here put a lot of work into getting you guys these leaked roms. They risk their credibility and their sources risk their jobs. So have some respect and remember it's just a phone.

Thank you,I'm sure a lot of people were wanting this.

What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!

Roman G said:
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Click to expand...
Click to collapse
For people not running windows and for people that don't want to risk flashing hboot or the radio.img.

See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!

Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.

obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
crazy, his link says zendroid in it too
http://code.google.com/p/zen-droid/downloads/list

obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
Yea I thought that was kind of funny. Nice name for a rom though

yeah well, I thought it had a nicer ring to it than fengshuidroid.... was going for a rom which was also centered around a nice clean theme to the sense ui. I'm still making headway on the project.

Re: [ROM] Stock 2.1 Hero Update.zip
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app

theclawpr said:
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
Click to expand...
Click to collapse
yes you need root and a recovery image

Roman G said:
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Click to expand...
Click to collapse
Interesting! What is the new PRI that you have now?

raynda said:
Interesting! What is the new PRI that you have now?
Click to expand...
Click to collapse
2.10_003 I believe it's the one that damage had that no one could figure out where he got it other than the official release!

okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?

rgildoss said:
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
Click to expand...
Click to collapse
adb shell
cd /sdcard
flash_image recovery blah.blah.blah

smw6180 said:
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
Click to expand...
Click to collapse
error
flash_image: not found

rgildoss said:
error
flash_image: not found
Click to expand...
Click to collapse
Thats because the flash images is not called blah.blah.blah

VinceOB said:
Thats because the flash images is not called blah.blah.blah
Click to expand...
Click to collapse
i know that ...lol
ever i try i can not load the damn recovery image ...
power + menu gives me a picture of the phone with ! .....
how can i load the recovery image ?
The phone is rooted but just wont take the revory image

Now this might be a stupid question, but do we need Root for this? I have a friend who's terrified of Rooting but really wants 2.1, so could he just Flash this through the Stock Recovery Image, or should I force him to Root?
Edit: NVM sorry I just read the 1st post on page 2. Told you it was a stupid question.

It seems like the flash_image command is missing.

Rooting the RUU 2.1 Sprint Leak

I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127

I guess you missed the sticky at the top.
http://wiki.xda-developers.com/index.php?pagename=CDMA Hero Guides

Thanks so much I appreciate it

amdme127 said:
I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127
Click to expand...
Click to collapse
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?

regaw_leinad said:
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?
Click to expand...
Click to collapse
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
becuase when you used the ruu, it overwrote the custom recovery image with the stock test 2.1 recovery image.
You'll have to load the flash_image file on the phone and chmod it. Then flash the custom recovery again. I think I saw a guide somewhere in here.

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
If you run the .exe it rewrites the recovery.

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
Already answered

So is it true that you can gain root access through ADB!

danknee said:
If you run the .exe it rewrites the recovery.
Click to expand...
Click to collapse
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.

Roman G said:
So is it true that you can gain root access through ADB!
Click to expand...
Click to collapse
Yeah, but, you don't have busybox installed, so you can't do really anything in adb shell.

regaw_leinad said:
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.
Click to expand...
Click to collapse
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image

danknee said:
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?

regaw_leinad said:
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?
Click to expand...
Click to collapse
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well....without the RUU...lol.
The bootloader is modified, so you can't just RUU the old fashioned way.
smw6180 said:
If it doesn't work, try this post: http://forum.xda-developers.com/showpost.php?p=6013606
It's basically going to stock without using the RUU.
Click to expand...
Click to collapse

danknee said:
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well.
Click to expand...
Click to collapse
cool thanks

http://forum.xda-developers.com/showthread.php?p=6142928#post6142928
I wrote up a tutorial on how to root any 1.5 based Hero using the Sprint 2.1 leaked test RUU. This might help.

Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help

amdme127 said:
Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help
Click to expand...
Click to collapse
he posted how to fix that right above you...
http://forum.xda-developers.com/showpost.php?p=6151388&postcount=12

Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again

amdme127 said:
Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again
Click to expand...
Click to collapse
No problem

[Q] is there a way to unroot and lock the bootloader again ?

is there a way to unroot and lock the bootloader again ?

quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.

but as of now no way to flash the stock recovery

slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.

distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery

slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi

can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !

distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?

quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.

slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.

distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery

slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).

distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse

quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod

got it all working now thanks to you and distortedloop .
thanks a lot guys.

New to Nexus, stuck in Fastboot! Please Help!

Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???

Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686

Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.

matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?

zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.

matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)

zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.

matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse

Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.

matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.

zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!

matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?

Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!

matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!

Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App

Successful root and unlock, can't get past splash screen :( Help

Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.

sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?

im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)

Over 500 posts and people still don't know what threads to post questions in...
Thread reported

Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.

sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2

gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium

Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?

sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.

blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.

xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.

sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?

You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2

wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.

sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2

AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?

Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!

sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.