Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
I have searched here and Google but can't seem to find the exact problem that I am having. Most similar issues are with different phones and I haven't found any solutions for the HTC Hero. I have been rooted for a couple of months and using CM6 (stable and nightlys) without any problems whatsoever. I have (had?) Clockwork recovery. My phone was running perfectly this morning and the battery was pretty low (down to 10%) so I pulled it and put in a fully charged battery. Now my phone won't boot past the HTC white screen. I can boot into HBoot ONLY (three skateboarding androids) and the screen shows:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
I have tried all the options on HBOOT and can get into FASTBOOT but am unable to reset device, go into recovery, etc. It just goes back to the white HTC Screen after choosing one of these options and never boots up. I've tried with the SD card in and with it out. I even tried to RUU with the .5 Sprint official release but when I run it, the program said my phone was not found and told me to make sure it was plugged into the computer which of course it was. I also tried to run the RUU in FASTBOOT USB mode but still receive the same error.
When I run adb shell on my PC it says the device was not found. When I'm stuck on the white HTC screen if the phone is plugged in to the computer and I unplug the usb from the phone it vibrates 5 times quickly and the screen goes off, but the green notification light is blinking. From this state I am unable to power up the phone at all without a battery pull.
I just don't understand how my phone can go from being PERFECT to FUBAR when the only thing I did was replace the battery. I'm hoping someone can help me. I am eligible for an upgrade but really don't want to spend the $$ right now for an EVO or Epic when my area will never see 4g and the extra $10 is ridiculous.
My setup prior to this morning when I pulled the battery:
Clockworkmod Recovery
CM 6 nightly (Full-73)
BFS #11 kernel
FireRat custom data partitions
And I was rooted with Universal Androot
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
chromiumleaf said:
Have you tried booting into recovery by holding Home and pressing Power? From there you could try wiping everything then reflashing the ROM of your choice.
Have you tried putting the original battery back in and just recharging it fully, then trying to boot?
Click to expand...
Click to collapse
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
debh945 said:
When I hold home and press power, I just get the white HTC screen of death. When I hold volume down and press power, I get the HBOOT screen and when I try to boot into recovery from that screen it again gives me the HTC screen of death. There is no way past the HTC Screen other than HBOOT and Fastboot. I also charged the phone with the original battery as you suggested and it still did not boot up beyond the HTC screen.
This afternoon I was in the FastBoot screen and plugged my phone into the USB that was connected to my computer. It changed to FastBootUSB and I was able to run the RUU. The program said that the ROM was successfully updated but I sat there for an hour with another white HTC screen before I unplugged the USB and then the phone shut off and I got the 5 quick vibrates. I really think it's toast. RIP, it was such a good phone!
Click to expand...
Click to collapse
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
rulyskull said:
Well you'll be the first to kill it this way but I'm sorry to here that and my touch screen is almost toast so ima start a first to
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
debh945 said:
Dang, that sucks. I was torn between getting an upgrade or buying a used Hero on Ebay until I find a phone I want. Turns out my phone was only 11 months and 10 days old so I'm still under warranty. My new Hero will be here Tuesday. I'm hoping it doesn't come with the .7 update but if so, I'm hoping I can RUU back to the .5 and re-root. Anyone know if this is possible? Thanks.
Click to expand...
Click to collapse
Try the one click root(forget What section in here) but ima wait to get the epic or something better
Sent from my HERO200 using XDA App
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Vandelay007 said:
Have you tried ruu'ing it?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yep, I was finally able to RUU while the phone was in FASTBOOTUSB mode and the program on the PC said the ROM was updated successfully but it still never got past the HTC white screen. When I boot into HBoot by holding the volume down/power button the screen flashes a bunch of things so fast I can't read them but it seems like it says something about HCERMG Image Not Found.
The Sprint tech(?) hooked it up and tried to diagnose, install the software but couldn't either. Anyway, since it is under warranty I get a new Hero on Tuesday. I am just baffled at how this happened when all I did was change the battery. You don't realize how much you love something until it's gone. I'm currently using my old Instinct and I find myself constantly turning the screen sideways and wondering why the display won't turn.
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
SportsPT said:
Same issue here, (2nd time actually). Last time I was able to put the HERCIMG.zip on the root of my SD Card and then load it with HBOOT, and then I was back to stock and all was good. However since then my HBOOT was updated to 1.47 and now the HERCIMG.zip doesn't work, it says "Main Version is older!" Update Fail!
I haven't figured anything else out yet. Is there an updated HERCIMG.zip for 1.47?
Click to expand...
Click to collapse
Do you mind telling me what you did (twice lol) that put your phone in this unusable state? Like I said I'm not sure how this happened and don't want to repeat it with a replacement phone!
Ok, I put the HERCIMG.zip on the root of my SD Card (found it through Google and had updated 1.47 HBOOT). I booted up holding the volume down and power and the blue progress bar filled up on the right side and when it was finished it went back to the HBOOT screen. I rebooted the system and still have the white screen of death. I'm convinced there's really nothing else I can do to get it running again and must painfully wait until my new phone comes in on Tuesday.
Couldn't tell you how it happened, may have to do with the battery completely dying, but not sure. I tried what you did but got the same results. I think what we need as an updated HERCIMG.zip that works with HBOOT 1.47
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
unCoRrUpTeD said:
While in fastboot, did you try
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
Click to expand...
Click to collapse
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
debh945 said:
I tried all kinds of fastboot commands in FASTBOOTUSB mode through adb but always received the error "remote not allowed" or something to that effect.
Click to expand...
Click to collapse
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
unCoRrUpTeD said:
What about when you power on the phone normally. You should be able to get into adb shell when it is booting up.
I am going to try fastboot flash boot.img right now on mine and see if I can't get something.
Edit:Haven't tried. Working on a multiboot and now I only have one more obstacle.
Click to expand...
Click to collapse
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
debh945 said:
If I was not in the FastbootUSB mode, there was only the white HTC screen and adb showed "no devices". I appreciate your help but I can't troubleshoot any longer as I had to turn my phone in to get the new one via warranty replacement. Your efforts might help someone else though with the same problem.
ps, I've been following the multiboot thread very closely and can't wait until this becomes a reality!! That will be so awesome!
Click to expand...
Click to collapse
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
obsanity said:
Did you pay the extra for warranty or are all heros on warranty for 12 months? Who did you sent the phone to or did you just go to the sprint store?
Click to expand...
Click to collapse
All Heros have a 12 month warranty, I didn't pay extra. I first called Sprint Customer service and since it wouldn't boot for them to troubleshoot on the phone she gave me an Eticket number and the location of the nearest Sprint store with a repair center. I took it in and the tech (?) hooked it up to his computer and could not fix it either so he said he would order me another and it would be here on Tuesday. This was Saturday evening. I received a call today (Monday) from the Sprint Store that my replacement phone was in. Picked it up and rooted it in 5 minutes with Universal Androot, installed Clockwork Mod Recovery, Nandroid restored a backup from the old phone's SD card and I was back in business in 1/2 an hour! Probably TMI, I realize you only asked how I got a new phone but I'm thrilled to have my Froyo back!
Awesome! Makes me feel better trying different ROMs
Funny thing I found this thread, this exact same thing happened to me today.. Hero is completely done.. Getting a replacement tomorrow... I was running firerats also which I can't blame but I'm not running firerats on my new device... Since I installed firerats I've lost 2 8gb sd cards and a phone...
Weird thing is, I had applied the unrevoked-forever and eng spl mod/hack, now when I boot into bootloader it says s-on like what the hell happened? How did I lose s-off and root all together after restarting my phone.
Hi.
I rooted my LG Optimus 2X with Super on click root. It worked great after right after. I uinstalled CarHome and F-Secure, and after that my phone restared.
Now, It would not start. I only boot until the LG logo, and after that it reboot. So it go on and on and on. I can get the phone into ADB, and I'm a newbie on android, so I got no clue what to do. I aslo tried to use the recover program by LG, but I get a message that tells me that my phone does not support the update.
Is there anything that can sovle my problem or do I need to take it to the place I bought my phone?
I had the exact same problem (a hole thread in here). Your phone is bricked (as of now there's no solution as far as I know). When you rooted your phone you lost the warranty, so if unlucky you cannot return it without having to pay to get it fixed... If lucky the might just switch the phone with a new one...
I've sent mine back to the seller and hopefully I'll get a new one...
This thread could be useful for you:
http://android.modaco.com/content/lg-optimus-2x-2x-modaco-com/334664/bricked-lg-optimus-2x/
There's actually new development in the right direction. Paul from modaco (2x.modaco.com) are preparing af NVflash of the 2x, which will completely reflash the memory with the standard rom from stock meaning we should be able to fix the easily...
Should be ready on wednesday...
I've been looking into these two treads, but could not found anything that my fix the problem.
Well, I've got to go to my the seller and hopefully they will fix it fast.
Try to remove the SD card and then try to switch on once more...
I've been trying with and without SD card , Sim card, Battery many times. So I thats not the problem I think
thats why you should freeze apps instead of uninstalling them.
Did you try to hard reset the phone?
If you got an adb connection and root, try to obtain the apk's (search the forum) and push them to system/apps.
Thats all I can think of for now. I'm no expert on this
Did you make a system backup using Clockwork Recovery before you rooted? If so, boot back into recovery and restore the backup. I bricked my phone the first time I installed a different ROM but luckily I had a backup that I was able to restore and try again.
Sent from my HTC Incredible using Tapatalk
xphire said:
Did you make a system backup using Clockwork Recovery before you rooted? If so, boot back into recovery and restore the backup. I bricked my phone the first time I installed a different ROM but luckily I had a backup that I was able to restore and try again.
Sent from my HTC Incredible using Tapatalk
Click to expand...
Click to collapse
The Optimus 2X does not (yet) have Clockworkmod Recovery working. At least not in a way available to the public (MoDaCo's Paul said he would release some stuff next week)
I can't get it to hard reset. When I boot up the phone I hold in the power button and the - volum butten. Then I come to a screen with the droid, I press the home button and I get Android recovery system (3e), but I'm unable to choose anything. I only can switch between the 4 chooses, by pressing +/- volum button.
Nope, can't get it to connect to adb. Tried, but I couldn't manage it.
Well then maybe someone here can point you to actually selecting something from that list. I mean, it has to be possible to "choose" one of the 4 options but I've never owned an android until (hopefully) in 3 weeks so I can't tell you how it works exactly.
Edit: Just checked the manual again, did you make sure you pressed home and vol- for 10 seconds ?
Well, yes. I pressed home and - volum until I got a recover mode or something.
But as I know theres know way to fix this problem atm. I'll have to send it back to my reseller or wait for Paul to release the fix.
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
A friend of mine tried to root his white tmobile g1 and im not sure what he did to it. heres what im working with.
press power button goes to g1 screen and then to the factory android recovery (e2)
can wipe, factory reset and can select install update.zip
the phone wont take any update i throw at it and ive tried like 7-8 i have found here on xda. I have no idea what phone was on previously.
I CANNOT access the bootloader no matter what i do. i even went as far as to dissasemble the phone and replace the buttons (thought home might be sticking), anyone have any ideas on how i can possibly ressurect this?
without bootloader access i cant flash to downgrade. Im at a loss here and really hate getting outsmarted by a phone. I dont think its a brick... yet being i can hit stock recovery and that blue led test works.
If bootloader is truly gone, not just hidden from you, the phone can not boot. I know of no flash able update.zip for a bootloader in the stock recovery which unfortunately means this is a brick. The blue light mode is only helpful for JTAG, sorry
Sent from my Nexus 7 using xda premium
I finally managed to get the phone to boot by swapping the cables out of another phone. Weird issue but nice having a half dozen phones laying around for parts
Sent from my HTC One XL