Yesterday, it randomly started force closing all apps repeatedly (force close loop) and often freezing until the battery was pulled. It would work fine after powering on for 30-60 minutes at a time but then start messing up again. Sometimes it messed up right away though.
Today I made a nandroid backup and then tried wiping data/factory reset and wiping cache. I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know that is not good. But what does it mean??
---
Anyway, now no matter what ROM I flash (CM7.0.0, or an old nightly 37, 41, etc), I click "Reboot system now" and the screen just goes to black forever. I have to pull the battery again.
But then it freezes at the MyTouch 4G screen (left it for 10+ minutes). It never gets past that.
Yes, I even did a nandroid backup before wiping. But even restoring that does the same thing: it restores, I click reboot, and it goes to a black screen.
But no matter what, after a battery pull, it just freezes at the MyTouch 4G screen forever.
I *can* get into the white hboot/fastboot screen via Power + Volume Down and then get into CWM Recovery from there.
It just can't *boot* into any Android rom.
Am I bricked?? Is there a way to fix this??
Please help!
Everyone that i am aware of that has encounter this has not been able to recover from it.
It looks like it might be truly bricked.
Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4
Yup it looks like your eMMC chip went bad. I have a phone here that is doing the same exact thing. I have tried everything from fastbooting a new bootloader to the PD15 whatever its called full restore image. Nothing is working at all. I fear you have a truly bricked phone.
Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.
Paul22000 said:
Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.
Click to expand...
Click to collapse
once they see Clockwork ROM manager they'll know it was rooted.
cmdmilitia13 said:
Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4
Click to expand...
Click to collapse
How do I check?
neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?
Paul22000 said:
How do I check?
Click to expand...
Click to collapse
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1
neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
I have heard of people frying their motherboards by over volting the charging port so they no longer turn on before sending it in for a warranty return. I cant comment on this but if I can get mine warrantied that way I will do it. Not like the motherboard is any good now so might as well try. However! I do not suggest doing this.
Paul22000 said:
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?
Click to expand...
Click to collapse
I'm sure they check first thing.
technically you could if you have the .85 hBoot.
But if you have the .85 hBoot they'll know the phone was tampered with since the engineering screen is different
neidlinger said:
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1
Click to expand...
Click to collapse
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?
Paul22000 said:
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?
Click to expand...
Click to collapse
to get the phone working again? nope. To get it to an honest warrant-able state yes.
I was able to check the eMMC chip version on my bricked phone so you should be able to also. You need to be in clockwork recovery to do it.
neidlinger said:
to get the phone working again? nope. To get it to an honest warrant-able state yes.
Click to expand...
Click to collapse
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!
Paul22000 said:
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!
Click to expand...
Click to collapse
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.
neidlinger said:
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.
Click to expand...
Click to collapse
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?
Paul22000 said:
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?
Click to expand...
Click to collapse
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.
neidlinger said:
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.
Click to expand...
Click to collapse
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289
Paul22000 said:
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289
Click to expand...
Click to collapse
a) with adb up and running you can flash the stock recovery image, but not the old school hBoot
b) i am at work and WebSense blocks alot of images.
c) yes
d) depends on if you had the pre or post OTA recovery image.
Related
I have read many posts, and did many tries.........we all know that Froyo ver that is out, is not a official one. In order to get Official OTA update, our phones must be in complete factory stage. Unlocked boot-loader is not an issue. Trust me, i tried many different ways to "unroot" my N1. Following many "how to's" uproot your N, in order to get OTA (Froyo), all tries have failed. I was flashing original roms (ERD79), replaced recovery image, and then i GOT an OTA with 2.1-update1, no sweat! Then, when it tried to install, there was an error every time. I was able to install that (ER27) update manually, but it was NOT the thing i wanted to accomplish. I knew that i will be able to receive next OTA with ver 2.2 (Froyo), but i also knew that this update will NOT install either. The problem is a recovery image! After been running many different custom roms, i have decide to try again to go back to the state from the beginning, so i can be sure i can be able to install official Froyo, when it is out. I was afraid to do this, but i did it anyway.............and it was successful. I restored my Nexus to the original state (except boot-loader of course), and after i got back to ERD79, momentarily i got OTA with ver 2.1-1. But this time, it has installed with no problem!!! I am running it right now, waiting for next (2.2) OTA update.
Ok, here we go:
Just go there and grab Google OEM file (PASSIMG.zip). Put it on your SD card (root dir).
Then restart your phone into boot-loader (trackball+power button).
Once there, top power button again. It will look for passimg file as always. It will load the passimg file. Note the blue status bar at right-upper corner of your screen.
Then, it will check that file, and finally you will see "do you want to start update?"
Press Volume UP, for YES............and wait.
After phone reboots - you are done! Completely back to stock!
Then you can go to "menu-settings-about-system updates" and you should see that your phone is already downloading update 2.1-1.
That is it.
If for some reason you end up with android screen with triangle and exclamation mark, just press VOL up and Power, at the same time, you will get into recovery screen, and reboot your phone from there.
One more thing...........i did that in my own risk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, please do not blame me, if something would happen to you Nexus (phone just exploded, or something....
)
Wow..can't get any simpler than that..thx for this.
Thanks. Very simple.
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
-------------------------------------
Sent via the XDA Tapatalk App
Wow... Much appreciated!
laughter95 said:
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
Click to expand...
Click to collapse
Nope. Even if you unroot your phone, your bootloader cannot be locked back again (if you unlocked it). Rooted or not, if your bootloader was unlocked, you always get that unlocked padlock image on your first screen when you turn on your phone. However, I read somewhere that someone has sent his phone back for warranty exchange, after he revert everything to factory stage (except bootloader of course) and they (HTC) accepted. I don’t know how that happened...maybe they (HTC) overlooked that first screen??
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
HA ha ha! You did NOT understand what i wrote! Read it again....and what if one does NOT have a Nan backup at all??
" You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. " <= that's total BS!!
Would this work on the AT&T N1?
RogerPodacter said:
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Th
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
RogerPodacter said:
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
Click to expand...
Click to collapse
Yeah, it should be something like "HTP123990" which is your device number. Click once more and it'll show all the backups for that device.
Or just browse your SD card to the nandroid folder with a file manager like Linda:
wow thanks! it's so easy to use..and works!
i had so many problems with the froyo 2.2..though i really LOVE the speed and the new interface...but afterwards decided to switch back to 2.1 wait for official OTA...
thanks op!
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
http://forum.xda-developers.com/showthread.php?t=686593
Well coming from a rooted MoDaCo rom, I performed the steps and am now running the stock ROM and just been informed that there is an update available. Update is installing now and it works great.
Now I have my stock OS back while still rooted, and getting updates.
I just recently got my Nexus one a few days before Froyo hit. I've been sporting Froyo while traveling and getting barely any coverage. So this is a good test.
I'm on Fringe coverage now. With Froyo and its radio, I kept getting network disconnects. Flashing back to stock+update = 2/3 bars of EDGE.
Finally!
RogerPodacter said:
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
Click to expand...
Click to collapse
It's the fastest way to reload stock recovery/image/radio altogether.
Not true. I can confirm the method in this thread.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
If i use mybackup pro to backup apps and data, how do I restore that stuff once I'm unrooted? Do you have to redownload mybackup pro? Sorry if this is obvious to some, I'm new to android and really want to be able to get the OTA update. Basically I'm wondering how the people that have used this method got all their info and apps back, Thanks.
I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bumpity bump!
hello there i got the exact thing on my TB and i downloaded the files to fix it but i get back a Main Version Older am i doin somethin wrong
you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?
scotty1223 said:
you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?
Click to expand...
Click to collapse
i was trying to flash this [ROM][TH3ORYROM] SHIFTAO5P V1.2X [AOSP/CM7] Eclipse B5 Kernel (8/26/2011) but when i was trying to flash the radio, i wasnt getting any receptions and i tried all four radio listed, so my stupid self thinkin hey let me use the radio PM05IMG from the root process and see if that would work, well as soon as the bootloader started flashin the files it pop back into bootloader with the security warning, i tried the file the jcase said to use to get out of that problem but the file never open or go thru it come back saying Main Version Older file not updated.
"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App
scotty1223 said:
"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App
Click to expand...
Click to collapse
Hey there Scotty i really appreciate you helping me out here, im sitting at work with my TB stuck in Bootloader, getting ready to bust out my old rooted Eris out, but ima go and try that MR2 RUU do you have a link to where i can download that. and also where you said Main Version Higher mines Said Main Version Older,
and yes i thought i did everything correctly i mean i guess since i had the rom flashed but wasnt getting any reception made me make the stupid mistakes, by the way scotty do you have a tb
i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.
scotty1223 said:
i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.
Click to expand...
Click to collapse
Ok ima download it but my other prblem is that the phone doesnt charge the battery its not enough voltage to run the files, i have no other way of charging the phone i might have to buy a battery charger or somethin
only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery
take an old pair if headphones and strip them til you have only the cooper wire and connect them to the gold connector from your phone to your eris battery and that should work
scotty1223 said:
only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery
Click to expand...
Click to collapse
Ok so today i brought an HTC dock charger with a extra slot to charge the battery alone, so i charge that puppy up, put the battery back in with the file you gave me to put on my sd card and bootloader comes on does its checking the file and loaded the update ask me to press yes and BAM it took 5 mins to do its process and rebooted itself and now back to where it was when i first brought it, damn so thx you Scotty for the help and guide, so can youo tell me a method to use to root it back,
good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten
scotty1223 said:
good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten [/QUOTED]
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse
portebr3 said:
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse
you will need a pc
scotty1223 said:
you will need a pc
Click to expand...
Click to collapse
Ok ill need a pc, how will i know im rooted will it give me the superuser app like the other root method does
theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/
scotty1223 said:
theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/
Click to expand...
Click to collapse
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,
portebr3 said:
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,
Click to expand...
Click to collapse
the market will only have the superuser app,youll need the matching binary files. the superuser app is linked on revolutionarys page,you must flash that in recovery to become rooted.
from: the revolutionary website:
Does Revolutionary give me root?
No. You will need to flash this this zipfile from recovery.
jcase said:
I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
Click to expand...
Click to collapse
all multiupload.com links are non-functional and should be disabled, and refreshed with current mirror links.
im actually trying to unroot my phone. i rooted it using unrevoked and was wondering where i can find a manual on how to unroot. thanks
Though I have seen no manuals, there are plenty of tutorials, walk-throughs, wiki's, etc... Just a search box away.
*hint check the stickies as well
just did this the other day.
Am still new xda user so i cant post the links, but the general steps are to get the 'unrevoked s-on' tool from the unrevoked site & follow their steps to reflash to S=ON.
After your phone is s-on download htcsync from the HTC site and install that (for latest usb drivers). If need be uninstall old versions first.
after htc sync is installed grab the RRU version you want to flash back to and double click the exe. From there its idiot proof, click 'next' to continue.
I used RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe (md5: 26dcb19a186128e46f6d52a29cccd7cc) from the shipped-roms site
needless to say, once you unroot dont get the OTAs from sprint, youll get hosed trying to root again until 2.3.3 (hboot 2.16) method is released.
Flash this in your custom recovery. S-on.zip
Download this and rename it to PC36IMG.zip and then put it on the root of your SDCARD, boot into your bootloader and select yes to the update.
Didn't mean to interrupt anyone's helping but it's easier with links.
mattykinsx said:
Flash this in your custom recovery. S-on.zip
Download this and rename it to PC36IMG.zip and then put it on the root of your SDCARD, boot into your bootloader and select yes to the update.
Didn't mean to interrupt anyone's helping but it's easier with links.
Click to expand...
Click to collapse
you don't happen to have the newest RUU?
evolishesh said:
you don't happen to have the newest RUU?
Click to expand...
Click to collapse
Not released yet.
Easiest way is to run that RUU and update OTA.
Warning if you do update to 2.3.3, root has NOT been achieved so you'll be stuck there.
mattykinsx said:
Didn't mean to interrupt anyone's helping but it's easier with links.
Click to expand...
Click to collapse
No sweat. You linked him to exactly what he needs. Good man!
Worked great! Thanks guys!!
Sent from my PG86100 using XDA Premium App
Thanks matty
sling said:
Thanks matty
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My power button is busted and need to take it to Sprint for repair. I used unrevoked to root and went into bootloader and see i have s-off, hboot 0.97 and radio 2.15.00.04.08. How am I able to get s-on if i cant flash the s-on tool due to my power button? Help is much needed, thanks.
Deadbolt said:
My power button is busted and need to take it to Sprint for repair. I used unrevoked to root and went into bootloader and see i have s-off, hboot 0.97 and radio 2.15.00.04.08. How am I able to get s-on if i cant flash the s-on tool due to my power button? Help is much needed, thanks.
Click to expand...
Click to collapse
Honestly, if you just run a RUU so that it looks stock they're not gonna notice.
mattykinsx said:
Honestly, if you just run a RUU so that it looks stock they're not gonna notice.
Click to expand...
Click to collapse
Which RUU do I run? And then how do I root it back when the power button is fixed?
Deadbolt said:
Which RUU do I run? And then how do I root it back when the power button is fixed?
Click to expand...
Click to collapse
Read the first post, part that's bolded for your s-on/power button issue:
http://forum.xda-developers.com/showthread.php?t=998372
Which RUU...well you can run the latest since you're returning it...
http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip
Rename it PC36IMG.zip
When you get a replacement it will likely have 2.3.3 installed so you have to use the revolutionary way.
http://forum.xda-developers.com/showthread.php?t=1228566
mattykinsx said:
Read the first post, part that's bolded for your s-on/power button issue:
http://forum.xda-developers.com/showthread.php?t=998372
Click to expand...
Click to collapse
I looked at that thread but ROM manager won't work from what I gathered when i ran the app. I don't have clockworkmod recovery installed to flash it through ROM manager. I currently have Amon RA recovery.
mattykinsx said:
Which RUU...well you can run the latest since you're returning it...
http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip
Rename it PC36IMG.zip
Click to expand...
Click to collapse
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Deadbolt said:
I looked at that thread but ROM manager won't work from what I gathered when i ran the app. I don't have clockworkmod recovery installed to flash it through ROM manager. I currently have Amon RA recovery.
Click to expand...
Click to collapse
You can just change your recovery to clockworkmod via ROM Manager...
Deadbolt said:
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Click to expand...
Click to collapse
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.
mattykinsx said:
You can just change your recovery to clockworkmod via ROM Manager...
Most likely I won't be getting a replacement because the problem is repairable. I'd like an RUU that I can easily root after they repair the phone.
Click to expand...
Click to collapse
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.[/QUOTE]
Lemme see if I can get ROM manager to flash the s-on tool...
I called the sprint repair store and they told me it was repairable and I wouldn't need a replacement but who knows if they were blowing smoke up my ass. I really don't want to pay a deductible...
Deadbolt said:
Lemme see if I can get ROM manager to flash the s-on tool...
I called the sprint repair store and they told me it was repairable and I wouldn't need a replacement but who knows if they were blowing smoke up my ass. I really don't want to pay a deductible...
Click to expand...
Click to collapse
It can be repairable.
It just depends on if it's the button itself or the board.
In my case it was the board and therefore was a defect.
As long as it's not due to physical/water damage they will replace it [if necessary] without a deductible.
mattykinsx said:
No reason that you can't easily root the newest RUU.
Also, I had this same issue and they couldn't repair it. Had to replace the Evo.
Click to expand...
Click to collapse
Currently trying to get ROM manager to flash the clockworkmod recovery...is there an RUU still available that allows me to flash to root with the capability of unrooting after I re-root my phone if needed? I've read revolutionary, you can't unroot.
Deadbolt said:
Currently trying to get ROM manager to flash the clockworkmod recovery...is there an RUU still available that allows me to flash to root with the capability of unrooting after I re-root my phone if needed? I've read revolutionary, you can't unroot.
Click to expand...
Click to collapse
I've read you can't get s-on but I saw a post in the thread in Q&A (asking how) with a response that might tell you how.
I'd give you the link but I'm in bed now.
I believe its still I page one on that sub.forum
Hi guys, I bought a 'bricked' phone on eBay, thinking it would be easy to fix it. Apparently not. I read the 'If you think your HTC Glacier is bricked' thread already. I have no idea of the history of the phone. I took it apart, and it has no water damage. The phone boots into hboot OK and is S-ON. I put the PD15IMG.zip on the SD card. However, the bootloader isn't showing the message that it is looking for this file. I've flashed the same PD15IMG.zip on another phone, so I know what I'm doing and the zip isn't corrupt. I'm not sure what SIMLOCK is supposed to do, but it shows 'SD init fail !!!' when I try it. So I was thinking that maybe the SD card reader was bad. I swapped it out with another working SD card reader from a working phone. Same problem still. I also tried factory reset, but the phone freezes at the white MyTouch 4g screen when it reboots. So maybe the motherboard is bad?
Can anyone think of anything else to try before I use this thing for parts? Thanks.
Hmm.. Somehow I got it to recognize the PD15IMG.zip. I think I plugged the USB cable into my laptop, pulled the battery, then disconnected the USB cable, then replaced the battery, and when it booted it found the file this time. I'm flashing it now. Wish me luck.
UPDATE: After flashing PD15IMG.zip, it's still locking up on the white MyTouch4G screen. Here is the output of the update:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
firesnatch said:
Hmm.. Somehow I got it to recognize the PD15IMG.zip. I think I plugged the USB cable into my laptop, pulled the battery, then disconnected the USB cable, then replaced the battery, and when it booted it found the file this time. I'm flashing it now. Wish me luck.
Click to expand...
Click to collapse
ah yes, i should add that... lmao
good luck man.
find me if you need any help. pm should be fine.
EDIT: um press the power button to reboot
saranhai said:
EDIT: um press the power button to reboot
Click to expand...
Click to collapse
Yeah, of course I did that. When it reboots it locks up MyTouch4G white screen again.
firesnatch said:
Yeah, of course I did that. When it reboots it locks up MyTouch4G white screen again.
Click to expand...
Click to collapse
hm... :/
well try flashing it again i guess...
also try flashing the 2.3.4 version, since from what i see, you flashed the 2.2.1 one correct?
How long are you giving it? A first time boot on sense can take 10 minutes.
Sent from my HTC Glacier using XDA App
saranhai said:
hm... :/
well try flashing it again i guess...
also try flashing the 2.3.4 version, since from what i see, you flashed the 2.2.1 one correct?
Click to expand...
Click to collapse
Yeah, I flashed the 2.2.1 image I believe. Tried it 3 times now. Still sticks on the MyTouch4G white screen. I've waited 10-15 minutes before giving up.
I just flashed 2.3.4. Same problem. Here is a shot of the phone just prior to the reboot:
FYI, the Android 2.3.4 PD15IMG.zip in your post here doesn't pass the Image check when trying to flash. It is size 306,558 KB. I instead used the one from this post here, which is 322,694 KB and passes the check + flashes.
Any other ideas? Am I bricked?
Happy New Year everyone!
estallings15 said:
How long are you giving it?
Click to expand...
Click to collapse
Let it sit for 45 minutes just now. Definitely hung.
firesnatch said:
Let it sit for 45 minutes just now. Definitely hung.
Click to expand...
Click to collapse
Hmm, is it still under warranty? Sounds like it might need replaced. . . That's really strange that a PD15IMG.ZIP successfully flashes (according to the bootloader), but refuses to reboot properly. The only thing I can suggest is to try a few more times, then call T-mobile.
EDIT: Nevermind. You bought it on ebay. Hmm. Paperweight?
Sent from my HTC Glacier using XDA App
how much did u buy it for?
comc49 said:
how much did u buy it for?
Click to expand...
Click to collapse
$75 shipped. Oh well
firesnatch said:
$75 shipped. Oh well
Click to expand...
Click to collapse
You could try manually flashing new hboot as it could be that that is corrupted and it believes its flashing it correctly when in reality it's corrupting the partitions try going to the "flashing the eng h-boot" thread in dev section and I believe there is the stock hboot, try flashing that through ADB, I would hope if you're smart enough to disassemble and switch hardware parts you'd be familiar with adb/fastboot commands but let me know if you need help this could be as simple as that although it could be the eMMC but you would usually get the fail PU error which is when the partition update fails (PU). Good luck and let me know!
Nicgraner said:
You could try manually flashing new hboot as it could be that that is corrupted and it believes its flashing it correctly when in reality it's corrupting the partitions try going to the "flashing the eng h-boot" thread in dev section and I believe there is the stock hboot, try flashing that through ADB
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately the phone is S-ON, so I don't think I can flash the engineering hboot. Let me know if there is a way with S-ON.
firesnatch said:
Thanks for the tip. Unfortunately the phone is S-ON, so I don't think I can flash the engineering hboot. Let me know if there is a way with S-ON.
Click to expand...
Click to collapse
No, try Re-flashing the stock one as it could've gotten corrupted somehow
I had this happen to me, i turned off the s lock and flash new rom
Sent from my HTC Glacier using XDA App
Have you try root again.?
sent from. my HTC glacier.s-off .xda premium.
I'm having the EXACT problem, and anyone have a detailed guide on how to turn off s lock for a phone in this condition? Most guides only work on a phone that can boot into the system, not for a phone like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Help! I think my Mytouch 4G is bricked!!!
i have seen a LOT of these threads lately, and this thread is made to hopefully be able solve some of your problems.
most people think that a brick means "can't get into android system, phone is dead beyond repair." most of the time, this is NOT true.
Disclaimer: Please make sure you know what you are doing before proceeding. if your device wasn't bricked before but you somehow screwed it up, i will not be responsible. YOU are responsible for whatever happens to your device. i am just here to give you a few tips, and to help you out. once again, PLEASE MAKE SURE YOU KNOW WHAT YOU'RE DOING BEFORE DOING IT!
Needed Things:
-computer
-android SDK, ADB. PLEASE TAKE THE TIME TO INSTALL AND LEARN TO USE ADB, IT COULD SAVE YOUR DEVICE BIG TIME. we have plenty of guides on how to use adb, please search them up and READ THROUGH THEM.
-a Mytouch 4G, or HTC Panache
-USB cable
-SDcard (doesn't matter what size)
ask and answer these two questions to yourself:
1) can you enter bootloader?
2) can you enter recovery?
if you've answered yes to any one of them, then chances are, you are still saved.
Note: if you can't enter either one of those, and your device doesn't show any signs of life, then don't bother reading on, you are truly bricked.
Notice: When you try flashing the PD15IMG.zip in bootloader, make sure the phone is NOT connected to the computer.
For S-On users:
Q: help! my phone is stuck on the Mytouch logo screen!
A: pull the battery, and see if you can get into the bootloader using volume down+power buttons
if you can get into the bootloader:
1) see if you can wipe data/do a factory reset in bootloader.
2) flash the stock Glacier PD15IMG.zip file choose from either
Android 2.2.1 OR Android 2.3.4
rename both files to PD15IMG.zip if not already.
-put both files in the ROOT of your SDcard, reboot into bootloader/hboot, and follow the onscreen instructions
note: if you are still unclear on what to do, read the "HOW TO RESTORE TO STOCK" section
Q: bootloader is giving me Fail-PU errors when trying to update
A: refer to the eMMC section
For S-Off Rooted users:
rooted S-Off devices are a bit more complicated.
Q: help! i can't get into the android system, phone stuck on Mytouch logo!
A: like for S-On users, see if you can get into either the bootloader, but also the recovery (usually clockworkmod).
if you can get into either of those, wipe data/factory reset, and reboot.
Q: bootloader factory reset, still stuck on Mytouch screen
A: well, if you have clockworkmod recovery (or 4EXT recovery) get into the recovery, wipe all user data/cache/dalvik cache and try reflashing a backup, or flash a new rom.
Q: reflashing didn't work, clockworkmod is giving me errors about mounting something.
A: new way! try to clear cache and dalvik in recovery, somtimes that works. thanks to urmothersluvr for reminding me.
A: there are two things that cause this. both have VERY similar symptoms. the first is because of the failed eMMC chip (refer to eMMC chip section), and the second is because the recovery got messed up, probably because you've been switching between a lot of EXT3 and EXT4 roms. if this is the case, just download the PD15IMG.zip (Android 2.2.1) file (IT WILL RETURN YOU TO STOCK) and start over again. OR you can reflash the recovery through adb (MUST HAVE ENG HBOOT 0.85.2007). thanks to Nicgraner for reminding me! if bootloader gives Fail-PU errors, refer to eMMC section.
HOW TO RESTORE TO STOCK
here are clear instructions on how to flash to stock using the PD15IMG.zip file:
1) download the PD15IMG.zip file:
Android 2.2.1 Android 2.3.4
2) rename the file to PD15IMG.zip if not already
3) place the file in the root of your SDcard, meaning not in any folders
4) power off your device, and reboot into hboot/bootloader by press and holding power + volume down buttons
5) hboot/bootloader should recognize the file, and ask if you want to update
6) select "yes", and wait for the update to finish
*Selections are made with the volume buttons, and hit the power button to select*
7) when the update is finished, hit reboot
8) wait for the device to boot up (may take awhile, first time boot only)
9) congrats, you are now back to stock Mytouch 4G, either 2.2.1, or 2.3.4
Click to expand...
Click to collapse
if you think you have a failed eMMC...
many things can cause the eMMC to die. if you suspect that your eMMC chip has died, please check your eMMC serial using this guide here using adb (for rooted users only, since you must be in recovery for the command to work).
symptoms of failed eMMC:
-massive lagging all of the sudden in android system
-phone suddenly shut down, and you can't turn it on, no matter what you do (if this happens, then yes, you're bricked)
-recovery showing errors about not being able to mount things
-BOOTLOADER SHOWING FAIL-PU WHEN TRYING TO RESTORE BACK TO STOCK USING PD15IMG.ZIP, IF THIS HAPPENS, THEN YES, THAT MEANS YOU ARE TRULY BRICKED. FAIL-PU MEANS FAILED PARTITION UPDATE, MEANING THAT YOU CANNOT WRITE TO THE PHONE/EMMC CHIP ANYMORE.
Click to expand...
Click to collapse
Ok, so my chip has died and i can't turn my phone on. can i send it in to t-mobile to replace it?
A: yes! BUT YOU MUST STILL HAVE YOUR WARRANTY WITH T-MOBILE. if you are S-On, you should have absolutely NO problems replacing at all. if you are S-Off, you might encounter some minor problems, but replacing should still be ok. what i did was play dumb with them, and they just sent me a new one. my old one died of bad eMMC, it was rooted, S-off and everything, even the splash screen said "rooted HTC Glacier" on it.
hopefully, this guide has helped you understand more of what has just happened to your beloved Glacier (MT4G).
if i forgot anything, or if you have anything to add to this, PLEASE LET ME KNOW
if i have helped, please hit thanks!
for the corrupted recovery you don't necessarily need to flash pd15img..you could boot into bootloader then fastboot and reflash the recovery img of your choice. Although some may not know how to.. just a thought
EDIT: Forgot to explain why lol, flashing pd15img will make you lose root whereas just pushing the new recovery will not!
Don't mean to be trollin, just some advice haha
Sent from my HTC Glacier using xda premium
Nicgraner said:
for the corrupted recovery you don't necessarily need to flash pd15img..you could boot into bootloader then fastboot and reflash the recovery img of your choice. Although some may not know how to.. just a thought
EDIT: Forgot to explain why lol, flashing pd15img will make you lose root whereas just pushing the new recovery will not!
Don't mean to be trollin, just some advice haha
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Where is the recovery pd15img.zip u speak of?
Sent from my HTC Glacier using XDA App
urmothersluvr said:
Where is the recovery pd15img.zip u speak of?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
It's in my OP. You can choose either the 2.2.1 version or 2.3.4.
Sent from my HTC Glacier Sense 3.5 using xda premium
saranhai said:
It's in my OP. You can choose either the 2.2.1 version or 2.3.4.
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
If it fails can I still use my phone I'm on? I know my cache won't mount
Edit: fixed it by formatting cache and rebooting recovery. U should add that up there for cache not mounting.
Sent from my HTC Glacier using XDA App
urmothersluvr said:
If it fails can I still use my phone I'm on? I know my cache won't mount
Edit: fixed it by formatting cache and rebooting recovery. U should add that up there for cache not mounting.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Alright i'll add that when I get home
Thanks!
Sent from my HTC Glacier Sense 3.5 using xda premium
EDIT: OP updated, thanks urmothersluvr!
OP updated with instructions on how to return to stock using the PD15IMG.zip file.... if you have any suggestions, PM me
I'm trying to load the pd15img.zip. I have a completely stock phone and for some reason it got stuck on the bootup screen so I'm trying to flash it to fix it.
However after I enter the bootloader and it finds the file, loads it and then checks it, it just returns to the bootloader screen. It never asks me to flash it.
Does anyone have a solution??
Exact same issue as mupepe. Does this mean the phone isn't saveable?
RussianSpring said:
Exact same issue as mupepe. Does this mean the phone isn't saveable?
Click to expand...
Click to collapse
is your phone connected to the computer? just wondering.
also, might be a bad download, try downloading again.....
It is not connected to the PC when flashing. I'll try redownloading the IMG. I get a "Wrong or bad image" thing in Hboot. Formatted SD card to fat 32 and tried a different card. This is a weird issue. I warrantied out the phone but TMO sent me a replacement with the washed out screen so I'd love to fix this.
Mine isn't connected to the computer. I get no sort of error. I'll redownload the image in a bit and report back. Thanks!
thanks a lot
Anyone have luck fixing the No Image or Wrong Image problem or the IMG file just checking loading then doing nothing?
RussianSpring said:
Anyone have luck fixing the No Image or Wrong Image problem or the IMG file just checking loading then doing nothing?
Click to expand...
Click to collapse
try redownloading..
could be a bad download
I downloaded it again and it still doesn't work
****. well 2.3.4 send me back to the bootloader screen and 2.2.1 gives me the main version is older error. All the solutions I've found to that error say to install 2.3.4 which doesn't work! ahhhhhh!
Problems
I bought a MyTouch 4G from Craigslist today (for $ 80, it has the superior screen, is cosmetically a 9.5/10 and it came with all accessories) and it is stuck at the MyTouch 4G screen. One of the local phone places told the seller that the phone needed to be flashed which I tried to do. I downloaded the file in this thread for 2.3.4, put it on the freshly FAT32 formatted MicroSD card, I booted into the bootloader, it found the PD15IMG.zip file, it loaded and checked it and went into the screen with the two green arrows and the one green arrow pointing downwards. Then every time in the middle of it, the phone turns itself off (battery is fully charged). It never asked if I wanted to update either. What could be the problem?
PCLiteratesJax said:
I bought a MyTouch 4G from Craigslist today (for $ 80, it has the superior screen, is cosmetically a 9.5/10 and it came with all accessories) and it is stuck at the MyTouch 4G screen. One of the local phone places told the seller that the phone needed to be flashed which I tried to do. I downloaded the file in this thread for 2.3.4, put it on the freshly FAT32 formatted MicroSD card, I booted into the bootloader, it found the PD15IMG.zip file, it loaded and checked it and went into the screen with the two green arrows and the one green arrow pointing downwards. Then every time in the middle of it, the phone turns itself off (battery is fully charged). It never asked if I wanted to update either. What could be the problem?
Click to expand...
Click to collapse
...lol i'm starting to think the link to the 2.3.4 PD15IMG.zip is wrong..
sorry guys if it is...
hmm have you tried to use the 2.2.1 instead?
I bought two MyTouch 4G's from the same seller (a couple) and his phone works fine, only hers is corky LOL. Both HBOOT screens are identical too, I checked his software version and it is the latest one (2.32.531.1), so I assume that hers is the same, it also shows the same date, July 15 2011 and the same radio 26.13.04.19_M in HBOOT. Maybe there is no PD15IMG.zip file for this latest updated ROM yet? After trying both different PD15IMG.zip files (2.3.4 and 2.2.1), I've been getting the "main version is older" errors on both. No Fail-PU though, so that makes me hopeful I'm thinking that she updated to the latest version and somehow it got corrupted, that is why the phone is stuck at the MyTouch 4G loading screen and won't go any further.
Update: I'm up and running again !! I found a PD15IMG.zip file on the t-mobile support website that worked specifically for the latest 2.32.531.1 update !! Here is the download link (I've uploaded it to megaupload): http://www.megaupload.com/?d=X1EAIPBJ