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
Here are the facts:
1. My defy+ with red lens had this rom :Android 2.3.5 "Gingerbread" DEFY+ 4.5.1-134-DFP-125 - CEE LINK
2. took the stupid decision to flash this A.2.3.6-MIUI-XIUIv4.04-13.06-DEFY+/red-fixed'sbf from this thread http://forum.xda-developers.com/showthread.php?t=1691901
3. the phone did not boot, remained at the black screen with the white writings on it so i decided to flash the image that i had (read point 1)
4. flash went relatively ok but now my phone is stuck at the animated motorola boot logo
5. if i take the battery out and power it on with the volume down i encounter a triangle with a "!" in the middle next to an green android - the 3e menu is missing - can't do a thing
if i power the phone with volume up the bootloader says "Bootloader 09.10, Battery OK, OK to program, Connect USB, Data Cable"
6. tried the following with no luck:
- let it run the animated boot loop for 10-12 minutes - hoping that will come out of it
- flashed it several times
- tried this http://forum.xda-developers.com/showthread.php?t=1618718 and it's exactly how it;s acting mine and i quote: "If that doesn't happen,it will ask you to reboot manaully and your phone will be stuck in MOTO logo.
- Now remove your USB cable and remove battery. Hold power button and vol + button, you will get that screen.
- Now connect usb, now it result should say pass.
- Press the power button and start the phone. First boot will take some time (Min of 10 minutes or more). "
I am tired, upset and kinda desperate... i thought it will never brick and... surprise
yo did not break your phone... that's almost impossible...
did you tried to flash a defy+ sbf from here http://sbf.droid-developers.org/umts_jordanplus/list.php using rsd lite???
try that first and later came back with results
dude, this is the wrong area but as you are desperate.... did you try to find some post
that could help you with your problem?
i'm sure that somebody already have the same problem as you do... so,
try searching for it in the general section
i can't help you with that, i have a green lens defy
best of luck
#edit
try doing what the guy above said
Questions go in the Q&A section
Did you do a full wipe from STOCK recovery prior to flashing your sbf? You MUST do a full wipe before you flash any sbf or you could bootloop. Reading your post it sounds like you can get to stock recovery (volume down +power) once you reach the triangle screen you describe press vol up, and vol down at the same time to get your menu and do a full wipe
Ok, brought it back to life!
First of all i want to thank all of you who wrote me in thread and private.
Second, yeah, i was pretty desperate mostly because i tried so many solutions, read so much and the thought that i was gonna empty the battery without finding a solution was really stressfull.
What did i miss? At step 6 what i should have done is press the volume up AND down at the same time to make the 3e Menu show up then wipe cache and everything and tadaaa... phone started.
Unfortunately it took me almost all night to figure out, read countless threads, googled like crazy till i found someone who posted the right and complete solution
Once again, many, many thanks guys
PS.
# espaciosalter20
i did several times with several images
# zyxwvut
i wanted to do a full wipe but the menu was not there, i thought that powering the phone with volume down pressed was enough to make the menu show up and do the wipe but unfortunately this was not the case... you had to press the volume up and down at the same time to make the 3e menu show up... stupid if u ask me... also not many ppl pointed this out in many tutorials/hints/threads so i had a hard time finding this piece of vital information.
edit said:
Ok, brought it back to life!
First of all i want to thank all of you who wrote me in thread and private.
Second, yeah, i was pretty desperate mostly because i tried so many solutions, read so much and the thought that i was gonna empty the battery without finding a solution was really stressfull.
What did i miss? At step 6 what i should have done is press the volume up AND down at the same time to make the 3e Menu show up then wipe cache and everything and tadaaa... phone started.
Unfortunately it took me almost all night to figure out, read countless threads, googled like crazy till i found someone who posted the right and complete solution
Once again, many, many thanks guys
PS.
# espaciosalter20
i did several times with several images
# zyxwvut
i wanted to do a full wipe but the menu was not there, i thought that powering the phone with volume down pressed was enough to make the menu show up and do the wipe but unfortunately this was not the case... you had to press the volume up and down at the same time to make the 3e menu show up... stupid if u ask me... also not many ppl pointed this out in many tutorials/hints/threads so i had a hard time finding this piece of vital information.
Click to expand...
Click to collapse
Next time, please, make a full wipe ALWAYS before flashing... Yo can do that even in custom recovery (not need to do in stock all times, just when things go really mess up )
Hi my nexus 4 is stuck on the google logo screen ,i noticed the nexus logo appear when i wasnt using the phone ,then the google logo appeared and i thought it was rebooting however it then wouldnt do anything else, i can get to the recovery screen but recovery mode and start just instantly bring up the google logo again
i did once see the android screen with the red triangle and no command written though i have no idea how i came to that screen as i was just playing with it
i have not installed or attempted to flash anything on this phone ,its exactly as i recieved it
when ive left it on the google logo for any length of time it does appear to heat up a bit
forgive me for being a complete noob to this sort of thing but some of the other threads ive read may as well of been written in elvish
any help gratefully recieved
nazarineo said:
Hi my nexus 4 is stuck on the google logo screen ,i noticed the nexus logo appear when i wasnt using the phone ,then the google logo appeared and i thought it was rebooting however it then wouldnt do anything else, i can get to the recovery screen but recovery mode and start just instantly bring up the google logo again
i did once see the android screen with the red triangle and no command written though i have no idea how i came to that screen as i was just playing with it
i have not installed or attempted to flash anything on this phone ,its exactly as i recieved it
when ive left it on the google logo for any length of time it does appear to heat up a bit
forgive me for being a complete noob to this sort of thing but some of the other threads ive read may as well of been written in elvish
any help gratefully recieved
Click to expand...
Click to collapse
Same thing here. I flashed a new CM. Did a full wipe including cache then flashed a new GAPPS, and now I'm stuck at the Google screen. I can get into fast boot, recovery etc but cannot get my phone to boot. Any ideas?
1. wipe factory
2. wipe dalvik
3. wipe cache
4. flash cm then gapps then kernel
Thanks zephiK. Problem is I don't have a ROM on my sdcard mount. How can I copy a ROM to my phone without getting into android? Thanks for any help!
If you can get into recovery (CWM) then you can use ADB to push the file. Look through some of the PINNED threads for the commands. Very helpful info.
I found that my data partition was not able to MOUNT once and nothing I could do via ADB shell would change to it to R/W so I just locked and unlocked my bootloader and all was well again.
you can either use fastboot to push the files to your phone or flash stock. if you dont know how to use fastboot try wugs toolkit
Hi,
My Nexus 4 is stuck in the Bootloop (where the Colored Dots fly around that should form the Logo) and I don´t know hat to do anymore. I´ve read dozens of threads but not a single Solution could be found...
I tried several Factory Resets and Cash Wipes with the Recovery Mode and Flashing Stock Android on it. I also just let it try to boot up over night, but after 8hours it was still stuck in the same Bootloop.
I´ve never Rooted my Nexus or something like that it was Stock Android all the time (haven´t used it since like half a year, when the Bootloop appeared first, but now i broke the Screen of my Galaxy Alpha which is too expensive for me to let it fix...).
One Thing thats different from many other People that get stuck in Bootloop is the fact, that after Holding the power button to power it down, i can enter the bootloader (where i can find recovery mode) if i only push the volume down button, not the power button. I also have to go into bootloader and select "power down", if i don´t want it to try and boot up again without me doing anything.
I apologize for my bad English (if it is, i´m not sure) and i´m thankful for every hint on what i could do, since Walking aroung without a Smartphone feels weird as f*ck
Greetz,
Slix
Slix37 said:
Hi,
My Nexus 4 is stuck in the Bootloop (where the Colored Dots fly around that should form the Logo) and I don´t know hat to do anymore. I´ve read dozens of threads but not a single Solution could be found...
I tried several Factory Resets and Cash Wipes with the Recovery Mode and Flashing Stock Android on it. I also just let it try to boot up over night, but after 8hours it was still stuck in the same Bootloop.
I´ve never Rooted my Nexus or something like that it was Stock Android all the time (haven´t used it since like half a year, when the Bootloop appeared first, but now i broke the Screen of my Galaxy Alpha which is too expensive for me to let it fix...).
One Thing thats different from many other People that get stuck in Bootloop is the fact, that after Holding the power button to power it down, i can enter the bootloader (where i can find recovery mode) if i only push the volume down button, not the power button. I also have to go into bootloader and select "power down", if i don´t want it to try and boot up again without me doing anything.
I apologize for my bad English (if it is, i´m not sure) and i´m thankful for every hint on what i could do, since Walking aroung without a Smartphone feels weird as f*ck
Greetz,
Slix
Click to expand...
Click to collapse
Is your bootloader unlocked? When you said you flashed stock do you mean you flashed a zip in recovery, or flashed it via fastboot?
I unlocked my bootloader and used the wugfresh toolkit to flash stock 5.1.1. in my nexus.
After hours of online search i finally found out how to "solve" my Problem. Apparently my power button was stuck (wrote sth. like that in my 1st post but wasn't sure yet), so i just slammed it on the desk with the side where the powerbutton is located and it worked!!
I think thats something you should tell everyone who is stuck in a bootloop an not even reflashing stock Android helps
Now i got the Problem that i can't fit my nano sim in the micro sim slot of the nrxus , wouls be nice if someone got an advice in this, but maybe i should just go and get an Adapter tomorrow
Greetings, Slix
If you do not have any data on it, you can reflash the whole device by downloading the nexus 4 factory image here https://dl.google.com/dl/android/aosp/occam-lmy47v-factory-b0c4eb3d.tgz
You will need adb and fastboot which you can get here http://forum.xda-developers.com/showthread.php?t=2588979 (if the latest version does not work use version 1.3)
Then simply unzip the factory image with 7zip and run
Code:
flash-all.bat
as admin
Hello Fellows,
First I'd like to explain my situation in details.
my phone fell while i was walking on the street and it got some dirt on it, so ( foolishly ) I decided to clean it.... and yeah... i washed my phone like washing a dish... i like rinsed the phone in water and in other cleaning liquids for no more than 3 seconds it was all quick thingy... anyway after washing it.... i directly powered it ON and it powered but the screen was OFF ( so i decided to power it OFF, solder it and to remove any clues of water inside on the board or something... after that i used a hairdryer ( which is not recommended ) but i used it at a descent distance so that no harm would be caused to the board... as i was only subjecting air to let water if any existed to dry..
i put the phone in rise and kept it for 1 day... after 1 day i wanted to check out how stuff went.. so i powered it ON and the screen actually turned ON and the vibrator, even the hardware back-light lighted up perfectly but here's the problem I'm facing.
the phone only boots into TWRP 3.1.0.0 no matter what i do.. things i tried:
1- flashed some ROM, through TWRP
2- used "Fixed Contexts" in TWRP
3- Repair File System "System partition" through TWRP
4- used file manager inside TWRP and checked if the internal storage is working and indeed i can show all my files, through TWRP
5- also used the file manager to access "System" Partition and everything was there, through TWRP
6- change File System into EXT4 "System partition" through TWRP
7- Resize File System "System partition" through TWRP
8- Wiping all Partitions "Excluding the internal storage"
and NON WORKED..
note that whenever i attempt to flash a ROM the result shows successful with no errors ..
so whats the problem in here?
i have a guess but i need help in order to apply it.. i think the VOL- is pressed and stuck somehow Electrically on the board ( but no physically as i can press the volume down and hear its tap or whatever you call it.. i even managed to boot into fast-boot and it worked.
is there anyway i can disable the vol- button temporary to see if its causing the problem?
the only thing is i cant see my ROM booting... not even the boot animation showing... just the boot-loader and automatically it goes into the recovery
also i have kernel log attached below followed by the recovery log
EDIT: i also forgot to mention that my PC recognize the phone and i have access to my internal storage.. no problems with transfer speed as well
after tons of attempts and searching online and flashing stuff and blablabla... (i flashed every recovery image op2 support )
FINALLY
I found the solution my self, and everything is back to normal...
the phone was stuck at the early stage of the booting process and maybe couldn't find the boot image in order to boot up the android OS, so all i did was i plugged in the phone into the PC, i started everything in fastboot mode on phone and on PC then i just sent the following command to my phone.
Code:
fastboot continue
fastboot then(meaning after the command) wasnt able to recognize the phone anymore so i knew that its now trying to search for partitions other than recovery.. i waited like 10 seconds and booom it booted into the best ROM i've ever used ( and actually missed ) which is Official RR from our great maintainer "nicesoni_ash"
P.S: the vol- as i said was really stuck and i noticed it not working while on RR ROM, so i just clicked it many times and tried mixing vol+ with vol- .. after many many attempts vol- worked and i then rebooted to make sure if everything is back to normal and no recovery auto boots and indeed it smoothly booted up :laugh:
thanks a lot for all who tried to help out in here or on oneplus forums :highfive:
#back_to_resurrect_and_will_always_remix
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I would consider it as bricked, after all attempts failed and go with the unbrick guide here on xda or oneplus forums, maybe this way it can be ressurected.
You probably have already backed up your data..
Damn, that hurts..
mithu.creative said:
Did you try reverting to stock ?
Try getting files from here..
https://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Click to expand...
Click to collapse
sorry for this late reply but yes i have tried flashing every ROM from stock to Custom ones even i flashed EVERY SINGLE RECOVERY IMAGE OUR PHONE SUPPORTS XD and non worked... first aid.. qualcomm toolkit... non...
hello bro, i updated a magisk module v4android and when i reboot, it boots up in twrp. and since then it keeps booting into twrp. So, i used fastboot continue and when it boot int the home i deleted that module.
but fastboot continue only works once. After that if i switch-off and switch-on the phone, it goes into twrp. it needs fastboot continue everytime.
please provide me a permanent solution. few other users are facing this too. plz reply i'm waiting.
Hey,
with the help of some others in a Discord server (thanks @thesanjayp#6251 on discord) i managed to find the issue. Appearantly there was a change in /dev/block/bootdevice/by-name/misc for some reason. There was a similar problem on the old LG Optimus G Pro which i owned, so i remembered this.
As I'm not sure if we can just wipe the partition or not, i got a working misc.img attached.
In any terminal (adb shell, twrp terminal or an terminal app in a rom) make sure you have su rights, and then execute the following command:
Code:
dd if=/path/to/misc.img of=/dev/block/bootdevice/by-name/misc
Make sure to adapt the path to the misc.img though to the location you saved it to.
The misc.img I used is attached to this post.
PS: Im not responsible for any broken phones if this didnt work for you.