I was using my N73G at home this evening and it spontaneously rebooted to the Google splash screen... and stayed there for well over 5 minutes. I tried long pressing power to reboot again, and it went back to the same screen.
TWRP is installed, and I am able to get into that. I tried wiping cache and dalvik, and it booted straight back to the splash screen again, solid for 3 minutes before I went back into TWRP. In the file manager my files all appear to be safe and sound. I am currently running a nandroid backup before I futz with it any further. TWRP has not given me any errors over the course of the backup.
I should note that I have had some trouble connecting to TWRP over ADB although I can use ADB when booted into the OS. So if I need to go fishing for files over USB, I hope I won't come up empty. If necessary I could try flashing CWM recovery instead, as I may be able to get my files more easily that way.
Anyway, ideas are welcome. I was running a bake of the Modaco custom ROM, and the zip for that ROM is still on the device, so I was thinking I might try reflashing that. But first I should try and get my nandroid off the slab.
As fortune would have it, I have already ordered an RMA device swap due to issues with the speaker blowing out. So if I fail to resuscitate it, help is already on the way. But I would like my tab to work again by the time I go back to work Monday
Update: Figured out the ADB recovery driver problem. Nandroid backup was successful. I'm now pulling the backup image to my desktop. Will try a ROM reflash next.
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices. So I typed in adb logcat and found some message about /system/xbin/busybox missing.
I browsed with ADB shell and found there is a busybox in /system/bin. So I did ADB remount, and then copied busybox from bin to xbin. Entered a reboot command, and bam! Five seconds on the Google splash, and then right to the booting X.
Why in the world would this have happened... maybe the busybox installer app got an upgrade and botched an attempt to upgrade busybox?
cmstlist said:
UPDATE UPDATE: The weirdest thing. I noticed while it was plugged into my machine, still stuck on the Google boot logo, that I was able to see the tab in ADB devices.
Click to expand...
Click to collapse
The adb daemon - adbd - is started by init as a service so long as you have previously enabled adb debugging. So, it happens before the whole android reboot sequence kicks off (checking that all .apks without odex files have up-to-date .dex entries in dalvik cache, permission checks, etc.) You can access it on devices that are "stuck" in the late stage of booting.
TWRP - for better or worse - does not claim the same USB vid/pid ID that is used by the N7's ADB facility, even though the exact same driver can be used for either adb mode ... so long as you manually went into the driver install package and add the "universal" vid/pid values used by TWRP to the driver's .inf file. I think this is done simply to minimize the effort keeping up with new device identifiers by the TWRP team. It does create the impression that separate drivers are needed - but only because neither of the two drivers (Google vs. Universal) have the "other's" vid/pid pair listed as matching devices in their .inf files.
Anyhow, you got it all sorted out - congrats.
Thanks! I had been worried maybe the whole file system was corrupted, so in comparison this was a relief.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Ok folks, I believe I have read 30 or 40 threads on this site and 20 or so on other sites regarding pushing to sdcard and I think it's ok I now ask for help here.
I have rooted my Kindle Fire successfully
I installed android market successfully
When I saw the people saying turn off wifi to avoid getting the 6.2.1 update I did so.
Now I want to install cm7 on my kindle so I don't have to worry about updates anymore. Ok, now onto the problem.
Downloaded whistlestops update-wipeall.zip and put it into C:\Program Files <x86>\android\android-sdk\platform-tools
Made sure device was fully powered and plugged into Windows 7 computer
went to command prompt and changed directories to C:\Program Files <x86>\android\android-sdk\platform-tools
Ran cmd prompt
adb push update-wipeall.zip /sdcard/
and problem is I get failed to copy 'update-wipeall.zip' to '/sdcard//update-wipeall.zip': Permission
denied
I have checked to make sure I am rooted and still nothing. at this point after reading and banging my head against wall I could really use some help from community.
p.s. apologies for repost not sure how planets aligned for previous to end up in Lenovo forum
I was having the same issue. I ended up installing TWRP (which took me all night to do) and flashing CM7 with that.
I have twrp installed but need to get the cm7 file to the kindle to flash. Heck I even went into twrp and did a full backup just to make sure I could restore if I needed.
So how did you get cm7 onto sdcard to flash or am I just hopelessly lost?
To push update.zip you must unmount kindle from your computer (right click on kindle disk in "my computer" and unmount/unplug)
and again, open command prompt
adb kill-server
adb devices
...bla bla bla
Thanks Kisman that did the trick.
Now I have a new set of problems but original was solved.
I went into TWRP did mount usb storage
Copied image over to kindle remounted
Went to install. There is my wonderful file, clicked the file, flash, even did the wipe as suggested in inital instructions (Thanks Whistlestop) rebooted and well nothing, I got the yellow triangle, it goes away to be replaced by nothing.
Rebooted again into twrp and restored backup (thank you twrp team)
back to square one, calling it a night now, maybe fresh eyes in morning will turn up something.
Moose66 I used this tutorial to install CM7 - and I suggest you to do the same thing
http://www.kindlefirewire.com/2011/12/06/how-to-install-cyanogenmod-7-on-kindle-fire-tutorial-video/
I copied update.zip file from this topic:
http://forum.xda-developers.com/showthread.php?t=1390773
From this topic I copied: log, last_log, stockrecovery.img and updaterecovery.img:
http://forum.xda-developers.com/showthread.php?t=1368012
Be sure you copied log and last_log without .txt extention. My firefox added extention .txt automatically
sorry for my English, good luck
I followed the whistlestop (thanks again) instructions using the first choice for unmodded roms, update-wipeall.zip to the letter. It says everything was successful but on reboot I get the yellow triangle like I should and then a backlit screen and nothing else. I waited 5 minutes and tried rebooting 3 or 4 times before I used twrp to restore the previous version.
I am not sure what I am doing wrong at this point.
p.s. appreciate all the community help I have received thus far
Write here step by step what you did exactly
Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.
factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!
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
Earlier, I did a wipe of my tablet and wanted to install a ROM through recovery, but using the mount function from TWRP is a no-go.
When I click the Mount button, it takes me to a list of which directories to mount, but nothing else. In the lists of available drives under Computer, my tablet is not listed.
What do?
Unfortunately, I don't know how to push through ADB or do an ADB sideload, so if anyone can walk me through that process, I'd be forever grateful.
Update: Got adb to work, but I can't get my PC to recognize that my device is plugged in.
I know for a fact that the problem lies on the device side rather than the PC side, so how do I fanangle my N7 to get recognized by my comp?
Did you really flashed correct twrp version for your n7?
So, I just did a crash course on how to use ADB and just flashed to stock.
Hopefully, I'll have no problems afterward.
Hexm.xx said:
So, I just did a crash course on how to use ADB and just flashed to stock.
Hopefully, I'll have no problems afterward.
Click to expand...
Click to collapse
Otherwise try to get the drivers installed manually just search Google for Nexus 7 fastboot drivers and here is a little help for you installing Roms like ubuntu (touch): http://forum.xda-developers.com/showthread.php?p=46823947#post46823947
I flashed a 4.4 stock rom on my 2012 32g N7, and unfortunately, didn't notice until too late that it was also overwriting my custom recovery with the stock. Also, in the flashing process I received an error while flashing GAPPS. When I first booted the tablet, everything was fine except for no GAPPS, but I figured it would be simple to just download an APK or two and load them - well, when I tried that with several play store APKs I got "cannot open file" error.
I have now resorted to ADB to "sideload" the apks (and a custom recovery) to the tablet. At first I had trouble with the drivers, but I have followed numerous tutorials and have a solid grasp of how ADB works now. (more on that later)
I also tried WUG's toolkit, but no matter what I tried (or how many drivers I un/installed) I could never get past the "no fastboot device" error.
I used a second version of the ADB from another XDA thread, and was finally able to get my PC at the command prompt to communicate with the N7, and recognize it with "ADB devices" - the result was "<serial> sideload". This is of course when I have the tablet in the stock recovery "adb sideload" mode.
I about yelled for joy, when after six hours of rebooting and tutorials, I was able to get "adb sideload update.zip" to load, but the joy was short lived - as it consistently hangs at "sending: 'sideload' 53%"
I have tried several different zips, of varying names. and even some APK's (which hang at 78%)
Any assistance which can be offered to get this N7 functional again would be greatly appreciated!
SOLVED
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Notable said:
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Click to expand...
Click to collapse
If you're flashing the stock KitKat, you shouldn't need to flash a separate gapps package. Aside from making sure you have UAC control, make sure you update boot to 4.23, if you haven't already done so. Flashing 4.4 is easy, as long as you don't make the mistake of ever owning another An droid device and plugging it in to your pc... Dealing with missing/conflicting Windows drivers might require a vacation day and a fist-full of xanax,
Sent from my Nexus 7 using Tapatalk