Related
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here for how to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
yeah i figured i should flash stock back, but the problem is trying to push the file or something. but ill look into that link asap!
thanks for the quick response
You'd probably do best to start from the top by reflashing the stock image... http://forum.xda-developers.com/showthread.php?t=2513701
This time don't use any toolkits or canned scripts, learn how to do each step by yourself, get familiar with all the commands, and do it yourself. You're less likely to screw anything up that way.
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I had the exactly same situation before. What I did was a factory reset by using the wiping function in TWRP, Then you get a freshly-new system. Hopefully you have backed up your data.
Guys stop flashing the cache it really isn't needed and causes issues... I haven't done it since Android 4.3 and not had one problem
Sent from my Nexus 5 using Tapatalk
hello xda. i need your help. im desperate. i dont know what else to do with my moto g here's what happened:
first of all, i dropped my moto g into the water.
right after i got it out, it startet bootlooping. then it turned off by itself after almost an hour had passed.
i put it in a bag full of rice for the rest of the night and almost the whole following day. then i plugged it into the wall charger, and it wouldnt charge at all. the only sign of life was the blinking led.
so i took it to Movistar-Peru for repair, and told me the obvious: water damage was not covered in the warranty, then my phone was returned to me.
so i decided to tear it down by myself.
everything was looking fine. the water indicators were red, but everything was clean except for the battery socket: there was mineral condensation around it. i wiped it out, cleaned it away and then the phone would actually charge the battery icon displayed normally.
so i let it charge for 3 hours and after it was completely charged i turned it on. just to run into a black screen after the bootnimation.
good news is it actually can boot into fastboot mode and can access recovery menu.
i did some research here, and seemed like my phone needed a full stock flash (that´s what i thought). i decided to unlock the bootloader, using motorola unique code. (i thought it may be needed for flashing, but it seems it is not necessary)
in recovery, my sdcard folders display normally, i can wipe data/factory reset it normally, BUT when i try to erase cache partition, the phone reboots.
so i started flashing my device through fastboot. i should mention that before i dropped it into the water, i had installed 4.4.2 ota update. but whenever i tried to flash a 4.4.2 rom, i got hab check failed for sysyem, for recovery and sometimes for boot.
now, i've tried several official motorola signed jelly bean roms (nextel br, movistar sp, claro ar, etc etc) including original Movistar Pe jb rom (which ive already flashed uncountable times) with no errors on flashing, but neither of them got me passed the black screen after bootanimation. (the phone is not off, cause the backlight remains on). the only way of getting out of it is rebooting into fastboot mode again (volume- and power).
i've also tried relocking the bootloader, and the process gives me no errors (the word "locked" displays by the end, though the phone then reboots into the "warning bl unlcked" screen) , but regardless of that and the relocking process turning out okay, status code 3 is displayed in menu, meaning the bl wasnt really relocked..?)
in short:
-dropped into water, started bootloop, then it turned itself off.
-next day it would display black screen after bootnimation, no matter what i did.
-if i choose wipe cache partition, the phone reboots.
-i've flashed it "sucsessfully" several times, still runs into a black screen after bootnimation.
-i've unlocked the boootloader
-if i try to reclock: process turns out okay("locked" word by the end), but status code remains being 3.
-i dont care about backups, i had nothing important in my phone (gdrive ftw)
my concearns are:
-possible hardware unrepairable damage
-bootloader got corrupted
-mineral condensation is still there deep inside the components
-maybe gpu? emmc corrupted? semi brick? idk..
my questions are:
-what can i do from now?
-i've read that a new bootloader can be flashed into the phone. risk of bricking my phone?
-if the bootloader is the problem, flashing a new one would solve it?
-in general, what am i doing wrong in all of this? has my phone any chance of functioning normally, at all?
please help me , i miss my phone, i got it for christmas, it is my first smartphone and i woudl like to bring it back to life if possible. thank you for reading.
I can help!
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Thank you for replying to my problem
i have already done your steps uncountable times.
every time i try to wipe cache, the phone reboots. it does not wipe anything at all, it just instantly reboots. then bootanimation, then black screen again, but nothing happens. not even after 2 minutes, after 5 or 10. nothing. just black screen until battery drains completely from continously powering the backlight. do you think maybe the water hardware-bricked my phone? also, im ocassionally getting blue screens out of a sudden, then the phone powers itself off.
Ah, ok, sorry my suggestion didn't help. I had exactly the same problem, so surprised this didn't help you. After being dropped in water, all I got was a black screen after the initial start animation. I don't really know much about phones tbh, I just managed to fix mine through trial and error. My girlfriends phone was initially sent to a shop for repair, and although the guy couldn't fix it, he said there was no signs of water damage. Not really sure then why the phone stopped working, but the method I suggested did work for me. I don't think there was anything else I tried. It's worth mentioning maybe that it took 6 weeks before I could fix the phone. Maybe it took that long to fully dry out? Straight after the accident though the phone was put in a bowl of rice for days so it should have been dried pretty quick. Don't really know what else to suggest, sorry I couldn't be more help. Have faith though, I reckon it'll come back to life soon
thank you for posting a reply and thank you for your advice. i appreciatte the attention given. i will further try some other methods in hope of a solution.
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
Click to expand...
Click to collapse
are you sure it has nothing to do with the bootloader? now that you mention this.. can a 4.4.2 bl load a 4.3 rom successfully? and moreover, if i flash another bl, it will overwrite my original one right? is there eny problem on that? i am asking because no matter what i do, regardless of the "locked!" message, the menu keeps showing code status 3.
what happens if i flash the recovery and cant mount or flash any rom? or if the black screen persist after that?
and i wish i had known the rice trick before, cause i kept the bag closed for almost a day :s
grahameaddicott said:
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Click to expand...
Click to collapse
It worked for me, Thanks
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Click to expand...
Click to collapse
ok i did what you said, i tried to flash cwm and fastboot presented no problems, (output is "okay"), but un the phone screen there's a message "mismatched partition size (recovery)", and when i enter recovery, it boots normal STOCK recovery!! i donw know whats happening. i renamed the cwm image to cwm.img and typed in these commands:
fastboot erase recovery
fastboot flash recovery cwm.img
then i clicked recovery option in the bootloader menu... but it booted into stock recovery!! this is so confusing
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
thank you i will proceed to try what you said. though i have a question: is it possible for the bootloader to be overwritten with a previous version?
and what does it mean when the phone outputs "hab check failed for boot/recovery/system (etc)" ? i sometimes get those errors when flashing other region (official) roms
liveroy said:
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
Click to expand...
Click to collapse
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
tenjou_89 said:
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
Click to expand...
Click to collapse
Hmm, maybe leave the recovery aside for now and try to boot a 4.3 ROM (stock one).
Also you cannot downgrade to bootloader afaik, but the newer ones work fine with 4.3 ROMs.
I don't think that the eMMC got damaged, cos nothing will work then.I really can't say if your problems are coming from the water dip or it's just the Moto G being stubborn if you do even one thing the wrong way.
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
what about the ram? a guy on some other forum said that maybe the ram got damaged to a point where only a part of it is now writable, and it gets flooded just before the complete boot up of the system, wichi is why the phone would then crash and display a black screen. what do you think about that theory?
i am going to try with 4.3 roms now. oficial and custom and post the results.
liveroy said:
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
Click to expand...
Click to collapse
yes, exactly that way.
edit: except i have images instead of bins, so:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot bootloader
Typo of mine, should be .img
About that RAM theory, it really doesn't sound viable to me, but who knows.
If I have to guess, I would say it's probably some crucial component failing to initialize properly and the kernel halts the system.
hmmm do you know of a method of checking for the conditions of individual hardware componets through a pc? like probing or running a full check of everything, not just the emmc..?
These seem not to work.
But if you find the correct details, maybe there is something to test in the service menu.
I have the same problem without water damage. I guess its the 4.4 OTA bug.
Tried reflashing the firmware i already have but of no use.
Mine shows the Blue Motorola logo and then doesn't show the boot animation.
Please can anyone help me out :'(
*D821 (E) - hammerhead
*KTU84M
*HW version: rev_11
*bootloader version: HHZ11k
*baseband version: M8974A-2.0.50.1.13
*carrier info: NONE (is this wrong?)
*signing: production
*secure boot: enabled
*lock state: locked
#I didn't touch this phone's system, still original.
my story:
so it's been 3 weeks since I bought my phone. I was happy with it, nothing was wrong.
a week later, the 4.4.3 came out, I updated it, and nothing was wrong too.
until last night, I turned off my phone, curious to see how the Nexus 5's recovery look like,
I pressed (volume down + power), and I noticed that it enters FASTBOOT mode. and I just learned, navigate with the volume buttons and select with power button.
NOTICE: I'm already familiar with things like this, I was in the Galaxy W forum and Galaxy SIII mini forum. *yes lol I came from Samsuck
so I selected recovery mode and enter it.. I saw the android logo there, the healthy one, not the murdered robot with a red triangle on it.
I saw nothing but that logo, I pressed volume up button and the text showed up. I navigate down with volume down button, until it was down at the "wipe cache partition", I wanted to go up to reboot my phone, but I realized, the up button just a switch to hide or show the recovery text, so there's only one choice, press the power button, *if I press the power button, I wipe the cache because it selects "wipe cache partition"*.
and then it writes "wiping the cache", I was confused why it was so long, until I decided to reboot with holding the power button.
NOTICE: it is strange to wait sooooo long for cache wiping. I know this.
the system turned on. I'm not sure if the cache wiped cleanly, I'm afraid it will make the system error. so I decided to change my runtime from ART to Dalvik, so the cache wiped out and built again, strange process that took only 64 apps to optimize, that before it was around 110 apps. and then after reboot, I decided to go ART again to saw how many apps that optimized, LOL it was again, 64.
I reboot my phone again, and wait the reception, LOL strange I got no signal in my home *usually full*.
NOTICE: the signal has already gone after first cache wipe.
somehow I go to About Phone, Status on the Settings, and I found out the IMEI is UNKNOWN. I tried to check it with *#06# and it shows nothing.
I repeat the process how I get to the recovery and try to wipe cache, and it said, "error: can't mount /cache".
so I think the cache was gone?? I look to the "Explorer" app *the one who makes the root version too (Root Explorer)*, well the cache partition still there.. LOL
MY QUESTION:
1. am I having a defective Nexus 5? or there is a bug?
2. my IMEI lost, I have 2 expectations: my EFS/IMEI is truly lost, or the system just can't detect it? how can I know?
3. I saw a thread that tells me Nexus 5 doesn't have EFS partition backup, so where does the EFS located?
4. if I follow you guys, unlocking bootloader, rooting and etc. can I make my phone's state default again? *I don't mean fix this thing, just go default*
5. most important thing, HOW CAN I GET MY PHONE BACK TO NORMAL?? *peace bro
please help, right now I'm trying to reset my phone as soon as my backup finishes.
thx
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
vin4yak said:
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
Click to expand...
Click to collapse
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
BirchBarlow said:
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
Click to expand...
Click to collapse
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
IvanKurnia said:
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
Click to expand...
Click to collapse
Strange indeed. Yeah, those errors are common. Just try wiping cache multiple times. If not, factory reset the device.
IvanKurnia said:
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
Click to expand...
Click to collapse
Since you're responsible for this mishap, I would certainly try to fix it myself if I were you. Wiping cache/factory reset is the only thing you can do with a locked bootloader. If that doesn't fix it, the phone's hosed!
IvanKurnia said:
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
Click to expand...
Click to collapse
ADB is used whilst you're in Android OS/custom recovery. You first need to unlock the bootloader, flash/boot a custom recovery and then flash the supersu.zip to gain root. I'm not sure what purpose it will serve in your situation though??
this happened to me too. and I waited for the the wipe cache operation for 15 minutes. After a forced reboot the phone was not connecting to the cell network, had a 1970 date and gave various google errors. I went back to recovery, noticed the comatose android and the missing cache partition messages but again I selected wipe cache and this fixed it. It took just a minute or so to create and format it. After the reboot the phone was fine. phew...
This problem happens when the cache partion is not formated properly. You can't take screenshots either, right? You should try to format the cache partition again, and again until your phone becomes normal, or unlock bootloader and flash the cache.img from the stock images. You can find all the instructions about unlocking bl and flashing cache image in the sticky posts of the general forum.
Tapatalk-kal küldve az én Nexus 5-el
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
DEVICE IS NOT ROOTED
So I went into recovery mode
I tried clearing partition... it didnt work (did that 5 times)
I tried reboot system (didnt work)
I turned it off and on like 10 times and it didnt work
I tried Wipe data/factory reset....lost everything (which sucks because I had photos that never got backed up)
I am official lost, can someone help me? I am not sure what to do next!
I have a macbook, if someone can help me I will greatly appreciate it!
agentjucey said:
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
Click to expand...
Click to collapse
Hello. I have this same problem.
I can't start my phone.
I have no idea what happened. Phone was connected to charger and everything looked ok, but this s**t happend ...
On error screen I've pushed power + volup button
Wipe cache
wipe device ...
nothing helped ...
Still getting this same error ...
Are you getting an error message on the screen or is the phone stuck at the boot animation?
audit13 said:
Are you getting an error message on the screen or is the phone stuck at the boot animation?
Click to expand...
Click to collapse
Android with red triangle and exclamation mark inside ...
Same problem here. This was after applying OTA latest security patch for April.
Would try to boot ("Google" word) 2x then go back to Android bot with red "!" - no command.
Tried wiping cache; factory reset - both multiple times. Still the same.
Tried also draining battery, then full re-charge, still the same problem.
Hope somebody could figure this out.
Thanks in advance.
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
audit13 said:
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
Click to expand...
Click to collapse
I did that ...
wiped cache - no result
reset to factory - no result
Flash the factory image. If your phone is not bootloader unlocked do that first
GtrCraft said:
Flash the factory image. If your phone is not bootloader unlocked do that first
Click to expand...
Click to collapse
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
tupper said:
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
Click to expand...
Click to collapse
Yeah its here in the general section
Flash factory images from NRT tool
1 Unlock ur bootloader
2 flash latest factory image and clear ur internal memory also! Coz the tool has an option to clear internal memory or not to clear internal memory!
3 Done!
Good day.
Thanks fore reading my post.
I had root on my phone like for 3 or 4 months. everything was great and all. I did not dwell in any ROM installing or playing with the firmware.
But I am not sure what I did that this happened.
When I restarted my phone, I experienced everything until the Logo faded to the rotating circle(loading). And it stays there. Always.
I did check on many sites and it seems to be a bootloop. I tried going into recovery, used every button combination possible(I have only 3 and also tried and for my phone and for others to work) and I can't.
It just continues normally and to the position I explained before.
I have a Vodafone Smart 4 Max and even though I want the fix for my phone, I know there are other users that also experience/experienced this problem on different phones.
Might there be a way to fix this?
Thank you for your time
EDIT:: I managed to enter in recovery mode and tried a hard reset of the android. The situation is still the same, the bootloop remaining
Go to bootloader and flash factory firmware with fastboot
I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)
andreinit said:
I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)
Click to expand...
Click to collapse
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)
minimale_ldz said:
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)
Click to expand...
Click to collapse
Hm, I know what you are saying. For me to enter in recovery mode though, I needed to do the following.
1). Fully shutdown the phone for like 30 seconds
2). Volume UP + power button until the first logo with android appears
3). Let the buttons go and I enter
The problem is that adb and fastboot don't see my device at all. I have been tweaking with the drivers for so long, thinking that may be the cause, but I have no results.
And I can use the backup thing to flash a new rom? It requests an update file though, not an image(a zip file)
I think this is about your phone, maybe it will point you in the right direction:
https://www.youtube.com/watch?v=bKHEZbj4NHo
They are figuring out firmware installation on a similair model here: http://forum.xda-developers.com/android/help/stock-rom-vodafone-888-t3002958