Related
If this is in the wrong area please mods answer and redirect it into the correct area.
I was wondering if your phone is looped at the first bootloader screen and you cannot access recovery or bootloader is there a way to unbrick your device using a code in the adb?
Please answer...... and move if nessasary.
Thank You
I had been running Cyanogen 3.5.2 and then switched to JACHero 2.2 to see the changes. Then when I tried to switch back to Cyanogen and I kept getting the bootloop. No matter what I did, wipe, flash, wipe again, flash again. Nothing. I assume it might have something to do with the Apps2SD setup but I have no idea. I just reflashed back to JACHero and it is working fine.
chuckhriczko said:
I had been running Cyanogen 3.5.2 and then switched to JACHero 2.2 to see the changes. Then when I tried to switch back to Cyanogen and I kept getting the bootloop. No matter what I did, wipe, flash, wipe again, flash again. Nothing. I assume it might have something to do with the Apps2SD setup but I have no idea. I just reflashed back to JACHero and it is working fine.
Click to expand...
Click to collapse
Did you reflash using the ABD. If you did not then you would have to use the recovery or bootloader mode on the device. Therefore not using the abd commands at all. Im not bashing you or anything btw.
about cyan to jachero same happened to me... it has somthing to do with apps2sd your correct. somthing like the .odex files from hero saving on ur sd partion and ruining the whole setup on cyans. so what i did was use paragon partion manager to completely reformat my sd card and then remade my ext3 partion on it. and it works fine. im never switching off of cyans rom thoe. anymore to much of a headache and stuff.
(as you can tell im drunk and i really dont understand all this rom lingo lol bare with me i hope i helped you?)
nickryan0612 said:
If this is in the wrong area please mods answer and redirect it into the correct area.
I was wondering if your phone is looped at the first bootloader screen and you cannot access recovery or bootloader is there a way to unbrick your device using a code in the adb?
Please answer...... and move if nessasary.
Thank You
Click to expand...
Click to collapse
There are other posts on this but if you can't get into recovery or bootloader you are toast adb may not connect(really it should connect to adb when on the boot screen but many have been through this and haven't been able to get their phones working. I bet you tried flashing the Haykuro SPL("Danger" SPL) right?
It is brick you will have to look into a replacement/exchange if possible.
savethechicken said:
There are other posts on this but if you can't get into recovery or bootloader you are toast adb may not connect(really it should connect to adb when on the boot screen but many have been through this and haven't been able to get their phones working. I bet you tried flashing the Haykuro SPL("Danger" SPL) right?
It is brick you will have to look into a replacement/exchange if possible.
Click to expand...
Click to collapse
Oh no was just wondering cause i am thinking about rooting my phone but under the right direction. Not the posts they have here cause they are to hard to follow. If you or someone could help me i only wanna upgrade to a hero that has flash player and can put notifications out like this one : http://4.bp.blogspot.com/_Q-JSg53A3...AFD4/6TWLdeIi3VY/s400/rosie7-lock-screen2.jpg
I also had bootloop when switching back from jachero to Dude's 1.3. I had to pull the battery out to get it to shut down, but then I was able to use recovery to flash Dude's... how is it that you're unable to get into recovery mode? Have you tried pulling ythe battery?
ohnoezmahfone said:
I also had bootloop when switching back from jachero to Dude's 1.3. I had to pull the battery out to get it to shut down, but then I was able to use recovery to flash Dude's... how is it that you're unable to get into recovery mode? Have you tried pulling ythe battery?
Click to expand...
Click to collapse
If you mess up the SPL you can't get into recovery. The only known method of messing up the SPL is with the "Hero" SPL (afaik, without manually trying to brick your phone).
If you get a bootloop, make sure you wiped AND completely cleared your ext2/ext3 partition with apps2sd. That always seems to cause a bootloop.
Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App
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.
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...
i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
lanceydavid said:
i installed a rom (royal ginger), it loads but after it loads it reboots the phone and does the same thing all over again, i rent to recovery to do a full wipe and re install and it comes up with "E: Cant open /cache/recovery/log" and some more errors, how do i fix this problem? i hope i havent bricked my phone
Click to expand...
Click to collapse
What exactly did u do to get that error??? Did u wipe data,cache,delvik & format system,i always format sd card also in case the sd card has a currupt file... did it automatically give the errors once u flashed?? Did u check the mdsum on the file to make sure u had a full zip file??? What recovery did u use 3.0.2.4 or 3.0.0.6??Sorry need to ask questions in order to help lol.... Ive heard of people fixin their phones with the part7backup-xxxxx.bin file & the pd15 file....just stick those to the root of the sd card go into recovery & let the phone to its thimg..
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
lanceydavid said:
@cmdmilitia13 Thanks so much for even trying to help! i have clockworkmod recovery 3.0.0.5 .... i flashed, worked perfectly, installed the rom the last night, woke up in the morning, phone wouldnt turn on, took out battery, and when it finally loaded, it kepts rebooting back to the loading screen.... i went back to recovery, tried to wipe data and cache, wont work, did delvik, and didnt say if it was successful or not but i formatted sd card, as soon as i try to format system it says:
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log and etc.
as soon as i try a wipe it says the similar
Click to expand...
Click to collapse
Royalginger requires recovery 3.0.0.6 or 3.0.2.4....3.0.0.5 was mainly for cm7 but clockwork updated to flash froyo & gingerbread now... I believe u can dwnload a cm7 rom to the sd card frm the pc then try to flash that if that dnt wrk then if u rooted by using gfree method & have the 0.85.2007 bootloader it should of created a part7xxxx.bin file & that will help unrootin the phne & startin frm scratch again...
Theres a couple threads on here that could help u out,ur not fully bricked tho... I had this issue about 3 months ago when there barely was a fix now at least u have a chance..
i have the 0.86.0000 bootloader, will that be a problem? if not if i google how to unroot i should be able to find it easily?
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
I believe u need to have that 0.85.2007 bootloader but look around the Q&A threads & look for the subjects that says bricked or I think im bricked,those would help u out,im headin to wrk so cnt helo u now sorry...
lanceydavid said:
i also downloaded cm7 tried to install, and the same rom and issues still pop up, so i guess my only choice is to unroot, but how do i unroot without using terminal?
Click to expand...
Click to collapse
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
darinmc said:
If you rooted with gfree, go back to the thread that guided you. It has instructions on how to unroot. Basically you want to place part7backupxxxxxx.zip on the root of your SD, download PD15IMG.zip, place on root of SD, then load bootloader and let it do it's thing, responding when prompted. If you can't mount the card you're going to have to find a way to mount it outside of the phone, either with an adapter or a card reader.
Click to expand...
Click to collapse
Doesnt he need the eng 0.85.2007??
cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
Nope. I'm on 86 and have rooted and unrooted this phone about 30 times helping people and trying stuff.
Sent from my HTC Glacier using XDA App
cmdmilitia13 said:
Doesnt he need the eng 0.85.2007??
Click to expand...
Click to collapse
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
darinmc said:
You need the engineering bootloader to use adb, both will run the PD15IMG.zip.
Click to expand...
Click to collapse
Thanks good to knw,i just thought u needed it since everyone talks about it...
cmdmilitia13 said:
Thanks good to knw,i just thought u needed it since everyone talks about it...
Click to expand...
Click to collapse
The reason we talk about is pretty simple. .85 allows you to use ADB commands and flash stuff via the HBoot engine. Where .86 does not allow you to. So if you get in "semi-brick" mode you can 9/10 times get your self up and rocking.
had it happen earlier today as a matter of fact.
http://forum.xda-developers.com/showthread.php?t=1040463
and this one rings a bell....
http://forum.xda-developers.com/showthread.php?t=1035413
They were both what most people would call bricked, but since they had the .85 engineering screen we could get them up and running.