Hello, xda-developers,
I have a myTouch 4G that was updated to the 2.3.4 Gingerbread software and wanted to root it. In order to do so, after many research, it states that there is no root for the 2.3.4 Gingerbread software and for it to be rooted you'll have to downgrade it.
The reason why I wanted to root it is because I am having a problem with the WIFI connectivity in my home and was wondering if it will fix it. Same reason why I update it to the 2.3.4 Gingerbread software in the first place. The myTouch 4G that I have will "RARELY" connect to my wireless router in my home but for some reason it doesn't fail me when connected to other wireless routers outside of my home even when having the same router. But this is now not the problem.
As you can read, the title says it all. My problem now is that I just soft bricked my myTouch 4G after a downgrade that I followed here: http://forum.xda-developers.com/showthread.php?t=1178912# Like the noob always say when something goes or went wrong, "Boohoo, I don't know what I did wrong. Someone, please, help me." But I THINK I know what I did or went wrong.
I followed the guide strict and carefully hoping I don't brick it but then I said to myself, "It's a 99.9% chance I won't, I think... what can possibly go wrong?" Everything went well. I did everything it says and once the update bar fills up to the top, BAM! It hits the "T-Mobile myTouch 4G" boot screen. I was happy. Very happy because I felt accomplished and one step closer to excitingly freeing my phone. But my hopes went down when it stayed like that for hours on end. I pulled the battery out and reboot it and nothing was fixed. Although it was stuck, I still can access the bootloader. I pulled out the battery again and boot it to the bootloader and re-updated it again and nothing was fixed. I yanked out the battery one last time and deleted the PD15IMG.zip file from the SD card to keep it from asking to update everytime I boot it to the bootloader so I can factory reset it but, still, that didn't help.
Like I said. I think I know what I did or went wrong. Examine the guide. The "Gaining Temp Root" part I did right. The "Changing Version Number to Allow Downgrade" I did correct and the results on the command prompt came out the way it stated it should come out. THEN! I yanked out the battery to reboot it after that. When I've done so I continued to the next procedure and everything went how it says it should go but, instead of the end results, I got it stuck on the "T-Mobile myTouch 4G" boot screen after the update. I think that's where I messed up. When I yanked out the battery to reboot it after the "Changing Version Number to Allow Downgrade" part. I believe it kicked it out from root. It is a temp root by the way and I read it somewhere that said, "Once you're rooted you CAN downgrade it." Something like that which made me think it wasn't rooted after that reboot and the downgrade wasn't a success. I also have two other guesses in which I think soft bricked the phone. I either have a bad eMMC-boot or the PD15IMG.zip was bad. These are my thoughts in what went wrong. I'm asking for your help. So can you help me find the solution to this problem?
Thank you very much in advance for your time and effort into reading this and helping me out. I really appreciate it.
-Victor​
P.S. Here's the information on the myTouch 4G's bootloader:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
Again, Thank you.
wow, same thing happened to me.
You could try updating it back up to the 2.3.4 RUU. If that works, nothing lost at least.
You used a wrong PD15IMG, most probably.
If you have used the correct one, your bootloader would be 0.86.0000, but it isn't.
Please re-download the correct PD15IMG and try again. When it works, if it throws any messages - write them here, so someone will be able to help you. If you see "Fail-PU" - your phone is dead.
Your mistake might have been removing the battery instead of typing "adb reboot bootloader". Yanking the battery off a working phone can destroy its eMMC. If that's what happened to you - well, you can replace your phone under warranty and follow the instructions better next time.
It was definitely the part where you yanked out your battery. You lost temp root then. Why you did it, not sure. But it's already been done so Let's not linger.
Have you tried starting over from step one?
Sent from my HTC Glacier using XDA App
You used a wrong Rom to downgrade or it is corrupted during download.
Download the official 2.2.1 rom, put it to the root of your sdcard, and try to update.
The original bootloader is 0.86.0000
You can download it here
Rename it to PD15IMG.zip before updating.
Do what he said
Do what the last guy said and rename the image and flashing.
Here is what has happened, you were probably installing a signed downgrade to a previous version. Either you got the wrong file, your download was corrupt (THANKS TO CHROME), or you didn't clear your cache dalvik needs to be clear if you run a different kernel. The main cause of hanging at the bootscreen is the incorrect cache either regular or dalvik. Thats what I've noticed from threads and just in general.
You don't appear to be running clockworkmod recovery. If you are going to mess with the system, DO IT ALL THE WAY! Don't get confused with this one... if you are planning to write radios, flash updates, or do anything YOU WILL NEED ROOT. This is because something could go wrong and you could be locked out. If you aren't willing to commit to basic root privileges, do not attempt to downgrade. Either go all the way, or don't go at all. That's just some friendly advice cause people will make the misconception if they just downgrade thats fine, but getting root is more dangerous... not true! If you have root, you can actually gain control of the phone and restore even a 'broken' one.
ROOT is mostly gained from within the phone in the operating system. You use an APP to gain root privileges. Once you get root, you need to get SU a program to grant privileges to programs that request them. Then you need to get clockworkmod rom manager so you can flash a recovery (internet and market access is required unless you can install from the .apk and use adb). ONCE YOU HAVE THAT RECOVERY you can downgrade, upgrade, flash, flex, backup, restore all with a simple push of a button, no expertise required!!
You can even revert to stock easier when you have root.
Once you get that recovery installed then look for ways to turn s-off and unlock your sim so you don't have to worrry about stuff.
And remember, they might not honor your replacement phone if you hack or modify it... but if you lose the phone they will replace it for you.
Big Thanks For the Help!
Hello, xda-developers,
Thank you, all, for your help! I've figured out the problem.
It was because of the PD15IMG.zip file. It was a bad one and I figured it out by downloading another one BUT, instead of downloading it from the same site I got it from, I downloaded it from a different site. I've barely figured this out and I could have fixed this problem way earlier if I had checked back my post.
Big thanks, again, to you guys for taking your time and helping me figure out this problem. It has been a month since I've been "Android-less" and now I am going to treasure it more than usual and I can not lie... I miss its awesomeness.
My phone is now back and it is officially perm-rooted! Love this phone more than ever with all the things it can do now. Rocking this phone out now with the Virtuous Unity rom and it blows... me... away!
-Victor​
Well..... at last you figured it out.....Iam happy for you....Try Virtuous Unity 2.39 you will really love it.
By the way, where did you get the PD15IMG.zip file???? Can you post the link, so that it will be easy for others with similar problem.
Thanks! You're right, I am trying out Virtuous Unity 2.39 right now and I love it. I was actually looking for an android "bone-stock" gingerbread rom but I can't seem to find one without the customization. Then I bumped into this one. They say sense 3.0 were only made to work on dual-core phones... they were wrong. I really love this rom and I'm sticking to it. Until I find a stock gingerbread rom that has been perfected for the myTouch 4G. You know, the one without the customization.
Oh! Here's the link where I got the radio (PD15IMG.zip) from: www1240.megaupload.com/files/89ce9e2eeb86bb659eceb64baa356c4b/PD15IMG.zip
Since I'm a new member of the xda-developers forum, I couldn't post a link. So, instead, here's the address.
So have you tried the link in my post? Did it work for you?
The link for the PD15IMG.zip radio? Nope. I went onto googling it and finding one myself. The link for the stock myTouch 4G 2.3.4 rom? Nope. Not a big fan of the myTouch 4G's overlay.
Related
I recently had to give up my rooted preordered Incredible for a refurb due to heat issues and reboot (loop) issues. For those looking for a guide as to what to do if you have to return your phone to Verizon and want to unroot. I welcome any comments to update/add to this information:
1) Make a NANDROID Backup if you want to simply port it over to your new phone
2) Mount your phone as DISK DRIVE
3) Walk the directories and delete any cached thumbnails of web sites you have visited
4) Copy any pictures you want to keep which were saved on the phone
5) Reboot into ClockWork recovery
6) Wipe the Dalvik Cache
7) Wipe the Data/Factory Reset
8) Go back
9) Wipe Data (main menu)
10) Power Down your phone
11) Remove your SD Card
12) Download one of the RUU's which are hosted around the web:
http://www.shipped-roms.com/shipped/Incredible/
13) Turn on your phone and plug it in to your USB
14) Run the RUU and let it do it's thing. When its done, so are you
15) If you have a screen protector, remember to remove it.
Any additions are welcome!
Yes it will revert everything back to normal, that's called an RUU btw
Cool
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
if i root and uninstall some apps, will this restore my phone to stock and allow me to get all future HTC updates?
jdmba said:
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
Click to expand...
Click to collapse
I don't think so, but it's easy enough to do a wipe and then apply the RUU (and hey, for the hell of it, you could wipe again).
Steps?
[deleted ... first post updated]
I'm pretty sure the RUU will completely wipe your phone. However, you can take giantcrazy's advice and wipe before running the RUU.
One more try
[deleted ... first post updated]
Ok, here is what you want to do.
there would be two things you need to un do before sending them back this phone.
make sure it says S-ON.
and then make sure you have stock recovery.
If you have these two things, your gold bod.
Probably to noob to know any better
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, big thanks for any suggestions
A Lex and Er said:
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, thanks
Click to expand...
Click to collapse
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
ACD168 said:
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
Click to expand...
Click to collapse
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is not as thrilled about my learning experience as I am.
I already rooted and unrooted once, will I get stock recovery back after unrooting?
A Lex and Er said:
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is as thrilled about my learning experience as I am.
Click to expand...
Click to collapse
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
A Lex and Er said:
I already rooted and unrooted once, will I get stock recovery back after unrooting?
Click to expand...
Click to collapse
To find out real fast if you have the stock recovery or clockwork-mod recovery, boot into HBOOT, (power off phone, hold vol down and power til screen turns on) and then vol down to select recovery and push the power button I think to select and then if you get a red triangle that means stock recovery.
Also need to return phone
I just got off with Asurion and they are over nighting a replacement. I had rooted my phone, installed some root only apps like wireless tethering and set cpu, removed some bloat like CityID and Tweet/Peep, and changed the boot animation. No custom ROM or radio update.
Then I wanted to get the OTA update so I applied s-off and flashed back to stock recovery.
So what do I need to do to return this phone. I know I will need to apply s-on. Then should I flash a stock 2.1 or just revert the changes I made to boot animation, restore the bloatware, and remove the root apps? Do I need to remove any other files that go with being root?
Thanks.........MM
ACD168 said:
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
Click to expand...
Click to collapse
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
A Lex and Er said:
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
Click to expand...
Click to collapse
First off, you are very welcome my friend, anything I can do to help do hesitate to ask!, and your not hijacking any thread brother, that's what these threads are for!!!
Thats real cool of the VZW employees!!
adb and sdk isnt that difficult I can help you!!
Read my post about warranty exchange.
I know alot of people are "better safe than sorry" mentality. but I have returned 2 phones that were fully rooted, updated, s-off running custom roms and I had no issues. in fact ive never had an issue using warranty exchange. ive exchanged phones that I broke (like broke.. with pieces coming off). I just call and tell the operator lady my phone doesnt work, i dont know why.. it was just working earlier and now it wont turn on.. they send me a new phone and I send back the broken one and everyone is happy.
They only confirm that the numbers on the phone match your account. Not the reasons you are sending it Back. the warhouse guy that opens your box isnt the same guy you talked to, nor do they have information about your phone call to the tech. They simply open the box, scan the numbers and move on.
dont stress to much about it
Great info here
Thanks to every one of you on this thread. I am finally breaking free from WinMo and getting Dinc after a lot of research. I like Verizon but hate the bloatware they pack onto Androids and all the other phones, so I will be fiddleing with ROMs. If I screw up I am looking here first to see how to get it back to stock so I can get my new one with the insurance coverage.
Everytime I get to serouosly looking around these forums I learn great new stuff. I will donate to the XDA someday soon!
Okay. so im a noob. Just need to ask. What do you guys mean by stock recovery? I just rooted my phone but need to unroot to send it in for work at Verizon. Could you help me out?
I'll elaborate on the title a little better.
I just recently rooted (successfully) my HTC Droid Eris, I've currently got a ROM of my original fresh rooted OTA software, I also have KaosFroyo v35 (I think it's 35, either 35 or 25).
For some reason or another, my bootloader is stuck on S-ON, and for the life of me I cannot find any way to get it off (that works). It's also 1.49.0000 as opposed to .2000.
I've still very new to the whole hacking ordeal, and it's not that I haven't searched the forums to find a solution to this problem, it's that because of the specific nature of my issue I'm bombarded with fixes and possible solutions to other things, many of which are completely useless to me. If anyone out there could help me shine some light on this situation, and maybe get my bootloader into S-OFF, I'd be forever grateful.
So you know, I'm wanting it in S-OFF so I can jailbreak my PS3. I keep getting an error while trying to boot files and research showed me it was due to my bootloader being on instead of off. Again, any help is greatly appreciated, and if anyone needs any additional information just ask and I'll get it.
Thanks so much for you time.
Kal245 said:
I'll elaborate on the title a little better.
I just recently rooted (successfully) my HTC Droid Eris, I've currently got a ROM of my original fresh rooted OTA software, I also have KaosFroyo v35 (I think it's 35, either 35 or 25).
For some reason or another, my bootloader is stuck on S-ON, and for the life of me I cannot find any way to get it off (that works). It's also 1.49.0000 as opposed to .2000.
I've still very new to the whole hacking ordeal, and it's not that I haven't searched the forums to find a solution to this problem, it's that because of the specific nature of my issue I'm bombarded with fixes and possible solutions to other things, many of which are completely useless to me. If anyone out there could help me shine some light on this situation, and maybe get my bootloader into S-OFF, I'd be forever grateful.
So you know, I'm wanting it in S-OFF so I can jailbreak my PS3. I keep getting an error while trying to boot files and research showed me it was due to my bootloader being on instead of off. Again, any help is greatly appreciated, and if anyone needs any additional information just ask and I'll get it.
Thanks so much for you time.
Click to expand...
Click to collapse
You'll want to follow the directions in this thread, http://forum.xda-developers.com/showthread.php?t=725047
Kaosforo v-34,35 or 35-1 for this to work
For starters, make sure that you have the correct firmware on your ps3 prior to doing anything (firmware version 3.41) If you have firmware 3.42 or 3.50 installed your S.O.L. If you have 3.41 your good to go. You can check in the XMB of your ps3 by going to settings-->System Settings-->System Information and the first line will tell you your firmware.
Once confirmed go to this link http://androidforums.com/eris-all-things-root/121597-how-install-engineering-bootloader.html and get your Eris to be rooted and S-off
Once confirmed that you have S-off of your rooted Eris (shut down your phone and while holding your volume down key boot your phone you will see on the top line either S-off or S-on) go to the Eris PS Groove wikki by clicking Here and follow the instructions from there and you should be all good to go
Good Luck
I got you kid it's very simple!!
Well 1st I have a thread on page 2 How to unroot your Eris if you are having problems with ruu's and other methods... In that I talk about a file called erisengspl.zip!!!! Give me your email address and I will email you the file, you flash it the same way you would flash a rom and thats it your phone is s=off!!!!! It takes 30 seconds!!!!! I promise you bro thats it, and your good!!!!
I wish I knew about that file before I got my phone to be s-off. I did it the "old fashion way"
Sent from my FroyoEris using XDA App
Haha! That file works wonders. I couldn't get S-Off, flashed that file, and BOOM! One minute later I was riding the S-Off train.
I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Call ahead of time and see what they say on the phone?
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)
I don't know what the policy is.... most likely, as soon as they see where you're at, the tech will figure out that you were trying to root your phone, and you'll be SOL.
Have you tried booting your phone via ADB? Maybe you can go into recovery via adb shell and see if you can go from there....
if you can get it to power up all is not lost, try pushing AMON's recovery via fastboot
Fastboot
Copy recovery-RA-evo-v1.8.0.img in your android-sdk-windows\tools\ folder
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
Since your phone turns on and you can boot into fastboot. Bricked would mean nothing happens period. There's still hope. Try this thread: http://forum.xda-developers.com/showthread.php?t=780141. There's a video walk-through showing you how to unroot and return to s-on. Then you may be able to start over.
Good Luck!
-kp
Edit: Try GMan's suggestion above 1st.
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
indagroove said:
Do you have TEP on this device? If so, and you were to accidentally drop your phone in a very deep lake, river or ocean, you would be covered for loss with a $100 deductible. You can add TEP in the first 30 days, if you don't already have it.
Click to expand...
Click to collapse
Sprint Insurance right? I don't... I might do that but that's my last resort.
josh4trunks said:
Sorry guys, itried all that stuff yesterday for several hours in the irc.
*adb doesn't recognize device (if you can help me with this that would be great)
*fastboot works but always gives
Code:
writing 'recovery'... FAILED (remote:image update error)
*flashes in hboot except for Radio_V2 always give
Code:
Parsing...[SD ZIP]
[1] RECOVERY - Fail-PU
Partition update fail!
Update Fail!
It's all in the opening post of the first thread I linked. Wanted to keep that thread about fixing my phone, and this one about getting it back to Sprint / HTC. Thanks
Click to expand...
Click to collapse
If you can boot into the hboot just run a ruu and restore the factory Rom, if all fail pm me your number and I will walk you thru it
Sent from my PC36100 using XDA App
shameless bump - completely changed opening post
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week.
What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.)
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
haplo1818 said:
I could be completely wrong but it's my understanding that, as long as you can get into the hboot, all hope is not lost. I thought I had bricked my wife's Evo when I was rooting it last week. What worked for me was:
1. Take the SD card out and put it in a PC.
2. Clear out all files on the root of the SD card. (Not sure if this is needed but it's what I did. I left the folders in place though.
3. Download the appropriate stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=838448 (Thanks xHausx!!)
4. Rename the ROM to PC36IMG.zip and place it on the root of the SD card.
5. Place SD card back in the phone and boot into hboot.
6. Your phone should detect the PC36IMG.zip and take forever to load it before asking you if you want to install. Say yes to the install and let it reboot after the install.
This brought my wife's phone back to stock so I could attempt the root again. My wife's phone is a white 0004 that came stock with 3.30.651.3 on it. I downloaded the 3.30.651.2_PC36IMG.zip from the site above and it worked just fine.
This is what worked for me but results may very. I'm still a nOOb with this, having just came from a Pre, you may want to wait till someone else comfirms that the above will work...
Hope this helps!
Click to expand...
Click to collapse
Tried this multiple time with different PC36IMG.zip, always get Failed-PU
Partition Update Error, I might try the 3.30 version though just to make sure.
Won't like my opinion but, you knew the risks of rooting. If you can't fix your phone then you should add the insurance and suck up the deductible fee. You don't deserve (or anyone for that matter) a free replacement for ****ing up your phone. It sucks but that's the risk. They'll normally have you one the next day.
Your phone is definitely not bricked and is fixable. Do you have adb drivers installed on your PC? If not find them and install them then try this: http://forum.xda-developers.com/showthread.php?t=829045?
Since you are already s-off you won't have to do all the steps, but by reading the entire OP you could figure out where to start and what to do. Just to be on the safe side you may want to start at the beginning using HBOOT USB from this screen you posted ftp://eto.homeip.net/shared/IMAG0004.jpg and start completely over. you are not bricked. Just hang in there and someone here will get you hooked up. You are in the right place my friend.
Evo's are really not that easy to fully brick.
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Have you tried using a different SD card? Is it possible that something is corrupt with it? I also hear that you need to have at least 1GB of free space on the card when your trying to flash it.....
Let me just say myself and this guy stayed up late last night working on this phone trying every possible root/unroot method you can think of.
The pc he is using has adb drivers installed but the computer wont recognize his device as a adb device. Fastboot on renders certain commands and we tried all with various recoveries. I hit up a dev and we went thru different things and cant seem to figure this one out
As I told the Josh it can not be bricked because we get the bootloader and fastboot screen, I think its not even the partition but the recovery. Also he has a modified hboot by someone on xda (josh please post the link) which I believe that pc36img is whats causing all the problems.
If anyone could help it would be appreciated!!
Jbcarrera said:
I know whats wrong with your phone problem is i don't know how to exactly fix it! When you tried to root it after taking the OTA or upgrading the HBOOT you messed up the partition table thats why you can't flash a rom what you need to do is try to run a ruu back to stock and then try to reroot but untill you get the partition table fixed you have a phone that is nand unlocked and can't flash any rom the ruu rewrites the partition table if your phone came with 3.70 then use that ruu but if you took the ota then run the 3.30 should work don't do a PC36IMG run the RUU in fastboot usb mode
Click to expand...
Click to collapse
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
I'm sure he thought you needed the engineering SPL to be able to flash roms. When I rooted mine back in June with toast's method, that was the way to do it. I rooted my girl's new Evo last month using Unrevoked, and I also downgraded the hboot because I thought I had to in order to flash a custom rom. Fortunately, I was able to do so with no issues.
Cleared all the caches?
craigbailey1986 said:
Let me clarify he didnt take any ota (this is what i told him to tell sprint)
He had a 2.02 hboot and rooted with tha method successfully. Then ( for reasons beyond my comprehension) he tried to downgrade his hboot. The method he used, used some sort of mod hboot which is supposedly .76 but says 2.10. This is where the bootloader screen began to loop.
Click to expand...
Click to collapse
The partition table is screwed but there has to be a way to reset it I knew that method was risky told my friends to stay away from it
Sent from my EVO at the edge of hell
Ok idk exactly what it is called but I know it has 777 in it. The file that is created on your SD card when you root using GFree. I saw someone had it posted on here somewhere a while ago but now I can no longer find it. Anyone have a link to that file? Please and Thank you! I think it may be my last chance at saving my myTouch with that stupid Cache error! The other way I fixed it last time isnt working this time
dcwiker05 said:
Ok idk exactly what it is called but I know it has 777 in it. The file that is created on your SD card when you root using GFree. I saw someone had it posted on here somewhere a while ago but now I can no longer find it. Anyone have a link to that file? Please and Thank you! I think it may be my last chance at saving my myTouch with that stupid Cache error! The other way I fixed it last time isnt working this time
Click to expand...
Click to collapse
part7backup-000000000.bin is created in root of your /mnt/sdcard/~ when you ran the gfree. If you lost it then sorry I don't think anyone ease's would work as I am not 100% sure if that is device specific but it may be leading to that.
Far as the cache error goes I hope it works out for ya as thats the closest soft-brick we have. But do you have adb installed? If so push and flash the CMWR2.5.1.2 manually. I didn't isolate the issue if it's gfree related as we still need data to verify those who are effected are only gfree users or folks who just simply did root.sh without gfree.
TmpUsr said:
part7backup-000000000.bin is created in root of your /mnt/sdcard/~ when you ran the gfree. If you lost it then sorry I don't think anyone ease's would work as I am not 100% sure if that is device specific but it may be leading to that.
Far as the cache error goes I hope it works out for ya as thats the closest soft-brick we have. But do you have adb installed? If so push and flash the CMWR2.5.1.2 manually. I didn't isolate the issue if it's gfree related as we still need data to verify those who are effected are only gfree users or folks who just simply did root.sh without gfree.
Click to expand...
Click to collapse
Yeah I know I had this stupid cache crap before and it was a b**ch to fix here is the link to my thread
http://forum.xda-developers.com/showthread.php?t=1043459
And I have ADB and EBL (Hboot 85.2007) and last time pushing the old CWM worked but this time no dice I get Write FAILED everytime. So I hear that the PMG15.IMG can possibly fix this issue as well but I need that part7 file and I dont have mine anymore thanks to CM7 killing my SD card a while back anyhow I have seen it posted for DL here before and I think it worked for the guy who used it, I mean its worth a shot. It's not like I can do ANYMORE damage to the phone! lol
dcwiker05 said:
Yeah I know I had this stupid cache crap before and it was a b**ch to fix here is the link to my thread
http://forum.xda-developers.com/showthread.php?t=1043459
And I have ADB and EBL (Hboot 85.2007) and last time pushing the old CWM worked but this time no dice I get Write FAILED everytime. So I hear that the PMG15.IMG can possibly fix this issue as well but I need that part7 file and I dont have mine anymore thanks to CM7 killing my SD card a while back anyhow I have seen it posted for DL here before and I think it worked for the guy who used it, I mean its worth a shot. It's not like I can do ANYMORE damage to the phone! lol
Click to expand...
Click to collapse
BTW it was me who posted the CMWR2.5.1.2 flash leak on another forum as I was here on XDA manually hacking the SLC-EUDA emmc block trying to replicate the issue the first person in MT4G to have in here. But if all you get now is fail partition update (fail-pu) then there is nothing else you can do. I still need more data to isolate if this is just gfree user based and not those who has s-off with eng boot without gfree. I try to do more test today but I can't roll the gfree maybe I am lucky? but ill post my finding if I ever able to get it and replicate the conditions. Only known meth to fix this is replacing the motherboard for now.
So you're saying PMC15.IMG wont fix this either? I don't understand why last time I was able to ADB push CWM 2.5.1.2 via Fastboot and then go into Recovery, Format cache and it was fine phone booted. I reflashed CWM 3.1.2.4 and went about my business...now it happens again and I can not flash CWM via recovery this time and thus I'm boned?? FML I JUST got this phone...my last ones screen peeled away, it was a referb from insurance so it was replaced with this one.
I work for T-Mobile so I really don't wanna bork my phone enough to hide root then send it in for a warrenty replacement cuz I don't think its right to screw my own company but damn I don't want to be out a phone, my back up phone's menu button doesn't work so it's really freaking annoying , guess I will deal till the Sensation 4g!
i dont rememeber which unroot thread but one of them has it, and supposedly it works with any mytouch 4g. not just the one it was created on
Well once you have fail-pu on hboot when you try to revert back to PD15IMG (rom/radio) both update will fail as you can't write to the partition block. Now far as I know this is only seen in CMWR3.0.0.0+ which at the time I flashed it manually though terminal. At this point there is way to many variables to consider mostly we need community input as those who is effected did use gfree as it could mean why the emmc simply gets -ro access now I am aware its using slc-euda so you can't low level format it this is the reason they replace the motherboard. We are not just talking about single partition here as it seems the recovery partition is first thing to be effected. I need to do some more work and atm I only have 1 phone and I don't feel like hacking it and end up with dead as I don't have any backup phones as I gave it away. Let me see if I can get another MT4G cheaper from ebay/cl and I can test on it.
VibrantOwnr said:
i dont rememeber which unroot thread but one of them has it, and supposedly it works with any mytouch 4g. not just the one it was created on
Click to expand...
Click to collapse
Thats the gfree revert meth which is the only place you use part7backup and then if you want to roll back to stock eng bootloader you do the unroot.sh which flash the eng.nb0 and turns S-OFF.
Alright so let me get this all played out in my terms so I can see if I understand it.
1. Do I actually need that part file? I rooted with gfree so I figure yes
2. Will PMG15.IMG work at all or no?
3. Should I just say F it all and try anyhow? If so anyone wanna throw me a link to the part file?
4. I STILL don't get why this happened the first time! And why the way I fixed it the 1st time isn't doing $hit the 2nd time...
UGH! Damn it why couldn't this happen the end of May closer to when the Sensation 4G is suppose to launch... :'( damn you CWM ghost...
So, I've now LITERALLY spent days on this. Don't tell me "read the FAQ/Stickies", because I already did :good:
I'm not a noob when it comes to rooting/installing ROMs on phones. I would estimate that I've done it on about 50 different models...but this one has me up a freakin tree. So, I rooted it and installed 4EXT recovery. I applied the Energy Rom on it, rebooted....just hangs at the MyTouch4g screen. Left it for 20 minutes....nothing.
Tried a different Kernel, same thing.
Tried 4 different roms (GB and ICS) and different Kernels....no dice.
So, I tried taking it back to stock. I downloaded the 2.3.4 update from the "you think you're bricked" thread. Renamed it and loaded it to the SD card. The blue bar progresses all the way through....then it just goes to the HBOOT screen like nothing happened.
I really need to get this thing back up and working (it's a phone from a wholesale lot that I got off ebay) so that I can sell it. It's losing value every day that it sits here
Any help from anyone, please?
Well, without knowing the exact steps you took for rooting it'll not be possible to help you. It's hard for me to understand how someone who "installed ROMs on approx.50 different devices" would require this explained.
Also, the only reason for the "return to stock" PD15IMG.ZIP to be read but not to proceed is the main_version being high. This is why a script (misc_version) is applied to allow downgrading. And if you searched, you'd definitely see the references to it.
A wild guess of mine - you unlocked the bootloader instead of gaining S-OFF, and didn't flash the kernel through fastboot? And/or didn't wipe data?