Hi everybody!
I get from Google the factory image hammerhead-lmy47d-factory-6c1ad81e.tgz for my nexus 5
In downloaded two times (and verify MD5) on two different computers.
To perform a clean upgrade manually.
I following the instructions below:
- Unzip factory image file and copy all neccesary .img files on platform-tools on windows directory
- Turn off the phone and enter to bootloader mode and running the following instructions:
fastboot flash bootloader bootloader.img
[succesful]
fastboot reboot-bootloader
[succesful]
fastboot flash radio radio.img
[succesful]
fastboot reboot-bootloader
[succesful]
fastboot flash system system.img
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
is pending
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
On the same Nexus 5 I test and performed the same steps to flash 5.0.1 version (hammerhead-lrx22c-factory-0f9eda1b.tgz) and have no problem, everything works fine
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
[all succesful]
The only way they could make the upgrade to 5.1 was using the OTA file:
e16268c5a3df75a65054ab258d7d615288b7e3b4.signed-hammerhead-ota-LMY47D-from-LRX22C-radio-restricted.zip
Using the following command in ADB mode:
adb sideload e16268c5a3df75a65054ab258d7d615288b7e3b4.signed-hammerhead-ota-LMY47D-from-LRX22C-radio-restricted.zip
I was left with the question of:
Why it could not flash the system.img file?
What does it mean error: cannot load 'system.img' in this case?
And how to fix it?
I need your support guys, thanks in advanced!
This may be daft, but you did have it in the same folder as the radio and bootloader img's as when extracting, the rest are in the next folder along
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
All files are in the same folder.
Ben36 said:
This may be daft, but you did have it in the same folder as the radio and bootloader img's as when extracting, the rest are in the next folder along
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
thanks, this helped
Thank you bmita. I had exactly the same problem as you. I followed your steps to revert back to 5.0.1 then used ADB process to upgrade to 5.1
I was totally stuck and thanks to you, I could find a solution.
This doesn't make any sense. I (and of course, many others) was able to flash 5.1 factory images, no problem.
Do you have the latest fastboot.exe?
Sent from my Nexus 9 using XDA Free mobile app
Anything that can go wrong, will go wrong. This time It happened to me. If that error had not occurred, then I would not give the job of writing this thread... :good:
beekay201 said:
This doesn't make any sense. I (and of course, many others) was able to flash 5.1 factory images, no problem.
Click to expand...
Click to collapse
I forget to mention, but before doing an update run the SDK Manager.exe program and perform the upgrade to support the new version of Android. Can you tell me please how I can check the version of fastboot.exe file?
jd1639 said:
Do you have the latest fastboot.exe?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
bmita said:
I forget to mention, but before doing an update run the SDK Manager.exe program and perform the upgrade to support the new version of Android. Can you tell me please how I can check the version of fastboot.exe file?
Click to expand...
Click to collapse
fastboot version
But Google 15 second adb install xda. That'll put the latest version of fastboot and adb on your pc.
Sent from my Nexus 5 using XDA Free mobile app
Previously try running fastboot version command, but only get the help screen display of fastboot.
adb version display: Android Debug Bridge version 1.0.32
jd1639 said:
fastboot version
But Google 15 second adb install xda. That'll put the latest version of fastboot and adb on your pc.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
bmita said:
Previously try running fastboot version command, but only get the help screen display of fastboot.
adb version display: Android Debug Bridge version 1.0.32
Click to expand...
Click to collapse
Looks like you have the latest.
Sent from my Nexus 9 using XDA Free mobile app
Yep.
On SDK Platforms Release Notes site
Android 5.1
Dependencies:
Android SDK Platform-tools r22 or higher is required. I have Rev. 22
Android SDK Tools 23.0.5 or higher is required. I have Rev. 24.1.2
jd1639 said:
Looks like you have the latest.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
Did you test on another computer?
I was in exactly the same situation as you and I tested on another computer with exactly the same cable and the fastboot flash system system.img worked without any problem.
Have look at the comments from Sp0KI in this thread : http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
you will see he also had the problem and also solved it by switching computer.
I still don't understand why it is so (memory or driver problem?) but it solved my problem.
Thanks for the info, I did the following:
I use the new hammerhead-lmy47i-factory-df127988.tgz on another machine with minimal_adb_fastboot_v1.2_setup.exe (adb version 1.0.32) and clean upgrade works fine.
I do not understand what could have happened...
Thises said:
Hello,
Did you test on another computer?
I was in exactly the same situation as you and I tested on another computer with exactly the same cable and the fastboot flash system system.img worked without any problem.
Have look at the comments from Sp0KI in this thread : http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
you will see he also had the problem and also solved it by switching computer.
I still don't understand why it is so (memory or driver problem?) but it solved my problem.
Click to expand...
Click to collapse
after googling for ages i think i finally have found the solution:
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
Ntress said:
after googling for ages i think i finally have found the solution:
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
Click to expand...
Click to collapse
Did this work for you? Usually when you get that error it's because you don't have the latest fastboot.exe. I'd be interested if this works. Thanks
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Did this work for you? Usually when you get that error it's because you don't have the latest fastboot.exe. I'd be interested if this works. Thanks
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, this method is worked for me.
The method you stated is wrong, i was using Wugfresh toolkit and then also downloaded the latest fastboot files and nothing solved it until i saw that link.
Ntress said:
Yes, this method is worked for me.
The method you stated is wrong, i was using Wugfresh toolkit and then also downloaded the latest fastboot files and nothing solved it until i saw that link.
Click to expand...
Click to collapse
Hey !
I got the same problem with Nexus 5 and the 5.1.1 factory image ... tried different computers, cables ... tried the mfastboot and got this:
target max-download-size: 1024MB
load_file: could not allocate 1046266608 bytes
error: cannot load 'system.img': Not enough space
Could someone help me ?
neuraman said:
Hey !
I got the same problem with Nexus 5 and the 5.1.1 factory image ... tried different computers, cables ... tried the mfastboot and got this:
target max-download-size: 1024MB
load_file: could not allocate 1046266608 bytes
error: cannot load 'system.img': Not enough space
Could someone help me ?
Click to expand...
Click to collapse
are you trying with a USB 3.0 port, my laptop has all USB 3.0 ports, and i get this error no matter what, so i flash on my friends laptop with USB 2.0 port and it works fine. try with USB 2.0 port.
madarchod said:
are you trying with a USB 3.0 port, my laptop has all USB 3.0 ports, and i get this error no matter what, so i flash on my friends laptop with USB 2.0 port and it works fine. try with USB 2.0 port.
Click to expand...
Click to collapse
At the beginning I was trying a USB 3.0 port ... but I tried with a 2.0 just after on the same computer and with my old laptop with the same results.
I can't flash my current system image again ... it's not the new system.img ... I guess ...
---------- Post added at 03:17 PM ---------- Previous post was at 02:25 PM ----------
neuraman said:
At the beginning I was trying a USB 3.0 port ... but I tried with a 2.0 just after on the same computer and with my old laptop with the same results.
I can't flash my current system image again ... it's not the new system.img ... I guess ...
Click to expand...
Click to collapse
Ok ... think I solved with this command:
Code:
fastboot flash -S 512M system system.img
source: Original post
It seems it divides the image in two and writes them in two phases ... if it works I would guess is some kind of fastboot or Windows limit ... even though I tried the "limitless" mfastboot with the same results.
EDIT: ok it worked ! 5.1.1 up and running !
Related
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Also tried in Ubuntu still no luck >_<
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
bige914 said:
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I am using a Asus Laptop. Thanks for the response!
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
got the same issue guys
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
We are all stuck with this unless we send it to asus for RMA
Sent from my VS840 4G using xda premium
SpyFi said:
Also tried in Ubuntu still no luck >_<
Click to expand...
Click to collapse
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
the problem is not the computer itself, the real problem is that the tablet doesn't get in fastboot mode...
Thank you for the update.
SpyFi said:
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Click to expand...
Click to collapse
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
matt95 said:
got the same issue guys
Click to expand...
Click to collapse
partypage said:
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
Click to expand...
Click to collapse
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
Try this:
-use unlock tool
-boot tablet into USB MODE
(it will say fastboot mode,waiting)
-using the steps,copying over the fastboot files to one folder, with TWRP as the recovery, run fastboot command.
-done successfully,you be good
Click to expand...
Click to collapse
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
I decided to automate the process of entering commands. Post
philos64 said:
Try this:
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
Click to expand...
Click to collapse
thank you, i'll try this out tomorrow! :good:
no way, i can't get it to fastboot damn it
---------- Post added at 11:45 PM ---------- Previous post was at 11:16 PM ----------
ok i solved the problem just now...
1-reboot the tablet in bootloader while connected to usb
2-use vol down to navigate to the usb mode and then vol up
3-the tablet won't show nothing but actually it is connected
4-proceed to any fastboot command
hope this helps
I had this issue when I first started flashing stuff (although I was flashing CWM not TWRP)
In my experience, if you don't see anything listed in fastboot devices, it doesn't matter because it still flashes.
Just try using the flash command (fastboot -i 0x0b05 flash blah blah blah.blah) and see if it works.
You -should- be able to see your device in "adb devices", and that's really what matters.
Also, what matt95 said is exactly what I do. Whether it shows anything or not, I just flash my stuff. Works fine, but I also don't use fastboot alot because with the new changes to the bootloader, one can flash stock through CWM now without having to fastboot flash it.
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
jm700wx said:
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
Click to expand...
Click to collapse
my solution above didn't help?
matt95 said:
my solution above didn't help?
Click to expand...
Click to collapse
I'm in the same wagon as all you guys, I just tried that and I can't get into fastboot still. Still waiting for device
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
I'm sorted now, I didn't realise that we needed a different command
I was using
Code:
fastboot flash recovery recovery-jb-touch.img
instead of the correct method of using
Code:
fastboot -i 0x0B05 flash recovery recovery-jb-touch.img
This worked perfectly
it's same as this:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse
Having an issue flashing a custom recovery via fastboot. Everything is set up properly, fastboot commands work, but it keeps telling me that it cant open the recovery.img. Here is the error I am getting:
Daniels-MacBook-Pro:~ danielmasterson$ fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
error: cannot open 'openrecovery-twrp-2.6.3.2-hammerhead.img'
I am at a loss. I have had this set up this way since the Galaxy Nexus and it's never not worked. Any ideas?
if it's showing up when you search for fastboot devices, it may be the file. have you tried re-downloading it, renaming it, or even grabbing the 6.0.4.4 cwm img and flashing that? i'm curious.
xBeerdroiDx said:
if it's showing up when you search for fastboot devices, it may be the file. have you tried re-downloading it, renaming it, or even grabbing the 6.0.4.4 cwm img and flashing that? i'm curious.
Click to expand...
Click to collapse
Yes, I've redownloaded, renamed, tried CWM, etc. I'm totally buffaloed...
Sent from my Nexus 5 using Tapatalk
Hell, I unlocked the bootloader via fastboot so...
Sent from my Nexus 5 using Tapatalk
what is the ls -l of the .img file? Maybe a permission issue?
Typically I always rename my recovery images to 'recovery.img' thats the only thing I do differently than you on my mac. Second, where are you storing your recovery file before you flash it? External HDD? Check the permissions on the file/ the source drive.
also, did you update your SDK/adb?
Thanks for the replies guys. I'm still not sure what was going on, I nuked my whole ADB setup and started over again and all is well. Liking the N5 so far, it's really nice stock. May not eben jack with it too much, but I know I'll get the itch sooner or later...
A couple of things to try...
1) Make sure the recovery image is in the same directory where you installed fastboot and you are executing the terminal commands from that directory
2) Try adding ./ in front of the command so it would be ./fastboot flash recovery nameofrecovery.img
Sent from my Nexus 5 using xda app-developers app
chef_christoph said:
A couple of things to try...
1) Make sure the recovery image is in the same directory where you installed fastboot and you are executing the terminal commands from that directory
2) Try adding ./ in front of the command so it would be ./fastboot flash recovery nameofrecovery.img
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
0dBu said:
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
Click to expand...
Click to collapse
I would think then you didn't update to the latest SDK/adb for N5.
0dBu said:
I got it worked out brother. What was strange though, is that I could fastboot flash a recovery on my Galaxy Nexus, but it wouldn't work on the N5, so I just re-did the setup and all is well...
Click to expand...
Click to collapse
Sorry, missed your post while I was typing mine. Glad to hear you got it working. Cheers!
Sent from my Nexus 5 using xda app-developers app
I lost BMM after I flashed PA nano gapps and JBX (which I read later that they don't go along well). So what?? FXZ!! But after I tried to connect the phone in fastboot and opened, the device wasn't recognized on my PC by RSDlite. My PC config is unchanged and I tried both USB 2.0 and 3.0.
So, I downloaded latest drivers and installed after uninstalling previous ones and also reinstalled RSD a number of times and countless restarts! Still NOT recognized! I'm so frustrated right now!!
If anyone did face a similar issue, plz help me get this sorted!! This has never happened before
Loop
shubham1120 said:
I lost BMM after I flashed PA nano gapps and JBX (which I read later that they don't go along well). So what?? FXZ!! But after I tried to connect the phone in fastboot and opened, the device wasn't recognized on my PC by RSDlite. My PC config is unchanged and I tried both USB 2.0 and 3.0.
So, I downloaded latest drivers and installed after uninstalling previous ones and also reinstalled RSD a number of times and countless restarts! Still NOT recognized! I'm so frustrated right now!!
If anyone did face a similar issue, plz help me get this sorted!! This has never happened before
Click to expand...
Click to collapse
Strange..i had same issue about a month back..device shows "connected" in fastboot but doesn't show up on rsdlite..soon my windows crashed (virus problem) and since i was fed up with Windows i installed Linux Mint n set up adb and fastboot and manually flashed in Terminal using fastboot commands..
You can flash using moto fastboot in Windows too manually..just search up xda..or using a script that alteredlikeness made to flash without rsdlite..its in the Atrix 2 icd AT N T firmware thread..post number 108
devilhunter47 said:
Loop
Strange..i had same issue about a month back..device shows "connected" in fastboot but doesn't show up on rsdlite..soon my windows crashed (virus problem) and since i was fed up with Windows i installed Linux Mint n set up adb and fastboot and manually flashed in Terminal using fastboot commands..
You can flash using moto fastboot in Windows too manually..just search up xda..or using a script that alteredlikeness made to flash without rsdlite..its in the Atrix 2 icd AT N T firmware thread..post number 108
Click to expand...
Click to collapse
Thanks for your reply but that script is a no go. I tried exactly what was mentioned in the steps but when it reboots in recovery, installs and gets softbricked, stuck at boot logo. I think I'm gonna try my bro's PC. I'll post it here.
shubham1120 said:
Thanks for your reply but that script is a no go. I tried exactly what was mentioned in the steps but when it reboots in recovery, installs and gets softbricked, stuck at boot logo. I think I'm gonna try my bro's PC. I'll post it here.
Click to expand...
Click to collapse
Why don't you try manually then??
Open command window in fxz folder
Enter the following
moto-fastboot wipe userdata
moto-fastboot wipe cache
moto-fastboot flash system system.img
moto-fastboot reboot
devilhunter47 said:
Why don't you try manually then??
Open command window in fxz folder
Enter the following
moto-fastboot wipe userdata
moto-fastboot wipe cache
moto-fastboot flash system system.img
moto-fastboot reboot
Click to expand...
Click to collapse
Only flashing system would solve the problem?? Because in the process of using the script, the recovery was wiped too.phone is stuck at boot logo! . Can you tell me exact set of commands for jb leak 3 . Equivalent to fxzing? I'm in a worse position than before coz now, I can't even charge my phone
Thanks
Edit- I read a bit and found that there's an incompatibility with windows 8 let alone 64 bit os. I was having both windows 8 and 64 bit. I found my spare windows 7 32 bit cd and flashed the rom! Now it's booting!!
shubham1120 said:
Only flashing system would solve the problem?? Because in the process of using the script, the recovery was wiped too.phone is stuck at boot logo! . Can you tell me exact set of commands for jb leak 3 . Equivalent to fxzing? I'm in a worse position than before coz now, I can't even charge my phone
Thanks
Edit- I read a bit and found that there's an incompatibility with windows 8 let alone 64 bit os. I was having both windows 8 and 64 bit. I found my spare windows 7 32 bit cd and flashed the rom! Now it's booting!!
Click to expand...
Click to collapse
Glad you sorted it out!!..i have tried these commands when i got stuck in bootlogo..it works..our recovery.img won't be wiped..it will work for any fxz provided the name of the .img files are the same..
Yeah you're right! I retried using altered script, after disabling the anti virus and it worked!
Sent from my MB865 using XDA Premium 4 mobile app
I have win8 64 bit and I can fxz with it !!
sameerm02 said:
I have win8 64 bit and I can fxz with it !!
Click to expand...
Click to collapse
Yeah man that's what stumps me.! It USED to work earlier win 8.1 64 bit and unchanged config; and then out of nowhere, it decided not to work.. ?
My only option is reinstalling win 8.1 which is not worth it considering I don't use jb leak unless I brick the device (only use banks gapps) lol
Sent from my MB865 using XDA Premium 4 mobile app
EDIT: made a typo the first few tries!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
please see post #2
i was making a mistake. the correct command line is
adb devices
adb reboot bootloader
adb sideload update.zip
in this last command line it says:
loading : 'update.zip'
error: device not found
what now? when i type adb devices it sees my phone before rebooting into bootloader. after i reboot into bootloader and i type adb devices it does not give me any result
cesar.maranhao said:
i was making a mistake. the correct command line is
adb devices
adb reboot bootloader
adb sideload update.zip
in this last command line it says:
loading : 'update.zip'
error: device not found
what now? when i type adb devices it sees my phone before rebooting into bootloader. after i reboot into bootloader and i type adb devices it does not give me any result
Click to expand...
Click to collapse
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
thanks, I see I am doing it all wrong..
i have found this guide
http://forum.xda-developers.com/showthread.php?t=2559200
when i get to the
adb usb
it also says device not found despite the deamon starting successfully on port 5037... i will need help please
cesar.maranhao said:
thanks, I see I am doing it all wrong..
i have found this guide
http://forum.xda-developers.com/showthread.php?t=2559200
when i get to the
adb usb
it also says device not found despite the deamon starting successfully on port 5037... i will need help please
Click to expand...
Click to collapse
First off, you need the stock recovery, not twrp or cwm to flash the update.zip. If you don't have the stock recovery you'll need to flash it in fastboot with the recovery.img from 5.0. Are you on the stock recovery? Also, are you rooted?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
First off, you need the stock recovery, not twrp or cwm to flash the update.zip. If you don't have the stock recovery you'll need to flash it in fastboot with the recovery.img from 5.0. Are you on the stock recovery? Also, are you rooted?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
yes, i am rooted with twrp custom recovery.
i tried to install the ota zip from the custom recovery. the ota file i downloaded and it failed. i tried all three options you see in this topic:
http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327
what should i do then?
1. Its adb reboot-bootloader to reboot into the bootloader.
Have to choose recovery from the bootloader, then press and hold power button then press volume up once to be able to choose adb sideload and press power. Once choosing this option from recovery then check adb devices. If it doesn't recognize your device then the USB drivers are not installed properly. Go to device manager on your PC to install the correct drivers. There are a few post already about this. Alternately you can use universal naked drivers. These work very well with Nexus devices.
2. Have to be completely stock to apply the OTA. Simply clicking unroot via supersu does not allow the update to apply.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
cesar.maranhao said:
yes, i am rooted with twrp custom recovery.
i tried to install the ota zip from the custom recovery. the ota file i downloaded and it failed. i tried all three options you see in this topic:
http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327
what should i do then?
Click to expand...
Click to collapse
First unroot using the full unroot option in supersu settings. Then you'll need to flash the system, recovery, and boot images from 5.0 with fastboot. Then you can sideload the update.zip in the stock recovery. If you've changed the radio you'll have to flash that from 5.0 too
It's a pita. The other option is to just flash in fastboot the radio, system, and boot images from 5.0.1 and forgo the ota.
Either option won't wipe data
Sent from my Nexus 9 using XDA Free mobile app
Jnewell05 said:
1. Its adb reboot-bootloader to reboot into the bootloader.
Have to choose recovery from the bootloader, then press and hold power button then press volume up once to be able to choose adb sideload and press power. Once choosing this option from recovery then check adb devices. If it doesn't recognize your device then the USB drivers are not installed properly. Go to device manager on your PC to install the correct drivers. There are a few post already about this. Alternately you can use universal naked drivers. These work very well with Nexus devices.
2. Have to be completely stock to apply the OTA. Simply clicking unroot via supersu does not allow the update to apply.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
jd1639 said:
First unroot using the full unroot option in supersu settings. Then you'll need to flash the system, recovery, and boot images from 5.0 with fastboot. Then you can sideload the update.zip in the stock recovery. If you've changed the radio you'll have to flash that from 5.0 too
It's a pita. The other option is to just flash in fastboot the radio, system, and boot images from 5.0.1 and forgo the ota.
Either option won't wipe data
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I am so confused.. when i bought my nexus 5 i upgraded kitkat several times by flashing a downloaded OTA from xda forums inside custom recovery. i just flashed the update and flashed the supersu afterwards to keep root.
i do not understand what is happening now, i never done such steps before.
were those kitkat ota's modified by xda members to help not so knowledgeable users like me to update?
this is what I have been using:
EDIT:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
Just noticed thisis only for 4.4.4 OTA's and below only.
cesar.maranhao said:
I am so confused.. when i bought my nexus 5 i upgraded kitkat several times by flashing a downloaded OTA from xda forums inside custom recovery. i just flashed the update and flashed the supersu afterwards to keep root.
i do not understand what is happening now, i never done such steps before.
were those kitkat ota's modified by xda members to help not so knowledgeable users like me to update?
Click to expand...
Click to collapse
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
you missed my last edit while you were replying.
EDIT:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
Just noticed thisis only for 4.4.4 OTA's and below only.
Click to expand...
Click to collapse
it is more clear for me now. i used all those fastboot command line when i flashed 5.0.0, one line for each image.
i will do that for 5.0.1. thanks a lot mate for all the clarification.
one last question: will I lose any data/configurations by apllying this method?
cesar.maranhao said:
you missed my last edit while you were replying.
it is more clear for me now. i used all those fastboot command line when i flashed 5.0.0, one line for each image.
i will do that for 5.0.1. thanks a lot mate for all the clarification.
one last question: will I lose any data/configurations by apllying this method?
Click to expand...
Click to collapse
No data will be lost. Everything will still be there
Oh, you're custom recovery will be gone and you'll have to re-root but that's easy. If you have problems let me know.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
No data will be lost. Everything will still be there
Oh, you're custom recovery will be gone and you'll have to re-root but that's easy. If you have problems let me know.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nice! i suppose i need to flash the custom recovery and root again right?
cesar.maranhao said:
nice! i suppose i need to flash the custom recovery and root again right?
Click to expand...
Click to collapse
Yep, flash the twrp.img in fastboot, fastboot flash recovery twrp.img (I recommend twrp, if you have a problem with this step let me know. It may try to keep the stock recovery). Then flash supersu 2.4 in twrp
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Yep, flash the twrp.img in fastboot, fastboot flash recovery twrp.img (I recommend twrp, if you have a problem with this step let me know. It may try to keep the stock recovery). Then flash supersu 2.4 in twrp
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
will you stay online for a while? if I run into trouble you already know what is going on
cesar.maranhao said:
will you stay online for a while? if I run into trouble you already know what is going on
Click to expand...
Click to collapse
I'll be here
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'll be here
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
cesar.maranhao said:
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
Click to expand...
Click to collapse
Put SuperSU beta flashable zip on your sdcard then fastboot flash TWRP. Boot directly into recovery and flash SuperSU
cesar.maranhao said:
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
Click to expand...
Click to collapse
I thought that would be the problem. You'll want to boot twrp, flash supersu and the flash twrp
fastboot boot twrp.img
Then flash supersu in twrp
Then boot back into the bootloader and
fastboot flash recovery twrp.img
There are couple of scripts, one in /system and one in /system/bin that put the stock recovery back on. You could remove the scripts put I find this easier
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I thought that would be the problem. You'll want to boot twrp, flash supersu and the flash twrp
fastboot boot twrp.img
Then flash supersu in twrp
Then boot back into the bootloader and
fastboot flash recovery twrp.img
There are couple of scripts, one in /system and one in /system/bin that put the stock recovery back on. You could remove the scripts put I find this easier
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
rootSU said:
Put SuperSU beta flashable zip on your sdcard then fastboot flash TWRP. Boot directly into recovery and flash SuperSU
Click to expand...
Click to collapse
i am having problems in putting the supersu file into my nexus 5, it says the device has either stopped or has been disconnected.. this never happened before. i haveit setup as MTP. also tried ptp without success
Hi ppl. I need help bad! I accidentally erased my os. So when I try to flash a rom using the mi flash tool(which is amazing) it won't work because I have no operating system to enable USB debugging.so it says enable USB debugging but I can't. Any help would be appreciated TW RP installed unlock bootloader. Thanks in advance!!
just flash recovery rom using twrp then.
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
So twrp is flashed? Then yes try sideload. Also make sure your ADB is up to date as I've had that cause issues with large files and sideload before.
M.
dirtyrott3njb said:
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
Click to expand...
Click to collapse
Miflash doesn't need for usb debugging to flash rom I believe. It's all fastboot. If ur phone is not detected by pc, it means drivers.
It does indicate USB debuging not on. So yes it does . I've used it before to flash TWRP. The flash will also install the drivers before you use it so I can understand why it won't let me transfer anything from PC to phone when fastboot mode. It won't let me get past that stuff in this USB debugging is enabled. Frustrating brand new phone to only a couple weeks old.
Have you booted to twrp and format data (the one where you have to type "yes")?
Mi flash only required adb because it needs to run adb reboot fastboot. I'm in the States as well, PM me and maybe we can get this guy working over remote support. I haven't seen this issue myself, so I can't comment much.
Sent from my Mi MIX 2S using Tapatalk
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
dirtyrott3njb said:
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
Click to expand...
Click to collapse
Its all good. I'm about to pick up my kids from school, so let me head home, I'll PM you in a bit. We can use TeamViewer or something. If it comes down to it, I also have my work login to use for remote assist. You just need a semi up to date laptop or desktop computer.
Hopefully we can get this solved quickly. I'm unfortunately not in your immediate area, otherwise much easier hands on. The company I work for is down the street from your location however, I'm just a remote systems guy.
Sent from my Mi MIX 2S using Tapatalk
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
dirtyrott3njb said:
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
Click to expand...
Click to collapse
Tried to pm you but msg sent failed.
Only thing is for some reason I can't transfer anything for my PC to TW RP or my internal storage some reason just doesn't accept it and it's not my computer
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
sg01fc said:
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
Click to expand...
Click to collapse
The OP's issue was solved by just flashing TWRP, booting to it and sideloading the Stock ROM. I had the OP download the fastboot files as well, but we ended up not needing them.