Database Users

Up shat creek

Did the 1 click root successful and loaded up cyanogen 6 and then tried thinking I was a big dog and screwed around and f'd up my phone,it won't get past any of the recovery screens,I will link what I have gone through over at nof.net,sorry for the link but I suck at typing because it takes me forever so please read,also I will paypal 20 bucks who can get me out of this debacle. Thanks.
oops can't link cause I'm new but If you are kind enough to go to nexusoneforums.net and read it ,It's titled In deep doodoo.
Basically it won't boot past the x no matter what i do,but I can see everything is still on my memory card through my laptop

direct link to his post
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/8483-deep-doodoo.html

thank you
10 char

I think you need to locate a stock, signed update zip file and put it on your sd card. I'd do this seperate from the phone. Take the card out and put it in your laptop or whatever you have to read it.
I'd then get back to where your were on page four of your other thread where it says apply update zip.
you don't know if you have the stock recovery img still? or Ra or clockwork?
your phone isn't broke, I wouldn't worry too much.
You also don't know if you bootloader is unlocked or not?
heres frf91 full if you choose to go this route http://www.mediafire.com/?xniymzimojg

Stock ROM's here: http://www.mediafire.com/n1passion
Sounds to me like you need to relax a little and read a bit more before jumping in with both feet... Rooting isn't necessarily for everyone.

I won't ever ever attempt this again.

Macklessdaddy said:
I won't ever ever attempt this again.
Click to expand...
Click to collapse
ahh don't do that! I don't even want to begin to count how many bootloops I've had, I'm pretty sure I've seen more of that X than I have of my home screen. I think once you've messed up once and had someone help you to fix it it kinda implants into your head how to fix it in the future. My only advice for future attempts is to Nandroid backup (make sure you have atleast 1 sure working back up, then do further updated back ups along side it)

Can someone tell me which file I need in post #5 for a tmobile n1.Thanks

http://www.mediafire.com/?xniymzimojg

jbrinkley,I downloaded the file and put it on the memory card,but I'm still getting the same x screen,anything else I can try.

I won't ever ever attempt this again.
Click to expand...
Click to collapse
The only way to master something is through multiple failures
Sent from my Nexus One using XDA App

Somebody help me,I had no clue this phone meant so much to me.

wrench115 said:
The only way to master something is through multiple failures
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I don't want to fail with my phone.Trust me when and If I get it working I will stay in my lane and leave the rooting to you guys.

Flashing back to thw original stock rom should fix it there's a link posted above. Atleast it worked when I had a g1 and royally screwed up. I would try that first.
Sent from my Nexus One using XDA App

I cant,or obviously don't know how to flash back to the original rom.Don't mean to sound ungrateful but it appears nobody is reading about the problem I'm having ,again I'm stuck at the x and can't get out.

I will paypal 20 bucks to the person who helps me out of this mess

OK, relax... take a deep breath... and try this out...
1. Download a full ROM zip (e.g. Passion-EPE54B.zip) from http://mediafire.com/n1passion
2. Pop out your SD card and pop that zip onto your SD card, be sure to rename it to PASSIMG.zip
3. Boot into bootloader mode (power off -> trackball + power)
4. The phone should pick up the PASSIMG.zip and ask you if you would like to update it... select yes!!
This will restore you to the stock EPE54B image, you can then download the FRF91 OTA or re-root you phone...

Craig,I downloaded the file from post#9 and renamed it PASSIMG.zip and went to bootloader and the x came up again,do I need to use the 54 one you were talking about to get to 91,sorry but I'm smartphone illiterate as hell.I get a message that says no image or wrong image
If I try to apply sd card update I get this message
failed to open\sdcard\update.zip(no such file or directory)
E signature verification failed
Installation aborted
Does it matter where on the memory card the file is at?

what we don't know is what recovery you have, if you bootloader is unlocked or not.
I don't know anything about that one click method. if you have a nandroid file on you sd look in there and see if you have actual backups.
and now i can't remember if you got to the restore menu or not.

