Related
Hi Guys
I have just busted my screen, and I am hoping there is a way to image the OS so that I can flash it to a replacement if need be.
nb. Before anyone mentions warranty, I bought it on ebay
I am calling around to get the screen replaced, but if not I might have to get a new one and I am loath to have to reconfigure it again.
I remember reading that this can be done, but can not find the article again, like making a custom ROM... Is it possible?
Thanks in advance
If you have clockwordmod recovery or New StreakMod Recovery installed then you can do a Nandroid Backup
Awesome!
I have clockwork recovery mod.
I'll see how I go, do you know of any detailed instructions? I will need to do it half blind, because I cant see the screen.
It may be a long shot, but it there a chance I can get into the clockworkrecoverymod via adb and initiate the nandbackup that way?
.. and by extension, is there a way to connect adb to the phone without usb debugging?
Or, just as unlikely... I don't suppose I can add a bootup script to the sdcard that turns on USB debugging when I turn on the phone?
I am in adb
I created a virtual dvice and used that as the guide for where to press
I am looking for the command to create a nandroid backup via adb (if there is one). But if anyone already knows, please fill me in
Thanks
This walkthrough is much less painful
http://nerdnewz.net/2010/10/21/backup-restore-android-apps-using-adb/
My apps and app data is all I needed
Hopefully this helps someone else with a similar problem.
So, I had been using my A500 for the last few days with no problems. Well, yesterday, I got home from work and powered it on. The lockscreen came up, but the screen was unresponsive. I turned it off and then back on, but screen still didn't work. Then I did a hard reset, which still didn't fix the problem. I put it into recovery, then did a wipe that still didn't fix the issue. I flashed the ROM again. Then a different ROM. All it does is is boot up and go to the lock screen, but the screen does not respond.
If I can avoid it, I don't really want to go through the hassle of returning it since I got it online. Hopefully it can be fixed without having to take it back. Thanks in advance for everyone's help.
Boot back into recovery.
Wipe your 3 things,
User Data
Cache
Dalvik
Then go to Mounts
Format the same 3 (user data, cache partition and Dalvak.
And Flexrom
Then flash your rom. Try and flash a basic rooted rom. No kernels, no gapps.zip
See what happens.
If you have a file called update.zip, on your sd, I would delete it. And anything else there except for the rom.
sounds like hardware failure. Has the tablet been dropped or banged around. The connector on the digitizer could have came loose.That would mean void warranty and take it apart ..
Send it back is likely your. Best option
Thanks for the quick responses! I'm gonna try these things, hopefully I don't have to take it back.
Guess it is a massive hardware failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
sikkboy626 said:
Guess it is a massive software failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
Click to expand...
Click to collapse
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Moscow Desire said:
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Click to expand...
Click to collapse
Thanks for all your help. I was able to get it back to stock. The return should go fine. You're awesome and I did not forget to use the thank you button.
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
You can use normal usb mouse with this tablet, you will get mouse pointer on the screen when you connect mouse...
erica_renee said:
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
Click to expand...
Click to collapse
I was able to flash using the physical buttons. I got it all back to factory specs so I can return it. you were correct I believe, it does seem to be a screen hardware failure. Everything else works but the touch response.
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
erica_renee said:
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
Click to expand...
Click to collapse
Guess I had to take one for the team
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
Hi folks,
yesterday my Nexus 4 hit the ground and the front glass just bursted. Touch is not working anymore and the screen is locked (only slide to unlock, no pin or gesture). I can connect it to my PC and can access the internal storage, so backing up images, music, etc. is not a problem.
I have some apps installed of which I want to transfer the app data to my new phone. Debugging is enabled so I thought, well that'll be easy just run adb backup. Thought so... As adb backup requires a user action when it comes to entering the password I'm doomed
Does anybody has an idea or experienced the same problem on how I can get adb backup to work without being able to use the touch screen?
I'm not limited to adb backup but as my phone is not rooted I assume there are not a lot possibilities besides.
Thanks a lot for your help.
calex
calex3141 said:
Hi folks,
yesterday my Nexus 4 hit the ground and the front glass just bursted. Touch is not working anymore and the screen is locked (only slide to unlock, no pin or gesture). I can connect it to my PC and can access the internal storage, so backing up images, music, etc. is not a problem.
I have some apps installed of which I want to transfer the app data to my new phone. Debugging is enabled so I thought, well that'll be easy just run adb backup. Thought so... As adb backup requires a user action when it comes to entering the password I'm doomed
Does anybody has an idea or experienced the same problem on how I can get adb backup to work without being able to use the touch screen?
I'm not limited to adb backup but as my phone is not rooted I assume there are not a lot possibilities besides.
Thanks a lot for your help.
calex
Click to expand...
Click to collapse
Do you have a custom recovery? Try flashing a non-touch one. Adb should work from within it.
abaaaabbbb63 said:
Do you have a custom recovery? Try flashing a non-touch one. Adb should work from within it.
Click to expand...
Click to collapse
As I wrote, my phone is NOT rooted nor unlocked, so no custom recovery. Or do I get something wrong there?
calex3141 said:
As I wrote, my phone is NOT rooted nor unlocked, so no custom recovery. Or do I get something wrong there?
Click to expand...
Click to collapse
Then you'll lose your app data.
calex3141 said:
As I wrote, my phone is NOT rooted nor unlocked, so no custom recovery. Or do I get something wrong there?
Click to expand...
Click to collapse
Your outta luck it seems then... If its that important to you you could buy a replacement screen for the n4... Get your data and sell it and get the money you spent in the screen back.
Sent from my Nexus 4 using Tapatalk
If the apps that u need data are on sdcard(their datas)then u just do adb pull /sdcard c:\sdbackup with phone on.
if not then:
@calex3141 :
1ST: IM NOT RESPONSABLE FOR ANY DAMAGE / FAIL WHILE DOING THIS METHOD, I TESTED ON MY FRIEND´S N4 BUT I CANT GUARANTEE THAT WILL WORK ON EVERY NEXUS (INCLUDING YOURS), USE AT YOUR OWN RISK.
2ND: DO NOT CRY IF U CANT GET BACK THE FILES IF SOMETHING FAIL. YOU COULD JUST BUY SCREEN REPLACEMENT OR GET A JTAG DUMP
3RD: do carefuly. if you are nervous calm down b4 doing this. one single command and u can format the nand so be careful.
4TH: I hope it Works for u .
5TH: u need to have adb seted up and also drivers. if you dont know how, search google(for drivers).
for adb just install minimal adb and fastboot
6TH: its recomended to test to see if cygwin(u will know what it is in a moment) is working (do some commands on it, like cd .. (to go back)or ls (list files) )
7TH: if u have any errors contact me asap and i will try to help you
LETS GO:
unlock the bootloader: (type in cmd prompt, fastboot oem unlock, and follow instructions on phone)(DO THE MANUAL WAY, DO NOT USE TOOLKITS, KEEP READING TO KNOW WHY)(it will say that u will loose files, but it actualy dosent format, it just change the 1st´s block of userdata partition to make it unmountable normally,thats why toolkits do fastboot format userdata after unlock.and tutorials say to format data in STOCk recovery, since custom ones dosent format, just delete everything except sdcard)
(do not format anything, even on stock recovery)
flash multirom recovery:http://d-h.st/pzv (Thanks@tassadar for his great work)(the only that i use, so i cant tell others)
then do this
http://forum.xda-developers.com/showthread.php?t=1994705
(instead of doing it with phone on, just do on recovery,adb is enabled on it)