First of all, I'd like to apologize if I'm breaking any forum rules. I just hastily made this account because I did something stupid and I need your help.
I rooted my Nexus 7 a few days ago, and it all went well. While looking through root apps on the Play store today, I found a font switcher. It looked alright, so I figured I'd download it. I picked out a font, hit install, and the device rebooted as I would expect. It showed the Google logo, as well as the padlock icon, and then went to the "X" as per usual. However, it stayed on that screen for quite a while and would not start up. The bootloader menu still works, but I can't really do much with it. I'm afraid I had USB debugging turned off as well. Please help, I don't have a clue what to do and I don't want to have it permanently bricked less than a month after buying it. Thank you in advance.
P.S. You'll have to explain the terms to me, rooting is sort of a new area for me.
Factory reset ?
hyperxguy said:
Factory reset ?
Click to expand...
Click to collapse
I wouldn't mind doing it, but I can't as I can only access the bootloader menu and I don't have any recovery programs installed.
I'm not very familiar with stock recovery (assuming that's what you have. I've never seen the stock recovery since I wiped stock off my tab as soon as I could). But doesn't it have a factory reset option ? (I thought I saw that on my old N7 when it was still on stock form)
Edit: you can get to stock recovery from the bootloader menu. Just use volume up/down to rotate thru menu options and hit power to select.
hyperxguy said:
I'm not very familiar with stock recovery (assuming that's what you have. I've never seen the stock recovery since I wiped stock off my tab as soon as I could). But doesn't it have a factory reset option ? (I thought I saw that on my old N7 when it was still on stock form)
Click to expand...
Click to collapse
I tried entering recovery mode and I got an error icon, then after a while it just rebooted.
Is your tab OK now ?
Don't worry too much, it's very difficult to "brick" a N7.
You may look at this tool:
http://forum.xda-developers.com/showthread.php?t=2389107
It's easy to do many things.
The hardest part would be to get your PC to fully recornize your tab (which you're there, since you rooted the tab).
If you don't mind losing data, you can just flash stock back from fastboot. If you want to try factory resetting, you can flash a recovery image from fastboot, then reset from there. Fastboot is done from the bootloader.
hyperxguy said:
Is your tab OK now ?
Don't worry too much, it's very difficult to "brick" a N7.
You may look at this tool:
http://forum.xda-developers.com/showthread.php?t=2389107
It's easy to do many things.
The hardest part would be to get your PC to fully recornize your tab (which you're there, since you rooted the tab).
Click to expand...
Click to collapse
Yes, it's fixed. I found a recovery tool in WugFresh's toolbox.
Related
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en
Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?
RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!
*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?
is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app
Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.
Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.
Ok, so I have a 32gb 2013 Nexus 7 which is now bricked and i didn't do anything to brick it! Really!
It's stock, not even rooted... nothing. Never got around to doing anything to it... just left it alone.
So last night it was having trouble connecting to my home wifi so I rebooted it. When it came back up, it got stuck at the white "Google" logo, and ... nothing... no animation, no nothing.
I left it for the day and came back, and it's still doing that.
So - dug a little and decided I'd do a hard reset.... i can get into recovery (stock), i cleared the cache... but now when I try to wipe data/factory reset... it gets stuck there too.
I've got the Android guy with "Erasing..." below him. A blue progress bar that is NOT MOVING and text ...
-- Wiping data...
Formatting /data...
and that's it just sits there.
have tried it twice already and nothing.
Any suggestions?
Download this: http://www.mediafire.com/download/2cg91ny5uidzodw/NRT_v1.8.2.sfx.exe
http://www.mediafire.com/download/xuozv5l1o5q14yi/PdaNetA4150.exe
You can use it to restore to stock without using recovery mode. As you open it you have to download some packages(just accept).
I will attach an image below to show you what it should look like.
Secondly you need to enter bootloader mode as shown in this video: https://www.youtube.com/watch?v=VV1ffMCXRg4 (Skip to 2:30)
Basically you make sure the tab is off then press the volume up button then press the power button and hold both.
Back to the Nexus Root Toolkit. Click Flash Stock+ Unroot while having the Status as: Soft Bricked/Bootloop just like in the picture below.
Just accept all the request made by the program and you should be fine.
@kenrothman don't worry, your N7 will be fine. Our device has a bit "nervous" /data partition. The method from the post above should work.
Alternatively, you could also do some other methods with price of data lost but try this first.
tetakpatalked from my N7100
can't seem to do this because my bootloader is locked.
100% stock, this one is.
i tried to unlock the bootloader, because at this point it's ok if i have to wipe everything...
but it just hangs on the "yes" "no" page after i select "yes" and hit the power button.
ugh.
kenrothman said:
can't seem to do this because my bootloader is locked.
100% stock, this one is.
i tried to unlock the bootloader, because at this point it's ok if i have to wipe everything...
but it just hangs on the "yes" "no" page after i select "yes" and hit the power button.
ugh.
Click to expand...
Click to collapse
Did you ever use ADB / fastboot? I prefer to do such things manually as the tools might do something else than I want.
If you didn't use it yet, there is an excellent guide by comminus for N7 2012 how to flash factory image with fastboot.
Find it and in the beginning is the part with installing drivers, SDK etc. That part is identic for the N7, also bootloader unlocking.
tetakpatalked from Nexus 7
Any updates yet? In the bootloader (if you can get to it) does the line "LOCK STATE" say locked or unlocked?
Localhost798 said:
Any updates yet? In the bootloader (if you can get to it) does the line "LOCK STATE" say locked or unlocked?
Click to expand...
Click to collapse
fastboot oem unlock
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Try to ADB Sideload the files to the nexus If your pc can't detect a device or the drivers are not set up correctly.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Wugs Tool kit
Why not use it to fix your device.
Heres the link: http://www.wugfresh.com/
sorry, didn't have much time over the weekend.
i had previously tried to use 'fasboot oem unlock' on my mac, but that hangs as well.
i'm beginning to think this may be a hardware issue... i did a support chat session with google who basically told me i had done everything they could think of and they sent me to Asus. I haven't tried with them yet.
I'm willing to completely wipe the thing to bone stock at this point... i mean, i hadn't even rooted it... never felt the need to.
The "factory reset" from recovery really should just stomp on it, but that hangs too.
I will probably give Asus support a shot... esp if it's hardware and needs to be replaced or whatever.
Hey guys, I've combed through so many sites and threads and I'm still lost. I bought this tablet from a company that went out of businesd. It's got airwatch installed and is pretty well locked down. It won't allow a factory reset via recovery mode and I can't even access the settings on this thing as they are disabled by it admin. The previous owners company is completely dissolved so I can't go to them for an admin password. This thing is locked to home screen only, no long press options, nothing but a small handful of useless corporate apps.
My question is this, is there anyway to wipe this thing of the admin lockdown? I'm not proficient with this stuff. But I'm not incompetent about it either. Please help! And thanks in advance.
Is there any way to completely wipe it with odin? Or a way to flash or sideload autoroot or something similar?
Note 10.1 2014 edition P605V
Kinda strange that you can't wipe it to factory through recovery mode. If it were me then, I'd get the same stock version firmware and get into download mode then odin/flash the stock firmware on it and see if that'll take. Hope this helps!
Aftrburnr said:
Kinda strange that you can't wipe it to factory through recovery mode. If it were me then, I'd get the same stock version firmware and get into download mode then odin/flash the stock firmware on it and see if that'll take. Hope this helps!
Click to expand...
Click to collapse
I'm gonna try that again, but last night I was getting a message about MDM not allowing it....it's terribly frustrating...almost to the point of removing the back cover and removing the battery LOL
Hey guys I've been on the XDA forums for a while to use XDA Labs, as well as get kernels and rom's for my Pixel 2 XL
I decided to factory reset to bring my phone back to a complete stock feel and now it won't go past the G logo with the loading grey bar.
I had Magisk and Kirisukura kernel installed. But prior to factory resetting I
1. Uninstalled Magisk, through TWRP and the magisk uninstaller.
2. Reflashed stock boot img to bring it back to an essentially stock phone with no modifications whatsoever.
The only thing that I'm thinking might have caused this is that I factory reset via the phone settings as opposed to clean flashing a factory image via ADB but I didn't think that mattered?
Regardless, no matter how long I leave the phone it doesn't go past the G Logo with the grey loading bar (Note: the bar does move and isn't frozen).
I've tried booting in recovery mode and wiping/factory resetting from there but regardless of what I do it doesn't seem to allow the phone to boot up.
Any help would do I really love this phone and it would break my heart knowing I've hard bricked it, the bootloader is unlocked as well but I don't think ADB works because I haven't been able to boot into the phone to allow USB debugging which is frustrating.
Thanks in advance for any help/replies
MrPariah said:
Hey guys I've been on the XDA forums for a while to use XDA Labs, as well as get kernels and rom's for my Pixel 2 XL
I decided to factory reset to bring my phone back to a complete stock feel and now it won't go past the G logo with the loading grey bar.
I had Magisk and Kirisukura kernel installed. But prior to factory resetting I
1. Uninstalled Magisk, through TWRP and the magisk uninstaller.
2. Reflashed stock boot img to bring it back to an essentially stock phone with no modifications whatsoever.
The only thing that I'm thinking might have caused this is that I factory reset via the phone settings as opposed to clean flashing a factory image via ADB but I didn't think that mattered?
Regardless, no matter how long I leave the phone it doesn't go past the G Logo with the grey loading bar (Note: the bar does move and isn't frozen).
I've tried booting in recovery mode and wiping/factory resetting from there but regardless of what I do it doesn't seem to allow the phone to boot up.
Any help would do I really love this phone and it would break my heart knowing I've hard bricked it, the bootloader is unlocked as well but I don't think ADB works because I haven't been able to boot into the phone to allow USB debugging which is frustrating.
Thanks in advance for any help/replies
Click to expand...
Click to collapse
Is OEM unlocking turned on in developer options?
If so, have you tried fastbooting the factory image?
Did you try a few hard restarts with the power button?
Badger50 said:
Is OEM unlocking turned on in developer options?
If so, have you tried fastbooting the factory image?
Did you try a few hard restarts with the power button?
Click to expand...
Click to collapse
Did a few hard restarts with the power button and and then tried flashing a factory image and it worked. Phone is up and running and working well thank you very much! How do I let a mod know to close this thread now that it is solved?
MrPariah said:
Did a few hard restarts with the power button and and then tried flashing a factory image and it worked. Phone is up and running and working well thank you very much! How do I let a mod know to close this thread now that it is solved?
Click to expand...
Click to collapse
The mods will see your post, and then decide if they want to close it or not. However, you'll likely not be the last user that this will happen to, so, they may very well leave it open for future reference
Hello @MrPariah,
We can absolutely leave the thread open since other member could use it for future questions / help.
If you have time, I suggest you to edit the thread title by adding [SOLVED] and you can even edit the 1st post yourself with the correct procedure to fix the initial issue ("...won't go past the G logo with the loading grey bar."). It may help other members with the same issue.
But if you still want to close the thread, you can send me a private message and I will do it.
Please let me know
MrPariah said:
How do I let a mod know to close this thread now that it is solved?
Click to expand...
Click to collapse
In case you need to request a thread closure (or XDA rule violations), you have to use the report button (using a web browser), any moderator available will handle it.
Thanks
Wood Man
Senior Moderator