I have a one xl that will reboot after being on for 2 minutes
evita pvt ship s-on rl
hboot-1.14.0002
it is unlocked, but i cant relock it. Every time i try it says fails then reboots. I have also tried flashing twrp and cwm recovery via fastboot, but everytime i try to enter one it hangs on the teamwin screen. I have tried the ruu it reads my phone at first then when it says rebooting to bootloader the phone reboots normaly and get error 107.
Any help would be greatly appreciated.
What method are you using to try to relock the phone? What method are you using to install the mentioned recoveries? Please give as much detailed information as possible.
Sent from my Evita.
To relock i have used fastboot in cmd and typed fastboot oem lock. I have done that 10 times with the same result phone reboots normally and when i reboot back into bootloader it still says unlocked.
To flash recoveries i have used fastboot flash recovery ********.img
fastboot erase cache
fastboot reboot-bootloader
but instead of rebooting to the bootloader it boots normally
What did you do to the phone before all this started happening? Phones don't usually just start doing things like this of their own accord.
Sent from my Evita.
I bought it like this. The last owner said it happend after he installed a rom. I was hopping i could unbrick it with out jtagging it becuase i am still able to fastboot to it.
If you can't get an RUU to work I think jtag might be your only option.
Sent from my Evita.
I've only tried 2.20. I even extracted the system IMG from it but fast boot says it is too large. The only reason ruu won't work is because I can't get my phone to reboot into boot loader. Is there any way I can flash a different boot loader through fast boot.
Just curious, but when you type fastboot devices from the Bootloader, what is the output?
Are you running fastboot oem lock from the bootloader?
Sent from my One X using XDA Premium 4 mobile app
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
keithman2567 said:
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
Click to expand...
Click to collapse
If when you type fastboot devices (while in the boot loader) in your computers command prompt, and it doesn't show your HTC device being attached, that means that your computer is not recognizing your phone. Have you installed the HTC drivers? Do you have the newest versions of fastboot and adb installed?
What OS are you running on your computer?
Sent from my One X using XDA Premium 4 mobile app
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
keithman2567 said:
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
Click to expand...
Click to collapse
Does your device boot into the ROM at all?
Sent from my One X using XDA Premium 4 mobile app
Yes. But only for 2 mins before it reboots.
keithman2567 said:
Yes. But only for 2 mins before it reboots.
Click to expand...
Click to collapse
If you can connect to Google Play store, download recovery tools, if you have time. From there you could try to install a new recovery for your device. With only 2 minutes you will have to be quick though.
Do you have access to your sdcard from your computer?
Sent from my One X using XDA Premium 4 mobile app
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
keithman2567 said:
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
Click to expand...
Click to collapse
Here is the app. Not sure if you'll have time, but you can try
https://www.dropbox.com/s/wa4u565woyrrrlw/de.mkrtchyan.recoverytools-2.apk
Sent from my One X using XDA Premium 4 mobile app
Thank you, but there isn't enough time to even transfer it over
keithman2567 said:
Thank you, but there isn't enough time to even transfer it over
Click to expand...
Click to collapse
Do you have USB debugging enabled in the phone?
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:15 PM ----------
Have you tried to flash a new ROM from fastboot? It sounds like your recovery partition might have been corrupted.
Sent from my One X using XDA Premium 4 mobile app
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
keithman2567 said:
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
Click to expand...
Click to collapse
Alright, so I have a few ideas.
1. Try flashing a new rom via fastboot. (the following is based on the assumption that you have adb and fastboot in your path)
Flashing a ROM through Fastboot
So Why Do I Need To Do This?
You don't, normally you would flash a ROM through recovery, but why not have another way? Maybe your recovery partition on your phone is corrupt?
Maybe you just want to say "I learned something new!" whatever your reason here are the simple steps:
To start:
Quote:
Quote:
We need to download the ROM of choice to your computer. Once complete find the folder that rom is in and open terminal/cmd to that directory
(quickest way for windows; just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
2. Boot into Recovery via fastboot.
Plug phone into PC, connect with USB cable and have phone in fastboot mode, now open CMD/Terminal in the same directory as your recovery image
Code:
fastboot boot recovery.img
Of course name image correctly to fit command or vise versa
Now you are in recovery of choice within your device without it being flashed to your recovery partition. There is a time and a place for everything, can you think of ways this may help you? Sure you can!
This doesn't actually flash the recovery.img... it will just allow you to boot into it. Make sure that you have a good TWRP version.
The previous quotes were taken from this guide on XDA-University:
http://forum.xda-developers.com/showthread.php?t=2277112
Related
hey guys, the issue I am having is that I am trying to side load rom manager touch but when I enter fastboot reboot bootloader it just says waiting for device. everything worked fine while running GB but now this. I also tried booting into fastboot and running the command, but still nothing. I downloaded the latest version of pda net. dont know if that makes a difference. also usb debugging is selected in developers options. any ideas?
Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk
gm` said:
Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.
Yes u can via flashboot.
Flashboot recovery newrecovery.img
Sent from my Nexus S using Tapatalk
CaptEvo said:
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.
Click to expand...
Click to collapse
Because is not in fastboot mode
Sent from my Nexus S using Tapatalk
I get that, any idea how to get into fastboot now?
In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc
I would love to do that except when I go into boot loader there is no option for fastboot
albundy2010 said:
In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc
Click to expand...
Click to collapse
Dear lord, I guess I forgot a bunch of stuff. Thanks for refreshing my memory
Got it done.
CaptEvo said:
I would love to do that except when I go into boot loader there is no option for fastboot
Click to expand...
Click to collapse
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S
DarkhShadow said:
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes thats true. But before running the commands run : fastboot devices. If you see a long number youre jn fastboot mode and the drivers are correctly installed.
Then you can run the commands
Sent from my Nexus S using xda premium
I posted this before but it was dead so I'm reposting, sorry. I was in the process of rooting my brothers phone, I turned S-off and flashed updated firmware, however I forgot to flash a recovery. Now the phone is in a bootloop. I tried downloading 4ext recovery file PG58IMG to flash in bootloader. I added his cid number to the file but when I run bootloader it doesn't give me the option to install the file. The other method I was told to try involves using CMD to do it with the flashing tool. But since I can't start the phone, cmd doesn't recognize the device. Can somebody please help me? How can I install recovery on this device?
You could always go into fastboot manually and use the cmd prompt. Fastboot flash recovery **********.IMG I'm almost sure that's the proper command.
Sent from my HTC Sensation 4G using xda app-developers app
Sloopjoshb said:
You could always go into fastboot manually and use the cmd prompt. Fastboot flash recovery **********.IMG I'm almost sure that's the proper command.
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
I tried doing that but nothing happened. cmd prompt said waiting for device but nothing happened. Do I have to have adb set up or what are the steps in order for me to do that?
smockpuv said:
I tried doing that but nothing happened. cmd prompt said waiting for device but nothing happened. Do I have to have adb set up or what are the steps in order for me to do that?
Click to expand...
Click to collapse
Hi,
You need to have THESE DRIVERS on your PC.
ADB is explained HERE
Installing recovery is HERE
Took the words right out of my mouth.
Sent from my HTC Sensation 4G using xda app-developers app
smockpuv said:
I tried doing that but nothing happened. cmd prompt said waiting for device but nothing happened. Do I have to have adb set up or what are the steps in order for me to do that?
Click to expand...
Click to collapse
this means you havent connected the phone properly to pc
the phone should show "fastboot usb" if connected to pc properly ..if it shows hboot and there is an option fastboot in the list . browse to fastboot using volume download ..then select fastboot using power ...then connect the device to pc ( at the end phone should show fastboot usb)
then try the command
fastboot flash recovery recovery.img
(if you got PG58IMG.zip open it and copy the recovery.img to the folder where you got adb/fastboot )
Hi,
Take a look at this thread, it may be able to help you out, plus the tool is simple to use to install the recovery as well. Just follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1668276
Hello,
I have recently rooted and loaded the cm10.1 rom, and now, i'd like to load a different rom.
My problem, however, is that when using the all in one toolkit and RUUs all lead to the same error, that my device is offline.
I have:
Unplugged/replugged my USB
Rebooted both computer and phone
added new adb to the toolkit data folder
But to no avail.
In the bootloader menu, the toolkit will say
error:device not found isntead
How would I go about flashing a new rom when my stupid computer won't recognize the phone :'(
you should go learn something instead of using the all-in-one kit as you should know how to flash a rom if you have cm10.1 on it now.
No idea how or where to start
Sent from my One X using xda premium
The FAQ stickied to the top of this forum is a good place to start, as it has the answer to your exact question: http://forum.xda-developers.com/showthread.php?t=2136172
The USB connects, and I can access phone files when I turn the USB connection on, but I can't get a custom ROM to flash
Sent from my One X using xda premium
ozymandius95 said:
but I can't get a custom ROM to flash
Click to expand...
Click to collapse
What does that mean exactly? You are in TWRP, you select the ROM zip, then what happens? Any error messages?
redpoint73 said:
What does that mean exactly? You are in TWRP, you select the ROM zip, then what happens? Any error messages?
Click to expand...
Click to collapse
I believe he is trying to use the kit to flash the ROM?
Because I can't flash boot.img in recovery.
And I can't figure out anything on flashing these things without the toolkit
First of all, make sure you have both ADB and fastboot in your computer. Go to CMD, then cd to your adb directory, and try "adb devices". If it doesn't recognize the device, try with a different usb cable, or download adb again. If it does recognize the phone type in "adb reboot-bootloader", once the
phone boots into the bootloader, type in "fastboot devices", then "fastboot flash boot boot.img", last step "fastboot reboot". And you are done flashing the boot.img
Ok, I can boot into Hboot, but when I choose recovery, I get stuck in a loop on the logo with the red disclaimer.(yes I cleared cache) I tried installing a rom and after that I cannot boot into ANYTHING. Just a loop. Hboot 1.14 I just want a working rom at this point. Stock is fine. But I am totally at a loss right now. Am I screwed? Thank you for your time.
I tried CM, Stock Recover, TWRP.....
HTC One X ATT
Rooted
Bricked?
Try to reflash the recovery and try again. Do you have the Evita or endeavor?
Sent from my Carbon-ize Evita using xda-developers app
Need to be more specific, but try this and for future reference
Are you unlocked? Did you fastboot flash boot boot.img (always do this when on hboot 1.14 or higher)?
Give me all the info you can about your phone. Recovery version, rom that was flashed, but failed, what did you do when flashing the rom step by step?
This should be fixable by ruuing heres a link on the basic directions
http://onexroot.com/one-x-unroot/how-to-unrootunbrick-att-one-x/
I think you can't use 2.20, you probably need a later ruu. Hope this works, but don't do this until after you have provided more info
---------- Post added at 01:28 AM ---------- Previous post was at 01:19 AM ----------
And I or someone better than me at this has given you the OK to.
Tried all of the fastboot methods
I have tried reflashing multiple times, multiple versions of TWRP. was trying to follow this youtube vid ((HD) Samsung Galaxy SIII (S3) Touchwiz for HTC One X - Cursed4Eva)
I only got to install the gapps file from the vid, then it failed to flash anything else.
**tampered**
**unlocked**
Grab version 2.3.3.0. It works just fine for me. Also when you get into recovery you need to flash the ROM and then flash the boot image.
Also if you can, open up fast boot and type "fastboot OEM getvars" and paste the results. It could be getvar if the previous does not work.
Sent from my Carbon-ize Evita using xda-developers app
wtf
Herc08 said:
Grab version 2.3.3.0. It works just fine for me. Also when you get into recovery you need to flash the ROM and then flash the boot image.
Also if you can, open up fast boot and type "fastboot OEM getvars" and paste the results. It could be getvar if the previous does not work.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Fastboot just displays the menu when I type that... 2048
now it says info[ERR] command error !!!
now that I see it... that tutorial I followed was for endevor.. does that mean I am fcked?
2.3 = failed
joeytortorici said:
Fastboot just displays the menu when I type that... 2048
now it says info[ERR] command error !!!
now that I see it... that tutorial I followed was for endevor.. does that mean I am fcked?
Click to expand...
Click to collapse
download twrp 2.3.3.1 or under.
Fastboot flash recovery nameofrecoverzip.zip
fastboot erase cache
Boot to recovery flash roms for evita, extract the boot.img from the rom and flash that. fastboot flash boot boot.img
Good luck.
been there.
exad said:
download twrp 2.3.3.1 or under.
Fastboot flash recovery nameofrecoverzip.zip
fastboot erase cache
Boot to recovery flash roms for evita, extract the boot.img from the rom and flash that. fastboot flash boot boot.img
Good luck.
Click to expand...
Click to collapse
What is a rom that I can use? confirmed for vita.
I can't even get into recovery.
joeytortorici said:
What is a rom that I can use? confirmed for vita.
I can't even get into recovery.
Click to expand...
Click to collapse
omg, get an iphone.
Any rom in the AT&T one xl sections. Evita is the phone we have, endeavor is the quad core one x, cross flashing has a high chance of bricking your device. Have you done any reading before risking your expensive piece of equipment?
...
exad said:
omg, get an iphone.
Any rom in the AT&T one xl sections. Evita is the phone we have, endeavor is the quad core one x, cross flashing has a high chance of bricking your device. Have you done any reading before risking your expensive piece of equipment?
Click to expand...
Click to collapse
Dude, I'm not an idiot. I am pretty tech savy. especially with linux. But i dont know what I did here... if I can get into hboot does that mean it's not bricked?
joeytortorici said:
Dude, I'm not an idiot. I am pretty tech savy. especially with linux. But i dont know what I did here... if I can get into hboot does that mean it's not bricked?
Click to expand...
Click to collapse
If you're familiar with linux, consider the stickies in this forum man pages and READ.
If your phone can make it to hboot, it's not bricked.
exad said:
If you're familiar with linux, consider the stickies in this forum man pages and READ.
If your phone can make it to hboot, it's not bricked.
Click to expand...
Click to collapse
. I HAVE READ. I joined this forum to get help. My situation is unique. I have tried everything. I just can not boot into recovery or normal os. kind of a bid deal.
I cant even use fastboot oem getvar
I get an error.
I disagree.
Download recovery check md5
Fastboot flash recovery recovery.img
Fastboot erase cache
Make sure the recovery you're downloading is for the right phone too. One xl aka Evita.
Sent from my One X using xda app-developers app
sdfsdfsdfsd
exad said:
I disagree.
Download recovery check md5
Fastboot flash recovery recovery.img
Fastboot erase cache
Make sure the recovery you're downloading is for the right phone too. One xl aka Evita.
Sent from my One X using xda app-developers app[/QUOTE
Literally done that 10 times now
Click to expand...
Click to collapse
joeytortorici said:
. I HAVE READ. I joined this forum to get help. My situation is unique. I have tried everything. I just can not boot into recovery or normal os. kind of a bid deal.
I cant even use fastboot oem getvar
I get an error.
Click to expand...
Click to collapse
First of all you should have done more research before flashing stuff on your phone. Youre lucky your phone is still alive after flashing that international rom buddy.
Second the command fastboot oem getvar is incomplete. THats why you are getting the error. Getvar must be followed by something like fastboot oem getvar cid.
So one more time.
First make sure you have plenty of battery
1 Boot into hboot.
2Select fastboot and press the power button.
3 Open fastboot in command prompt and and type "fastboot devices"
4 If it shows a serial number it is recognizing your phone. If not try different cables and ports
5 IF recognized type "fastboot flash recovery ( navigate back to your fastboot folder and drag the recovery.img into the command window. The recovery.img MUST be in the same folder as the fastboot program!!)"
6 Press enter.
7 Type "fastboot erase cache"
8 Type "fastboot reboot recovery"
If this doesn't work you have another problem. I would suggest running a ruu if your're not super cid. To check super cid boot back into fastboot mode and type "fastboot oem getvar cid" If it shows "11111111" you have super cid and cant run a ruu. If not you can run a ruu.
If the steps above did work and your're now in recovery. Then.
1 Wipe everything. Cache/dalvik cache/system/android secure/ and sdcard.
2 Mount sdcard and transfer your rom to your sd card. MAKE SURE THE ROM IS FOR THE DUAL CORE ONE XL EVITA model. For now just stick with a sense rom. If you want a suggestion I suggest you use this one for now. http://forum.xda-developers.com/showthread.php?t=2181891
3 Once transfered. Safetly unmount sdcard and flash the rom.
4 Select reboot bootloader in recovery.
5 Once in hboot select bootloader.
6 Open the rom you just flashed and copy the boot.img that is in the root of the zip to the folder where you have fastboot.
7 Type "fastboot devices" to see if the pc recognizes the phone.
8 If you see a serial number the pc recognizes your phone.
9 Type "fastboot flash boot (go back to explorer and drag the boot.img from the fastboot folder to the command window."
10 Hit enter
11 Press the vol down button and navigate to power off.
12 Hit the power button.
13 Once phone is completely off press and hold the power button till the phone comes on.
14 If it still boot loops a ruu is your only option.
fmlll
Installed HTC Sync, RUU up and running. Thanks guys. Sorry for so noob. nearly trolling.
Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app
Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?
Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app
Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.
And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app
beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5
OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)
One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Good catch.
Sent from my Nexus 5 using xda app-developers app
samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app