I am trying to recover my nexus 7 2013 wifi by sideloading a factory image.
When I go into the recovery screen, and try a factory reset I get failed to mount errors
then if I use the adb devices command it does not see any devices.
If I select the apply update from adb in the recovery menu, and run adb devices again, I get my tablet number sideload
then trying to use adb sideload filename.zip it gives me with same failed to mount errors....
Any thoughts on next steps? I appreciate your help.
Related
I can't seem to get the custom recover working on my eris. I followed the "adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
4. Close the command prompt and turn off you phone."
to the tee and everything seemed to work.I didnt recieve any error msg on the cmd console but when I boot up holding the Vol+ and power I get and Android under a ! in a triangle and a message that says "E:Can't open /cache/recovery/command then I only get 4 options and none of them are to flash a rom so I always reboot system. I really want to put a rom on here but I have no idea what went wrong. Im sorry if this is a redundant post. I combed a hundred of them and couldnt find anything like this. Thank you for any help in advance.
Oh and before I forget I tried the adb fastboot bootloader version as well. Everytime I do it it sits in the command console stating "waiting for device". Im plugged in so I dont understand what Im doing wrong.
Curious to know... are you using windows or mac? have you tried:
adb shell reboot recovery
to see if that does anything?
Maybe you have a different version of the recovery saved than I do, but mine is named "recovery-RA-eris-v1.6.2.img"...maybe you just had an input error somewhere along the line? forgot a capital letter or something? I had the same error myself and following the directions I got the recovery image back
Im running windows 7 and I have both recovery-RA-eris-v1.6.2.img and the recovery-RA-eris.img. I have been using the v1.6.2 and I just modify the command to look like this "adb push recovery-ra-eris-v1.6.2.img /sdcard" How would I use adb shell reboot recovery would I just sub that in place of something? kinda getting discouraged because I have tried this 10x now. I have checked and the usb debugging is on and I do have the eris 2.1 root and not the leak. I wonder is there any way I can flash this with something from the droid mkt place like SUFBS? Or maybe change a rom's name to look like an update zip?Just looking for ways to make this work Im so jealous of everyone that has got it to work.
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Dachix said:
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Click to expand...
Click to collapse
when hes saying fastboot will be highlighted in red he's referring to booting your phone into the standard recovery mode (when power is off) hold volume up and power.
Walking Taco seriously love that name. The only options I get when I hold down vol+ and pwr is 1. reboot system now 2. apply sdcard update 3. Wipe Data/ factory reset 4. Wipe cache partition and all are in purple and at the bottom on the phones screen is "E:Can't open/cache/recovery/command"
The website fuzz4net says to:
WINDOWS USERS
From your tools directory in the sdk do the following command
adb fastboot bootloader
You will have FASTBOOT highlighted in red like it is here
Now on your computer do the following
Fastboot flash recovery recovery-RA-eris-v1.6.2.img
Ok after that completes pull the battery then power back up with Vol Up + Power to enter recovery
But when I get done ...after the last step the cmd.exe window states <waiting for device> any ideas? Thanks for helping too. Leave it to me to hit a snare
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Dachix said:
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Click to expand...
Click to collapse
I honestly don't know man, I would factory wipe it and try and start from the beginning. I followed the fuzz's instructions and was rooted in less than a half hour. Sorry brother.
Thanks!
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Dachix said:
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Click to expand...
Click to collapse
Awesome news! Have fun with your rooted phone!
Hi Guys.
I don't know if this is the right forum, please tell me if so.
I think that I've screwed up bigtime when i tired to upgrade my recovery image. Here is what happende.
I have rooted my Hero a long time ago, so what i did was trying to follow this guide for installing the latest recovery image: http://forum.xda-developers.com/showthread.php?t=645253
when i tired to flash the recovery image using this command: flash_image recovery /sdcard/recovery.img. I was using Terminal Emulator.
What happened was i got a lot of error messages saying that the phone was out of memory. This resulted in that i couldn't get acces to the recovery menu when rebooting my phone and that i cant access my phone rom.
I then tired to flash the recovery image using the installation guide of this thread: http://forum.xda-developers.com/showthread.php?t=561124
The thing is that i can see that the phone is mounted through the "fastboot devices" commando
When i try to flash the recovery image using fastboot i get this error message:
C:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
finished. total time: 0.001s
HELP! What can i do? Is my hero 'saveable or is it bricked?
//Mads
First of all its not bricked don't worry. Do you still have old recovery of Amon_Ra or not ? If have than put latest version of Amon_Ra recovery into your sdcard & reboot your phone into old recovery of Amon_Ra Than just follow these commands
Code:
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
when its done just type adb reboot . your phone will reboot
Hope it helps
Hi, it's good to hear. I think that my old recovery mode was screwed up during the attempt to upgrade. because if i tries to boot into it it just stops at the HERO bootscreen and goes no futher. If i just try to boot normally it goes to a black screen and then nothing else happens. Tried to let it boot for 30 min without anything happening.
The only thing i can access is fastboot.
when i try adb shell it says the following:"
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
you need to update your drivers that means you are not having latest drivers .. there was a thread i guess download drivers & check how to set up correct adb drivers on windows .. & by the way do you have installed HTC Sync ? make sure you have installed HTC Sync because it finds all htc drivers i guess than try
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Thx for the help, but that didn't work either.
I found this guide http://forum.xda-developers.com/showthread.php?t=714519 which did the work. So now i'm back at 1.5 for a little while, just need to root right away The good thing is that my phone is working
Thx for the help.
Glad to hear it Men .. Well come abroad
Well, I've used the RootZenFone 1.4.5 version apk method and it worked out for me... problem is, by modding the system I am now getting a boot loop on the main splash and have no adb access. Does anyone know how to force a manual sd update using the downloaded firmware packages and a micro sd card?
My Recovery is stock, so is the Droidboot (fastboot) image, though I cannot get anything through the adb and fastboot commands.
The only time I get something is when i get it into recovery and enable the sideload - pushing a file using the adb sideload command results in a status 0 error / signature verification failed
I have 32GB WIFI, Nexus 9 bought from Amazon which unfortunately has got stuck in boot loop after updating to 5.0.2 (LRX22L) released on air . My device is locked and it doesn't give permission to use "fastboot oem unlock" command thus I can't flash factory image because it says device is locked. I've tried Factory reset from fastboot mode and also from Recovery menu (wipe cache partition and wipe data/factory reset) and it still has the problem. That's worthy to note that PC recognizes device with "fastboot devices" command but it doesn't recognize using command "adb devices".
my PC's OS is 64bit windows 8.1
Then I tried using "Apply update from ADB" in recovery menu and sideload which gave me E: footer is wrong and signature is unspecified but in this mode command window in platform-tools path recognizes device as "adb device" command used.
The other thing I tried was unlocking the device using adb shell (and so on) and it says :closed
I'd be grateful if you folks, helped me with your solutions.
npa2194 said:
I have 32GB WIFI, Nexus 9 bought from Amazon which unfortunately has got stuck in boot loop after updating to 5.0.2 (LRX22L) released on air . My device is locked and it doesn't give permission to use "fastboot oem unlock" command thus I can't flash factory image because it says device is locked. I've tried Factory reset from fastboot mode and also from Recovery menu (wipe cache partition and wipe data/factory reset) and it still has the problem. That's worthy to note that PC recognizes device with "fastboot devices" command but it doesn't recognize using command "adb devices".
my PC's OS is 64bit windows 8.1
Then I tried using "Apply update from ADB" in recovery menu and sideload which gave me E: footer is wrong and signature is unspecified but in this mode command window in platform-tools path recognizes device as "adb device" command used.
The other thing I tried was unlocking the device using adb shell (and so on) and it says :closed
I'd be grateful if you folks, helped me with your solutions.
Click to expand...
Click to collapse
You only have one solution: return it to Amazon for replacement.
cam30era said:
You only have one solution: return it to Amazon for replacement.
Click to expand...
Click to collapse
You mean there is no other way for rooting or unlocking Nexus9 ? any program, application , command etc?
npa2194 said:
You mean there is no other way for rooting or unlocking Nexus9 ? any program, application , command etc?
Click to expand...
Click to collapse
Correct. No way if your bootloader is locked.
Hi there!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me...