Alright, so i hadn't used my nexus 7 (2013 wifi only version) for awhile but i decided to start using it again. It was running a custom ROM (paranoid android) but it was very outdated. I decided i would just start fresh, and would flash the stock ROM before doing anything else.
So i tried to put the stock ROM (4.4.3 from google's site) but it would not let me flash it using clockwork recovery mod when i just put the file onto the device. So i tried to adb sideload it. This is where the problems started.
In my command prompt (using windows 8) it showed it was loading files, then it started to fail, im not sure where because it was moving very fast. But it said it failed and ended the side load. On my nexus 7 the screen was at the bootloader but none of the hardware buttons did anything so i turned it off. turned it on again and let it sit for 5 minutes but it just stayed at the google screen. I turned it off and held the power and volume down to launch the bootloader. This time i could use the hardware buttons but when i tried to select the recovery mode option it just rebooted and stayed on the google screen again...
So right now, it is either stuck at the google screen, in the bootloader, or off and i can go between these. I also can't seem to get it to show up on adb but im going to try to install the drivers again.
If anyone knows of a fix to get the device working again, preferably on the stock android ROM but I'll take anything at this point I just want my tablet working again Thanks.
Hello,
The issue you are experiencing is because the files found on https://developers.google.com/android/nexus/images from google can't be flashed through a custom recovery. They must be flashed through the bootloader. If are able to get ADB to recognize the device in bootloader then you should be good to go.
You can follow the steps listed here: http://forum.xda-developers.com/showthread.php?t=2382618
Related
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
rs18 said:
I've done about 3 hours of research on this forum and the internet in general, and I can't seem to find a situation like the one I'm in. I'm not particularly savvy at all of this, but have successfully rooted a few phones and have played with a variety of ROMs for both tablet and phone. I have the Android SDK installed, the drivers for my phone installed on my computer, PDANet, the works. I'm on a Windows 7 laptop.
I had a new JRO03L ROM build for my verizon GNex flashed, and was getting quicker than expected battery drain. So I decided to flash a custom kernel. I must have flashed the incorrect version of this kernel.
When I rebooted after flashing the kernel in CWM, it went into a bootloop on the Google screen. I waited an hour, pulled the battery and tried to boot into hboot (volume down+power button). Lo and behold, I can't get back into CWM! I have no option to enter recovery, I'm only able to start the boot process.
So I plug it into my computer, hoping that I might be able to use the GNex Toolkit (v7.8) to restore to stock and start over, or even just try to use fastboot to ... do something - anything! - and my computer doesn't recognize my phone when in hboot. When in hboot, my device manager recognizes the phone as "SAMSUNG Mobile USB CDC Composite Device" and as a modem. When I start the boot process and it is bootlooping, my computer recognizes it as my phone, but can't install the drivers properly.
Any help would be greatly appreciated, even if you can get me back to stock. I have a nandroid backup on my SDCard; I just need to be able to get to it and flash it. I would be forever in your debt if you can help me out! Thank you in advance!
Click to expand...
Click to collapse
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Jubakuba said:
Post three of my guide.
Push another rom.zip to your phone and flash it (if you don't already have one there).
If you have one...You're not getting into the correct menu.
You're in ODIN.
Bootloader/Recovery is BOTH volume buttons.
Click to expand...
Click to collapse
Thank you. I'm an idiot. It's been a long while since I've put this into recovery via physical buttons.
By the way, your guide is excellent. How have I not stumbled across this?
Hi there,
I'm not new to rooting and flashing devices, but something went wrong during my last root. I was using CWM to root the most recent paranoid android rom, a 4.4 rom, and after I rebooted, the device started normal and works fine. However, it's completely lost root AND has no recovery. Just the little opened up android guy with his red triangle.
I've tried using the toolkit, but the ADB drivers just are not being recognized. I've tried all of the driver options, and it says that it worked, but when I run the driver test it says failed. When I connect the device as MTP, it shows up as having recognized the device, but I can't actually access the device from the computer. When I try fastboot, nothing happens. The device just goes black and sits like that until I hold the power button down for awhile.
So, the toolkit can't get me back to stock, at least not any way I've tried. And since I can't install a recovery, I can't flash a new rom or stock.
I guess it could be worse, as the device does still work, but I want it fully functional.
Does anyone have any solutions?
Hopefully this is the right place to ask this question.
Thanks in advanced!
lasnaranjas said:
Hi there,
I'm not new to rooting and flashing devices, but something went wrong during my last root. I was using CWM to root the most recent paranoid android rom, a 4.4 rom, and after I rebooted, the device started normal and works fine. However, it's completely lost root AND has no recovery. Just the little opened up android guy with his red triangle.
I've tried using the toolkit, but the ADB drivers just are not being recognized. I've tried all of the driver options, and it says that it worked, but when I run the driver test it says failed. When I connect the device as MTP, it shows up as having recognized the device, but I can't actually access the device from the computer. When I try fastboot, nothing happens. The device just goes black and sits like that until I hold the power button down for awhile.
So, the toolkit can't get me back to stock, at least not any way I've tried. And since I can't install a recovery, I can't flash a new rom or stock.
I guess it could be worse, as the device does still work, but I want it fully functional.
Does anyone have any solutions?
Hopefully this is the right place to ask this question.
Thanks in advanced!
Click to expand...
Click to collapse
Few things:
try another soft reset. power the device on, and then hold the power button down until it restarts.
download superuser/supersu to see if there actually is no root. sometimes it's just being difficult and says there is no root.
Following that, try downloading ROM manager and seeing if it'll flash the recovery.
Once Nexus 7 (2013) is being on, it straight away leads me to teamwin custom recovery, it doesn't boot to android. Also in teamwin it says that the data can not being mounted
dhaseegaren said:
Once Nexus 7 (2013) is being on, it straight away leads me to teamwin custom recovery, it doesn't boot to android. Also in teamwin it says that the data can not being mounted
Click to expand...
Click to collapse
Did you get this fixed yet? I was stuck in a TWRP bootloop after trying to flash stock 6.0 is that what you did? If all else fails you can try to boot fastboot and flash the stock firmware, that's what I had to do.
Try this:http://forum.xda-developers.com/showthread.php?t=2471341
Android 6 Marshmallow,MRA58V, TWRP, Rooting, MultiRom
Ok my experience with rooting using N7 2013 and Ubuntu adb stuff. (When I say N7 I mean the 2013 version)
Put Marshmallow MRA58V on the N7 (deleted link per prompting) Tried some of the older rooting methods but one thing is certain, TWRP no longer behaves like it did in the past.
I was running a Cyanogenmod ROMs from July and decided to upgrade from scratch. When I get to the TWRP screen to where I expect it to say it will allow me to globally root the device, I get the "Read Only" mumbo jumbo.
One can hit yes or swipe to go on. Doesn't matter what you select.
Once I get TWRP installed, I have it install Elemental X and SU. Ok up to now. Marshmallow boots up fine and dandy to a usable, stock system that's stable. Now for the fun part. When I install Multi-Rom while in Android 6/Marshmallow, the unit goes through the nominal process of installing the app. It goes back into reboot mode, finishes the install and when it reboots again, it gives me the standard MultiRom screen and the choice to boot into "stock". When I select stock, it boots directly to TWRP period. No amount of dinking around allows me to do otherwise. It will only boot into TWRP and not into Marshmallow. I've done 5 installs with various iterations of "rooting" I could find on the internet ( and here) to no avail. I also tried MRA58K ROM
My goal was to have a stock kernel for app stability and an experimental kernel I could experiment with.. Any suggestions? Do I go back to an older ROM from the 4.4 set?
I will say I bricked up the N7 2013 several times. I found if I brought up the boot loader to START in the N7 screen, I could run the sudo ./install.sh command on the Ubuntu box from the ROM directory directly without the adb command. The command prompt responded it was accessing the bootloader but would sit there for awhile. When I hit the on/off button on the N7, the laptop responded with loading the fresh ROM to the N7 2013 and it fired right up with a fresh install from an apparent "bricked" state. Happy for me. I discovered this as I thought I had bricked the device but good 'ol Unbuntu Linux showed on a "dmesg" command
that the N7 was connected to the USB port. I read that someone did the ./install.sh command directly and by golly it was brought back to life.
I did try to backup the system right up to just before I installed multirom during one of the installs. When I got the perpetual boot behavior into TWRP, I restored the backup and the booting behavior still occurred into TWRP only.
Any suggestions for this "script kiddie" here? I hate to be without Multi Rom but I will at least be able to run a stock kernel. I couldn't find anything but the Open Gapps for Marshmallow and I REALLY miss that
shutdown screen that gave me something like 5 choices. Now I can only "shut it off". Best regards, Kurt
Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.