From Mrom.
Playing with stock sbf 141 which i have RSDlite'ed a few times - last time after updating to 145 I tried to root and it said no room left, so this time after clearing data/cache/dalvic, I formatted system.
That apparently cost me my bootloaders and now when I boot I get "failed 1", vol up yields fastboot (RSDlite recognizes it as fastboot), vol down yields a quick flash of failed 1, entering recovery, and then blank screen and nothingness (RSDlite doesn't recognize it. It will not let me flash a 4.0.0.2 image.
mhelpmmmm
Thanks!
Your boot is fine. Just flash a custom recovery via fastboot.
ravilov said:
Your boot is fine. Just flash a custom recovery via fastboot.
Click to expand...
Click to collapse
1. power on and vol up:
failed to boot 1
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol Support
(connect to PC)
fastboot devices:
"TA207.... fastboot"
fastboot flash recovery recovery-en-goapk-0630-1029.img
pause
"E:\My Documents\CELL PHONE and WAP\MOTO ATRIX 4G\CWM RECOV 4.0.0.2\atrix4gcwm2>f
astboot flash recovery recovery-en-goapk-0630-1029.img
sending 'recovery' (4612 KB)...
OKAY [ 0.287s]
writing 'recovery'...
FAILED (remote: (00180004))
finished. total time: 0.357s
E:\My Documents\CELL PHONE and WAP\MOTO ATRIX 4G\CWM RECOV 4.0.0.2\atrix4gcwm2>p
ause
Press any key to continue . . ."
That particular flash I have used many times with no probs.
Path to disaster:
wipe data/cache/Dalvic
format /system
boot (successfully) to RSD (Power+vol up)
use RSDlite to flash 141 sbk as I have done about 6 times with no prob. (sbk is in root of PC partition and dragged it to RSDlite window)
Went through 99% and rebooted for switch to BP Pass through and hung until fail because phone did not reboot, but stopped at failed to boot 1.
EDIT: phone showed :
Flashing partition recovery
Flashing MBR to device
Failed to process command flash: recovery error (0x180004)
KrisM22 said:
1. power on and vol up:
failed to boot 1
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol Support
(connect to PC)
fastboot devices:
"TA207.... fastboot"
fastboot flash recovery recovery-en-goapk-0630-1029.img
pause
"E:\My Documents\CELL PHONE and WAP\MOTO ATRIX 4G\CWM RECOV 4.0.0.2\atrix4gcwm2>f
astboot flash recovery recovery-en-goapk-0630-1029.img
sending 'recovery' (4612 KB)...
OKAY [ 0.287s]
writing 'recovery'...
FAILED (remote: (00180004))
finished. total time: 0.357s
E:\My Documents\CELL PHONE and WAP\MOTO ATRIX 4G\CWM RECOV 4.0.0.2\atrix4gcwm2>p
ause
Press any key to continue . . ."
That particular flash I have used many times with no probs.
Path to disaster:
wipe data/cache/Dalvic
format /system
boot (successfully) to RSD (Power+vol up)
use RSDlite to flash 141 sbk as I have done about 6 times with no prob. (sbk is in root of PC partition and dragged it to RSDlite window)
Went through 99% and rebooted for switch to BP Pass through and hung until fail because phone did not reboot, but stopped at failed to boot 1.
EDIT: phone showed :
Flashing partition recovery
Flashing MBR to device
Failed to process command flash: recovery error (0x180004)
Click to expand...
Click to collapse
Jw, why use 4.0.0.2 when 5.0.2.0 and 5.0.2.7 are available?
Try renaming the img to just recovery and then flash it via fastboot
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Jw, why use 4.0.0.2 when 5.0.2.0 and 5.0.2.7 are available?
Try renaming the img to just recovery and then flash it via fastboot
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your time. I have 5020 and 5027 as zip. I d/l'ed 5020 as image and tried it and same thing, even with the rename to just recovery.
KrisM22 said:
Thanks for your time. I have 5020 and 5027 as zip. I d/l'ed 5020 as image and tried it and same thing, even with the rename to just recovery.
Click to expand...
Click to collapse
Odd, idk why that is happening
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Odd, idk why that is happening
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
ditto, but huge thanks for your looking in!!!
any ideas? anybody? anything I can do in fastboot?
fleshing this out, I find that if I power on with no vol buttons pressed, I get failed boot 1, I am in RSD mode. So I can re-RSDlite 141, but again get failed boot 1. The reason for this is that when I was last on 141, I ota (wifi) updated a 20mb file to 145. And as it is reported across the net, you can't go backward.
Anyone found a fix for "going backward"?
Nevermind, I'm up. The solution may have been to remove the SD card while doing stuff. Or else I got lucky.
Related
so i had rooted my 2.3.4 phone and installed gingerblur on it, now im dealing with a problem it seems to be in bootloop, and i have tried to wipe all the data/cache and still no boot :/ and i noobishly did not back up my phone and the gingerblur is on the internal card and not on my external, any idea? i have rsd on there but i dont know if my usb debugging is enabled.
helppp lol
Ok. Search the android development forums for fruitcake. Download the 2.3.4 fruitcake onto your computer. Take your sd card out of your phone and hopefully u have a mini sd card holder so u can plug into your computer to put the fruitcake on your external sd card. Once its on, boot into fastboot and erase system, user data, webtop, preinstall, boot, and cache. Then fastboot reboot into recovery and flash the fruitcake.
Sent from my MB860 using XDA Premium App
when i turn it down and hold the volume down there are quite a bit of options to choose from
garrett_tx said:
when i turn it down and hold the volume down there are quite a bit of options to choose from
Click to expand...
Click to collapse
Yeh keep hitting down till u see fastboot then hit up to get into fastboot
Sent from my MB860 using XDA Premium App
do i delete everything via android recovery?
alrighty sorry about all the questions
sorry not reading
and what should i type into cmd for the flashing of fruitcake
fastboot erase system
fastboot erase data
...etc...
Just go through and erase what Phalanx621 listed and then boot into recovery. Make sure you do NOT erase the recovery.
garrett_tx said:
alrighty sorry about all the questions
i have fruitcake zip on my sd card now and its plugged into usb do i press the volume up when i get to fastboot?
and what should i type into cmd
Click to expand...
Click to collapse
Alternatively, you can just use "fastboot -w" to clear the data and cache in one shot. Just thought I throw that in there...
live4nyy said:
fastboot erase system
fastboot erase data
...etc...
Just go through and erase what Phalanx621 listed and then boot into recovery. Make sure you do NOT erase the recovery.
Click to expand...
Click to collapse
But you still have to do system, webtop, preinstall, and boot.
how do i flash fruitcake? do i just NvFlash or what
After you finish erasing everything you just power down the phone and then power it up while holding down "VOL Down" and wait for it to say "Fastboot", then press the "VOL Down" until it says "Android Recovery" and then press "VOL Up". You should be able to flash using the menu there. Of course, it would help if you had Tenfar's or romracer's recovery. Do you have either one of those?
If not, you will have to go to one of their threads, download it to your computer, put it in the same folder as fastboot, reboot into fastboot, and then run the commands:
fastboot erase recovery
fastboot flash recovery "file name.img" (make sure you type in the file name exactly)
After that, you can boot into recovery and flash the fruitcakes by using "flash from zip" > "external SD"
garrett_tx said:
how do i flash fruitcake? do i just NvFlash or what
Click to expand...
Click to collapse
garrett_tx said:
how do i flash fruitcake? do i just NvFlash or what
Click to expand...
Click to collapse
Phalanx7621 said:
Ok. Search the android development forums for fruitcake. Download the 2.3.4 fruitcake onto your computer. Take your sd card out of your phone and hopefully u have a mini sd card holder so u can plug into your computer to put the fruitcake on your external sd card. Once its on, boot into fastboot and erase system, user data, webtop, preinstall, boot, and cache. Then fastboot reboot into recovery and flash the fruitcake.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Right there buddy.
Here is romracer's recovery:
http://forum.xda-developers.com/showthread.php?t=1204500
live4nyy said:
After you finish erasing everything you just power down the phone and then power it up while holding down "VOL Down" and wait for it to say "Fastboot", then press the "VOL Down" until it says "Android Recovery" and then press "VOL Up". You should be able to flash using the menu there. Of course, it would help if you had Tenfar's or romracer's recovery. Do you have either one of those?
If not, you will have to go to one of their threads, download it to your computer, put it in the same folder as fastboot, reboot into fastboot, and then run the commands:
fastboot erase recovery
fastboot flash recovery "file name.img" (make sure you type in the file name exactly)
After that, you can boot into recovery and flash the fruitcakes by using "flash from zip" > "external SD"
Click to expand...
Click to collapse
i do have tenfars, when i try to erase stuff it says failed to process command erase recovery error (0x180001)
im not getting an option to flash
Are u typing the command properly ? Errors show up usually if u mistype the commands
Sent from my MB860 using XDA Premium App
you have to be more specific about where you're getting these errors
garrett_tx said:
im not getting an option to flash
Click to expand...
Click to collapse
yeah i am, its saying
C:\root>fastboot flash recovery "root.img"
sending 'recovery' (32768 KB)... OKAY 2.052s
writing 'recovery'... FAILED (remote: (00180002))
Are you leaving the quotation marks out of the command?
Also, why is it called root.img? It should be a recovery. If that's what you renamed it then it should be fine. Which recovery are you using? have you tried typing "fastboot devices" to make sure it is recognized?
garrett_tx said:
yeah i am, its saying
C:\root>fastboot flash recovery "root.img"
sending 'recovery' (32768 KB)... OKAY 2.052s
writing 'recovery'... FAILED (remote: (00180002))
Click to expand...
Click to collapse
i guess i dont know the orginal recovery name from tenfars cwm so its not flashing it it just fails every time
im so lost right now -____-
Hello guys,
I just rooted my HTC explorer for the first time. I was following this tutorial: http://forum.xda-developers.com/showthread.php?t=1415223
Everything was working fine until after installing the recovery.
After copying the superuser.zip to the SD and rebooting to bootloader menu, I click recovery and just get stuck on a HTC green logo.
If i take the battery out, I power back the phone and it works fine.
If i try to enter bootloader menu, and enter recovery, i get stuck again at that screen.
In the menu my phone appears as "unlock" so i supposes all steps before were fine..
If you guys could help it would be immensely appreciated!
apparently this is something that happened to many users but i couldn't find a straight answer on how to solve it!
I've tried to flash the recovery again, and i have the following error:
"sending 'recovery' (289 KB)... OKAY [ 0.059s]
writing 'recovery'... FAILED (remote: image error)
How can i install the recovery then?
DavidSnake said:
I've tried to flash the recovery again, and i have the following error:
"sending 'recovery' (289 KB)... OKAY [ 0.059s]
writing 'recovery'... FAILED (remote: image error)
How can i install the recovery then?
Click to expand...
Click to collapse
try installing clockword mod recovery
make sure that USB debugging is selected on ur phone, after that
goto fastboot and connect ur phone to USB
and flash it using command
fastboot flash recovery recoveryname
or alternatively if ur phone is running fine:
then install ROM Manager and from there u can flash recovery to ur mobile
Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app
First of, I'm running Cyanogenmod 12.1 on my Z2.
On the install it vanished my TWRP Recovery, so I decided to reflash it using their app - this was unsucessfull. I thought I would flash it the next day using adb, so I didn't mind.
However in the next hours I needed to reboot the phone - resulting in the Sony logo and nothing more. So I bootet into the CM recovery and tried to reflash the CyanDelta zip - this failed and resulted in "footer is wrong - signature verification failed - Installation aborted". The next thing I tried was flashing a zip by adb recovery sideload - this failed as well and resulted in "protocol fault (no status)".
This was when I tried to boot into the bootloader using the recovery menu entry. The screen got black, the LED lighted up blue and nothing happened forever. The same thing occours when I try to boot into the bootloader by hardware keys (hold VolUp and insert MicroUSB cable).
So, in short:
I can't boot android
I can't install zips by CM recovery
I can't boot into the bootloader [EDIT: I can.]
I can't install nandroid backups since the CM recovery doesn't offer that
Any idea?
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
the_crevis said:
If the phone's LED lights up blue it means that you are in fastboot mode (AKA the bootloader) . It is normal for the screen to be black. I suggest that you download a stock FTF and flash it using the windows flashtool application. Your phone is fine. Good luck.
Click to expand...
Click to collapse
Ah, I feel dumb now. I might be damaged from the informational Nexus bootloader.
So, I tried to flash a new recovery - fastboot flash twrp-2.8.6.0-sirius.img - which succeded, but it still boots the CM Recovery. Buh.
Seems like something is overriding the recovery on boot. So lets erase everything:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot flash twrp-2.8.6.0-sirius.img
Aaaand - still CM Recovery.
I also tried to flash a stock image as you suggested, however:
Code:
fastboot flash system system.sin
sending 'system' (1800183 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
No worries, I came from a nexus 4 and it confused me as well at first. Try exacting http://forum.xda-developers.com/xperia-z2/development/kernel-m5-kernel-t2858912 and flashing the boot image via fastboot. That should give you a working recovery.
As I said, flashing a recovery by fastboot results in the CM Recovery.
I just tried to wipe my device using the CM Recovery, it told me it was unable to mount /data - my guess? The filesystem is ****ed up.
EDIT: I got it. Seems like TWRP needs some custom stuff to work (which is provided by CM). Flashing philz worked fine and allowed me to sideload a proper ROM. Everything fine now
Hi,
I tried to install TWRP on my Honor 5X KIW-UL00, but its seems to fail..
I successfully got my unlock code and unlock the bootloader. (Somes stranges chineses signs are appearing under the boot logo )
I flash TWRP using the command
Code:
fastboot flash recovery twrp-3.0.2-0-kiwi.img
I get the response:
Code:
C:\adb>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.466s]
writing 'recovery'...
OKAY [ 0.704s]
finished. total time: 2.171s
BUT ! When I reboot to recovery mode (Power + Volume Up) I get the "Huawei eRecovery" and not TWRP...
Any ideas ?
What am I missing ?
Thanks
Ok, it seems solved.
I tried it 2 times again and it happens something differently at the reboot (There was a "Optimizing" screen).
I try recovery mode again and tatatata ! it worked !
bmerklen said:
Ok, it seems solved.
I tried it 2 times again and it happens something differently at the reboot (There was a "Optimizing" screen).
I try recovery mode again and tatatata ! it worked !
Click to expand...
Click to collapse
Glad you fixed it mate.
bmerklen said:
Ok, it seems solved.
I tried it 2 times again and it happens something differently at the reboot (There was a "Optimizing" screen).
I try recovery mode again and tatatata ! it worked !
Click to expand...
Click to collapse
Are there more details to this solution? I'm stuck with this issue and I've tried a tad bit more than 2 times haha.
For me the secret was the reboot after the flash. You need to reboot peacefully at least 1 time before accessing the recovery.
bmerklen said:
For me the secret was the reboot after the flash. You need to reboot peacefully at least 1 time before accessing the recovery.
Click to expand...
Click to collapse
To clarify, your way that fixed it is:
- Flash the Recovery
- Reboot Normally
- Reboot to Recovery
instead of
- Flash the Recovery
- Reboot to Recovery
Alright, I'll try this when I am home. Will Update!
Update: Didn't work, unfortunately D:
fastboot boot kiwi_twrp_3-21_recovery.img
Yes, that's the key, after flashing recovery, I always do a system reboot rather than recovery