Related
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
I just partitioned my SD card and flashed a new rom (RunnyBliss HybriD) tonight. Everything was working fine, I just reinstalled all of my apps and everything was perfect. I went to unplug my phone from the computer (which was on charge only) and just unplugged it. After that, all of the apps I downloaded were gone and the home screen pages that I just setup were gone. I decided to reboot and see what happens and to my surprise it wouldnt boot back up. It is stuck at the white "htc evo 4g" screen. I tried to boot into recovery and it vibrates 3 times and then does nothing. I assume that the phone was actually in USB mode and I corrupted the usb by removing it without ejecting it. Long story short, I have an Evo that doesn't work and I dont know what to do. My computer wont recognize it so I cant access the SD card. Please help.
Correction: If I press volume down I can get into hboot. What do I do from here?
try to install a recovery via the bootloader
How would I do this?
npreisler08 said:
Correction: If I press volume down I can get into hboot. What do I do from here?
Click to expand...
Click to collapse
I'm kind of new to this but, in HBOOT there should be a recovery option, select that and recover the latest backup.
EDIT: If Recovery doesn't load then I'm at a lose, sorry.
I figured it out. I got a new micro usb and placed AmonRA on it and then booted into recovery, then went to usb mode and dropped a new rom on it and flashed. Big bam all fixed
I was going to use the EC05 to EI22 update.zip file posted here to get myself some gingerbread goodness, but I have a couple questions plus I ran into a problem.
Questions (have asked in multiple threads but because of the frenzy over gingerbread release it's like trying to talk at a heavy metal concert: I am fully stock ec05 EXCEPT for having done root so that I could do wi-fi hotspot (from advice given in this thread a little while back - http://forum.xda-developers.com/showthread.php?t=1236669). Will this interfere with doing the EI22 update or do I need to back it out? I want to say I recall someone mentioning the update would go fine and I'd just have to re-root.. but looking for specifics.
Problem: I put the update.zip onto my SDcard, reboot my phone..... and it's just sitting there staring at me, Samsung boot logo as bright as ever, for about 20 minutes now. I had been trying to do the vol-down, camera, power key set to get into service mode, but it never got past this boot screen - yanked the battery and SDcard and trying again and it's still just sitting here.
Help?
--update--
Leaving it off, plugged in the power and rather than getting a proper charging display with the battery and charge meter/status - it has a blank battery with the radial spokes that would normally be rotating just sitting there. What happened to my phone? O_O
tigerknight said:
I was going to use the EC05 to EI22 update.zip file posted here to get myself some gingerbread goodness, but I have a couple questions plus I ran into a problem.
Questions (have asked in multiple threads but because of the frenzy over gingerbread release it's like trying to talk at a heavy metal concert: I am fully stock ec05 EXCEPT for having done root so that I could do wi-fi hotspot (from advice given in this thread a little while back - http://forum.xda-developers.com/showthread.php?t=1236669). Will this interfere with doing the EI22 update or do I need to back it out? I want to say I recall someone mentioning the update would go fine and I'd just have to re-root.. but looking for specifics.
Problem: I put the update.zip onto my SDcard, reboot my phone..... and it's just sitting there staring at me, Samsung boot logo as bright as ever, for about 20 minutes now. I had been trying to do the vol-down, camera, power key set to get into service mode, but it never got past this boot screen - yanked the battery and SDcard and trying again and it's still just sitting here.
Help?
Click to expand...
Click to collapse
Pull your battery..
Boot back into stock recovery and do a full wipe/reset
Reboot.
Should be fine
Paul627g said:
Pull your battery..
Boot back into stock recovery and do a full wipe/reset
Reboot.
Should be fine
Click to expand...
Click to collapse
No joy.. all these steps started with no AC power, no SD card, and pulled battery, with at least a minute of full lack of any form of power:
insert battery, power on: sits staring at initial 'samsung' boot display
insert battery, plug in AC: gets blank battery meter as described and won't boot
no battery, plug in AC: gets blank battery meter as descrobed and won't boot
http://forum.xda-developers.com/showthread.php?t=1052813
1. Use this to get back to EC05
2. Rename update to update.zip and place in root of SD card
3. Boot into stock recovery and flash update.zip
I was having the same problem with the OTA. So I odined back to EC05 and then applied EI22 via update.zip in stock recovery. Same result, stuck at boot screen.
BLARGH. I was hoping to not have to wipe my phone. Oh well, here goes nothing. Will post results as I get them. Thanks for the assist, guys.
I have seen confirmed reports of users booting back into stock recovery and doing a full reset/wipe then rebooting with no problems.
Had to cheat to get into download mode. Page says no battery, only USB cable - soon as I plug that in though it gets stuck on the battery meter screen and won't go further.
I had to use the battery and boot into download mode that way, THEN connect the USB cable and so far it seems to be functioning as planned.. keeping my fingers crossed.
--update--
Odin completed and phone booted fine. inserted SD card - tried updating but it is refusing, complaining of low battery. Guess I'll have to let it charge for a while and try again.
Can you boot into download mode? You might have to ODIN/Heimdall EC05 and start from scratch again.
Edit: Ignore this... I don't know why your reply wasn't on the page when I replied...
I was running CWM 3.1.0.1 which gave an error when trying to apply update.zip (looks like it failed a checksum check on recovery).
Thinking it was CWM causing the issue and I needed to revert back to the stock recvoery, I took the stock recovery from this thread:
http://forum.xda-developers.com/showthread.php?t=1027904&highlight=rerfs
and renamed it recovery.zip and applied it via CWM.
After rebooting, my phone is having the same symptoms as tigerknight:
insert battery, power on: sits staring at initial 'samsung' boot display
insert battery, plug in AC: gets blank battery meter as described and won't boot
no battery, plug in AC: gets blank battery meter as descrobed and won't boot
Unfortunately, I cannot boot into recovery mode anymore either. It seems to get hung on the same "Samsung" screen as when trying to boot normally.
I'm going through the de-bricking process now. <sigh>
I let my phone charge for a little and then the update.zip ran just fine. I didn't actually lose much data thanks to stuff being on my SD card, but I need to go through and recall what apps I used regularly now.. mostly work related stuff so not a whole lot, thankfully.
Yay for EI22 and VERY snappy handling compared to before off of just completely stock image!
I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.
Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?
I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.
Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.
Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.
first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.
I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.
lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Just reflash the rom you are on without wiping. That should fix it.
Is the phone an i337? If it is, you're in the wrong s4 forum.
GDReaper said:
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
Click to expand...
Click to collapse
Okay and suppose i could get adb working how would i copy the "usr" file back to the "/system"
audit13 said:
Is the phone an i337? If it is, you're in the wrong s4 forum.
Click to expand...
Click to collapse
Yea it is the i337 my bad i didnt noticed can it be moved?
Contact a moderator and ask him or her to move your thread.
Lennyz1988 said:
Just reflash the rom you are on without wiping. That should fix it.
Click to expand...
Click to collapse
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
DaFrenchTaco said:
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
Click to expand...
Click to collapse
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Lennyz1988 said:
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Click to expand...
Click to collapse
I think AT&T and Verizon phones always had locked bootloaders, just that the earlier versions were easier to hack.
if its hard bricked, try jtag
thnx to everyone in this thread you were all of help my phone is now working even better then it did before much appreciated