jbrinkley said:
what we don't know is what recovery you have, if you bootloader is unlocked or not.
I don't know anything about that one click method. if you have a nandroid file on you sd look in there and see if you have actual backups.
and now i can't remember if you got to the restore menu or not.
Click to expand...
Click to collapse
bootloader not locked,under clockwork mod I see recovery and there is 3 backups under recovery

[Solved] T-Mobile OTA My touch 3G Update Files 1, 2 and 3 (?).

File 1 http://android.clients.google.com/packages/ota/tmobile_opal/894fb8631db9.hboot-1.33.0013.opal.zip
File 2 https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
File 3 (Still Not sure what this file is)
https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
Here are the correct downloads. This update only works on the Original My Touch 3G. Not the My Touch 3G 3.5 or Fender Version.
I took these instructions from Smapdi's Post
Renamed 894fb8631db9.hboot-1.33.0013.opal.zip to update.zip and placed it into the root of my SD card. Rebooted into recovery and flashed it (Turn on with Home then Power Key to boot into recovery). The process restarted the phone a few times (DO NOT TOUCH THE THING ONCE YOU START THE FLASH!!!!!) and eventually booted into 1.6.
I rebooted into fastboot and saw HBOOT was now 1.33.0013 :-D
I then took e059adc603a3.signed-opal-ota-60505.e059adc6.zip and renamed it to update.zip and put it into the root of the SD card deleting the previous file. Repeated the same steps as before and the phone did the whole restart itself a few times thing and eventually booted to 2.2!!!
Great work guys!
Thanks for everyones help I hope you enjoy Froyo 2.2.
Stingerrray

Stingerrray said:
File 1 (I Think) https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
File 2 (I Know) https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
The downloads worked for me can someone confirm that theses are the correct files. And maybe help with installation.
Thanks "Phateless"
Stingerrray
Click to expand...
Click to collapse
I do concur, the Philly Cheese Steak is quite delicious, however I find that nothing beats a good Cheeseburger!

Which one is which?
And do they need to be flashed in a specific order?

File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.

Stingerrray said:
File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.
Click to expand...
Click to collapse
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?

Foo_Blyat said:
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?
Click to expand...
Click to collapse
actually the I believe the first file is the spl and would be flashed first. Be careful.

XfooYen said:
actually the I believe the first file is the spl and would be flashed first. Be careful.
Click to expand...
Click to collapse
i thought file 1 should be flashed first aswell but to me it looked like the 2.2.1 update since theres a "FRG84-from-DMD64" line in the code.
anyone else care to maybe back that assumption up or throw in your own 2 cents, wouldnt mind a few opinions before i flash these files.
Both downloaded, both have been put onto the root of my sdcard. Just waiting on a guiding light before i boot into stock recovery and flash

I also have the files ready but I dont have the guts to flash. I barely use the MT3G lately but I dont want to risk a brick.

negative
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..

has anyone tested these file yet with success?

PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"

PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
I got the same error message and installation aborted. I tried file #2 first. Rebooted and went back to normal. Mytouch 3g stock.....
Same thing happened when I flashed #1 .....

Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
Before you continue being an ass had you thought about he is someone that upgraded from a mytouch 3g to a vibrant and still has his old mytouch? That is exactly what I did and I am still trying to update my mytouch.

Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
My Vibrant runs off MT3G roms ...
On a serious note .. I have an original MyTouch 3g, a Cliq, a G1, and a Vibrant ... usually just lurk around these forums and try not to intervene too much because people are quick to become trolls on this site .. then they complain when no one will help them .. gee i wonder why ... learn to be a little nicer, and maybe we can get some work accomplished as a whole ...
and just to clarify, I tested this on an original MyTouch 3g, 1.33.006 SPL, (stock) and unrooted DMD64 build.
This made me think that a "...*** from DMD646" update file would work. I'll be sure to keep my testing to myself so i can avoid trolls like you.

