Related
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.
Take a look at the restoring to stock section of the guide in my sig
Sent from space
Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk
i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.
i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody
More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.
you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working
Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)
hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...
Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...
Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even get to the red android error screen.I am forever stuck at the GOOGLE screen or a blank one. When stuck at the google screen it is recognized as Nexus7 but when i try to reset to bootloader (black screen) its QHSUSB_DLOAD.
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
vinland123 said:
New to the forum but regularly read it.
I think I may have hardbricked my nexus 7. I was originally trying to root the phone. However, I somehow got into a bootloop before I was able to install superSU (http://forum.xda-developers.com/showthread.php?t=2382051). Attempted to factory reset because the internal memory was always at 0. However, this always failed.
To fix that I consulted this: (http://forum.xda-developers.com/showthread.php?t=2380913). Same issue happened and it was unable to fix the problem. And I would be stuck in bootloops with the X logo. I did another attempt with this because it seemed to help others with my problem (http://forum.xda-developers.com/showthread.php?t=2381438). However, after going through the steps and factory clearing the data I was stuck at the GOOGLE logo and never able to boot into the bootloader.
After I tried to hold the power and VOLup button i still get to the android with the red triangle screen HOWEVER i am unable to get any menu to reboot the device or clear data. After shutting the device down I am now unable to even turn it on. My device manager recognizes the nexus 7 as "QHSUSB_DLOAD"
Obviously, i screwed up, is there any way to fix this or am I out 240 bucks?
Unfortunately its even harder because this nexus 7 isnt available outside the US.
Click to expand...
Click to collapse
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
cgehring said:
I'm sorry to hear about your nexus 7. I hope we can get it working. Have you tried holding VOLdown and power button? It should get you into fastboot mode. If you can get that we should be able to do something. You may have to hold them down for quite a while so if nothing happens at first keep holding it for 20 seconds or so.
I think the reason you got the android with the red triangle is because there wasn't a custom recovery installed yet.
Let me know what happens and we can go from there.
Click to expand...
Click to collapse
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Aria807 said:
http://forum.xda-developers.com/showthread.php?t=2381582
Here is your solution
Click to expand...
Click to collapse
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
vinland123 said:
Gonna give it a shot. See what happens. Ill let yall know. Guess i ought to give up on rooting at least until bugs are worked out?
Click to expand...
Click to collapse
If you can get to your bootloader, and follow directions, then the above will work. Good luck!
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Why did you try to install the factory images from the old Nexus 7?
vinland123 said:
It worked! I can finally use it again.
I am still peeved i couldnt root my phone. I have bootloader unlocked still apparently. I obviously am not the most skilled at this but maybe there is a less error prone way to root it? I want access to a few nice apps/features with root access.
The problem I had came with TWRP and getting boot loops (with 0 internal storage). Any tips or alternate methods to rooting?
Click to expand...
Click to collapse
Glad to hear you got it running again!
http://forum.xda-developers.com/showthread.php?t=2381438
Try this. I had the exact same problem as yours and I fixed it. This works!
vinland123 said:
OMG, finally got to the bootloader. I was beginning to freak out. I can access bootloader, at least its not hardbricked. Thank you. I am in your care for getting this fixed (im way in over my head). Thank you.
It definitely cannot go into recovery mode like you mentioned. I reinstaled TWRP recovery. I then tried to install the nexus 7 "nakasi" factory image, however, I am still in a GOOGLE screen boot loop and I had to reinstall the TWRP recovery afterwards. I still have the 0mb internal memory error. I cannot wipe data successfully either (says Failed when I try) So I am not sure where to go from here, feel like giving up on root and just go for the original factory state. Once again, thank you.
Click to expand...
Click to collapse
Not sure if you are clear on this or not but the Nakasi image is for the old Nexus 7. The new Nexus 7 is named Flo and the official Google image will have that as part of the file name (Google still hasn't released a factory image for our device though. However, there are a few unofficial versions floating around on the forum).