huge adb problemo - myTouch 3G Slide Q&A, Help & Troubleshooting

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.

Related

Please help messed up gfs evo

I was trying to root and nand unlock my gfs phone and now Im at a point where usb and nothing is working. All i want do is go back to stock and make it like nothing happened. And no i dont have a nandroid backup. Im screwed. Please help.
i have the sd card error and usb error similar to here: http://forum.xda-developers.com/showthread.php?t=695243
but I cant get into adb because it says device not found.
when I connect USB it says error setting up new hardware in windows.
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
she's going to cut his..... SOMEBODY HELP HIM!!!!!
gatorran said:
she's going to cut his..... SOMEBODY HELP HIM!!!!!
Click to expand...
Click to collapse
Yes why is this so much more difficult compared to winmo?
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes read above, I can't get into adb shell to do that. Thanks!
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
Was adb working for you before? You may need to install some drivers
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
so the first part of the commands using fastboot you don't do from adb shell. when you get the phone into fastboot, attach to your computer, you then open command prompt on computer and navigate directories until you are in the android sdk tools folder on your computer wherever it is (most people it is somewhere like c:/android-sdk-windows/tools/)
THEN you type
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
no adb shell.
most people have installed adb in such a way that they can access it's tools from any directory. however, at least on my computer, fastboot commands will only work from within the android tools folder where fastboot is located.
hope this helps.
riotburn said:
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
Click to expand...
Click to collapse
Did you download the drivers??? they are not the same as the ones installed when you connect the phone....
yea also try pulling the battery and sometimes thats all it takes to get the use to be seen
then tell ur girl to mod the evo her self in case something like this happend my wife rooted and mods her's she love's to tinker
Lol at ruining your girlfriends phone. What tutorial were you following?
Sent from my HTC EVO via XDA App
i love how this is like, atleast the 4th thread someone has ruined there GFs evo due to inexperience, or the inability to read.
seriously, im not even trying to flame. i love reading this stuff.
its like general information for what NOT to do, for us that do read.
if you find the answer that works for you, mind mentioning said message?
i like to see threads that answer the questions at least, rather than have 10 suggestions, and no final response
Dam that sucks
Sent from my PC36100 using XDA App
how do i transfer the files for the second part of the usb is broken?
I was following the one that has pic by pic, and got to the point where pc36 wouldn't work. Saw that with the newest version this method wouldn't work. Went to the tutorial for that workaround and started following that. I think it got mixed up in there and thought i had nand unlocked it. Went to install the new radio, checked the system info and it wasnt the new one and started to get the problems.
Think it is rooted though because i get the # in adb shell.
How does one check to see if they did unlock nand, besides of the problem causing method i did?
I believe i ****ed up the custom recovery part. When I would load custom recovery it would flicker back and forth to the stock recovery, dont know if thats normal.
update: with more searching i found this http://forum.xda-developers.com/showpost.php?p=7136621&postcount=128 to use a update to fix the usb.
I did this and at least now it is charging, still not connecting to computer though it will charge through comp.
Can i flash back to the stock rom now? Will that fix it? How do i flash the stock rom?
Laughed at the thread title. Is the phone messed up, or the girlfriend? Gotta love misplaced modifiers.
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
dglowe343 said:
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
THANKS! I got it now. I had root but not nand so that prob f'ed it up. The link you sent me requires nand and has go do toasts method. I did that with no problems and had nand unlocked. So I installed the 2.0.... radio and freshevo with no problems. Thanks to everyone who helped, I will post in the first post what I did, at least what i can remember. I love xda, thanks so much guys.

[Q] Help. I'm stuck in the middle of a root of my evo via linux terminal/ adb