Don't get your panties in a bunch...
I already tried 1.5 -> 2.2.1 and both builds of 1.6 -> 2.2.1, doesn't work in any order

I've tried to update with both files no luck. They are definitly part of the update. I did notice from an earlier post with photos that one file was looking to the system cache file for the other file. So just a thought maybe both files need to be in place before the update can take place. Maybe this could be the problem. Any thoughts on this?
Stingerrray
Sent from my T-Mobile G2 using XDA App

I thought that the first update was supposed to be 300-400kb? Where did you discover this link out of curiosity?

I saw the file name in another post with a view of a botched upgrade due to root. put the file name in the url for the other update and it was a valid url.
Sting
Sent from my T-Mobile G2 using XDA App

The post was here.
http://forum.xda-developers.com/showpost.php?p=8687201&postcount=175

First off any time you want to test if a file is legit or not ( coming from htc/google ) you can just test the keystore via command prompt if the java development kit and runtime is in your system path. Don't remember the code off hand.
Second I would really suggest either using someone elses update script or at least replace/delete most of it. As well as install su and busybox. Because it won't run in a custom recovery.
Enjoy if you can!

( GUIDE ) Custom SPLASH1 on CDMA Desire.

I'M BEING VERY CLEAR HERE-THIS IS FOR CDMA DESIRE ONLY, NOT GSM!!!
You have to be S-OFF to do this.
Because the CDMA desire does not have extended fastboot yet, this is the only way to change the ( white with green HTC ) screen to a custom splash1 ( anything you want ) screen.
Giving credit where its due, I'd like to thank:
Team unrevoked for S_OFF
MRE-net for his guide with the .img converter tool and half of his how to that I was able to use, I will put his link in here.
ipfreelytech for his encouragement and unknowingly pointing me in a direction that made sense.
The only part I played in this is bringing these together and finding the right way to create the .txt file.
If I missed anyone, feel free to point it out.
I'm going to make this quick and simple but explain in detail so no one should have a problem but not to where you have zero legwork yourself; it took me 3 weeks to figure this out.
Requirements: my android-info.txt file
MRE-net's nbimg coverter tool
And whatever flavor archiver tool to make the .zip
Download this-[URL=http://www.4shared.com/document/ymcXsiz-/android-info.html]android-info.txt[/URL]
Go to this link http://forum.xda-developers.com/showthread.php?t=795132,
download NBIMG command-line splash<-->image converter tool for your platform, read how to use the nbimg tool in command prompt ( extremely easy ). Read his how to thoroughly but PAY NO ATTENTION TO THE FASTBOOT PORTION!!!!!!!!!! Basically don't bother past #8.
Now, after you have converted it with nbimg tool, you want to zip up the android-info.txt and the splash1.img you created together and name it PB99IMG.zip ( exactly how I have it underlined ) and place it on the root of your sdcard. Reboot into booloader ( which on my phone the screen goes straight to fastboot ) the fastboot screen has the word FASTBOOT highlighted in RED, and below it a little, BOOTLOADER is highlighted in BLUE. If thats what you see then hit the power button once and you should see HBOOT highlighted in BLUE under the phone info. Give it a few seconds ( 10-15 ) and you should see this:
Parsing...(SD ZIP)
(1) SPLASH1
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
You want to hit vol up obviously and when you do it happens very quick, almost instant and then hit vol up again to reboot and BAM, you should see your new SPLASH!!!!!!
Now for those who this didn't work for, its NOT the .txt file. More than likely its a bad archive or you didn't do the image right, so I don't want a lot of negative feedback because people can't figure it out. I have changed mine a couple times before I wrote this up, WORKS GREAT!!!!!!!!!
Note: If your baseband differs from the mainver: in the .txt file then edit it to what yours is before you make the .zip or it wont work.
ENJOY GUYS!!!!!!!!!!!

why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?

Rastaman-FB said:
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Click to expand...
Click to collapse
So far nothing else worked on cdma. The tool or manual commands. I'm going to try this out after work. Thanks for finding this!

Definatly going to give this a shot after work as well. Thanks for figuring this out.

Rastaman-FB said:
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Click to expand...
Click to collapse
Currently the CDMA Desire does not have extended fastboot commands, despite having s-off. The Alpharev team is working on getting it working so this is our only method available for now

It totally works! Thanks lohp75 for doubting me when I said it couldn't be done lol

Like I said bud, doubt creates possibilities .
Sent from my HTC Desire CDMA using XDA App

heavymetalmage said:
Currently the CDMA Desire does not have extended fastboot commands, despite having s-off. The Alpharev team is working on getting it working so this is our only method available for now
Click to expand...
Click to collapse
my bad mate, as you had s-off i assumed they would have included extended fastboot commands

AWESOME!!!! very easy to do just sounds difficult. thanks for getting it working and posting for us all!

You guys are very welcome :+). Its good that I am able to contribute back to the community instead of being a full time mooch . And like I said in the post, I detailed it so everyone should understand how to do it, but it will be so much easier when extended fastboot comes available to us!
Sent from my HTC Desire CDMA using XDA App

