Hey guys,
I did something stupid, by accident, that I know better than, and now I need help. So my phone is rooted, using the 1 click root method that came out when the phone first dropped. Everything went fine with that and it has been working great. Someone asked about an update and if it was available and so I thought I would use my software update to check and see if one was available. Mecha_VERIZON_WWE_1.13.605.7-1.12.605.6 was sitting there waiting to be installed, and I accidentally hit OK instead of reject. This cause the phone to reboot and attempt to install the update. It fails however, with CMR saying failed to verify whole-file signature, which is fine. The problem is, when I reboot and the phone starts up, I get in for about 15 seconds and then it shuts the phone down and attempts to install the update file again. It will then fail on the signature verification again, and I can then reboot, and that just starts the whole process over. What do I need to do? How can I keep my phone from attempting to install this update every time it starts up?
Any help is greatly appreciated!
Thanks,
Ray
I take it that you did not make a backup in recovery. If so you should try to boot in recovery and install the backup.
I didn't. My guess is because I was stupid and lazy and did the one click method rather than putting in the time and energy to do it all myself and make sure that step was done. What recourse do I have at this point? Is my only option to wipe data/factory reset?
Remove your SD card, put it in an adapter, put it in your PC (or a card reader connected to your PC), and delete the PG05IMG.zip file.
Agree with the post above. But the issue doesn't have anything to do with your method of rooting.
There are a few things you should always do... Make backups and either rename the PG05IMG files or delete them.
Don't even need to remove the card most explorer apps can delete from the sdcard
Sent from my ADR6400L using XDA App
tumbleweed65 said:
Don't even need to remove the card most explorer apps can delete from the sdcard
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Not if its in a loop that only gives him 15 seconds to access it. Unless he is crazy fast lol. Try using the card reader method...although I wonder if an update sent by Verizon is handled the same way as the ones we do are. Hopefully it will be as simple as finding the PG05IMG.zip file on your sd-card.
Beastclaw said:
Not if its in a loop that only gives him 15 seconds to access it. Unless he is crazy fast lol. Try using the card reader method...although I wonder if an update sent by Verizon is handled the same way as the ones we do are. Hopefully it will be as simple as finding the PG05IMG.zip file on your sd-card.
Click to expand...
Click to collapse
My bad didn't catch the 15 sec reference.........but with REALLY fast fingers......lol
Sent from my ADR6400L using XDA App
Related
I have a rooted thunderbolt running bamf and i found the font settings in the toolkit and i thought wow this would be cool to change fonts, so i picked out one that i liked and it said has to reboot to apply so i clicked reboot and now my phone is stuck on the htc screen when you initially boot.. the only thing i did was pick a font..
.. i tried to get into bootloader but it wont let me pick any options to reboot it just goes to a update and wont let me pick any option..
i did have a backup in clockwork made but i dont know how to get into it since i cant even get the phone on
need some help guys..
Well if it is trying to update while in HBoot that means you have an existing PG015img.zip on your phone (probably a radio that you flashed awhile ago). This is a big mistake to have not deleted this file. Always delete a PG015img.zip after using it (or renaming it)
The only thing I can suggest is if you have a friend with another smartphone, put your SD card in their phone, and delete that file.
Or if you have a micro sd card reader for your computer, use that to delete the file.
With that file on your SD card, you won't be able to boot into your bootloader, because it will automatically flash a PG015img.zip
xebryus said:
Well if it is trying to update while in HBoot that means you have an existing PG015img.zip on your phone (probably a radio that you flashed awhile ago). This is a big mistake to have not deleted this file. Always delete a PG015img.zip after using it (or renaming it)
The only thing I can suggest is if you have a friend with another smartphone, put your SD card in their phone, and delete that file.
Or if you have a micro sd card reader for your computer, use that to delete the file.
With that file on your SD card, you won't be able to boot into your bootloader, because it will automatically flash a PG015img.zip
Click to expand...
Click to collapse
Yeah thats where im at right now, i just got a sd card reader and removed it so i could get it into recovery, got that part out of the way, now i need to put it back on so i can get it updated and then get a radio on there
Willis_G said:
Yeah thats where im at right now, i just got a sd card reader and removed it so i could get it into recovery, got that part out of the way, now i need to put it back on so i can get it updated and then get a radio on there
Click to expand...
Click to collapse
?? Don't put the radio back on there. Once you flash a radio, its done, its on your phone. The only time you should have a radio on your SD card is when you need to actually put a different one on your phone. You phone does not run off of radio on your SD card
I agree...the one time I forgot to delete the radio image off my SD after an update...I had my phone get caught in hboot trying to update again while at work. I had to borrow a friends micro SD reader to pull the file before I could resolve my issues. Would have been much easier if I had deleted it when I was done.
xebryus said:
?? Don't put the radio back on there. Once you flash a radio, its done, its on your phone. The only time you should have a radio on your SD card is when you need to actually put a different one on your phone. You phone does not run off of radio on your SD card
Click to expand...
Click to collapse
I know i realised that shortly after and never reinstalled it Thank you for the reminder.
jbg25 said:
I agree...the one time I forgot to delete the radio image off my SD after an update...I had my phone get caught in hboot trying to update again while at work. I had to borrow a friends micro SD reader to pull the file before I could resolve my issues. Would have been much easier if I had deleted it when I was done.
Click to expand...
Click to collapse
Yeah thats exactly what i had to do too, it freaked me out becuase i couldnt use any of the options in the menu and it kept just jumping to the updates
but its all good now.. kinda crazy how the phone bricked because of a font selection, i wont ever touch that option again though.
If you have a back up from clockworkmod try using adb... type adb reboot recovery in command prompt while your phone is connected to your computer, and once you get into clockworkmod recovery restore your back up. I had a problem with my lockscreen, I also didn't delete my radio, and this worked for me.
Sent from my Xoom using XDA App
Willis_G said:
Yeah thats exactly what i had to do too, it freaked me out becuase i couldnt use any of the options in the menu and it kept just jumping to the updates
but its all good now.. kinda crazy how the phone bricked because of a font selection, i wont ever touch that option again though.
Click to expand...
Click to collapse
It didn't brick. It just froze.
If it bricks you will know it.
As for the radio, keep it on your SD. That way if you need to change it, its there. Just rename it.
For example: "MR2-PG05IMG.zip"
Sent from my Synergized Thunderbolt via XDA Premium App
CanesDrew said:
It didn't brick. It just froze.
If it bricks you will know it.
As for the radio, keep it on your SD. That way if you need to change it, its there. Just rename it.
For example: "MR2-PG05IMG.zip"
Sent from my Synergized Thunderbolt via XDA Premium App
Click to expand...
Click to collapse
That's exactly what I do, and what I suggest in my q AND a thread. Also, after it's there on your root and renamed, CHECK the MD5!
The problem started when after I flashed the recovery with Odin. When I booted into the recovery and tried to install the superuser zip file I keep getting this message: "E:cant copy META-INF/google/android/update-binary". I get this message when I try to flash a Rom: "E:Can't open /sdcard/update-unamed-1.3.1-full.zip". I've been trying to flash the CM7 nightlies and the "Unamed" Rom. Any help with this will be much appreciated.
Also, I ended up having to install superuser via SuperOneClick
Honestly, I stopped trying after the phone kept confusing me with SD Card, External Card, and Internal Card/External SD Card BS it was giving me.
I just left my phone rooted, lol.
Sometimes, this tends to happen if you rooted your phone with an anti-virus software running on your PC which can hinder the rooting process. (always the case with my HTC Inspire 4G). So turning it off could allow you to re-download Odin, and run the program again to root it again so it can install the proper files.
Once you get it re-rooted, get into CWM, do a backup, and Clear your Cache, Data and reinstall the ROM from your Internal Card or External Card (which ever you used to place the ROM in).
Good luck.
homescrub said:
Honestly, I stopped trying after the phone kept confusing me with SD Card, External Card, and Internal Card/External SD Card BS it was giving me.
I just left my phone rooted, lol.
Sometimes, this tends to happen if you rooted your phone with an anti-virus software running on your PC which can hinder the rooting process. (always the case with my HTC Inspire 4G). So turning it off could allow you to re-download Odin, and run the program again to root it again so it can install the proper files.
Once you get it re-rooted, get into CWM, do a backup, and Clear your Cache, Data and reinstall the ROM from your Internal Card or External Card (which ever you used to place the ROM in).
Good luck.
Click to expand...
Click to collapse
CWM and root are not even related....
root is root access to your OS /system and its functions. it has nothing to do with RECOVERY or anything outside of a RUNNING OS. i wish everyone would understand that.
as long as CWM is there, AND WORKING PROPERLY, rooting has nothing to do with it. you can flash a new rom from bone stock OS, as long as you have the CWM kernel.
@OP, you have these files (roms) located on the INTERNAL SD right?
I think that's why @homescrub said:
"and run the program again to root it again so it can install the proper files."
Proper files being cwm. As of yet I don't know of a way to install cwm without root on this phone. I know the captivate previously allowed an update to be flashed using stock recovery to get cwm.
Sent from my páhhōniē
Are you clearing your cache before trying to flash zip from sd card? I know I got a similar problem when I didn't clear cache.
Sent from my Samsung GT-I9100
gr8hairy1 said:
I think that's why @homescrub said:
"and run the program again to root it again so it can install the proper files."
Proper files being cwm. As of yet I don't know of a way to install cwm without root on this phone. I know the captivate previously allowed an update to be flashed using stock recovery to get cwm.
Sent from my páhhōniē
Click to expand...
Click to collapse
how do you flash CWM?
through ODIN
that does NOT require root. you dont flash it via ROM manager....so whats the need for root to add CWM?
and what is this 'proper files' crap? you either have CWM or you dont, its not half-assed
nah its cool. im done here. i will let the misinformation fly. let the noobs run in circles. this website is going to **** so fast these days.
No man ....you should help these guys....just lighten up...and I apologize for coming off like that.....and one place I CAN understand is seeing what's going on in the forums....it is chaos sometimes.....I am just tired of seeing noobs who need help get ripped up.....just as much as I am tired seeing noobs posting +1 and Great Job, in the Dev forums. I just think this is the place to help them get a good understanding so there is not another new thread with this same question.
Sent from a HD2 ICS
AntwanL said:
Are you clearing your cache before trying to flash zip from sd card? I know I got a similar problem when I didn't clear cache.
Sent from my Samsung GT-I9100
Click to expand...
Click to collapse
Thanks this really helped!! Lol I can't believe I forgot to do something like this lol I Odined back to FULL stock, flashed the zedomax kernal with root, wiped data and cache, flashed the rom now all is well
Come on guys, you are both better than this. Shake hands, help the OP, and lets make xda a better place..
verizon forced an update on my rooted stock thunderbolt. i have Revolutionary for recovery but when i load it up it immediately tries to install an update. i cannot select any options.
it asks for me to install or cancel the update. after canceling there are no options but reboot.
what should i do to try to recover out this?
thanks
You need to download a recovery and clear caches and then see what happens. You will have to fastboot flash the recovery. I'm not 100% sure but you may be able to delete the update file from your sd card to stop the update.
Sent from my ADR6400L using Tapatalk 2
you need to boot into rev and goto advanced unmount /cache and format /cache and reboot the ota update will say failed when u and you'll be good had the same issue couple days ago
the issue is i cannot clear cache via Revolutionary because as soon as it starts i get "Do you want to start update?". if i choose no i can only reboot from there. if i choose yes it will just try to update and hang
i also cannot seem to get to fastboot because of the above as well.
any other options here?
You need to delete the downloaded update from your sd card. If you don't then it will continue to do this.
Sent from my ADR6400L using Tapatalk 2
thanks so much.
i booted to Revolutionary w/o the SD card. Then flashed Clockwork using
http://forum.xda-developers.com/showthread.php?t=1122694
After that i was able to the wipe the cache using Clockwork and get back into my phone. from there deleted the update file
going to add the OTABlock from this thread http://forum.xda-developers.com/showthread.php?t=1664082
hopefully that will stop verizon from pushing on another one
thanks!
Deleting Update File
Forgive me, bit of a noob to rooting and such. I downloaded Astro File Manager and also hooked up my phone to my PC and entered the USB storage but cannot find the update zip.
How should I find it?
It will be in the root directory of the SD card and called "PG05IMG.img" i believe
Finding update ZIP
Can I find it via Astro File Manager or do I need to plug into a PC?
Yeah you sure can
Sent from my ADR6400L using Tapatalk 2
Big Red been killing me too. I just cleared the cache on the sd and will see what that does. I am a complete n00b at this so I dont know how to load the blockota program without a .exe. GGRRRR
Deleting Zip
I'm not sure what I'm doing wrong, but I have looked all over the SD Card, and I cannot find the file. For the third straight night, after deleting the cache, it tried to force the update, and my phone went into the shut down loop.
I went into a folder labeled "root" but it was empty. I'm trying to flash the zip that will disable the OTA now, but can anyone instruct me on where to go on the SD Card to delete the update?
SBS0311 said:
I'm not sure what I'm doing wrong, but I have looked all over the SD Card, and I cannot find the file. For the third straight night, after deleting the cache, it tried to force the update, and my phone went into the shut down loop.
I went into a folder labeled "root" but it was empty. I'm trying to flash the zip that will disable the OTA now, but can anyone instruct me on where to go on the SD Card to delete the update?
Click to expand...
Click to collapse
When you open the SD card it will be below the folders. You won't have to go into any folders to find it.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
When you open the SD card it will be below the folders. You won't have to go into any folders to find it.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
When I Open the SD card with Astro, the only files below the folders are "pcsc_pcsc_00001," "SELog," and Superuser. No update Zip.
Try this. Go into system/etc/security and change otacerts to otacerts.bak this will prevent the update from trying to start ever again.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Try this. Go into system/etc/security and change otacerts to otacerts.bak this will prevent the update from trying to start ever again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Before I do that, I finished installing the OTA Block Zip about an hour ago. Should I wait to see if that holds and fixes the issue before I do what you suggested? Thanks for all the help, appreciate it.
SBS0311 said:
Before I do that, I finished installing the OTA Block Zip about an hour ago. Should I wait to see if that holds and fixes the issue before I do what you suggested? Thanks for all the help, appreciate it.
Click to expand...
Click to collapse
It wouldn't hurt to wait and see.
Sent from my ADR6400L using Tapatalk 2
SBS0311 said:
Before I do that, I finished installing the OTA Block Zip about an hour ago. Should I wait to see if that holds and fixes the issue before I do what you suggested? Thanks for all the help, appreciate it.
Click to expand...
Click to collapse
Did it work for you? My girlfriend's phone is in the same situation and I really don't want to take her off stock as she is happy with her phone even after all this time (got her tbolt a month after it dropped).
Sent from my Kindle Fire using xda premium
I really thought I got it when I found what I thought to be the update in the folder temp.apk. but no. please give me a cliff note hoe to load the OTAblock HELP ME I AM GOING TO SET MY HAIR ON FIRE
ok I'm also new to the thunderbolt on 2.2.1 but this is what i did to fix it. first thing i did was turn on wifi and connected to my home network by the time it connected the phone rebooted and tried to flash update but it failed and got stuck at the android with the triangle so i did a battery pull and it booted normally as soon as i could open the playstore i downloaded rom manager free.as soon as it finished installing the phone powered down and tried the update again and failed and got stuck so i did another battery pull. i powered up and as soon as i could i opened rom manager and flashed a recovery as soon as it finished the phone powered down again, it tried to flash again and failed i did one last battery pull and when it rebooted i opened rom manager and rebooted into recovery and just cleared cache and then rebooted. finally when it booted it said install failed and hasn't came back yet I'll post if it tries to update again
Hey all. Can anyone tell me exactly what "success rebooting by reason oem-00" means? And why is it every time I boot into recovery I get can't mount cache/recovery/command. I believe its my sdcard. Thanks!
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Hey all. Can anyone tell me exactly what "success rebooting by reason oem-00" means? And why is it every time I boot into recovery I get can't mount cache/recovery/command. I believe its my sdcard. Thanks!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I doubt it's your SDcard. Its mount point is at /sdcard, not /cache. Sounds like you either need to wipe your cache or you're trying to do something with s-off when you're still s-on.
This is making the assumption that you're trying to flash an update via recovery. If not, please ignore.
Tourney3p0 said:
I doubt it's your SDcard. Its mount point is at /sdcard, not /cache. Sounds like you either need to wipe your cache or you're trying to do something with s-off when you're still s-on.
This is making the assumption that you're trying to flash an update via recovery. If not, please ignore.
Click to expand...
Click to collapse
I'm completely stock. Just when I make a selection in recovery I get a bunch of errors. I can't factory reset, well I can but it won't fix the problem. I can run an ruu over and over and still get the same errors. I'm just wondering what the success reboot means and why it won't let me choose anything in recovery. Should I flash 4ext?
Sent from my PG86100 using xda app-developers app
Ya me to think its sd card problem i recomennd format card ree root re install clock work mod it will fix it .....
HOPE SO
DONT JUST SAY THANKS CLICK IT..
Sent from my LG-P500 using xda premium t from my LG-P500 using xda premium
harshgpt816 said:
Ya me to think its sd card problem i recomennd format card ree root re install clock work mod it will fix it .....
HOPE SO
DONT JUST SAY THANKS CLICK IT..
Sent from my LG-P500 using xda premium t from my LG-P500 using xda premium
Click to expand...
Click to collapse
I've already formatted, without backing up my picture music ect.., and still won't fix. What could be causing the ruu not to fix my phone?
Sent from my PG86100 using xda app-developers app
It still sounds to me like it's not an SDcard issue since the mountpoint isn't /sdcard, but after looking at some Google results I could be wrong. Do you still get the error if you boot with the SDcard removed?
Tourney3p0 said:
It still sounds to me like it's not an SDcard issue since the mountpoint isn't /sdcard, but after looking at some Google results I could be wrong. Do you still get the error if you boot with the SDcard removed?
Click to expand...
Click to collapse
I'm not sure. But I really don't wanna pull the sd. That requires taking the battery out and if I do that I'm stuck in a boot loop.
Sent from my PG86100 using xda app-developers app
I believe you can unseat the SD card without entirely removing it or the battery. If not, no big deal.
What method are you using to flash the RUU? It seems to me like the installer would automatically wipe the /cache directory, but that's probably not a safe assumption to make. At this point it couldn't hurt to install 4ext and make absolutely sure all partitions other than sdcard are wiped. Also, do you get any mount errors other than /cache/recovery/command?
I would try the following, seeing if there is progress after each step:
1) Unseat the sdcard without removing the battery, if possible. If not then skip this step.
2) Install 4ext and wipe cache (all cache, not just davlik)
3) Remove battery and remove sdcard. I know this sucks and you'll get boot loops, but it doesn't matter because the next step is:
4) Wipe all partitions other than sdcard. Even wipe sdcard if you've got a backup. Then attempt an RUU install.
If none of these work, I'm out of ideas. Maybe someone else can chime in. I know there used to be a lot of reports from other devices about /cache/recovery/command and some other directories not being mountable when the eMMC died. It's possible yours is dying and the cache is getting corrupted by hardware failure. That's a worst case scenario, but we gotta eliminate all other possibilities before we make that call.
Tourney3p0 said:
I believe you can unseat the SD card without entirely removing it or the battery. If not, no big deal.
What method are you using to flash the RUU? It seems to me like the installer would automatically wipe the /cache directory, but that's probably not a safe assumption to make. At this point it couldn't hurt to install 4ext and make absolutely sure all partitions other than sdcard are wiped. Also, do you get any mount errors other than /cache/recovery/command?
I would try the following, seeing if there is progress after each step:
1) Unseat the sdcard without removing the battery, if possible. If not then skip this step.
2) Install 4ext and wipe cache (all cache, not just davlik)
3) Remove battery and remove sdcard. I know this sucks and you'll get boot loops, but it doesn't matter because the next step is:
4) Wipe all partitions other than sdcard. Even wipe sdcard if you've got a backup. Then attempt an RUU install.
If none of these work, I'm out of ideas. Maybe someone else can chime in. I know there used to be a lot of reports from other devices about /cache/recovery/command and some other directories not being mountable when the eMMC died. It's possible yours is dying and the cache is getting corrupted by hardware failure. That's a worst case scenario, but we gotta eliminate all other possibilities before we make that call.
Click to expand...
Click to collapse
Yes when I try to wipe the cache in stock recovery I get a bunch of mourning errors. Recovery.log last.log and a few others. I'll try yo get the SD out. If not I'll install 4ext and try to wipe cache. How would I go about wiping my partitions? I can use 4ext without root correct? Thanks!
Sent from my PG86100 using xda app-developers app
AGoogleUser said:
Yes when I try to wipe the cache in stock recovery I get a bunch of mourning errors. Recovery.log last.log and a few others. I'll try yo get the SD out. If not I'll install 4ext and try to wipe cache. How would I go about wiping my partitions? I can use 4ext without root correct? Thanks!
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Installing 4ext without root should be no problem. Just make sure the device is unlocked using the HTC Dev Tool (mandatory). Then go through the flashboot process for recovery.img. It couldn't hurt to install SuperSU while you're in there, though that's outside the scope of what we're trying to repair right now. Once you're in 4ext, under the Wipe menu, there should be an option for "Wipe all partitions other than sdcard" (paraphrased). Go with that. Though if the stock recovery didn't do it, I don't have high hopes for 4ext to be able to.
The fact that you're getting multiple mounting errors leads me to believe you have a bad eMMC. If all the steps from the previous post fail, that'll tell you for sure.
Tourney3p0 said:
Installing 4ext without root should be no problem. Just make sure the device is unlocked using the HTC Dev Tool (mandatory). Then go through the flashboot process for recovery.img. It couldn't hurt to install SuperSU while you're in there, though that's outside the scope of what we're trying to repair right now. Once you're in 4ext, under the Wipe menu, there should be an option for "Wipe all partitions other than sdcard" (paraphrased). Go with that. Though if the stock recovery didn't do it, I don't have high hopes for 4ext to be able to.
The fact that you're getting multiple mounting errors leads me to believe you have a bad eMMC. If all the steps from the previous post fail, that'll tell you for sure.
Click to expand...
Click to collapse
Okay. Just gotta wait since I let my dad borrow my laptop. Should be home soon. If it is emmc, where does that put the phone? Beyond repair? If so I'm not to worried since I'm upgrade eligible soon. Just worried that I'm gonna get stuck in a bootloop and have to use the recovery option from fast boot since thats the only thing that cures the bootloop (until next battery pull) and start over again. Pain in the butt!
Sent from my PG86100 using xda app-developers app
I would recommend that you do a Titanium Backup, but since you don't have root that's out of the question. Kind of an unfortunate situation. I've never done this, but it seems like you could probably use Online Nandroid to make a nandroid backup of your working system. Then if you ever get stuck in a boot loop, you could restore the backup to your current (hopefully) working configuration. It doesn't help you right now, but it might help in the future. Just make sure to root it while you're doing all this.
I believe eMMC is on the main logic board. You might want to call Sprint to confirm, but it stands to reason that you could probably swap in another one. I'm noticing a couple on eBay in the 30-40 dollar range. Not sure if there are any phone-specific values on the logic board that make the board unswappable, but hopefully Sprint could tell you for sure.
Maybe you'll get lucky and that's not the problem anyway.
Tourney3p0 said:
I would recommend that you do a Titanium Backup, but since you don't have root that's out of the question. Kind of an unfortunate situation. I've never done this, but it seems like you could probably use Online Nandroid to make a nandroid backup of your working system. Then if you ever get stuck in a boot loop, you could restore the backup to your current (hopefully) working configuration. It doesn't help you right now, but it might help in the future. Just make sure to root it while you're doing all this.
I believe eMMC is on the main logic board. You might want to call Sprint to confirm, but it stands to reason that you could probably swap in another one. I'm noticing a couple on eBay in the 30-40 dollar range. Not sure if there are any phone-specific values on the logic board that make the board unswappable, but hopefully Sprint could tell you for sure.
Maybe you'll get lucky and that's not the problem anyway.
Click to expand...
Click to collapse
Normally i use App Monster Pro. No root. Im going to back up and and flash the recovery right now. Ill let you know what happens. Hopefully this works.
well i removed the battery and sd card and replaced the battery and she booted up fine! no bootloop this time. Maybe its the sd after all? but i think your right cause i get cant mount cache recovery command and thats not on the sd like you said. Im going to boot back down, remove battery reinstall sd and then see if it boots up.
EDIT: reinserted sdcard and it booted up fine AGAIN. Why phone?! haha. Wonder what was causing the bootlooping when the battery was removed?
I checked for those locations in my cache directory and they don't exist for me either. That probably means they're created dynamically during recovery, but I know very little about what happens behind the scenes there. Maybe certain parts of your cache are unwriteable. Just to clarify, the mount errors happened even while the sd card was out and continued to exist even after it was put back in, right? Maybe it's the sd card after all if not. Any errors while wiping all the partitions?
Glad to hear that it's at least sort of working for now. Couldn't hurt to do a nandroid backup anyway just in case it happens again while you're out and about and don't have time to do a full manual reinstall.
Tourney3p0 said:
I checked for those locations in my cache directory and they don't exist for me either. That probably means they're created dynamically during recovery, but I know very little about what happens behind the scenes there. Maybe certain parts of your cache are unwriteable. Just to clarify, the mount errors happened even while the sd card was out and continued to exist even after it was put back in, right? Maybe it's the sd card after all if not. Any errors while wiping all the partitions?
Glad to hear that it's at least sort of working for now. Couldn't hurt to do a nandroid backup anyway just in case it happens again while you're out and about and don't have time to do a full manual reinstall.
Click to expand...
Click to collapse
Haven't flashed the recovery just yet. My primary goal was to get this boot looping to stop. Success! I will flash recovery tonight. And I haven't checked the recovery.
Sent from my PG86100 using xda app-developers app
Today, I wanted to flash myself to the "stock RUU" provided by Wind Mobile for my HTC Amaze (4.0.3). Since I no longer had the stock recovery to flash this and, for some reason my phone had cleared the backup I made of HTC sense, I decided to use a trick I read on the forums. This trick some of you may had heard is to Relock the bootloader. Which I did using Hasoon2000's Amaze All in one tool kit. My problem after I had done that was it displayed a "Security Error" in the Bootloader and, each time I turned off the device it will put me in the bootloader with that devastating message. So being the person I am I panicked and, reverted back to what I knew before. So I had unlocked the bootloader again, without having access to Android so far. Now as I turned on the phone, I was greeted with the Cyanogenmod 10 bootscreen. I had thought that it was over.However I could have not been more wrong. It would not get passed the screen. I kept it there for a good hour. Again I knew my next course of action is to go into my recovery which is 4ext for your information. It took longer then usual to get into the recovery. In the past it only took the recovery to the count of 11 to get in however this time at the count of 21 . "Please wait! Recovery takes a long time booting without access to /internal_sdcard" at around the count of 42 it says "Error mounting sdcard" Then the recovery booted into safemode. In safe mode I cannot run backups recoveries or anything. After a bit of looking around at what I can and cannot do I decided to wipe the cache and, return to factory settings. This seemed to work because, Now I can boot into Cyanogenmod 10. However I am now encountering my roadblock. Apps and, the system cannot access the SD saying it is not mounted. Which I find ridiculus because, I had been able to save my Google Account, It synced my settings and, background and, gave me my wifi pass code. I am also to set alarms and, rearrange icons on my homescreen. Now I am not entirely sure but, I am almost certain to does kind of changes you need to write to the internal memory. Another odd thing is I can flash recoveries onto the device from my PC using Hasoon2000's tool. Which from what I remember while dragging files to my phone a week before this is saved to the internal storage. Unfourtionatly I think the worst that there is some corruption on the phone storage. All I know is I cannot install Apps,Can not access my storage in anyway but, use all basic services like phone calls text messages and, data. If any of you have encountered this problem and, fixed it please tell me I am stuck with a crippled phone for another year until I have the ability to purchase another.
Thank you for reading all this I wanted it to be in detail so I won't need to write it later on. Hope this issue can be solved ASP but, I am not picky as of when it can get fixed. If you skimmed it please read it all the way through.
Can you format the internal phone memory?
Sent from my IdeaTabA2109A using xda premium
stevedebi said:
Can you format the internal phone memory?
Sent from my IdeaTabA2109A using xda premium
Click to expand...
Click to collapse
I have not tryed to but it maybe possible since 4ext does show me I have a possibility to format my card. However I am afraid if I do this and, it does not work I maybe left with a pretty serious softbrick. So I need to be insured that I won't brick my device before I get to doing that. Thank you for the suggestion I will take it into account as a last ditch effort if nothing else which seems more favorable to me comes in.(or if I can build up the courage to do it which ever one comes first)
Are you s-on? I don't think you can flash ruu of you are. You need to place the ruu on you SD card and rename it to PH85IMG (for t mobile, may be different for wind). Install it from boot loader. Search the return to stock thread for more info
Sent from my Amaze 4G using xda app-developers app
jaytee20 said:
Are you s-on? I don't think you can flash ruu of you are. You need to place the ruu on you SD card and rename it to PH85IMG (for t mobile, may be different for wind). Install it from boot loader. Search the return to stock thread for more info
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
Thank you over much for posting a reply however, my current problem is that my Amaze won't read or write to the phones storage. (Or mount the internal storage) However, thanks for telling me this it will come in handy once I fix my current issue.
Megapead said:
Thank you over much for posting a reply however, my current problem is that my Amaze won't read or write to the phones storage. (Or mount the internal storage) However, thanks for telling me this it will come in handy once I fix my current issue.
Click to expand...
Click to collapse
You have to do that on the external card. Try putting the stock ruu on a micro sd and rename it PH85img and then boot into bootloader.
stevedebi said:
Can you format the internal phone memory?
Sent from my IdeaTabA2109A using xda premium
Click to expand...
Click to collapse
Thank you I finally built up the confidence to do this. It worked. I appreciate it alot.