Develop Bugs

HELP! unable to update radio to get past network lock!

Hey,
I just updated to the 1.21... generic stock rom and since im on orange its network locked the phone. Ive looked around and it seems that flashing an older radio will sort this problem out. So i have the older radio but when i try to connect to the phone using the recovery-windows.bat file, it keeps saying "error: device not found"
I can confirm i HAVE installed the USB driver via the android sdk and rebooted my computer. The device is not rooted though
Is the lack of root the issue here or should it still be able to connect?
Thanks for your help

gyro11 said:
Hey,
I just updated to the 1.21... generic stock rom and since im on orange its network locked the phone. Ive looked around and it seems that flashing an older radio will sort this problem out. So i have the older radio but when i try to connect to the phone using the recovery-windows.bat file, it keeps saying "error: device not found"
I can confirm i HAVE installed the USB driver via the android sdk and rebooted my computer. The device is not rooted though
Is the lack of root the issue here or should it still be able to connect?
Thanks for your help
Click to expand...
Click to collapse
Yep, you definately need root access to update your Radio version.

but will not having root stop the recovery-windows.bat file even recognising the phones attached to the pc?

Yes but this is also happening because you have not yet created a Gold Card, which will unlock your CID and Device ID. Create the Gold Card first and then root your phone.
-------------------------------------
Sent via the XDA Tapatalk App

The Gold Card is needed because you have a branded phone.
-------------------------------------
Sent via the XDA Tapatalk App

im pretty sure i already turned my sdcard into a gold card. ill try rooting first then have another look at the gold card

gyro11 said:
im pretty sure i already turned my sdcard into a gold card. ill try rooting first then have another look at the gold card
Click to expand...
Click to collapse
Yes, that is precisely what you must do. Not only do you need to create a Gold Card because of your branded handset, but you also have to root it to have write access to the system partition. Once you do this, you will then be able to flash any compatible ROMs with problems.

argh, this is being a nightmare...i have redone the goldcard and am trying to do the root, but when i type the (linux) command cd /mnt/cdrom/root it says "cant cd to /mnt/cdrom/root
when i do a ls of the directory it says the folders there are boot and desire
please help, its unusable unless i can root this and get the new radio in there

gyro11 said:
argh, this is being a nightmare...i have redone the goldcard and am trying to do the root, but when i type the (linux) command cd /mnt/cdrom/root it says "cant cd to /mnt/cdrom/root
when i do a ls of the directory it says the folders there are boot and desire
please help, its unusable unless i can root this and get the new radio in there
Click to expand...
Click to collapse
To root, try this guide instead, it's pretty straightforward:
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
You flash the Radio zip file via Recovery the same way you would do when flashing a ROM.

ok, it turns out the usb lead just wasnt being consistantly connected for some reason. Ive managed to sort this out and managed to flash the new rom. However, now i have a new problem but i will put this as a new post as its different to what ive written before in this thread