Ok I have followed this guide exactly.. I have done and re done the picture in Photoshop, tried converting it with several file converters, and they all get the same result...
That is the file I made.. I changed the baseband to coinside with my device (US Cellular HTC Desire)..
And it completely refuses to flash the zip. There are some error messages that pop up VERY quick, what I can see, says no image in zip.. but its there... converted with the tool...
Any ideas???

Well bud, the only problem I saw with it is you must not be s-off. If that's the case then go to unrevoked.com and get what you need for your phone. I looked in your zip and for ****s and giggles flashed it to my phone and it worked as smoothly as mine does. Of course I had to flash back to mine. So your zip is good.
Cythrawl said:
Ok I have followed this guide exactly.. I have done and re done the picture in Photoshop, tried converting it with several file converters, and they all get the same result...
That is the file I made.. I changed the baseband to coinside with my device (US Cellular HTC Desire)..
And it completely refuses to flash the zip. There are some error messages that pop up VERY quick, what I can see, says no image in zip.. but its there... converted with the tool...
Any ideas???
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App

good job! I knew this would work, glad you figured it out. Rocking a custom splash on my phone now

lohp75 said:
Well bud, the only problem I saw with it is you must not be s-off. If that's the case then go to unrevoked.com and get what you need for your phone. I looked in your zip and for ****s and giggles flashed it to my phone and it worked as smoothly as mine does. Of course I had to flash back to mine. So your zip is good.
Sent from my HTC Desire CDMA using XDA App
Click to expand...
Click to collapse
Yes its S-Off.... I have Cyanogen Mod on it... I can do everything else except change the boot splash...... I am at a loss why it's not working for me.... Followed the guide exactly...
EDIT::: Just tried the Unrevoked FOrever patch too.. still the same issue....
This is what the Bootloader says:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.0000
MICROP-051e
TOUCH PANEL-SYNW0101
RADIO-2.05.10.06.29
Jul 5 2010, 19:14:11
Everything seems right and correct... Oh well... I give up...

Does it give you the option to update, or does it flash a bunch of crap real quick then back to hboot? Maybe try and redownload my original. txt file and don't modify it at all, zip it up and try again. I was able to flash yours without changing the mainver: surprisingly.
And the unrevoked that you did was through recovery right?
Cythrawl said:
Yes its S-Off.... I have Cyanogen Mod on it... I can do everything else except change the boot splash...... I am at a loss why it's not working for me.... Followed the guide exactly...
EDIT::: Just tried the Unrevoked FOrever patch too.. still the same issue....
This is what the Bootloader says:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.0000
MICROP-051e
TOUCH PANEL-SYNW0101
RADIO-2.05.10.06.29
Jul 5 2010, 19:14:11
Everything seems right and correct... Oh well... I give up...
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App

