So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect
The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7
I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.
I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.
chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.
I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!
Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2
Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas
Related
Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App
I am not a computer guy--tried to install latest update and am now stuck in recovery--I tried to install a recovery off an sd card but seemed to fail and now cant get anywhere. Can anyone walk me through a fix??
Thanks
press ctrl+alt+del
not suer
Need more info. Were you on a stock or custom ROM? Are you stuck in stock or custom recovery? What method did you try to install another recovery?
Sent from my SGH-I777 using xda premium
stuck
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
this worked for me...my situation sounds very similar to yours....
http://forum.xda-developers.com/showpost.php?p=23587495&postcount=47
ostism attachable
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
voodoo_dr said:
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
Click to expand...
Click to collapse
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
voodoo_dr said:
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
Click to expand...
Click to collapse
Why you trying a stock ota on a custom rom?
feisty_noodle said:
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Click to expand...
Click to collapse
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
tegezee said:
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
No, this is overkill and won't fix his issue.
This will work period
fone_fanatic said:
Why you trying a stock ota on a custom rom?
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
No, this is overkill and won't fix his issue.
Click to expand...
Click to collapse
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
tegezee said:
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
Click to expand...
Click to collapse
His problem is with it getting stuck in recovery, which is a known issue with Koush's 5.5.0.4, simple fix with adb. No need to reflash the whole rom.
voodoo_dr said:
I am not a computer guy
Thanks
Click to expand...
Click to collapse
Well if he's not good with a computer, my method is the easiest especially if he doesn't have it figured out by now...
Thanks for the help everyone--Ended up using NVflash to load a rom called prime 1.6. 3:30 a.m. and I am as good as new. No ICS but at least it is stable
Good to see you got it back working...
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
fredphoesh said:
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
Click to expand...
Click to collapse
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
abdel12345 said:
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
fredphoesh said:
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
Click to expand...
Click to collapse
Your welcome I'm glad you got it working. Make sure to that k wugfresh as well for his awesome tool
Sent from my Nexus 10 using xda app-developers app
OK so I know there is A TON of info on these forums.
I searched around but I did not see anything similar to my situation.
If there is a thread, please just link it and ill delete this thread.
Basically I had rooted my N7 back earlier this year and had a custom rom as the 5.0 OTA made my N7 run like crap.
It was fine until the last few months, it got REALLY slow. I didnt update it, or mod it other then flashing the roms.
So I set out to get a new rom. I figured id try the 6.0 AOSP rom.
DL it, as well as the GAPPS and tried to install it. All I ever got was a continuous error saying, "setup wizard has stopped".
Searched some more and saw that someone fixed it by installing a bare bones GAPPS and then WIPING Dalvik and cache immediately after flashing GAPPS.
I did this and no change. Still an error.
So I noticed that when I was in Windows, my N7 showed as having 5+/- gigs free out of 13gb.
So I figured let me wipe this whole thing clean and start fresh.
BTW- this has all been done with Wugfresh toolkit.
So I went ahead and erased/ formatted and planned to return to stock and then re-root and flash a 4.44 rom as I saw that on the grouper nothing over 4.44 works great and all I want is a stockish N7 that stays fast and works 100%.
Well now all I get is the Google scree with the Unlock icon and a green start icon and when you try to go into bootloader it says booting failed in upper left corner.
Any ideas hahaha.
Thanks!
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
twics said:
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I had the latest twrp recovery, I think 2.08 ?
I can't seem to get to the recovery screen.....only the bootload screen.
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
twics said:
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
NO!! Your device is not toast if it powers on then it should be recoverable, my advice forget WugFresh check out this page on how to get TWRP installed> https://twrp.me/devices/asusnexus72012wifi.html for latest twrp recovery, on this page you will find info how to get ADB running properly, once you have Twrp recovery installed try this Rom it is stock Lolliopop and runs great better than previous ones http://forum.xda-developers.com/nexus-7/development/rom-t2931064
---------- Post added at 02:00 PM ---------- Previous post was at 01:54 PM ----------
Please let me know how you get on. also if you get TWRP installed wipe everything apart from internal storage before install Rom.
1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
twics said:
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
1993cb7 said:
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
Click to expand...
Click to collapse
OK Im back. Roughly an hour and a half. Not bad.
So what I did(if you're stuck on the bootloader screen like me)
Updated to the latest version of Wugfresh.
Made sure it updated all of the files it needed etc.
I then went through the process of uninstalling and reinstalling the drivers for ADB etc. I actually had an issue with it not detecting my device so it recommended installing the generic Google drivers....I did that.
Even after doing that, when I would check ADB connectivity it would say no devices found. I remembered that sometimes it would still communicate with the device even though it said nothing was found. I decided to do a fastboot format under advanced utilities because I knew that i erased it previously and I think that is where I ran into problems.
Sure enough adb found my device and formatted the bootloader no problem. I then continued with the restore to stock/w boot loop function and had patience...it took FOREVER to load the system image and then it took like 10 minutes to reboot but it did and I have a fully functional device right now.
I logged in and turned USB debugging on and re-locked the device. I then did a system wipe from inside the system and will sell it tomorrow.
So have faith, its not over till its over.
and p.s. I changed the USB port that I was plugged into. I have a USB hub that I usually connect too but I figured id connect directly to a USB port on the machine. Not sure if that helped, but people recommend it anyway.