OMG!! How the heck to unroot? =(

I have to exchange my EVO to Radio Shack and I just can't find a way to leave the phone back at stock settings!
I am currently rooted with Toast's method and running the Baked Snack 9.6 ROM. I have tried running the RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe file but it keeps saying that it cannot connect to the phone, even though I have tried it both as USB Charging only and Hard Drive only.
PLEASE, anyone can help me? I have SEARCHED the forums but haven't been able to find a way to do it properly.

You might have a better chance asking this in Q&A section, or else you are going to get lit up by the cops here.

Honda hit me up on Twitter
Sent from my PC36100 using Tapatalk

vboyz103 said:
You might have a better chance asking this in Q&A section, or else you are going to get lit up by the cops here.
Click to expand...
Click to collapse
LOL Ok
jiqqaman said:
Honda hit me up on Twitter
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Done!

I had the same issue and this is how I did it:
I turned off the phone. Turned it back on holding the volume down key and power key. Selected FASTBOOT, then I opened RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe and it worked perfect.
Just remember that your phone will no longer be rooted (you won't be able to can't access the recovery).

krosemm said:
I had the same issue and this is how I did it:
I turned off the phone. Turned it back on holding the volume down key and power key. Selected FASTBOOT, then I opened RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe and it worked perfect.
Just remember that your phone will no longer be rooted (you won't be able to can't access the recovery).
Click to expand...
Click to collapse
Ok, I got to the FASTBOOT link and selected it. Then it switched to FASTBOOT USB. I ran that exe file on my PC but it still says that it can't connect to the phone. It keeps saying ERROR [170]: USB CONNECTION ERROR

Get the update.zip from the RUU
I believe you can also open your temporary directory.
Start, run, %tmp%
Do a search for update.zip and copy it to your sd card and boot into recovery.
If you can't find the update.zip it MIGHT be named something else, so try searching for *.zip, or delete all your temporary files, open the RUU, and then search for *.zip.

HondaCop said:
Ok, I got to the FASTBOOT link and selected it. Then it switched to FASTBOOT USB. I ran that exe file on my PC but it still says that it can't connect to the phone. It keeps saying ERROR [170]: USB CONNECTION ERROR
Click to expand...
Click to collapse
Do you have HTC Sync running? I had it running and my phone was synced when I ran the .exe file.

HondaCop said:
Ok, I got to the FASTBOOT link and selected it. Then it switched to FASTBOOT USB. I ran that exe file on my PC but it still says that it can't connect to the phone. It keeps saying ERROR [170]: USB CONNECTION ERROR
Click to expand...
Click to collapse
I did it without the fast boot, just conect the usb cable, run the RUU and that's it, anyways, i,m uploading the update.zip so you will be able to go to stock flashing from SD
http://depositfiles.com/files/2dp2m33kp

devin.slick said:
I believe you can also open your temporary directory.
Start, run, %tmp%
Do a search for update.zip and copy it to your sd card and boot into recovery.
If you can't find the update.zip it MIGHT be named something else, so try searching for *.zip, or delete all your temporary files, open the RUU, and then search for *.zip.
Click to expand...
Click to collapse
THIS WORKED! The file was actually named rom.zip, so I renamed it to PC36ENG.zip and placed it on my sdcard. THANKS!

mikevillarroel said:
I did it without the fast boot, just conect the usb cable, run the RUU and that's it, anyways, i,m uploading the update.zip so you will be able to go to stock flashing from SD
http://depositfiles.com/files/2dp2m33kp
Click to expand...
Click to collapse
I got it done by kevin.slick's tip. Thanks for your tip aswell, my friend.

HondaCop said:
I got it done by kevin.slick's tip. Thanks for your tip aswell, my friend.
Click to expand...
Click to collapse
Trankilo mi pana!

mikevillarroel said:
Trankilo mi pana!
Click to expand...
Click to collapse
is the zip you uploaded the same thing that they used to do it?
cant get mine to work either

huge adb problemo

Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!

wow 58 views and no one has any ideas? Please help!

Try turning on USB debugging mode?

Yes its always on, always check marked

I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.

gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build

tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App

They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App

well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?

javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing

i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...

javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?

yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...

javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one

can't unroot if my device is not seen with adb in hboot / recovery

javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps

Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.

Rooting new Evo 4G - stuck at red triangle - please help!

[Edit: I've now resolved this issue. Thanks to all who helped. Please see end of thread for my solution. I've made some edits below too. When things looked bad, the solution was to remove the microSD card, copy and load a more reliable PC36IMG.zip (there are a huge number out there), and only then could I use adb when the red triangle was present. Note that just renaming stuff randomly or worrying about the USB cable isn't a proper way to come up with a solution even though I did it also (and that may be the case for some units but it can't be the general problem or solution). I'd guess there's a huge amount of misinformation out there and some people may have tried random stuff but it looks like from playing with all this, there is a method to the madness of how phone and the adb communicate, as well as how the phone loads, and once you UNDERSTAND HOW that process, all this stops being so much of a black magic.
Note that the problem I had was because I used an outdated set of instructions. Here are the ones that worked for me in the end:
http://forum.xda-developers.com/showthread.php?t=829045
Thanks to all who did reply to my message.
]
--------
I've tried literally everything I've read to get out of my red triangle situation so please help if you can. This is not your standard "hold volume up and power button" response.
I was trying to get to root using the method at evo4g.me.
And I got a red triangle after the first application of the PC36IMG.ZIP. I then held the volume up and power button and, I get a blue lettered screen with 4 options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Well, I've seemingly tried everything but I can't seem to get past this screen. I've pulled the battery out and rebooted, I go back to the above screen. Option 1 above gets me back to the same spot. Option 2 says it can't find sdcard/update.zip. I did option 3 but it does that and turns off and on and comes back to this same position. Even when I try to hold the volume button down. When I try to access this using adb, I get "device offline".
I can take the battery out, hold the volume down button, and then power on, and it takes me the through the same steps as before and I don't seem to have control over the choice of whether it should load the PC36IMG.ZIP file or not (i.e., the menu I see before it doesn't to be controllable by me).
So I'm at a loss. I really would like to finish this process and get to root, which shouldn't be too hard in my view but here I am.
I could move the SD card elsewhere and put an update.zip file on there but I'm not sure what to do here exactly so I can recover (and hopefully with root). Is this the correct thing to be thinking about? Move the SD card to another device, replace the .ZIP file, and then go from there? Is there a way to do this without moving the SD card?
[Edit: this is indeed what I did in the end. I found the correct PCIMG.zip file by trial and error.]
Thanks a lot!
BTW, I backed up all my apps on my sdcard so I should be fine right? I'm not sure what I'd need to do reinstall them.
[Edit: I lost some public keys, etc. with app reinstalls but I just had too many apps doing backups in different places and wasn't matching the right app restore to the right location in part.]
--
Backgrround: I'm new to the Evo 4G and in general new to doing stuff like rooting phones and the like, so please forgive me if my questions (or actions) or too naive. I have been using Unix systems all my life and Linux when there were fewer than 100,000 users of it (back in 1992-1993) and am extremely comfortable with it and do all my science (work) exclusively with Linux.

ramdom said:
I've tried literally everything I've read to get out of my red triangle situation so please help if you can. This is not your standard "hold volume up and power button" response.
I was trying to get to root using the method at evo4g.me.
And I got a red triangle after the first application of the PC36IMG.ZIP. I then held the volume up and power button and, I get a blue lettered screen with 4 options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Well, I've seemingly tried everything but I can't seem to get past this screen. I've pulled the battery out and rebooted, I go back to the above screen. Option 1 above gets me back to the same spot. Option 2 says it can't find sdcard/update.zip. I did option 3 but it does that and turns off and on and comes back to this same position. Even when I try to hold the volume button down. When I try to access this using adb, I get "device offline".
I can take the battery out, hold the volume down button, and then power on, and it takes me the through the same steps as before and I don't seem to have control over the choice of whether it should load the PC36IMG.ZIP file or not (i.e., the menu I see before it doesn't to be controllable by me).
So I'm at a loss. I really would like to finish this process and get to root, which shouldn't be too hard in my view but here I am.
I could move the SD card elsewhere and put an update.zip file on there but I'm not sure what to do here exactly so I can recover (and hopefully with root). Is this the correct thing to be thinking about? Move the SD card to another device, replace the .ZIP file, and then go from there? Is there a way to do this without moving the SD card?
Thanks a lot!
BTW, I backed up all my apps on my sdcard so I should be fine right? I'm not sure what I'd need to do reinstall them.
--
Edits based on trying to fix this: when I do `adb devices`, I get:
List of devices attached
HT0B6HL05287 offline
--
Backgrround: I'm new to the Evo 4G and in general new to doing stuff like rooting phones and the like, so please forgive me if my questions (or actions) or too naive. I have been using Unix systems all my life and Linux when there were fewer than 100,000 users of it (back in 1992-1993) and am extremely comfortable with it and do all my science (work) exclusively with Linux.
Click to expand...
Click to collapse
That is the stock recovery you are seeing there, does it let you do anything at all in the bootloader? If you can get it into fastboot mode you can fix it from there.