lohp75 said:
Does it give you the option to update, or does it flash a bunch of crap real quick then back to hboot? Maybe try and redownload my original. txt file and don't modify it at all, zip it up and try again. I was able to flash yours without changing the mainver: surprisingly.
And the unrevoked that you did was through recovery right?
Click to expand...
Click to collapse
yes it does exactly that.. flashes up a bunch of crap real quick then back to HBoot.. And yes I applied the Unrevoked forever with recovery too (which told me I already had S-OFF). I have also tried it with your original text file (which is why I edited the baseband as I thought that was the issue)..
Its pretty odd that it doesnt work at all.... its got me totally scratching my head atm.... Im gonna try a couple of other things, but I think I wont be able to do it until the next release of Unrevoked that allows the Fastboot stuff like the GSM Desire...
EDIT:: Just tried removing all zips from the root of the SDCard and only have the PM99IMG.zip there.. Still the same result...

Ok, when I first started to play with this I got the same thing. I uploaded the zip to ipfreely who then told me it was corrupt, if he couldn't open it then phone can't right. So the next night I stopped using my windows environment and went back to using the mac osx archiver and tried it again. This time it showed flash errors, that told me the zip was good but info bad. So now I strictly use my mac and that's also where my cs5 is at.
Point being don't give up. Two more suggestions, try a different archiver, and as stupid as it sounds download your zip attachment from your post straight to your phone, again sounds stupid but exhaust all possibilities!
Cythrawl said:
yes it does exactly that.. flashes up a bunch of crap real quick then back to HBoot.. And yes I applied the Unrevoked forever with recovery too (which told me I already had S-OFF). I have also tried it with your original text file (which is why I edited the baseband as I thought that was the issue)..
Its pretty odd that it doesnt work at all.... its got me totally scratching my head atm.... Im gonna try a couple of other things, but I think I wont be able to do it until the next release of Unrevoked that allows the Fastboot stuff like the GSM Desire...
EDIT:: Just tried removing all zips from the root of the SDCard and only have the PM99IMG.zip there.. Still the same result...
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App

lohp75 said:
Ok, when I first started to play with this I got the same thing. I uploaded the zip to ipfreely who then told me it was corrupt, if he couldn't open it then phone can't right. So the next night I stopped using my windows environment and went back to using the mac osx archiver and tried it again. This time it showed flash errors, that told me the zip was good but info bad. So now I strictly use my mac and that's also where my cs5 is at.
Point being don't give up. Two more suggestions, try a different archiver, and as stupid as it sounds download your zip attachment from your post straight to your phone, again sounds stupid but exhaust all possibilities!
Click to expand...
Click to collapse
Tried 2 different archivers now.... WinRAR and 7zip... both same result.. I will get round to putting a Virtual Linux box with Virtualbox and try it with that... I all also try winzip just to be sure...... Not giving up just yet...

To be honest, thinking about it, if it was the archiver I was using then it should not have worked (my archive) on your phone either. The fact that it did, says its nothing to do with the Archiver otherwise you would have had the same result as me....

Cythrawl said:
To be honest, thinking about it, if it was the archiver I was using then it should not have worked (my archive) on your phone either. The fact that it did, says its nothing to do with the Archiver otherwise you would have had the same result as me....
Click to expand...
Click to collapse
I know I had an issue the first time around because I named the file PB99IMG.zip which really made it PB99IMG.zip.zip and it didn't show up. Probably not your issue but just a thought. Maybe you'd like to post the image, your baseband version, and we can make a file, test flash it and repost it for you to verify it works. Then, if it still doesn't work, we know it is your phone and possibly an issue with s-off that you may have to alert the unrevoked folks to. Try mounting /system to rw while booted and see if that works. That would be an indicator whether s-off is truly working.

[Q] another noob with a rooting issue

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.

Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App

when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.

I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.

thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?

