Database Users

Can't root, did before though

Ok so I've done a bit of searching and asking on androidforums but nobody can figure out my an answer to my problem. Alright, first off originally the phone had android 1.5 but when sprint released the 2.1 update I did it. From there, I used regaws tutorial on rooting the official 2.1 release which worked great. Basically I was on a mission at this point, a mission to try out all the 2.1 based custom rims. I had been using the rom manager app for its ability to wipe and flash new roms without even rebooting to recovery. As you are probably aware, to do anything with rom manager, you have to have their clockwork mod recovery flashed, which is simple to do with this app. So one day I wiped and flashed a new rom, aloysius I think, and after it was trying to boot the new rom it gave me some error message and the installation failed. I think at this point I tried to restore my nandroid, which also didn't work, I'm guessing that you have to be using the same recovery you were using when you created the nandroid? No matter what I did from recovery I could not restore my nandroid, as a last ditch effort I did a factory wipe and then rebooted. I didn't think it would reboot at all, honestly I was way scared and thought that I had bricked the phone but after about 5 minutes it finished booting up. Now I don't understand why or how, but when it came to it was quite obvious, I was back at stock 2.1. I immediately look in the app tray for the superuser app and obviously it isn't there, I've been dealing with the phone as is for about a month. A couple of weeks ago I decided to get back to work, sat down at the computer and tried to root it again using the same exact method. After like 5 attempts I get the same problem, I get to the step where command prompt spells out "UNREVOKED" really big but I notice that instead of having a "$" like it shows in the picture I have a "#". At this point the guide instructs you to open the Superuser app on the app tray on the phone, sure enough, I don't have one. I have tried this probably like 7 times all with the same result. I've even tried to install that .6 update to patch whatever remnant of root access I have and go from there as I'm sure the fact I was rooted once and lost it has something to do with my failure. I've tried running RUU's many times as well and always wind up getting an error 171 USB connection error. I havent heard of anyone else having an issue like this. I'm not sure whether I posted this thread in the right place to really get help either so if this needs to be moved to development or whatever don't hesitate. I'd really appreciate anyone trying to figure this out as I am tired of running the slow stock rom but have exhausted virtually every option that I am aware of, PLEASE HELP ME!

I know everyone is probably still reading that book I posted, but once you get to the end lol please gimme some advice, i've tried everything and don't wanna live with the phone as is for the next year....

It's a little hard to read your original post, but I'll do my best to help. From the sound of it you may still have root.
I haven't had to root on stock 2.1 install, so I'm not familiar with the new method. If you get to a bash shell or terminal prompt that is a '#' rather than a '$', you still have root.
You said that you did a factory wipe on the phone. Did you RUU or did you simply wipe through recovery? Are you still able to get to the clockwork recovery?
If you can get back to your modded recovery, you're golden. I would STRONGLY recommend you flash the newest Amon_RA. http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
If you can get that far, you should just be able to wipe and flash a new ROM.

have you tried to update your sync/drivers on your computer lately?
Sent from my Hero CDMA using XDA App

Oh well I finally got it all figured out, had to rum the ruu twice back to back whole the phone was still frozen at the bootloader. From there I finally was able to re root it.

For ANYONE having difficulty installing TnT Lite 2.00-2.xx

Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662

Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.

Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.

roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task

LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.

roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.

roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App

LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App

Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!

HELP! Getting an error trying to flash 2.5.1.4!

I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.

Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.

I'll give that a shot, thanks!
Sent from my HTC Glacier using XDA App

k20matt said:
Same thing happend to me this morning. it was weird cause before that i was flashing it fine in order to use CM7. I tried reboots but still nothing. I then just flashed ICE and used the rom manager from the ice Rom and it worked. I was able to flash 2.5.1.4. Try that.
Click to expand...
Click to collapse
IT WORKED! Thanks again!

How did it work? Share what you did.

Same thing happened to me yesterday.
Check the clockwork/download/mirror1.kanged.net/recoveries folder on your SD card. Is there a .img file in there called recovery-clockwork-2.5.1.4-glacier.img? If it's not in there that's why you can't flash it, because it can't find the file.
Not sure why the file was missing from the folder.. but thats what it turned out to be.
You should be able to download the image from: http://phones.crackflashers.com/glacier/recoveries/glacier-cwm3src-2.img
Or you can get the file already named correctly out of this zip: http://goo.gl/nZJ7U
But you'll have to dig for it to find it.
then rename it to exactly "recovery-clockwork-2.5.1.4-glacier.img" and put it in the folder. It should work then.

shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.

OptLynx said:
How did it work? Share what you did.
Click to expand...
Click to collapse
I just flashed ice glacier, went to rom manager, select all clockworkmod recoveries, select 2.5.1.4, and that's that
Sent from my HTC Glacier using XDA App

OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Well I had the problem and went through the steps i described above to get it to work... So not sure.
Oh and it didn't say no legacy recoveries found, it said there was an error trying to flash. But it's working fine for me now after I out the img in that folder... so up to you guys if you want to try it.
Sent from my HTC Glacier using XDA App

Skunk2 DC said:
I've flashed it before, but decided to install evil's rom (reverted back to 2.5.1.2).. I didn't like it so I went back and restored CM7, now I can't flash 2.5.1.4.. I get an error saying "an error occurred while flashing your recovery". Please help! I'm new to these stuff, thanks guys.
Click to expand...
Click to collapse
its not just you, everyone is getting this error. Youll need to flash cwm 3 through fastboot or terminal emulator if you want to go to CM7 or MIUI until TrueBlue_Drew gets it fixed and releases an update.

Skunk2 DC said:
IT WORKED! Thanks again!
Click to expand...
Click to collapse
No Problem. Glad it worked. it was the only way i knew.

OptLynx said:
shortskoolbus it makes no diff. Now if you were missing the file then it would give you this error message "No legacy recoveries found, Are you connected to the internet?" and if you do have the file then it gives you this error message "An error occurred while flashing your recovery."
I was trying to install new OC kernel and came across this as I originally thought it maybe linked to ClockworkMod as some folks in thread reported installing kernel without wipe cache/davlik. So I try to update it to 3.0.0.5 and it was successful but without result so I had to manually install 3.0.0.0 via console.
As I posted it originally on Q&A section when it happened none had issue and now everyone is having issue, POS I can't even access Dev thread as its says I need 10 posts when I have more I can't post it.
Click to expand...
Click to collapse
Actually I am not sure what you are talking about OptLynx. What shortsloolbus said is 100% correct. If you are missing the image or it is in the wrong place it does not give you the "no legacy recoveries found" error. It will just say "error flashing recovery". And the reason it worked when people switched to a old Ice glacier rom is because IG isnt running the latest Rom Manager that has now changed the location of where it keeps the recovery images.
See my thread here for the new zip that places everything in the correct place. http://goo.gl/O5SlI

[Q] EVO Rom/Root problems

I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!

Try reflashing your recovery image.

BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.

noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.

Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/

Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?

noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.

Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard

noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.

Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.

ok thanks, i'll try it when I get back home

jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...

So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?

noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.

noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.

bricked?

I am stock at tmobile screen, it doesnt go any further
i went in recovery it returns as
E:Can't Mount /cache/recovery
all the way down
the "fastboot erase recovery" returns with "FAILED (remote: not allowed)" and the "fastboot flash recovery recovery.img" returns the same thing. Any other suggestions???
I tried to restore pd15img and
it works little bit, and it asked me to upgrade, i pressed the volume up
1 BOOTLOADER - Fail-PU
partiton update fail!
update fail!

This has happened to quite a few people lately and I don't think they have been able to come back from it. Out of curiosity though, what caused this? Were you flashing something and this happened? Do you have the engineering bootloader? Attached is a thread of someone with the same problem, and like I said, there are a couple more out there.
http://forum.xda-developers.com/showthread.php?t=984790

I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.

I had the same fastboot errors when trying to flash from 3.0.0.5 to 2.5.1.2 after i mistakenly flashed 2.5.1.2 when i had cm7. You may need to update your sdk. I had to install my HTCdrivers on a new box and Download the tools folder from here http://forum.xda-developers.com/showthread.php?t=928370 to get it working.