I rooted using regaw's instructions also, and also got that damn triangle, lol. Pretty sure all I did was reboot to bootloader and let it update the PC36.img again to get out of it.

xHausx said:
That is the stock recovery you are seeing there, does it let you do anything at all in the bootloader? If you can get it into fastboot mode you can fix it from there.
Click to expand...
Click to collapse
Yes, I believe so. I can let the PC36IMG.ZIP reload again and then AFTER that I can say "no" to the update and then "no" to reboot devices and I can get into a menu that says:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HSB USB
From there I can select FASTBOOT and head into another menu that says:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Trying BOOTLOADER gets me through the same HBOOT cycle where the PC36IMG.ZIP is reloaded and asked to be applied. Trying REBOOT gives me a white HTC screen (unless I need to wait a while).
Thanks! I assume I need to pull the SD card out, load it on my computer through another source, and then remove the PC36IMG.ZIP file and then replace it with something else that I can use to get rooted? Or will just removing the PC36IMG.ZIP file do it?
I'm also looking to achieve root so if I am going to the trouble of removing the SD card and putting it back, I'd like to know if if there's another PC36IMG.ZIP that'll let me have a nice version of the HTC evo that is rooted.
--Ram

I know a few people who have recently purchased EVOs and they still have Hardware version 3 and Hboot .97
what versions do you guys have on your phones?
If the hboot is still .97 you can used unrevoked forever for a full root and nand unlock.
if higher there is a tutorial on these forums for Hboot 2.02.

