Related
Hi, My DHD volume buttons no longer work and I've been reticent to send it off to get fixed as I can do with out the volume controls as opposed to being without a phone for 2-3 weeks.
However I used Rom manager to boot into CWR and was in the process of upgrading to revolution 5.2.4 from 5.1.8.
I ran the full wipe script then my fat fingers rebooted the phone rather than flashing the rom.
I now cant get back into CWR to flash the new rom. It just sits at the boot logo, obviously as all other partitions have been wiped.
Is there any other way I can force the phone to boot into CWR, perhaps using the sdk tools or similar?
I've tried adb devices, but it doesnt show up. Is there an external way to force the phone into flashing a new ROM or booting into CWRM ?
Thanks
Ron
I would like to help, first lets try using adb, command would be adb reboot recovery
Hi, thanks for the help.
As mentioned in OP. I have powered the phone on and have have already attempted this, but the device is not recognised by adb.
tools>adb reboot recovery
error: device not found
My question is how to get the device to be recognised if its simply sitting at the boot image?
R
Sorry I over looked that, it seems to me if adb (which is an sdk tool) won't recognize the device as being attached, i don't see any other sdk tool doing any different, also as far as I know there is no alternate method to scrolling through the boot loader that would allow you to choose recovery and flash a zip other then the volume keys , so it seems the solution is, to send the phone off, get the volume keys fixed, and then you will be able to get back into the boot loader, and select recovery, and reflash a rom. Other than that, I don't see any other method, if adb doesn't recognize the device as being plugged in, I am assuming you attempted to boot into boot loader as well, and see if adb recognized the device?
EDIT: stupid question you can't boot into boot loader without volume key
I just want to confirm that I need do nothing else other than configure the sdk and ENV path etc, such that if i can run adb and get the deafult output, eg switches fr command line options etc...
then all I should need to do is turn phone on and connect via usb to computer. I dont need to edit any config files for specific phone versions or whatnot?
If not then Ill try and bring it to a vodaphone shop and see if they can fix the volume button...
R
if you get the volume buttons fixed, we don't even need adb, I was simply thinking adb since your volume buttons are broken. Once the volume buttons are fixed, you simply need to boot into boot loader, then to recovery, mount USB mass storage, put a new rom on there, wipe the phone, flash the rom and your good
Good luck mate, do some mediation meanwhile and learn to keep patience, so when your phone is back, you can treat it gently while in the recovery.
You will be alright once your vol keys are fixed.
I used ZeroNull's method to unlock the bootloader, but for returning to stock bootloader, he only gives instructions for Linux. How do install the original bootloader via Windows and then install the stock rom?
Install the stock recovery then use the update.zip method to install a stock Acer ICS which will also replace the bootloader, its the safest way as people tend to brick doing this stuff.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Install the stock recovery then use the update.zip method to install a stock Acer ICS which will also replace the bootloader, its the safest way as people tend to brick doing this stuff.
Click to expand...
Click to collapse
Thanks, pio. Where can I get the stock recovery and how do I install it? Is there a guide somewhere? (Don't want to brick my tab.)
I can probably build a package for this sort of thing as it keeps coming up.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
I can probably build a package for this sort of thing as it keeps coming up.
Click to expand...
Click to collapse
If you do, I would very much appreciate it! Thanks!
xda_rulz said:
If you do, I would very much appreciate it! Thanks!
Click to expand...
Click to collapse
I'll have to see if I still have this stuff around, a lot of the hosted files are gone now.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
I have the stock ICS recovery.IMG. I will upload it in a little bit.
The stock ICS zip from zeronull is still up. http://forum.xda-developers.com/showthread.php?t=1611696
Here is a second link to it. http://ubuntuone.com/7DZtbNqZzOk7qsaQxNk99a
---------- Post added at 06:37 PM ---------- Previous post was at 06:25 PM ----------
Alright here is the ICS recovery http://db.tt/n3VeKLo9
Do you know how to flash the recovery with adb in fastboot?
Romman0 said:
Do you know how to flash the recovery with adb in fastboot?
Click to expand...
Click to collapse
No, but I've used adb before and I'm good at following directions.
xda_rulz said:
No, but I've used adb before and I'm good at following directions.
Click to expand...
Click to collapse
Alrighty then.
I'm assuming you have SDK (with adb platform-tools) installed and the acer drivers from their support website installed.
Grab the recovery image I posted up, and copy it to the platform-tools folder. Boot the tablet into fastboot. Either by using the app "quick boot", terminal app, custom power off options, or manually. To manually, with the tab off, press and hold at the same time the power button and the volume rocker closest to the corner, when the tab vibrates quickly release the power and toggle the rotation lock a few times. After the bootloader message appears you can release the volume and stop toggling.
Open a command prompt in the platform-tools folder (shift-right click).
type:
adb devices
To make sure it is seeing your tab
type:
fastboot erase recovery
fastboot flash recovery ics recovery.img
type:
fastboot reboot
All done.
Now you can verify the stock recovery by powering off and doing the above button sequence without the rotation lock, just hold both the buttons until it reboot to the recovery. You might be able to use quick boot or terminal also, but I have never used them with the stock recovery. You should now see the stock recovery, which you cant really use for anything besides updating from the sd card.
Now rename the stock ICS 014.zip to "update.zip", no quotes (make sure it is named with only one "zip", uncheck hide file extensions on known file types in the folder options). And copy it to the root of your microSD card, . Power off the tab, press the buttons to boot to the recovery. It should take over.
Romman0 said:
Alrighty then.
I'm assuming you have SDK (with adb platform-tools) installed and the acer drivers from their support website installed.
Grab the recovery image I posted up, and copy it to the platform-tools folder. Boot the tablet into fastboot. Either by using the app "quick boot", terminal app, custom power off options, or manually. To manually, with the tab off, press and hold at the same time the power button and the volume rocker closest to the corner, when the tab vibrates quickly release the power and toggle the rotation lock a few times. After the bootloader message appears you can release the volume and stop toggling.
Open a command prompt in the platform-tools folder (shift-right click).
type:
adb devices
To make sure it is seeing your tab
type:
fastboot erase recovery
fastboot flash recovery ics recovery.img
type:
reboot
All done.
Now you can verify the stock recovery by powering off and doing the above button sequence without the rotation lock, just hold both the buttons until it reboot to the recovery. You might be able to use quick boot or terminal also, but I have never used them with the stock recovery. You should now see the stock recovery, which you cant really use for anything besides updating from the sd card.
Now rename the stock ICS 014.zip to "update.zip", no quotes (make sure it is named with only one "zip", uncheck hide file extensions on known file types in the folder options). And copy it to the root of your microSD card, . Power off the tab, press the buttons to boot to the recovery. It should take over.
Click to expand...
Click to collapse
I'll try it as soon as I get home, thank you so much! I'll post if I have problems, but it sounds pretty clear and straightforward.
How did it go?
xda_rulz said:
I'll try it as soon as I get home, thank you so much! I'll post if I have problems, but it sounds pretty clear and straightforward.
Click to expand...
Click to collapse
Did you return your tab to stock? Any problems?
It worked!
Finally got around to restoring my tablet. Everything worked smoothly! No problems at all! Thanks, Romman0!!
Just made an easy tut thread, on how to go back to stock. Due to the inquiries.
http://forum.xda-developers.com/showthread.php?p=33574648#post33574648
I have a rooted/unlocked Verizon GNex running CWM and Linaro 4.2.2 (http://forum.xda-developers.com/showthread.php?t=2106640)
It has a totally busted screen and digitizer, meaning i have a black screen and i don't believe any touch input is being passed to the OS. The phone still turns on, vibrates when it receives messages, and rings when a call comes in and may take a charge. I have full donate version of the GNex tookit. I have CallLog Backup and Restore Installed and SMS Back and Restore installed as well. When i installed that ROM above about 7 days ago, i did not enable USB debugging so i cannot access, backup or view any files on the phone from my PC or the Toolkit. When i try to do a nandroid the Toolkit says "Waiting for USB debugging to be enabled." Can someone please tell me how to enable USB debugging via the toolkit or some other method of retrieving all the data off the phone? Can i rescue the SMS messages as well? I have several nandroid backups, call log and SMS back up files, and many pictures and videos etc i would like to recover. Any help is greatly appreciated. Chris.
Boot up to a custom recovery, then execute this in terminal/command prompt: adb pull /data/media
Beamed from my Maguro
Mach3.2 said:
Boot up to a custom recovery, then execute this in terminal/command prompt: adb pull /data/media
Beamed from my Maguro
Click to expand...
Click to collapse
i guess i need to know the exact key strokes ( hold down volume up and power while booting, then press volume up the power then volume down 3x then power etc.... )to boot up to CWM where i can be able to run adb commands. Won't i have to get to the place in the menu where i can mount the sd card?
Also, that will pull the data from the card, but the toolkit will do a nandroid of the current ROM if i can get the USB debugging enabled, which will allow me to save the SMS messages since the last backup. I was really hoping i could run a nandroid of the current ROM and pull that to restore to a new phone.
Mach3.2 said:
Boot up to a custom recovery, then execute this in terminal/command prompt: adb pull /data/media
Beamed from my Maguro
Click to expand...
Click to collapse
I have CWM recovery installed... so if hold Volume Down and power, then what combination of buttons do i press to be able to pass adb commands to the device?
Thanks!
TurbineTester said:
I have CWM recovery installed... so if hold Volume Down and power, then what combination of buttons do i press to be able to pass adb commands to the device?
Thanks!
Click to expand...
Click to collapse
turn off the phone, press volume up + volume down + power, when it vibrate, you are in fastboot mode, then press 2 times on volume up then one time on power, wait for 10 seconds, connect your phone, open command line where adb file exist and type
Code:
adb devices
you should see the serial number, then
Code:
adb pull /sdcard/
or
Code:
adb pull /data/media/
samersh72 said:
turn off the phone, press volume up + volume down + power, when it vibrate, you are in fastboot mode, then press 2 times on volume up then one time on power, wait for 10 seconds, connect your phone, open command line where adb file exist and type
Code:
adb devices
you should see the serial number, then
Code:
adb pull /sdcard/
or
Code:
adb pull /data/media/
Click to expand...
Click to collapse
Ok, got the ADB drivers installed and tried what you said. The phone shows up in devices with a long number and then "recovery" next to the number
When i type either of the adb commands i get the following:
pull:building file list...
0 files pulled. 0 files skipped.
What about just the key strokes to get to "mount sd card" in CWM?
[UPDATE]
I was just able to get the phone to mount in windows and i can see the files and folders there. I've pulled my call log and SMS backups, titanium backups, and some other files. But one thing i cannot find is my nandroid backups from CWM. I can't seem to find them anywhere on the device.
Is there a trick to be able to see/copy them from Windows?
I looked in
clockworkmod - no back up folder just a download folder
data - only three fodlers there, none of them is media
Thanks again for the help!
I recently also encountered phone card data recovery problem after accidental formatting. In order to copy off all stored card data, I just read and searched a lot.
Finally, I just successfully restored all my card photos, pictures and documents by using some data recovery tools like Recuva, iCare Data Recovery, 4Card Recovery and PhotoRec, etc.
They all works well.
Note: Also learn a valuable lesson to back up everything important on different drives or cards in case of any data loss problem.
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you
hey guys,
i was bored and flashed a .zip on my phone and now I'm no longer bored. Long story, short... I'm booted into the os (almost) with constant errors popping up. I can't get the power button down for 10 seconds to reboot phone and i want to get back to recovery to flash by back up. How can I use terminal (mac) to force back into recovery if phone is not in mode for adb to recognize phone?
Thanks in advance.
Try hold power button + volume up to force reboot. Once the screen goes black release those buttons and hold volume down button to go to hboot
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
Click to expand...
Click to collapse
Power + Volume Up should work. But as you asked for adb/fastboot
1) "adb devices" to check if device is recognized
2) "abd reboot bootloader" so the phone reboots into bootloader
3) go to recovery and try a reflash
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Click to expand...
Click to collapse
This should always work as long as the screen is on. It might take 10 seconds or more, so you may not be holding the buttons long enough.
Alternately, you can use:
adb reboot bootloader
or
adb reboot recovery
There is no required more for adb commands, as long as the screen is on. Fastboot on the other hand, requires the phone to be in fastboot mode.
What did you flash? Was it a ROM, and if so did you do a full wipe (data, cache and Dalvik) before flashing?
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
andason said:
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
Click to expand...
Click to collapse
Glad it worked and that we could help a
adb reboot bootloader should be recognized nearly any time.
Sent from my HTC One_M8 using XDA Free mobile app