Related
Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Is 'fastboot devices' detecting the phone?
Sent from my HTC Desire using XDA App
my phone detects the fastboot usb
and in the command line doesn't stand [waiting for device] like when the phone is not connected
edit:
ah i guess you mind the fastboot devices command
yeah there is one device HT072...6 fastboot
Now I also got another error here the Details:
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.002s
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
edit:
okay got it and flashed recovery v3.0.0.5 (i know not uptodate there is already 5.0.0.2 or sth =P)
looked up for the other error here and found a solution had to take another usb-port
but i still got the problem that i can not "install zip from sdcard" when i select it, i get a black screen with the icon of clockworkmod :S
try this http://forum.xda-developers.com/showthread.php?t=839621
you might have a PVT4 device which doesn't work with cwm
i already flashed my desire about 4times with clockworkmod
btw just checked its pvt1
but ill try alphaRev just give me a sec
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
NeroBoron said:
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
Click to expand...
Click to collapse
no prob, here to help
NeroBoron said:
Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Click to expand...
Click to collapse
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
mullamadd said:
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
Click to expand...
Click to collapse
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
bortak said:
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
Click to expand...
Click to collapse
First of all, thanks for your answare.
My S is ON, how to make him go OFF??
When i type in fastboot devices i see my device HT97....
so, my ges is that it recognise my device...
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
=JP said:
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Sory, i dont get it...downloaded apherev.iso but dont know how to use it?
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
WRson said:
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
Click to expand...
Click to collapse
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
I dont know what you have to do with a magic , sorry about that.
You may look a the magic forum if their is anything written about usbbrick ?
Ask in magic section, not in the one for desire.
Sent from dGB with Transparent XDA App
mullamadd said:
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
Click to expand...
Click to collapse
Magic ≠ Desire
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
dimitrisvel said:
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
Click to expand...
Click to collapse
try another recovery like RA Recover you can find it here:
http://forum.xda-developers.com/showthread.php?t=839621
I also got some problems with clockworkmod before, so i switched to RA and it works fine for me.
Well, I think I have a big problem with my Nexus phone, I will relate you what happened with it this morning:
I was using Winamp app, listening music and suddenly my phone went crazy and it turned off, after that, it was rebooting again by itself (the image do a little shake), i was waiting to put my pass but it kept rebooting once and over, I had to take out the battery to turn it off. Now that I'm trying to ressurect him via fastboot it throws me this message:
sending 'bootloader' (2038 KB)...
OKAY [ 0.228s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.43s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.004s
sending 'radio' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.640s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.641s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
-----------------------------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.706s
Press any key exit...
My phone was takju 4.1.1 and then I flashed 4.1.2 Stock factory image from google (takju), I did it this way:
Downloaded SDK Manager and installed these packages:
1.- Android SDK Tools
2.- Android SDK Platform-Tools
2.- Google USB Driver
I downloaded Galaxy Nexus ToolKit and installed drivers for Nexus Takju 4.1.1.
I downloaded Factory Image "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) ----> 4.1.2 (JZO54K).
I extracted factory image and put all files in the same folder as Platform Tools (android-sdk\platform-tools).
I used "fastboot devices" to check if my pc recognizes my phone and then I executed "flash-all".
When I first did it 2 days ago it worked and I had my phone updated to 4.1.2 but today i tried to do the same (Thinking this will fix it) and it shows me the error that I described above, now I don't know if my phone is bricked, neither if I can make anything to ressurect him from this, I need your help, guys! What can I do?
Thanks in advice!
Too many links sometimes means a bad connection. Try a different USB cable and/or port.
Even a PC reboot can sometimes help in my experience.
Sent from my Galaxy Nexus using xda premium
El Daddy said:
Too many links sometimes means a bad connection. Try a different USB cable and/or port.
Even a PC reboot can sometimes help in my experience.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just tried changing USB port and it didn't work. I don't have any other USB cable.
Still waiting for another suggestion.
Still needing a hand!
With GNex Toolkil i'm trying to:
1.- Push files into my phone to flash a rom via CWM but it doesn't let me. (I can go into Recovery Mode, that's why I wanna put a rom in the sdcard)
2.- Reboot phone to Android OS it worked only once but as soon as first screen appeared to unlock it the phone freezed and kept rebooting once and over.
3.- Flash stock factory image and it keeps throwing me the same error described above.
I let the phone rebooting once and over and sometimes it tries to upgrade something but as soon as it does the phone reboots again.
The image keeps moving weird.
Please, guys, I need your help.
You should not be using toolkits at this point. They are designed only for properly functioning phones.
As far as I know, "too many links" either indicates that there is a problem with the connection, or a problem with the hardware that is beyond end-user repair capability. Your phone needs to be fixed or replaced by Samsung.
Search for an odin rom and give it a shot
here try this for the GSM nexus
http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://forum.xda-developers.com/showthread.php?t=1760787
Also try a different USB port and a different computer...
A few of the "too many links" posts point out that at some point they're able to smell something burnt. At that point you are definitely toast
Bricked = Not turning on no matter what you do.
Bricked is a permanent condition with no recovery method.
You are not bricked, so please don't use that word to describe your situation.
I would recommend flashing via a different computer, and don't use the stupid toolkits.
Manually install the drivers and the android sdk, and use that to flash your device.
DynamicRam said:
Search for an odin rom and give it a shot
here try this for the GSM nexus
http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
I'm gonna try that, I'm downloading files.
cmstlist said:
Also try a different USB port and a different computer...
A few of the "too many links" posts point out that at some point they're able to smell something burnt. At that point you are definitely toast
Click to expand...
Click to collapse
I already did it, same with another pc or usb port.
GldRush98 said:
Bricked = Not turning on no matter what you do.
Bricked is a permanent condition with no recovery method.
You are not bricked, so please don't use that word to describe your situation.
I would recommend flashing via a different computer, and don't use the stupid toolkits.
Manually install the drivers and the android sdk, and use that to flash your device.
Click to expand...
Click to collapse
My first try was with no toolkits, I used flash-all file that makes everything without typing any command, I'm gonna try to unistall drivers and android sdk and install them back.
ernesuat that
LOL! Now i think I'm completely lost, I tried Odin (And I know it was an stupid thing) and it stock at NAND Write Start!! Now I can't even get to bootloader/recovery/download mode, I only see a Phone--Warning Icon--Pc on my Nexus screen. I tried flashing OMAP but nothing happened, same Phone--Warning Icon--Pc.
Thanks for your help, I'll be googling 'till i get tired.
Does your phone still have any warranty on it?
OMAP flash?
Beamed from my Grouper.
cmstlist said:
Does your phone still have any warranty on it?
Click to expand...
Click to collapse
No, it doesn't coz I bought it from Amazon and I'm out of US.
Mach3.2 said:
OMAP flash?
Beamed from my Grouper.
Click to expand...
Click to collapse
I tried OMAP flash, pull out battery, execute OMAP and connect the phone, put battery back and it only shows Phone--Warning Icon--Pc, I, I can't turn it into Download/Recovery/Bootloader mode.
I'm not really sure how odin works, maybe you can try it again?
I can feel your frustration but all these methods are tested and 100% working
if you can still get into odin mode try again and make sure to read all the steps and that the drivers are installed correctly if everything fails then i think it could be a hardware problem
so try
-Odin mode
-Omap flash
-USB Jig to get into odin mode
-Does your PC recognize the phone ??
Mach3.2 said:
I'm not really sure how odin works, maybe you can try it again?
Click to expand...
Click to collapse
DynamicRam said:
I can feel your frustration but all these methods are tested and 100% working
if you can still get into odin mode try again and make sure to read all the steps and that the drivers are installed correctly if everything fails then i think it could be a hardware problem
so try
-Odin mode
-Omap flash
-USB Jig to get into odin mode
-Does your PC recognize the phone ??
Click to expand...
Click to collapse
I can't go into Download Mode (Download and Odin are the same mode). I can't boot it into Bootloader Mode, I can't boot it into Recovery Mode. My pc recognizes the phone, I can't boot it into any mode, all I see as I said is Phone--Warning Icon--Pc.
Odin says added since the first time I plugged it, it still say it and port gets yellow (at Odin window), I try flashing .tar file and it stock in: bootloader.img and then NAND Write Start!!
vermillion66 said:
I tried Odin (And I know it was an stupid thing) and it stock at NAND Write Start!!
Click to expand...
Click to collapse
How long did you wait for it to complete?
Cilraaz said:
How long did you wait for it to complete?
Click to expand...
Click to collapse
30 minutes.
DynamicRam said:
Search for an odin rom and give it a shot
here try this for the GSM nexus
http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
As El Daddy and cmslist mentioned, the "too many links" error usually means a connection problem or hardware problem. Using Odin to flash something when there is either something wrong with the connection or something wrong with the hardware, is never a good idea, as it will corrupt your bootloader.
@OP, If your computer still recognizes your device, then Odin will still be able to flash it, but it still needs a "good" connection. What I would at this point is use OMAP_Flash (which will reflash your bootloader), reboot into fastboot mode, then uninstall whatever drivers you have, make sure your device is plugged int a USB port at the back of your PC, and install 1wayjonny's driver pack. Then proceed to flash each of the images.
efrant said:
As El Daddy and cmslist mentioned, the "too many links" error usually means a connection problem or hardware problem. Using Odin to flash something when there is either something wrong with the connection or something wrong with the hardware, is never a good idea, as it will corrupt your bootloader.
@OP, If your computer still recognizes your device, then Odin will still be able to flash it, but it still needs a "good" connection. What I would at this point is use OMAP_Flash (which will reflash your bootloader), reboot into fastboot mode, then uninstall whatever drivers you have, make sure your device is plugged int a USB port at the back of your PC, and install 1wayjonny's driver pack. Then proceed to flash each of the images.
Click to expand...
Click to collapse
Well, this is interesting, I downloaded a PIT file and flashed it via ODIN and now I can boot it into Bootloader Mode and Download Mode, but when I tried to use fastboot it get stock at the first command:
C:\Users\MyPc\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
And when I disconnect USB cable and restart the phone it is like dead (It doesn't turn on) so I have to use OMAP Flash and then I'm able to turn it on.
I uninstalled drivers as 1wayjonny's drivers pack post says, All the time I have always used USB ports from the back of my pc.
Bootlooping, adb not recognized, softbricked.
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Not sure what happened with regards to the update freeze, but we're past that point now. Your next attempt failed because the bootloader is locked, and since you now have no way to enable debugging, you may have no choice other than to try to revert to factory.
Before trying it, issue a: 'fastboot devices' command and make sure your device appears if not you may have to fix your drivers, make sure you get the right image for your device.
https://developers.google.com/android/nexus/images
EDIT: Oh crap, you don't have USB debugging enabled. Try the link anyway, fastboot should still work.
I will give it a go
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
rohanjoshi said:
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
Click to expand...
Click to collapse
Do you have a camera on the front and back? And is WiFi only? If yes, it is a FLO and you want this one.
Do you have a camera on the front and back? And has LTE and WiFi? If yes, it is a DEB and you want this one.
Based on your initial post, it looks like you have a FLO.
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
If you wanted the latest you'll want the 4.4.2...aka KitKat, that is what it was trying to update you to before this all happened. If you just want to go back to where you were, use the 4.3, but you will get prompted to update again.
Just keep in mind, runing flash-all as-is wipes everything, BUT, you can open the flash-all script in a text editor and remove the -w and it won't wipe userdata.
...also, if I may suggest, strongly, is if/when this works, and your device is backup, I suggest you unlock the bootloader first (since this wipes all data you might as well do it before you put anything on there), then go in and enable debugging. Now you can root, use adb if something happens again, etc.
rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
hey did u tried doing a factory reset from the stock recovery?
varuntis1993 said:
hey did u tried doing a factory reset from the stock recovery?
Click to expand...
Click to collapse
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
rohanjoshi said:
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
Click to expand...
Click to collapse
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
SOLVED
mdamaged said:
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
Click to expand...
Click to collapse
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
rohanjoshi said:
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
Click to expand...
Click to collapse
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
mdamaged said:
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
Click to expand...
Click to collapse
No, i understood that. I did not have the correct drivers installed and whenever I ran 'fastbook devices' nothing showed up.
I wiped all google drivers and re-installed one of the recommended packages and everything ran smoothly after that.
I was loading up my Nexus 7 (2013) with the Project L rom and ran into a problem. At the end of the install, I got an error that it could not erase the cache. I can boot into Bootloader but nothing else. It won't boot into recovery or launch the system OS. When I try to launch the system OS, I just get that updating animation that sits there for hours. Fastboot does recognize the device though, but when I try to do a fastboot erase of a partition, it just hangs. Anyone know how I can get out of this?
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
ritchea said:
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tried the process again. Whether I am trying to erase a partition, re-format a partition, or flash a partition, I get write errors. It is almost as if the rom is write-protected or something. It will copy partition images to whatever partition the bootloader is using, but just won't write them to the proper partitions.
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Check if your Android SDK is up to date
ritchea said:
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
ADB doesn't find the device any longer, although it did when I started the process. So I am left with using Fastboot. When I try to go into recovery, the screen goes black, then I get the Google logo, and it just sits there. When I try to launch into the system, I get they Andy lying down with the rotating geometric shape in his belly - forever. All that seems to work is the bootloader, and it's not really working. This is the kind of results that I am getting.
Code:
C:\Users\Daniel\Downloads\Nexus 7>fastboot devices
07b8be03 fastboot
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash recovery openrecovery-twrp-2.8.
0.1-flo.img
sending 'recovery' (7878 KB)...
OKAY [ 0.254s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.015s
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash bootloader bootloader-flo-flo-0
4.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.067s
C:\Users\Daniel\Downloads\Nexus 7>
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power]
Although I've found many instances of the write write failure you describe, no definitive answers. It does seem that Wug's Toolkit is worth a try. I read the following on his site. I realize it's about unlocking, but the point is you don't need adb to run commands from fastboot.
"WugFresh Mod Carey Parks • 4 days ago
You don't need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the "Unlock" button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use "Flash Stock + Unroot" with softbrick/bootloop mode to get your device back to normal. Cheers!"
Using the toolkit from fastboot without adb might help. (In fact, I didn't know this.) He further brought up these commands: You could also try to issue the commands (NRT advanced utilities > launch cmd prompt):
fastboot format system
fastboot format data
fastboot format cache
Of course this clears everything. But from this point, you could try the "Flash Stock+Unroot" step on the first page of the toolkit.
Have you tried to flash a totally different set of files (like the official 4.4.4 decompressed and placed into the fastboot folder)?
It is possible that your SD card has become corrupted. I'm pretty sure you can't issue any mount commands without adb so you can't set the card to write.
For the 15-20 minutes it will take to set up the toolkit and use it (it has to download files for your device, too). it may be worth the effort. Also, Wug is very good about helping. If you can provide him with a copy of what's happening (while using the toolkit), he will try to help. He really understands this stuff. If you're a "toolkit snob" (my term for those who deny usefulness of toolkits), then ignore that suggestion. You already understand how to use fastboot (which is why some say don't use toolkits). My personal experience is that the kit has helped me get out of bootloops a few times.
ritchea said:
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen.
Click to expand...
Click to collapse
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
djeaton said:
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
Click to expand...
Click to collapse
Oh, I understand on the Andy. OK. Have a great day.
Kinda weird-- http://forum.xda-developers.com/showthread.php?t=2917463different circumstances but same problem. No one responding there, either.
I don't know why this would work when wug's does not, but some claim it did http://forum.xda-developers.com/showthread.php?t=2381582. You would download, extract, click Dead_Nexus7.bat file and run from fastboot.
I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.
I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).
In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.
I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.
On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.
I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.
I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).
I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.
I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).
While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.
I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.
I do have one more interesting piece of information that I do not understand.
I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.
Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:
U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony
...
OKAY [ 2.969s]
finished. total time: 2.969s
After doing so, Emma STILL says it is locked.
Flash tool however allows me to flash it.
Any clue why Emma would say "locked" when I just finished unlocking it?
In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
ham5 said:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
Click to expand...
Click to collapse
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).
Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).
I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.
When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).
Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.
Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?
Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).
I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.
I think your really digging way to deep into this...
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
Click to expand...
Click to collapse
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
Click to expand...
Click to collapse
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
ham5 said:
I think your really digging way to deep into this...
Click to expand...
Click to collapse
I'd welcome a shorter, simpler path.
ham5 said:
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
Click to expand...
Click to collapse
Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.
Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.
ham5 said:
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
Click to expand...
Click to collapse
As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.
And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.
Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.
Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.
Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?
To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.
Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
ham5 said:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
Click to expand...
Click to collapse
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.
I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.
But I'm not clear whether it is a driver problem, since some fastboot commands work fine.
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
ham5 said:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
Click to expand...
Click to collapse
Yes, in fastboot mode I can do the getvar version. It says 0.5.
I had read the wiki; as mentioned that is why I was trying to flash boot.img.
As requested here is a fastboot session log:
Code:
U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s
U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s
As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.
Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.
Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.
The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.
It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).
There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.
I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.