98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .

Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.

98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.

This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium

Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem

98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.

both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.

98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".

Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!

now i'm off to screw something else up!

[GUIDE] 2-step unroot back to stock 2.3.4 from s-off and ANY ROM

I noticed a lot of people asking "How do I unroot back to stock 2.3.4 with s-off bootloader when the ruu's will not work with s-off bootloader?"
So in light of this there is a simple way to do this without installing the froyo PG06IMG.zip and going through the hassle of downloading all the firmware OTA's to get back to stock 2.3.4 firmware. I have used this method and it works great. You must be rooted with s-off for this to work. If your running a custom rom that is not sense based or based of the stock HTC sense roms, attempting to run a RUU will fail which makes this method usefull for anyone on any rom
More information can be referenced from HERE
Requirements:
Note: if you rooted using the method from HERE then you should already have all the requirements for this to work.
1) Windows
2) Android SDK
Once you download the sdk place it in the root of your C: drive and rename it to something easy like "android" or "sdk". Go into your sdk\tools folder and double click on the android file or right click on the file and select open. It should open a command prompt and then load the sdk.
INSTALL PLATFORM-TOOLS ONLY!
3) Download and install HTC Sync necessary for drivers in using adb and fastboot
4) Install a md5 utility like WinMD5Free for checking the hashsums of the files.
===============================================
Unrooting back to stock 2.3.4 firmware
WARNING: This will completely unroot your device. I or xda will not be held responsible for anything that may occur to your device if you do not follow the instructions properly. You have been warned!
5) Download the 2.3.4 hboot
Check the MD5sums of the file hboot_0.99.0000.img: 3008853f805b107fda434ce623f43318
If the MD5sums do not match the above numbers DO NOT CONTINUE
Place the file in your platform-tools folder in the android sdk
6) Download the 2.3.4 ruu
Note: MUST DOWNLOAD THIS FILE ON WIFI ONLY BECAUSE OF THE SIZE
Check the MD5sums of the file RUU_Speedy_S_Sprint_WWE_2.77.651.3_Radio_1.08.01.0111_NV_SPCS_2.97_01206_PRL60674_release_237263_signed.exe:
6e624a8ab1e1caa523a547c1fa54953b
Again if the MD5sums don't match the above numbers DO NOT CONTINUE
7)Plug your phone into your usb cable to your PC and make sure "USB debugging" is enabled on your device under Menu >> Settings >> Applications >> Development
open a cmd prompt (start button then type cmd and enter) and cd to your sdk\platform-tools folder.
Example: cd C:\android\platform-tools or cd C:\sdk\platform-tools
8) adb reboot bootloader
Make sure the device is in fastboot mode (a lot of times it's not). It should say fastboot in red letters on the top.
9) fastboot flash hboot hboot_0.99.0000.img
10)fastboot reboot-bootloader
If all goes well you should see "s-on locked"
11) Make sure your phone is in fastboot mode once again. Next run the ruu file and follow the instructions to install the factory images of 2.3.4
Congrats your phone is now back to stock 2.3.4 :victory:

I just unrooted my phone yesterday using the 2.3 RUU. Well actually I accidentally used the 2.2 RUU first and when I realized I then used the 2.3 RUU. It worked fine for me doing it that way.

BigSplit said:
I just unrooted my phone yesterday using the 2.3 RUU. Well actually I accidentally used the 2.2 RUU first and when I realized I then used the 2.3 RUU. It worked fine for me doing it that way.
Click to expand...
Click to collapse
This isn't for getting to 2.3.3 it's for 2.3.4...
And you can't even use a ruu on s-off because the bootloader verification fails.

Oh sorry, it wasn't the RUU, it was the 2.2 PGxxx zip I flashed in fastboot first. Then used the 2.3 RUU. Same outcome, back to factory 2.3.4 in 2 steps.
...And now it's time to re-root since they replaced my touch screen right there on the spot... I was surprised

