[SOLVED] (not sure how to tag as solved in the title, if mods can do that please or tell me how)
Flashed Clockwork Mod Recovery following these instuctions
droidviews.com/2013/install-clockworkmod-recovery-on-motorola-droid-razr-hd-xt925gsm/
Installed Rom manager.
Booting into recovery results in robot on his back with the triangle and exclamation point animation and stays there unless I
force reboot by holding the power button. Phone boots to stock rom or fastboot just fine.
Tried reflashing CWM just in case.
I am rooted via motochopper
Unlocked bootloader via motopocalyspe.
I factory reset my phone prior to all this so there are only a few apps installed, also SuperSU installed.
Rogers version XT925
Anyone else have this issue or know how to fix it?
Are you using the cmd 'fastboot flash recovery recovery.img'
?
Sent from my Desire HD
ykdr-scott said:
Are you using the cmd 'fastboot flash recovery recovery.img'
?
Sent from my Desire HD
Click to expand...
Click to collapse
Thanks for the quick reply; yes that is the command I used to flash the recovery image to my phone.
check see if your recovery image is in the same directory as your fastboot eg Cmd > cd C:/fastboot flash recovery recovery.Img
I always paste my files directly into cd C:/ .
If you have them in a folder in c it would be ' cd C:/folder name here fastboot flash recovery recovery.img
Sent from my Desire HD
ykdr-scott said:
check see if your recovery image is in the same directory as your fastboot eg Cmd > cd C:/fastboot flash recovery recovery.Img
I always paste my files directly into cd C:/ .
If you have them in a folder in c it would be ' cd C:/folder name here fastboot flash recovery recovery.img
Sent from my Desire HD
Click to expand...
Click to collapse
They are in the same folder, in the mean time I actually found another thread with the same problem. I guess I didn't search hard enough the first time before posting. I found a 1 click installer for CWM/TWRP that fixed my issue. I'm guessing I may have just had a bad recovery img or something.
http://forum.xda-developers.com/showthread.php?p=42255792#post42255792
links to the thread with the 1 click installer.
Related
I was trying to flash faux kernel via recovery but i got the status 7 error so i guess the problem is that because iam s-on so plz anybody knows how to flash a custom kernel with s-on.
yus99 said:
I was trying to flash faux kernel via recovery but i got the status 7 error so i guess the problem is that because iam s-on so plz anybody knows how to flash a custom kernel with s-on.
Click to expand...
Click to collapse
Flash the boot.img from the zip via fastboot.
You can find the instructions here: http://forum.xda-developers.com/showthread.php?p=25587345
Make sure you use the boot.img from the zip & not the one from the guide.
HI
So just to make sure these are the steps:
Put the"boot.img" in your "C:\Android" (or wherever your adb and fastboot are located)
Shift right click in the white space on that folder
Select "Open command window here
Type in: adb
Type in: adb reboot-bootloader
Your phone will reboot, wait until you see a white screen which says "FASTBOOT USB"
Type in: "fastboot flash boot boot.img"
Wait until it's done flashing
Type in: "fastboot reboot"
One more thing i didnt see the boot.img in the zip of the kernel there are three folders:
1- kernel
2- META-INF
3- system
In the kernel folder there are these files:MKbootimg,dd,unpackbootimg,zImage,mkbootimg.sh,modclean.sh
What to do I am so confused
yus99 said:
So just to make sure these are the steps:
Put the"boot.img" in your "C:\Android" (or wherever your adb and fastboot are located)
Shift right click in the white space on that folder
Select "Open command window here
Type in: adb
Type in: adb reboot-bootloader
Your phone will reboot, wait until you see a white screen which says "FASTBOOT USB"
Type in: "fastboot flash boot boot.img"
Wait until it's done flashing
Type in: "fastboot reboot"
One more thing i didnt see the boot.img in the zip of the kernel there are three folders:
1- kernel
2- META-INF
3- system
In the kernel folder there are these files:MKbootimg,dd,unpackbootimg,zImage,mkbootimg.sh,modclean.sh
What to do I am so confused
Click to expand...
Click to collapse
thats a recovery flashable zip
you can flash that via recovery only
as you are SON ...better have 4EXT recovery
there ..just enable smartflash in 4EXT-> tools and then flash the kernel package
EDIT:
this thread explains the reason for error 7 and the probable fix
http://forum.xda-developers.com/showthread.php?t=1556620
hi
just one more thing do i need to uninstall my current recovery to install the 4-ext one or just install it.
yus99 said:
just one more thing do i need to uninstall my current recovery to install the 4-ext one or just install it.
Click to expand...
Click to collapse
just install it either via fastboot
fastboot flash recovery recovery.img
recovery.img from here (its rc3 ...and latest is rc5 btw)
or
via 4EXT updater app available in sensation development thread
Hello,
I have followed a tutorial for solving the problem of "Fastboot mode started
udc_start()" from this thread http://forum.xda-developers.com/showthread.php?t=2131247 and something was go wrong.
I have done this steps in the sdk platform tools folder:
1- fastboot erase recovery
2- fastboot flash recovery recovery.img ( here i've got an error)
3- fastboot reboot
Everyting was ok until I have tried to write the .img file on the phone. I've got an error that I don't have enough space. I think I have deleted the recovery file and now it's stuck, because it's not booting. The 4 leds from the bottom it's flashing continuously and the screen remains to the LG logo. I have tried to connect the phone to the PC but the device it's not recognized anymore. I get this message in the adb tool "Waiting for device"
I really appreciate if it's someone that can help me
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Logan_M said:
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Click to expand...
Click to collapse
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
catalin11 said:
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
Click to expand...
Click to collapse
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Logan_M said:
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Click to expand...
Click to collapse
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
catalin11 said:
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
Click to expand...
Click to collapse
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
catalin11 said:
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
Click to expand...
Click to collapse
now i'm in the emergency mode
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
some1 pls help me
catalin11 said:
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
Click to expand...
Click to collapse
can u plz elaborate...i too have the same problem....plz..
Logan_M said:
If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located.
Click to expand...
Click to collapse
That is incorrect. The recovery does NOT have to be named recovery to use fastboot to flash it, although it does make life simpler
i was try to flash SVHD 2.0.0 rom and i successfully flashed it via recovery .i flash its boot image with HTC Desire S All In One Kit and boot image was successfully flashed but when i switch on the phone after the HTC logo it shows the black screen and phone doesnt boot up . Will any one help me about this problem or can anyone tell me where i am going wrong .
I am having hboot 2.02.0002 and radio 3831.19.00.110
Did u flash the boot.img from the latest svhd zip or an older version?
Extract the boot.img from the zip and try flashing it via cmd in fastboot.
Cheers
FromBeyondThisWorld
#Fear said:
Did u flash the boot.img from the latest svhd zip or an older version?
Extract the boot.img from the zip and try flashing it via cmd in fastboot.
Cheers
FromBeyondThisWorld
Click to expand...
Click to collapse
i flashed boot.img of new svhd rom 2.0.0 and i flash it through HTC Desire S All In One Kit . please help
Try flashing it manual without using the toolkit.
First you would need an adb and fastboot setup.
Open the rom (.zip file) you downloaded and put the ''boot.img'' file in ''C:\android-tools''.
Make a nandroid backup
Full wipe(except sd)
Flash rom
Select reboot into fastboot
Flash the boot.img manual by :
- Go to start->run-> type cmd and press enter. A command prompt will now appear.
cd c:\android-tools [press enter]
fastboot flash boot boot.img [press enter]
Click to expand...
Click to collapse
Do make sure you're in fastboot and not the other.
After it's successfully installed, turn of your phone and just boot normally. It may take a while for your phone to boot up.
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Go to bootloader and run "fastboot devices" and see whether your device gets detected or not? If it does, then flash the factory images. System and boot img files would do the job.
If it doesn't then you need to fix the adb, fastboot issues first. Follow these threads:
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
If you have an OTG cable with you, you can directly flash the rom from a usb stick!
tangosierra_ said:
Flash the factory image through fastboot. Download and run flash-all.bat (something along those lines)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
You havent got fastboot installed.
Go to teh link in my signature.... Then go to section 1b, 1
usb/otg
Dixi1801 said:
Hello all,
as the title says, I'm stuck in TWRP recovery after wiping my rom to revert to stock... then realising that the recovery doesn't recognise the image as it's a .tgz file.
I've tried to ADB into it, but no such luck, I just get error: device not found.
Does anyone know a way I can fix this?
I've also tried the adb sideload feature of TWRP to no avail.
Thanks in advanced guys.[/QUOT
Download any compatible rom to a usb/otg..mount from TRWP and your good to go..Happens to me once..Just download any compatible roms just to bring up your phone..
Click to expand...
Click to collapse
Dixi1801 said:
'fastboot is not recognised as an internal or external command, operable program or batch file.'
Also, i'm trying this from the PC just to be clear, as I can't boot my phone lol.
soon as i run flash-all.bat i get the error i put on the first line
Click to expand...
Click to collapse
remove all old drivers and restart
install http://forum.xda-developers.com/showthread.php?p=42407269&__utma=248941774.1031819907.1403635167.1403781687.1403790944.7&__utmb=248941774.1.10.1403790944&__utmc=248941774&__utmx=-&__utmz=248941774.1403790944.7.7.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
shhbz said:
remove all old drivers and restart
install http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=239174656
place the android sdk windows file attached here in c: drive
now start cmd prompt and type
Code:
cd c:\android-sdk-windows\platform-tools
now proceed with fastboot command in this order
Code:
fastboot flash bootloader C:/hammerhead-ktu84m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/hammerhead-ktu84m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/hammerhead-ktu84m/system.img
fastboot flash userdata C:/hammerhead-ktu84m/userdata.img
fastboot flash boot C:/hammerhead-ktu84m/boot.img
fastboot flash recovery C:/hammerhead-ktu84m/recovery.img
fastboot erase cache
note:remember to extract the factory stock image till u see these files attached and place it in C: drive and yes the built name should be same as yours of 4.4.4 then KTU84P inplace of ktu84m
Click to expand...
Click to collapse
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
rootSU said:
Too Long. 15 second installer is the best way to get adb and fastboot. See previous post
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great and flash-all.bat script does not work evrytime so just wanted the guy to be sure the he type the commands in right direction instead getting error cant find and stuff
shhbz said:
was unable to find link to 15 second installer as what i remember was the minimal adb and fastboot and both works great
Click to expand...
Click to collapse
1b1 in the link in my signature.
Minimal is fine but you have to manually add to environment variables or cd to the directory but that's all done with the 15 seconds one.
Sent from my Nexus 5 using Tapatalk
Thanks for the help guys.
RootSU, you saved me haha, was sat at work stressing trying to sort the mess I made out!
I'm all stock now... But the screen keeps going off because of the proximity sensor haha -_-
Thanks again though. Can always count on a Yorkshireman
The important thing is to remain calm and know it can be fixed
Sent from my Nexus 5 using Tapatalk
Im trying to flash either CWM or TWRP viea fastboot, i download the recovery, re name it to recovery ( recovery.img) place it in my C drive folder and then type fastboot flash recovery C:\recovery.img
however each time when entering recovery from the boot screen it ends with a dead android and an exclamation mark, what next?
Are you booting android before booting recovery
It's easier to put the image in the same location as fastboot so you just type
fastboot flash recovery recovery.img
After classifying I've rebooted into android, then powered off and back to recovery, followed by recovery then the dead android.
That should read after flashing, not classifying.
2Pints said:
That should read after flashing, not classifying.
Click to expand...
Click to collapse
Your on 5.0.1? I had the problem too what worked for me and I can't tell you why was to boot into twrp, flash supersu and then boot back into the bootloader and flash twrp
Fastboot boot twrp.img
Flash supersu, then
fastboot flash recovery twrp.img
Sent from my Nexus 5 using XDA Free mobile app
I cant get to the TWRP bit
download twrp rename it to recovery
fastboot flash recovery C:\recovery.img
fastboot reboot
boot into bootloader, select recovery, phone reboots ( google splash screen) then dead android.
2Pints said:
I cant get to the TWRP bit
download twrp rename it to recovery
fastboot flash recovery C:\recovery.img
fastboot reboot
boot into bootloader, select recovery, phone reboots ( google splash screen) then dead android.
Click to expand...
Click to collapse
Try opening a cmd window in the folder with your image and flashing, ( shift+right click) and boot straight into recovery, without restarting...
2Pints said:
I cant get to the TWRP bit
download twrp rename it to recovery
fastboot flash recovery C:\recovery.img
fastboot reboot
boot into bootloader, select recovery, phone reboots ( google splash screen) then dead android.
Click to expand...
Click to collapse
Are you actually reading what we're posting? The post above yours tells you what to do so follow that and it should work
Its because of the install recovery shell script replacing recovery on first boot of android. You'll want to remove those scripts
Basically dont do "fastboot reboot". Just boot from bootloader directly into recovery, then using TWRP file manager, delete the scripts.
/system/recovery.init.boot.p
/system/bin/install-recovery.sh
rootSU said:
Its because of the install recovery shell script replacing recovery on first boot of android. You'll want to remove those scripts
Basically dont do "fastboot reboot". Just boot from bootloader directly into recovery, then using TWRP file manager, delete the scripts.
/system/recovery.init.boot.p
/system/bin/install-recovery.sh
Click to expand...
Click to collapse
Exactly. Gosh, how hard can this be.
People don't read - if they did, they would know.
Android has been using this for a while now, to ensure stock recovery stays there.
a maguro wrote this.