chris66 said:
I rooted using regaw's instructions also, and also got that damn triangle, lol. Pretty sure all I did was reboot to bootloader and let it update the PC36.img again to get out of it.
Click to expand...
Click to collapse
How did you do it?

Tuffgong4 said:
I know a few people who have recently purchased EVOs and they still have Hardware version 3 and Hboot .97
what versions do you guys have on your phones?
If the hboot is still .97 you can used unrevoked forever for a full root and nand unlock.
if higher there is a tutorial on these forums for Hboot 2.02.
Click to expand...
Click to collapse
I have:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02-0000
TOUCH-PANEL-ATMELC-03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I assume the tutorial you're referring to is here:
http://forum.xda-developers.com/showthread.php?t=829045
But I'm not sure how to get out of this particular PC36IMG.ZIP (gotten from evo4g.me) and replace it with the PC36IMG.ZIP posted in the above URL above easily, since I can no longer access this device using adb. Unless I am missing something obvious.
Well, I'm learning a lot! Thanks!
I do agree having root on these systems will be fantastic. I don't understand why it's not just a ready option. Things like tethering, etc. should be a given and built into the $10 cost or something else of the network. I'd like to port things like csh on there, and have a powerful terminal like I can get in the Mac OS X. Is there any way this is possible at all? We can get bigger and bigger microSD cards right? An entire stripped down Linux system can fit in a few gigs (but I want to be able to use it as a phone too).
--Ram

Went backward in the directions.
This the whole post that I used, pretty sure I just went backward and started again, it did take a seemingly HUGE amount of time the first time thru flashing the PC36.img
http://forum.xda-developers.com/showthread.php?t=765496
PULL THE SD CARD and put the image on the root? , lol

chris66 said:
Went backward in the directions.
This the whole post that I used, pretty sure I just went backward and started again, it did take a seemingly HUGE amount of time the first time thru flashing the PC36.img
http://forum.xda-developers.com/showthread.php?t=765496
PULL THE SD CARD and put the image on the root? , lol
Click to expand...
Click to collapse
The instructions at the above URL are what I used to get to this place with the red triangle that I can't seem to get out of. I can no longer access the phone using adb so I can't push anything. I can't access the phone through my computer right now once it has become stuck at the red triangle, this is my main issue. No access. Nothing. It just says "error: device offline" no matter what I try.
You don't think the SD CARD strategy will work?

