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.
Related
I am running the stock rom without root and unlock and I got the 4.0.2 OTA update 3 days ago. Today when I do the pattern unlock my phone froze and reboot. Now I cannot get pass the Google logo boot screen.
I am able to get into the recovery mode but I don't want to do a factory restore as I don't have anything backup yet.
Is there any solution to this boot loop problem? I am surprise that I am getting this problem as I am running the stock rom without any root / mod.
If there is no solution to this, is there any way I can backup my phone before doing the factory restore?
Many thanks!
You can back up via adb. Try searching in the General threads, since there's a long topic on this...
Good luck!
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
When i got stuck at the Google screen with a bootloop i booted into the bootloader/fastboot screen with vol up+down power and i redid the one click all process and it basically rewiped my device and put it back to working again with unlocked bootloader rooted etc....
All you have to remember is what build number you have and let the toolkit work its magic.
tigersgt said:
Thanks, I do find information about backup, but I can't find anything regarding the bootloop...
Click to expand...
Click to collapse
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
danger-rat said:
Sorry, forgot to mention. You're probably gonna have to wipe via recovery - which is why I pointed you to a back up...
Click to expand...
Click to collapse
I can't find a way to backup without going into Android. I can only go to Fastboot Mode.
Anyone know how to backup the file using abd without getting into android?
Why did make 2 threads about this. Unlock the boot loader and use adb to flash your stock. Image files. You will loose all data unfortunately but I think that's the only way to fix it.
Sent from my Galaxy Nexus using xda premium
Ok I'm stuck with the same problem now. I wanted to flash a ROM, so I downloaded AOKP, flashed it and rebooted and the phone refuses to boot past the Google logo and keeps rebooting again and again. I am able to get into the recovery. I have flashed the ROM several times and its still the same. I have done a complete wipe as well. Still no go.
Fastboot command doesnt work in the bootloader either. I have made sure the drivers are installed, still there is nothing when I type fastboot devices. If I type any fastboot command it just says <waiting for device> or something like that.
Any other suggestions? :-s
I've been lurking for quite some time and haven't been able to find a solution for my issue. Here's what happened:
I cracked the screen on my Galaxy Nexus and got an insurance replacement. I then used ClockworkMod Recovery to copy over from my old device to my new device. All was good for about 12 hours when the new device started boot looping with the flashy color animation screen. I figured that might have been something I did, so I tried doing a factory reset and the like with ClockworkMod Recovery and managed to totally mess the phone. After trying to do a factory reset, the phone wouldn't boot up at all anymore -- I just get the dreaded red triangle with exclamation point. I tried formatting all the partitions with ClockworkMod (which was a bad idea). Ever since then, I've been stuck. I've spent several days so far trying to get this thing working. I have to note that Odin and fastboot modes work perfectly fine.
Among things I've tried unsuccessfully:
Flash to stock using Odin
--Odin says everything is fine, when I flash with a stock ROM that I downloaded. Upon reboot, nothing is any better and I still get the red triangle/exclamation point.
--When I try to use the tar files that ClockworkMod generated, Odin crashes immediately.
Push custom ROMs to /sdcard/ using adb while booted into ClockworkMod in hopes of getting the system to boot.
--This never works successfully. Sometimes I get no error but can't find the zip file. Other times I'll get an I/O error, or even a read-only error. The original backup is giving me checksum errors.
Flash factory ROMs using fastboot.
--I always get the red triangle/exclamation point.
Restore and flash with WUG's toolkit.
--Same thing as when I try to use fastboot. It seems that flashing the device goes fine, but the device will still not boot.
After every time I've flashed the device, whether using Odin or fastboot, I've tried doing a factory reset by pressing power+vol up+vol down and then selecting factory reset. This hasn't made any difference.
I'm about to give up on it and send the device back to the nameless insurance company, but I would like to lock the bootloader first. I can't even seem to lock the bootloader! In fastboot, I type the usual 'fastboot oem lock', and the device reports that it is locked, but after rebooting, the device always reverts back to having an unlocked bootloader.
Have I missed anything? Any thoughts? I'm lost.
Fyi, the red exclamation point is the stock recovery screen.
Try following the instructions in the "flash" link in my sig.
Sent from my Galaxy Nexus using Tapatalk 2
As well, issue the following commands when in fastboot:
Fastboot erase system
Fastboot erase userdata <- this will wipe by the way, including/sdcard
Fastboot erase boot
Fastboot erase recovery
Fastboot erase cache
And then flash the images in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
enginerrd said:
Thanks a ton for the helpful info -- I hadn't tried flashing userdata and system using that method before, and your write-up was definitely one of the more helpful I've seen.
Unfortunately, it doesn't seem to have helped. I used the factory 4.0.2 mysid/toro image on the link you provided. While flashing, the system seems to work absolutely fine, but it just reboots into recovery at the end.
I followed your instructions twice, including erasing the partitions. Also, after each try, I've tried doing a factory reset from recovery and then rebooting (after trying to boot a couple times), though none of this helped.
Click to expand...
Click to collapse
If you've flashed the system, userdata and boot images using fastboot, and you are still not able to boot into Android, I can only suspect that you have either a corrupt bootloader or a hardware issue.
And if odin does not work, then unfortunately I would suspect that there is a hardware issue.
This sounds like what happened to my phone as well. Someone else had it happen too. That's 3 nexus's in a week. Mine didn't even last 2 months.
I have a thread about mine and another user posted another thread a day or 2 ago. Mine boots into the system but is not erasable, not writable. Can't lock my boot loader. I've tried odin, adb, everything possible. I wish we could start a lawsuit because Samsung won't help me. I'm in the US and it's a gsm nexus that was purchased before the play store sold it. USA wont accept an international phone and UK Samsung won't take a phone from overseas. Basically they said I'm sh*t outta luck.
Thanks again for the help. I'm going to bite the bullet and just call the insurance company and try to send it back as a defective device. Hopefully they don't rake me over the coals.
I'll post back with an update as to how that goes.
You guys need to learn how to use fastboot and adb commands correctly to restore google's stock images.
Stop realying on toolkits thinking it will help you.
Also learning that the Red Exclamation Android is stock recovery!
Press the Power and Vol Up button will get you the stock recovery menu options to come up!
Not to be mean, BUT I hope the insurance company denies you, you totally screwed up the phone yourself.
I did not screw my phone up myself. My phone was never even rooted. I know very well how to issue adb commands and install images. Learn what you are talking about before you jump onto people or come across as a total di*khead
Alright, replacement phone is on the way. Thanks again for the help. I tend to think it is a hardware issue because of how the issue originally presented itself, but I'm still pretty new to the Android platform. It seemed to me that a watchdog timer was timing out or something similar.
Perhaps this will be the push I needed to start developing Android hardware/software... I'm all about embedded systems and would like to move beyond basic ucontrollers.
Hi
I converted from Yakju to Takju when 4.2 started rolling out in the Autumn. Now my GN has tried to install the OTA twice and failed both times.
So using adb I tried to apply the patch manually. However, it's giving an error:
assert failed: apply_patch_check ("EMMC:/dev/block/platform/omap/omap_hasmmc.0/by-name/radio (it then goes into a very long number)
Installation aborted
Do I need to upgrade the radio baseband? Will it work if I flash the whole image rather than just the update?
EDIT: I should say I'm on stock 4.2.1, unlocked, no root
Yes, the radio is why its failing. You could flash the whole image instead, or just fastboot flash radio radio.img, reboot, then try the update.
Download whole takju 4.2.2 image, flash LJ radio and fastboot update image-takju4.2.2.zip without -w parameter to avoid userdata overwrite, more faster since you skip the OTA flash this way.
OK, cool. Thanks for the info. Though I have a dodgy USB port at the moment, so will have to wait until that's fixed I think. Can't get a reliable connection at the moment
I've been trying to follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1995482
to flash the radio and update, as I figured it should work. I'm using OSX.
However, I'm getting the "no device detected" error in Terminal. Is this just my dodgy USB connection or am I doing something wrong? USB Debugging is on (and I have an icon when connected)
That's not a very good guide. Use this one: http://forum.xda-developers.com/showthread.php?t=1626895. You're typing ./adb devices, and it says no device detected? What version of osx? For me, on 10.6.8, if im not connected via usb, ./adb devices just returns "list of devices attached" with a blank line under it.... I think i've read about some issues connecting a gnex to newer osx versions, and if that is the case, google it. If your phone is registering a connection, I doubt the usb port is the problem.
Got it working with the guide. Flashed bootloader and radio with no problem.
Had a couple of errors whilst flashing system, but tried it a few times and eventually got an OK on the phone and in Terminal. Flashed recovery, cleared cache and rebooted.
However, my phone has now been on the Google logo for over 5 minutes. Dead?
EDIT - Went through the whole process again, no errors... seems to be fine, though doing its tediously slow 'optimising app' thing...
How about boot.img? you should've flashed that too... You've got a bootloop, so go back to the guide, see what you've missed and try it again.
I wonder what kind of errors you had while flashing system.img..
bodh said:
How about boot.img? you should've flashed that too... You've got a bootloop, so go back to the guide, see what you've missed and try it again.
I wonder what kind of errors you had while flashing system.img..
Click to expand...
Click to collapse
Yeah, flashed boot just forgot to put it in here. The error I was getting during system.img was 'no such folder' (can't remember the exact phrasing). But I started again from scratch, didn't get any errors and it's all working fine. Not sure what the difference between attempts was.
I use the Teshxx rooted version of the stock 4.2.2
I used TWRP to flash the zip file and then used the Galaxy Nexus Toolkit to fastboot the latest radio and bootloader.
All the threads are in the galaxy nexus development sub-forum.
If you need any help let me know.
Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Edit: fastboot commands worked, then after wiping as pandae suggested i then flashed the latest boot loader, and then flashed recovery from the zip file.
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
danqe said:
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
Click to expand...
Click to collapse
It's a pain you got through this.
I went through the same. But glad to have my Tablet working after some time figuring out what went wrong or what I have done to have messed it. But I figured that out. Somewhere along the way of my ventures, I have done something that forced my TAB to bootloop forever.
That being said, you can just look back to the things you might have done that caused it. Figure out what you did before that. When was it okay?, Things like that.
There is a thread in here with a one-click recovery that promises a Dead or Alive nexus to be unbricked. Though I never had success with it, go figure if that will solve your issue.
All the best!!
danqe said:
My nexus was giving me problems of not picking up touch, i think it was bad digitizer, because it would go in and out almost randomly.
It was unlocked, and rooted, and i tried a couple factory resets to fix the problem but no luck. Then it would boot loop constantly, until it wouldn't get passed the google screen with the unlocked icon.
I was still running jelly bean, not sure witch build specifically
It can get into fast boot mode, but not recovery.
windows 7 would only recognize it as an android device and not establish adb, I've tried WUG toolkit.
I tried setting up the sdk on unbuntu, I can establish adb on my galaxy nexus, but noit on my 7
adb devices returns nothing when the nexus 7 is plugged in but, lsusb shows it connected as google, inc something
I'm not sure if usb debugging was enabled before it wouldn't boot anymore.
I just want to relock if that is possible, wanted to RMA to ASUS for the touch screen
any help would be great
Click to expand...
Click to collapse
If you're at the bootloader, use "fastboot devices" to see if your tablet is recognized. (ADB is for when you're booted into Android.)
If you can get to the bootloader and your N7 is unlocked and recognized, there's a lot of hope. Run these:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that, you'll need to reflash your favorite custom recovery and ROM.
Pandae said:
If you're at the bootloader, use "fastboot devices" to see if your tablet is recognized. (ADB is for when you're booted into Android.)
If you can get to the bootloader and your N7 is unlocked and recognized, there's a lot of hope. Run these:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that, you'll need to reflash your favorite custom recovery and ROM.
Click to expand...
Click to collapse
Hi Pandae,
Thanks for the reply so good news is fastboot commands work, but now I'm having trouble flashing recoveries and roms.
Flashed twrp 2.6.3.1, and rebooted, but I was still stuck at the google logo when I tried to get into recovery
Tried going to stock
the bootloader flashed to flo-04.02
then tried system and it failed( remote: Unknown chunk type
gonna try some other versions, this just might work.
Fixed
I flashed recovery from the newest stock from the zip and after 30-45 min of the google logo the animation played.
Thanks for the help.
That was a really long time to wait, but still, whew! :good: Gotta love our Nexus devices. As long as you can get to an unlocked bootloader, there are great odds of fixing things at home.
Where did you get the stock ROM? Once you wipe the five partitions I mentioned with fastboot, you can download the stock ROM, then run the "flash-all.bat" file within, without having to worry about individual image files within. The bach file flashes the stock recovery as well as the ROM.
https://developers.google.com/android/nexus/images#razor