theghazi said:
I change roms many times, and recovery many times, this time i had been using 3.006 modified with battery charge.
didnt have a problem until i put the royalglacior 1.5 version.
than i could use the wifi, it gave me an error, i rebooted few times, and always error, and finally gave up.
Click to expand...
Click to collapse
First, there is only RoyalGlacier v 1.2 as of the latest for now. Since you used that CWM 3.0.0.6 while battery charge off, there is a chance it might have reverted back to CWM 3.0.0.5 and RoyalGlacier requires 3.0.0.6 and stock restore requires 2.5.1.4 but your recovery may be 3.0.0.5. Try flashing a ROM that just requires 3.0.0.5. For future reference, use this version of CWM 3.0.0.6 from here (http://forum.xda-developers.com/showthread.php?t=944681). That sticks and never reverts back to .5.

Thanks for replies, n advices.
I have tried every which way possible to put the recoveries, and all failed.
I have had 3.0.0.6 modified for a while. was not going back and forth with 2.5.1.4
anyone else come out of this mess,
if not is there a way to get it to even at s - on and unroot?
I dont think so, but worth to ask
thanks

I'm having the same issue where it gets stuck at the Tmobile spash screen and when i boot into clockwork, it gives me the cache error. Formatting it through clockwork doesnt work, and when i try to restore it it also give me an error. I tried to format through adb but that hasn't worked either, unless I'm typing in the command wrong

I dnt believe there is a way to fix that issue,i had that issue awhile back on my 1st mytouch 4g,i had cm7 & made the mistake of tryin to nandroid restore a backup which I forgot was stocked froyo & everythin flashed ok but got stuck in bootloop,so battery pulled went to recovery & had all those errors u mentioned & never found a fix.....called tmobile,got a replacement no problems 2 mnth later & warranty still there..... Now I have clockwork 3.0.0.6 & havent ran into that issue yet,goodluck let us knw if u find a fix....
Permrooted s=off-MyTouch 4g-White
Eng-0.85.2007
Rom-RoyalGinger

I like balls

I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App

theghazi said:
I am not using tmobile. I know it is covered under HTC but wont they refuse if they see s off?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Im not really to sure,a friend of mine had the same issue & went thru HTC & got a replacement so want im guessin is they dnt care but dnt hold it against me,it could of been 1 of those lucky times. All he said was that the phone wnt boot & they just sd it was a known issue & sent him another one...

well I think I've successfully bricked my mt4g. It was working fine until I installed the latest clockwork version and RoyalGinger, tried to restore some applications + data with mybackup root but it froze. Then it was stuck on a bootloop, went back into clockwork and started getting the "can't mount cache" errors. Now it's stuck on the T-Mobile splash screen if I try to do a normal boot, bootloader works and it also goes into clockwork, but it's not able to do any factory resets/wipe. Tried the factory image file and it fails on the first 5 or 6 items, skips another item and hangs at flashing the radio. Now it needs to be replaced and T-Mo is out of stock of the red mt4g's, so I have to wait until they have stock of red ones, then it's going to suck if I get one with a bad screen. I got offered a black one, but I just like my red one too much.

did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).

darinmc said:
did you include the part file when flashing the PD15IMG.zip?
"there needs to be part7backup-1294463706.bin file on your sd card with the PD15IMG.zip file...both on the root of sd card."
I'm thinking that the file comes stock on the sdcard, but when we format our sdcard it wipes it. I know I personally ran the PD15IMG.zip file twice on my phone and both times it worked great, but both times I did it before I wiped my sdcard (and I do remember a ridiculous amount of extra stuff on the sdcard when it came with the phone).
Click to expand...
Click to collapse
That part7-xxxxx.bin file is created when u root with the gfree method,it doesnt come stock on the sd card... what method did u use to root...dnt use unlockr.com methods,its old & doesnt give true oerm root...

I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.

darinmc said:
I made an assumption, i just used the basic root.sh script so I didn't read into the gfree method (see no need). I just know that people who have had trouble reverting to stock with the PD15IMG.zip fixed the issue by putting that part7backup file on the root of their sdcard.
Click to expand...
Click to collapse
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...

cmdmilitia13 said:
gfree method would of gave u S off & that backup file,really I dnt think theres a fix for that just yet,without that file..... For future reference never restore data fron any backup app(ex.titanium,astro erc) u can only restore apps cause then u restorin data from a different rom & tryin to put it on a current rom that probably isnt the same...
Click to expand...
Click to collapse
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.

darinmc said:
no idea where this is coming from. I was just offering a suggestion to the op. As you can clearly see I am not the op. I do not have issues. I simply made an assumption about the gfree method, which was cleared up, though I still think it's a very real possibility that the op didn't put the part7 file on the root of his sdcard when he flashed the pd15img.zip. Either way, I thank you for your advice, but I'm not the one seeking it here.
Click to expand...
Click to collapse
My fault I should of double read,i have an issue with just skimmin thru things & look what happens lol...

Has anyone found a fix for this? Same issue.

Isubbie said:
Has anyone found a fix for this? Same issue.
Click to expand...
Click to collapse
nope nothing yet,not that I knw off...