Related
[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.
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Megadarkwood said:
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Click to expand...
Click to collapse
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
http://waynekent.com/page6.html
NWKENT said:
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
Click to expand...
Click to collapse
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Megadarkwood said:
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Click to expand...
Click to collapse
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >> http://sbf.droid-developers.org/phone.php?device=14
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >>
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Megadarkwood said:
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Click to expand...
Click to collapse
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #
Click to expand...
Click to collapse
I am not concerned about any data, just need to get it working. I will flash TWRP as soon as I get back to my computer
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
nArdow said:
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, how am I supposed to sideload the .img for TWRP?
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Clarkiieh said:
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Won't work, says "Waiting for Device"
Megadarkwood said:
Won't work, says "Waiting for Device"
Click to expand...
Click to collapse
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
The Closet Candian said:
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
Click to expand...
Click to collapse
Alright, but do I need a OS file or something in the folder before I do this?
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Megadarkwood said:
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Click to expand...
Click to collapse
Since you are in fastboot mode you should use "fastboot devices".
meekrawb said:
Since you are in fastboot mode you should use "fastboot devices".
Click to expand...
Click to collapse
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
Only thing I can think of is to re-install the drivers or try different USB ports.
Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
eg0097 said:
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
Click to expand...
Click to collapse
Got TWRP on and everything flashed but carbon is still in a boot loop.
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Clarkiieh said:
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yeah I hear the beep.
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
Does this sound like an ok process for me to upgrade without losing data? I have a Nexus 5 with stock recovery and currently non-rooted. No modifications to the system that I am aware of.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Do I need to flash the system.img and/or the bootloader.img too?
Matthewlawson3 said:
Does this sound like an ok process for me to upgrade without losing data? I have a Nexus 5 with stock recovery and currently non-rooted. No modifications to the system that I am aware of.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Do I need to flash the system.img and/or the bootloader.img too?
Click to expand...
Click to collapse
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
Elluel said:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Generally speaking, is their a proper order for commands or does it matter? I noticed your command order is a little different from what I did when flashing in the past from one previous version of android to the next version.
Matthewlawson3 said:
Generally speaking, is their a proper order for commands or does it matter? I noticed your command order is a little different from what I did when flashing in the past from one previous version of android to the next version.
Click to expand...
Click to collapse
There is no order. The same things are flashed, the end result is the exact same.
Elluel said:
There is no order. The same things are flashed, the end result is the exact same.
Click to expand...
Click to collapse
So technically speaking I could flash in order and receive the same result?
Matthewlawson3 said:
So technically speaking I could flash in order and receive the same result?
Click to expand...
Click to collapse
I just said there is no order and it doesn't matter, you quoted the post that just said this lol.
Elluel said:
I just said there is no order and it doesn't matter, you quoted the post that just said this lol.
Click to expand...
Click to collapse
Oh, so I did. Thanks for the help!
"1. Extract the radio image to platform-tools folder"
Why this is necessary? Yesterday I flashed 5.1 using sdk's fastboot tool and I didn't do that. Was it wrong? My nexus model is D821 and it was stock 5.0.1. I'll be very grateful If you could guide me to do it right!
btw I followed this tutorial https://www.youtube.com/watch?v=5ka5dnPghzI
Thank you for your help!
gonzalobasterra said:
"1. Extract the radio image to platform-tools folder"
Why this is necessary? Yesterday I flashed 5.1 using sdk's fastboot tool and I didn't do that. Was it wrong? My nexus model is D821 and it was stock 5.0.1. I'll be very grateful If you could guide me to do it right!
btw I followed this tutorial https://www.youtube.com/watch?v=5ka5dnPghzI
Thank you for your help!
Click to expand...
Click to collapse
Radio is optional. On the Nexus 5, you can use any radio on any version of Android.
there is no reason to extract them to the platform-tools folder or to rename them. If you have fastboot in the cmd window just drag the img file into the cmd window after the command and it will have the correct path. So, fastboot flash boot (drag boot image here).
wangdaning said:
there is no reason to extract them to the platform-tools folder or to rename them. If you have fastboot in the cmd window just drag the img file into the cmd window after the command and it will have the correct path. So, fastboot flash boot (drag boot image here).
Click to expand...
Click to collapse
..and if you have adb/fastboot set up PROPERLY, you don't even need to open your cmd/terminal specifically in platform-tools.
It really doesn't matter, the result is obviously going to be the same. People will do whatever seems to be easiest for them.
Hey,
first of all i KNOW there is a subject with nearly the exact same topic, and i followed the directions but somethng doesn't work.
I still have TWRP on the phone, and when im in bootloader mode and run "fastboot devices" i see the result.
but i can't seem to ADB push or anything else (maybe im missing some commands?)
so i used the NRT root kit and i use the "fastboot flash" function and install the .img file - the software says my device is identified and it installs the system.img file (found on the "image-hammerhead-mra58k" zip), but then the device boots to TWRP and still can't boot to the system itself.
help please!
Sideload a factory rom and u will be fine. U can do it in the advanced portion of TWRP, but u need a pc, or ur hit
Sent from my Nexus 6 using Tapatalk
Sounds to me like you're using adb commands in fastboot.
Boot into bootloader (not recovery)
Type fastboot devices
It should return showing your device
Then you need to make sure you have stock img's downloaded and completely extracted so you have all the img files in the folder you're running fastboot from (rename the radio to simply radio.img)
Then type
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash radio radio.img
Then boot back into recovery and wipe cache and dvalik for just in case fun
Then reboot system and wait
Sent from my Xperia z5 by Tapatalk
Thank you very very much guys!
that worked! WOOHOO!!
Good good!
Sent from my Xperia z5 by Tapatalk