So I'm not fluent in the linux terminal. I'm basically illiterate, deaf and dumb. So here I am trying to root using toasts tutorial, How To Root The HTC EVO ~ Part-1 \0/
the forum won't let me post links yet., and apparently the software here thinks some part of the code I'm posting is a link.
Anyway I'm at this step,
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Click to expand...
Click to collapse
I may be root but I had a problem and had to redo this step... my sdcard was not being recognized. After reflashing/ updating I was able to access it again.
Now this rename the zip file step... I'm thinking if I rename it the code I'm supposed to enter isn't going to work. What should I rename it to?
How should I enter this code? first off my sd card isn't called sdcard it's called an 8 digit number.
I tried this (can't post the code for some reason) without changing the name of the zip file. I'm thinking I don't have the locations right because I know the file is in there.
I need some direction to get to the next step.
Thanks
Mods please move this thread....
to wherever it will get the most or correct exposure. Sorry if I put it in the wrong place.
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
okay form what i read you have already flashed the .zip. Make sure you clear your data and cache as these will cause boot loops if not cleared. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
oshizzle1991 said:
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
Click to expand...
Click to collapse
I'm running 2.1. I never upgraded. The tutorial I'm following is in thread #690762 I'll try to pm the link but I don't think they'll let me. I thought unrevoked wasn't a full root. I want to unlock nand. I'm also using Ubuntu here, not windows.
http://forum.xda-developers.com/showthread.php?t=690762
nfaust01 said:
okay form what i read you have already flashed the .zip. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
Nice looks like I'm allowed to put up links now... Thanks!
Yes I flashed the .zip my phone called it "updating" when it was going on.
Make sure you clear your data and cache as these will cause boot loops if not cleared.
Click to expand...
Click to collapse
Do I do that from the boot menu?
Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
I just removed the .zip part. What is the point of the next step, which I couldn't get to work, if I rename the file?
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
Well I guess I'm going to start over and wait for the latest unrevoked to come back out. Thanks to everyone that tried to help. "NO ROOT FOR YOU!"
You have a lot to learn....
First of all, don't rename the sdcard, rename pc36img.zip. Just rename it to anything you want so boat loader doesn't recognize it and try to update itself. Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
dkdude36 said:
First of all, don't rename the sdcard, rename pc36img.zip
Click to expand...
Click to collapse
Yes, I know I have a lot to learn. I didn't rename the sdcard, that wasn't possible. I figured part of the problem with getting this to work was the path. My sdcard wasn't called sdcard it was called some 8 digit number. I eventually worked around pushing the file to the sd card by installing the phone as a drive and dragging the file to the sdcard.
Just rename it to anything you want so boat loader doesn't recognize it and try to update itself.
Click to expand...
Click to collapse
After I rebooted and updated/ flashed the file, I renamed the file on the sdcard by removing the .zip. I did this via disk drive on my laptop because I wasn't getting anywhere with the command line.
Again this part didn't make any sense to me, not that most of it does, but what was the point of the next command in the directions if I renamed the file?
Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
Click to expand...
Click to collapse
Right "I have a lot to learn" I thought following the directions in toasts tutorial step by step would have gotten me to that point. I didn't realize I was just supposed to skip stuff when I run into problems. That kinda seems like what your telling me to do. I thought all of the commands were important.
I was hoping you had some follow up insight dkdude.
if you still on 2.1, try this method (just make sure the files aren't corrupted)
http://forum.xda-developers.com/showthread.php?t=741294

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.

Update recovery permanently and AlphaRev start up image.

I followed 2 guides to get my phone rooted and get my HBOOT patched to allow S-OFF - AlphaRev and Clockwork Recovery 2.5.0.1.
I want to get rid of the Joker from start up - had I would of known that I would of remained S-ON till they fixed that. That did permanently add Clockwork Recovery to the recovery area. There is a new version I downloaded and told it to install from ZIP and it reloaded and came to 2.5.0.7 but it never permanently patched it in. I am seriously considering going to AmonRA if it is available - I have done so many searches my head is spinning from lack of finds.
Am I missing something or is this something that needs to be done via ADB/Fastboot? If thats the case, I may need some help.
Permanently flashing recoveries has to be done through fastboot with a .img file, the update.zip way will never permanently flash a recovery, unfortunately. Here is a download link for the 2.5.0.7 recovery image, here's how you flash it (you must have the android sdk installed, and you have to have the fastboot.exe command in either \tools or \platform-tools):
Open up a command prompt window and type this:
fastboot flash recovery C:\location\of\recovery.img
When you reboot into recovery again via hboot, it should be 2.5.0.7.
As for the splash screen, that can be changed too (thank god, I hated the joker screen as well). Follow the instructions on this thread, there are plenty of screens to choose from, including the stock t-mobile screen.
If you need anything better explained, I can try to better explain it.
Thanks for the tips. I did find one I wanted - simple and Tmobile-ish. I do have the SDK installed with all updates from the Java Frontend that it uses BUT I still do not have fastboot.exe
I tried one from a friend but it keeps sticking at WAITING FOR DEVICE. Do I need to be in fastboot first on the phone then do this? It is detecting the phone with ADB devices command.
I'm pretty sure you need to be in fastboot to do this. Why the need for permanent recovery anyway?
I tried fastboot mode on the phone and it worked - Thanks for the tip! Flashed just fine and with help of some of the threads on the themes area i got the splash screen modified. (joker is gone - thank goodness!)
I am wanting to change the boot animation - I know how that works but I can't seem to find any for the MT3GS.
Again, I appreciate the tips. They have been helpful. ( I had to transpose what your talking about to the mac - and find fastboot for the mac - HTC had it on their site with a google search )
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
MusicMan374 said:
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
Click to expand...
Click to collapse
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
thronka said:
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
Click to expand...
Click to collapse
There is no AmonRA recovery for our phone, I don't believe. It was requested of him after we got s-off, but we don't know since he doesn't own a slide, and it's awfully hard to develop for a phone you don't have, haha
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Been flashed for a while now. I did not know this method but it is good to have and try when there is an update.
I have been tinkering with the ArayrayMod Revamped files since Arayray moved on to a MyTouch 4G. (traitor! LOL)
Looks like I may be going into the developing side of roms but I am just waiting for approval to post the rom for public viewing. a .32 kernel with Wifi calling included and thats really it - well retaining OC on that rom as well.
Much more tough than I thought doing this by hand - and I always thought my Unix Administration skills would be wasted.

Categories

Resources