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
Related
Warning: whether you preform these steps correctly or incorrectly, you may be left with a device which cannot be recovered to a previous state. Because this process operates on the recovery partition it leaves you with little room to recover if flashed incorrectly, especially if your normal Android mode doesn't boot.
(although realistically you can just flash ESPRIMG.zip from HBOOT to recover, or fastboot)
So here it is ladies and gentlemen: Clockwork 3.0.0.5, based on a git version pulled/compiled on January 6th, 2011 from the CyanogenMod 7.x (CM7) repository. So what's new? Nothing that I can tell! Not sure why it deserves version 3.x, but I guess changing the text color and background is considered a 'major upgrade'.
This is provided in .img format - NOT an update.zip format. That means you'll have to flash it to your recovery partition using flash_image. Obviously that means you first need root AND S-OFF. No, I won't tell you how to root your phone or what S-OFF is.
Instructions:
Code:
$ su
# flash_image recovery recovery-cw3-test1.img
'flash_image' isn't included intentionally - if you're smart enough to know how to flash this properly and understand the risks, then you might be smart enough to know where to get 'flash_image'.
How'd I do it? Top Secret - I'd have to kill you if I told you.
Download link: [REMOVED - use one from CM7]http://dl.dropbox.com/u/14943973/recovery-cw3-test1.img
Need to revert back to 2.5.0.1? Flash this: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Enjoy it? Thank me!
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
SKAm69 said:
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
Click to expand...
Click to collapse
Not from me, sorry. I don't see any point in supporting the legacy method, especially when this version of CW doesn't give any readily-apparent advantages to the older one.
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
JAWheat411 said:
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
Click to expand...
Click to collapse
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash at this point
MusicMan374 said:
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
But the only new features you see would be the new color?
Ace42 said:
But the only new features you see would be the new color?
Click to expand...
Click to collapse
Pretty much yeah. It was orange instead of green. Some of the menus had different names, easier to understand for noobs, but they had the same content. But don't flash it until it's more functional.
Sent from my T-Mobile myTouch 3G Slide
Ok well can someone post an older Clockwork recovery.img so we can reflash it? We can't use this one to do anything.
MusicMan374 said:
It IS a test build.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
I was at work when I uploaded the image and because of that I only briefly tested it. The errors at the beginning aren't critical, but I'll look into the overall functionality being broken, at some point tonight.
Hence this being a "TEST".
Thanks
I appreciate that. I like beta testing new things. It does seem to have a few more functions. I just couldn't revert back.....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Flash this to go back to 2.5.0.1: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Actually.. i see a new option to partition SD card straight from the recovery menu... this is a very useful feature... and i think thats why it deserves that build jump from 2.5 to 3.0..... but at this point... it is in an UNUSABLE state.. i understand it is a test build... but i cannot test anything because it crashes on every single option you can possibly choose... will go back to 2.5 and wait for a stable, or at least more functional test build... hope to see some improvements soon... I do not doubt that you guys can have this thing up and running in no timee.. its a good starting point.. Keep the work going... looking forward to it...
was anyone else hoping for a terminal like in good ol' amon_ra? I was...
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
elry567 said:
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Thnx
Sent from my T-Mobile myTouch 3G Slide using XDA App
mymomma8 said:
it crashes on every single option you can possibly choose
Click to expand...
Click to collapse
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
I don't think that file was cw3 I flashed it and still have 2.5 (file by musicman)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
MusicMan374 said:
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Click to expand...
Click to collapse
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
guitarist5122 said:
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
mymomma8 said:
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
Click to expand...
Click to collapse
Alright thanks it works now!
My phone upon reboot usually gets stuck on a "Sorry! Process system is not responding" "Force Close" or "Wait".
Neither option works and I have to do a battery pull.
It doesn't matter what ROM I use it always happens.
Would someone be able to tell me how to get a log from bootup? And would someone be willing to look at the log for me?
Thanks guys!
Sent from my PG86100 using XDA Premium App
tes5884 said:
My phone upon reboot usually gets stuck on a "Sorry! Process system is not responding" "Force Close" or "Wait".
Neither option works and I have to do a battery pull.
It doesn't matter what ROM I use it always happens.
Would someone be able to tell me how to get a log from bootup? And would someone be willing to look at the log for me?
Thanks guys!
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I don't mean to sound like a tool by suggesting this, but, have you wiped? Wipe cache and dalvik to start off with see if that works...and if it doesn't do a full wipe and get back to us.
Again, I'm not trying to be a ****...if you are beyond this level of help, well, we're gunna need more details.
i can tell you how to get a log but i cant tell you whats wrong using the log
plug your phone into your computer, using adb type in "adb logcat" and press enter and you should see a whole bunch of text start appearing
before you flash a rom do you do factory resets and make sure to wipe your cache and dalvik cache? that could be the problem..
I have done it all, wiped dalvik, cache, and everything else. I even tried using CWM instead of twrp and the issue remains.
Thanks everyone for trying to help...
Sent from my PG86100 using XDA Premium App
tes5884 said:
I have done it all, wiped dalvik, cache, and everything else. I even tried using CWM instead of twrp and the issue remains.
Thanks everyone for trying to help...
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
If you've done a full wipe and tried different roms then I would be inclined to believe that the issue is likely hardware.
tes5884 said:
I have done it all, wiped dalvik, cache, and everything else. I even tried using CWM instead of twrp and the issue remains.
Thanks everyone for trying to help...
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I would use TWRP and do this:
Go into wipe menu, then Wipe cache, wipe dalvik, wipe data (factory reset). Go into advanced menu (I think) and there should be another wipe menu. Wipe /system. Then flash the ROM of your choice and it should be fixed. Wiping /system manually is the key since some ROMs don't do that (mine does, however)
Thanks ill try the advanced system wipe.
Sent from my PG86100 using XDA Premium App
Negative I tried formatting system and all the rest. It didn't work. The strange thing is when I remove my sdcard it boots fine, I tried a second sdcard and the same issue.
Thanks again guys.
Sent from my PG86100 using XDA Premium App
Another strange thing is, when I reboot via "adb reboot" it works fine...
tes5884 said:
Negative I tried formatting system and all the rest. It didn't work. The strange thing is when I remove my sdcard it boots fine, I tried a second sdcard and the same issue.
Thanks again guys.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
stock card?
daneurysm said:
stock card?
Click to expand...
Click to collapse
none of these are stock card, I cant seem to find my stock card.
As a matter of fact I dont think I ever even booted with my stock card. Do you think that can be the issue?
Thanks
tes5884 said:
none of these are stock card, I cant seem to find my stock card.
As a matter of fact I dont think I ever even booted with my stock card. Do you think that can be the issue?
Thanks
Click to expand...
Click to collapse
In a word, yes. Are any of these 'bargain' cards you got online by chance? If not and they are from a reputable vendor I would put them in the computer, copy data off and format them....and if that still doesn't help find a 'known good' card and go on from there. The stock card would be preferable, but, if you can't find that a 'known good' card is the next best thing. If the stock card or a 'known' good card doesn't help I'm still inclined to think it's a hardware error...but after hearing about the SDcard I'm leaning towards the phone is fine the card is screwed.
daneurysm said:
In a word, yes. Are any of these 'bargain' cards you got online by chance? If not and they are from a reputable vendor I would put them in the computer, copy data off and format them....and if that still doesn't help find a 'known good' card and go on from there. The stock card would be preferable, but, if you can't find that a 'known good' card is the next best thing. If the stock card or a 'known' good card doesn't help I'm still inclined to think it's a hardware error...but after hearing about the SDcard I'm leaning towards the phone is fine the card is screwed.
Click to expand...
Click to collapse
ok I appreciate the help and I will look for a new card.
Went to a sprint store, they said its probably a hardware issue and they ordered me a new one.
Here's to hoping the new one one won't have any issues....
I appreciate all the help from you guys.
Sent from my PG86100 using XDA Premium App
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..
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.
Hi All,
im trying to revive my old atrix (now have a HTC OneX as my main phone). The problem with my atrix is that every app on it is randomly popping up with a Force Close Or Wait message, this is completely random and if i click wait the app i was waiting to load normally appears.
my first theory was that there was a problem with the install so I did a hard rest, the problem continued,
second thaught was that the rom it self was damaged some how, So i followed a guide and installed Cyanogen Mod 7 with clockwork recovery, this all went well, but after booting into Cyanogen im still getting the force close issues (although it happens a lot less)
here is a list of the problems:-
1. Force close or wait messages randomly for any app it feels like including system process's
2. the camera no longer works, im assuming this is a hardware issue.
3. when updating apps the download speed is super slow sometimes it will just stop for an hour or 2 (even when on my home Fibre connection)
so what do we think? im open to suggestion and pulling this thing apart as it is basically a spare phone,
what should i do?
Cheers
Dazzler
I would try a factory reset first, if that doesn't work, the install a custom rom o reinstall the one you have
Sorry i should have put a TLDR:
TLDR - I have hard reset and installed a new ROM the problem is still there.
Cheers
Dazzler
is there anyway to test the hardware on an android phone?
I have my suspicions that the problem could be a fault with the internal storage or RAM... but it would be nice to have a way to test it.
the weird thing is that although apps take ages to load and come up with the not responding (force close or wait screen) if I press wait 9 times out of ten the app will appear right after that message and work fine....
any one have any ideas?
Cheers
Daz
Well now i have a situation, my lovely HTC OneX has died....
so im back to using my old Atrix 4g full time, this force close issue is driving me nuts, from what i can tell every application is slow and likes to attempt a force close 2 or 3 times before it becomes usable.
I have tried a full reset, clearing caches and re flashing, still got the same problem.
does anyone know of a tool to test the internal memory of a phone? is there anyway to do a full format as such? a complete clear and start again??
any help appreciated
Thanks
Dazzler
dazzler22 said:
Well now i have a situation, my lovely HTC OneX has died....
so im back to using my old Atrix 4g full time, this force close issue is driving me nuts, from what i can tell every application is slow and likes to attempt a force close 2 or 3 times before it becomes usable.
I have tried a full reset, clearing caches and re flashing, still got the same problem.
does anyone know of a tool to test the internal memory of a phone? is there anyway to do a full format as such? a complete clear and start again??
any help appreciated
Thanks
Dazzler
Click to expand...
Click to collapse
you can flash an .141 full sbf and start over (unlock bootloader, flash recovery, flash custom rom) to see if that's the problem.
Another way is to format everything via cwm recovery (mounts and storage -> format /data /cache /webtop /preinstall /system) and try a custom rom freshly downloaded and with md5 checksum, to avoid download corrupted issue.
andresrivas said:
you can flash an .141 full sbf and start over (unlock bootloader, flash recovery, flash custom rom) to see if that's the problem.
Another way is to format everything via cwm recovery (mounts and storage -> format /data /cache /webtop /preinstall /system) and try a custom rom freshly downloaded and with md5 checksum, to avoid download corrupted issue.
Click to expand...
Click to collapse
Thanks for the reply,
I dont have webtop listed in the mounts and storage, Im just downloading a new rom, once i have got that on the sd card, i boot into clockwork format the above and then install rom from sd card.
will give it a go!
also what is format /emmc? is that the internal storage? im assuming this is a big no no?
Cheers
Daz
dazzler22 said:
Thanks for the reply,
I dont have webtop listed in the mounts and storage, Im just downloading a new rom, once i have got that on the sd card, i boot into clockwork format the above and then install rom from sd card.
will give it a go!
also what is format /emmc? is that the internal storage? im assuming this is a big no no?
Cheers
Daz
Click to expand...
Click to collapse
I don't recall (and also don't have my phone at hand) if it's called /webtop, /osh or /vendor.. Any of those will go.
yup, /emmc is what the roms see as the internal storage, don't do it unless you want to start fresh
great thanks, will give that a go!
ok so i did a clean slate install with a full format of everything and a new rom (CM9 unofficial one)
it is working better but im still getting force closes, I think my guess of something inside failing is prob about right, hopefully HTC will fix my OneX quickly....
Cheers
Darren
Glad to know that it is working, but sad to know it's getting to it's end