BigSplit said:
Oh sorry, it wasn't the RUU, it was the 2.2 PGxxx zip I flashed in fastboot first. Then used the 2.3 RUU. Same outcome, back to factory 2.3.4 in 2 steps.
Click to expand...
Click to collapse
No not two steps... This is much faster and easier. And stop changing your story lol. Don't like the method don't use it...

i thought you could RUU with s-off?

VICODAN said:
i thought you could RUU with s-off?
Click to expand...
Click to collapse
It's basicly the same as this:
http://androidforums.com/evo-v-4g-a...evo-v-4g-ruu-flashing-guide-unroot-guide.html
Execpt for we're not doing fastboot oem lock'ing our bootloaders. We're just straight up flashing the locked s-on 2.3.4 bootloader so the ruu can think we're already on a stock firmware even though we're not.
Edit: if your running a custom rom attempting to run a ruu can cause a lot of issues which makes this method a lot easier for everyone OP updated with more info.

It appears the link to the 2.3.4 hboot file is dead! Any way you could re-upload it? Please and thank you!

capn-tightpants said:
It appears the link to the 2.3.4 hboot file is dead! Any way you could re-upload it? Please and thank you!
Click to expand...
Click to collapse
Link is fixed I accidentally deleted it from mediafire :laugh:

My screen broke and I need to return my phone to Sprint. I spent 3 hours looking through other unrooting guides until I found yours. Works flawlessly. My most sincere gratitude to you.

Peon the Professional said:
My screen broke and I need to return my phone to Sprint. I spent 3 hours looking through other unrooting guides until I found yours. Works flawlessly. My most sincere gratitude to you.
Click to expand...
Click to collapse
Thanks glad it worked out for you. Please hit the thanks button on the OP if it helped you.
Sent from my HTC Evo Shift using xda premium

No luck
I flashed the hboot, and it seemed fine through there, but cannot get the RUU to work. It keeps telling me that the usb connection isn't connected. Any thoughts?

dyebhai said:
I flashed the hboot, and it seemed fine through there, but cannot get the RUU to work. It keeps telling me that the usb connection isn't connected. Any thoughts?
Click to expand...
Click to collapse
Sounds like your missing some drivers. HTC sync or pdanet? Did you follow all the instructions?
Sent from my HTC Evo Shift using xda premium

RTFM - Then more problems
sparksco said:
Did you follow ALL the instructions?
Click to expand...
Click to collapse
Boy do I feel like a tool. The answer, of course, is no. I hadn't installed HTC Sync.
That said, it still wouldn't update the thing.
"The ROM Update utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again."
Error[131]: Customer ID Error
So, who has any idea why this happens?

After you flash the 2.3.4 bootloader you need to reboot bootloader so the rom utility can see the new bootloader as one it recognizes. After that you should be good to go.
Sent from my HTC Evo Shift using xda premium

Anyone have alternate links for the OP? It's kinda urgent
Thanks really appreciate it
---------- Post added at 03:18 PM ---------- Previous post was at 02:56 PM ----------
I found the RUU but still can't find the Hboot file. if anyone has it I'd greatly appreciate it.

bbedward said:
Anyone have alternate links for the OP? It's kinda urgent
Thanks really appreciate it
---------- Post added at 03:18 PM ---------- Previous post was at 02:56 PM ----------
I found the RUU but still can't find the Hboot file. if anyone has it I'd greatly appreciate it.
Click to expand...
Click to collapse
I had them, but I can't remember where I put them. Needed to create a seperate folder and didn't . You might want to PM Sparksco, see if he'll repost them.

I'll put the on too manager beta tonight. Apparently my Dropbox account was almost banned for too much traffic from these files. Luckily they just suspended it for 3 days. Didn't think it was in that much demand as hardly anyone post on this thread.
Sent from my Nexus 7 using Tapatalk 2

Links updated to goo.im

Thank you.
TEAM MiK
MikROMs Since 3/13/11