This is where I scared the **** outta myself.....
"If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue."
It worked for me, but I don't know what hardware version and all you have.

ramdom said:
The instructions are the URL are what I used to get to this place with the red triangle that I can't seem to get out of. I can no longer access the phone using adb so I can't push anything. I can't access the phone through my computer right now once it has become stuck at the red triangle, this is my main issue. No access. Nothing. It just says "error: device offline" no matter what I try.
You don't think the SD CARD strategy will work?
Click to expand...
Click to collapse
just pull the sd card out of the evo (behind the battery) and put the new img on the root of the card.

chris66 said:
This is where I scaref the **** outta myself.....
"If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue."
It worked for me, but I don't know what hardware version and all you have.
Click to expand...
Click to collapse
Me too, but I pay for the extra warranty that's supposed to cover nearly everything, which I think should cover this.
So from the above instructions, am I to understand that I remove the sdcard out and clean it out in my computer and install a new PC36IMG?
Should I try the one from here? Even here, there are like 3 versions:
http://forum.xda-developers.com/showthread.php?t=829045
Sorry for all the questions. Normally I'd hack and figure this out without even googling it but after googling it, the amount of stuff out there is enormous which is throwing me off. I think I have like 10 versions of the PC36IMG and not sure which to go with next that'll not destroy everything and give me root! Crazy.

Tuffgong4 said:
just pull the sd card out of the evo (behind the battery) and put the new img on the root of the card.
Click to expand...
Click to collapse
Thanks a lot. Pulling the evo card was easier than I thought it would be. Which particular one? I'm looking here:
http://forum.xda-developers.com/showthread.php?t=829045
Should I just manually copy all these files over to the sdcard and then reboot and see what happens? I guess I'll try that. Thanks.
Thanks guys!
--Ram

Well, I solved this problem and am now enjoying root. Thanks to all who helped. I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=829045
But I still couldn't get past step 10. I even read the FAQ and followed the renaming suggestions (this wasn't the issue but I did it anyway) and it still didn't work. Basically the problem was that I wasn't even able to get to the shell even though I was able to use adb to push files (weird?).
So I was playing around with the EVO-recovery.zip (http://www.knowyourcell.com/htc/htc-evo-4g/evo-4g-guides/463925/how_to_root_the_htc_evo_4g.html) and ran the recovery-linux.sh script, which then put me into the green recovery screen. The rest was straight forward after that (as per the instructions at the URL above). So perhaps the difference of which adb to use was what it was, since that zip file comes with its own adb.
I am now rooted. Now what?
My wi fi doesn't seem to work, and neither does the google wireless tethering app, which is one of the reasons I wanted to root. When I run "adb shell" I now get a "#" instead of a "$" so I assume this (among other things, including the S-OFF) means I am rooted. So no wi-fi, did I trash something?
[Edit: I fixed this by installing the fresh ROM; thanks chris66 and others who helped!]
I'm just using the stock ROM provided from the URL above. Not sure what the best one to use is and how to use it.
[Edit: Stil no idea. Way too many ROMs out there. It's crazy. Fresh seems to have a good rep. It works pretty well, after one week.]
I also backed up all my apps on my sdcard, is there a way to restore them in one quick fell swoop instead of opening them one by one?
[Edit: I figured out how to do the multiselection option and apply it apps. A good file manager will do the backups for you. I went from ASTRO to ES File Explorer. Latter looks slightly cleaner. Probably better ones out there.]
Thanks to all who helped! I am excited about playing around with all this further. Only PITA is reconfiguring everything again the way I like it.
[Edit: Favourite apps are ConnectBot; Android Wireless Tether; AndroidVNC; DropBox; ES File Explorer; System Panel; --- from Ubuntu, I ADB to access stuff at the prompt which when having a # is really really powerful. Maybe I was wrong but before I put the new ROM on I didn't think the "more" command was available.]

Cool, try superuser and the wifi app from the market. Flash almost any of the newer roms, and they're already both usable, wifi and usb.
Sent from my PC36100 using XDA App

[Q] HELP FIX /dev/block/mmcblk0p1

Does anyone know how to fix an EVO that gives this error?
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD
I was flashing firerant's mtd partition to make up more space to install more apps. When I try to reboot my evo it turns on then vibrates 5 times and shuts down. I can get to hboot mode (volumen down + power). On top instead of s-off it changed to s-on. When I try to use command from my mac's terminal it says error: device not found.
I unrooted by flashing a PC36IMG.zip in hboot. Im in stock now. The phone seems to work fine but now the phone does not recognize the memory card (only in hboot mode) or the usb being plugged in. when i plug in the usb to the computer evo does not give me the notification nor charges or the light come on. Then I tried to root it but it's imposible because I still get terminal's error: device not found because the evo's usb is messed up or something. And since there is no notification to mount the memory card to my computer I can't transfer any files to/from evo.
Then I downloaded Unrevoked3 but still it does not do anything for the same reason the usb is not being detected.
Now I am unroot, evo not detecting memory card (when its on) and usb is messed up (when its on and in hboot mode).
Can Anyone please help me out. Maybe there is a zip that I can flash in hboot mode since is the only place my memory card is being read. Terminal commands through USB doesn't work in hboot or fastboot i dont know why.
Thank you so much everyone.
p.s. I am not blaming this on firerant's mod. I am just describing how it happened. I appreciate all devs work. and I am aware of their disclaimer we can brick our devices. Thank you.

pretty sure you fubar'd your internal partions there buddy.

Go get a new phone. Run over it with your car first.
Sent from my PC36100 using XDA App

Yes that's what I think. The partition is fubar'd, so there is no way to fix that?
Thanks for replying.

mrcamposd said:
Yes that's what I think. The partition is fubar'd, so there is no way to fix that?
Thanks for replying.
Click to expand...
Click to collapse
im sure there is but only by someone who knows what the hell they're doing. lol ;-)

can that person come to the RESCUE :/

lol @ the advice on here. I wouldn't exactly say I know what Im doing but I'll try to help anyway.
From a adb shell run 'cat /proc/mtd' and 'cat /proc/partitions' and that should tell you what your partitions look like. If you can copy them on to here.
Edit: Just remembered he had a custom recovery set up to use with it, were you using that to flash it? You'll most likely need that to recognize the partitions.

If you can flash a zip why not give Caulk's "format all" a try this may restore your partitions. I'm far from a dev but seems like i read about this same problem somewhere and they ran calks zip and presto all was well. I tried to find the thread but couldn't, just what I remember they flashed this then rom then kernel then radios. Of course they were rooted ... maybe rename to PC36IMG.zip ....but if you can flash a zip cant see how this would hurt.

xHausx said:
lol @ the advice on here. I wouldn't exactly say I know what Im doing but I'll try to help anyway.
From a adb shell run 'cat /proc/mtd' and 'cat /proc/partitions' and that should tell you what your partitions look like. If you can copy them on to here.
Edit: Just remembered he had a custom recovery set up to use with it, were you using that to flash it? You'll most likely need that to recognize the partitions.
Click to expand...
Click to collapse
cant adb shell in terminal it does not recognize the device. thanks though

ifly4vamerica said:
If you can flash a zip why not give Caulk's "format all" a try this may restore your partitions. I'm far from a dev but seems like i read about this same problem somewhere and they ran calks zip and presto all was well. I tried to find the thread but couldn't, just what I remember they flashed this then rom then kernel then radios. Of course they were rooted ... maybe rename to PC36IMG.zip ....but if you can flash a zip cant see how this would hurt.
Click to expand...
Click to collapse
thank you so much you are a hero... but will try this next time it happens because I went to the sprint store and told them the new update had messed up my phone hahahaha...
thank you all intelligent people i appreciate your help so much. it means a lot to me.