Database Users

Nexus 7 stuck at "Google" screen

Hello Forums,
I went on vacation like 2 months ago, and i brought my Nexus with me, and I thought i had lost it. My relatives found it and it was handed to me. With this being said, my nexus was uncharged for the duration of the time, and when i tried to recharge it, it flickered several times and nothing happened. I found that i should hard reset and and put it into recovery mode, but it would always say booting failed.
I searched everywhere and found that i should try and flash the stock image so i looked up several guides on how to do so. On this site i found to use a Wugfresh toolkit. When i tried flashing on both occasions, each time the cmd prompt would come up it would say
sending 'bootloader' <2096KB>....
FAILED <remote: Bootloader is locked.>
finished. total time: 0.012s
rebooting into bootloader....
OKAY
finished. total time:0.021s
<waiting for device>
BUT, my device won't ever reboot. I would always have to press power vol up and vol down.
I noticed that this is a reacurring pattern. I is unable to reboot on its own.I searched everywhere and cannot find a solution.
I am able to get into the menu
FASBOOT MODE
PRODUCT NAME
VARIANT
ETC ETC
LOCK STATE-LOCKED
I would think to unlock it, but it wont ever reboot when i tried to.
I have also tried opening cover to see if the battery wire was loose, it was slightly out of place but i put it back, but same thing.

Since you can access the bootloader, I would recommend learning how to use fastboot. I had a similar situation, and fastboot saved my N7. I'm not that experienced with fastboot, but learning was pretty simple. Search Google for instructions on how to set up SDK. Let me know if you run into any problems, and I'll do what I can to help.

chrisbo4 said:
Since you can access the bootloader, I would recommend learning how to use fastboot. I had a similar situation, and fastboot saved my N7. I'm not that experienced with fastboot, but learning was pretty simple. Search Google for instructions on how to set up SDK. Let me know if you run into any problems, and I'll do what I can to help.
Click to expand...
Click to collapse
im following a guide, but im stuck where i have to update my drivers. since my Nexus is off, when i go into the device manager, all i see is APX under other devices. Do i turn on my nexus in bootloader, or update the APX drivers?
EDIT: I did get the drivers working when i put it into bootloader , so when i look at the device manager i see "Google Nexus 7 Bootloader Interface". When i put in adb devices in the command prompt, i see
List of devices attached
C:\Users\etc\etc\....
I dont get a serial number, i dont know what im doing wrong ):

Arroma said:
im following a guide, but im stuck where i have to update my drivers. since my Nexus is off, when i go into the device manager, all i see is APX under other devices. Do i turn on my nexus in bootloader, or update the APX drivers?
EDIT: I did get the drivers working when i put it into bootloader , so when i look at the device manager i see "Google Nexus 7 Bootloader Interface". When i put in adb devices in the command prompt, i see
List of devices attached
C:\Users\etc\etc\....
I dont get a serial number, i dont know what im doing wrong ):
Click to expand...
Click to collapse
Okay, and the command prompt is where I had some trouble too. Unfortunately all of the tutorials I read assume that that the user already knows how to use a command prompt, which I didn't. So you'll want to make sure your SDK manager has "platform-tools" & "USB drivers" up to date. Also make sure that your factory image has been extracted and placed in the platform-tools folder. I used 7-zip to extract.
When you're in the command prompt, type "cd android-sdk-windows", then "cd platform-tools". From there you're ready to use fastboot. You can type "fastboot devices", and you should (if everything is installed correctly) see your devices serial number displayed. From there you can type the necessary commands to restore your device.

Arroma said:
Hello Forums,
Click to expand...
Click to collapse
android adb folder (password to zip is jt100)
^ download that and extract the Android folder to the root of your C: harddrive (so it'll be C:/Android) this is the main adb/fastboot/whatever folder you'll ever need, ever.
- hold down shift and then right click within the android folder and select "open a command prompt here" (or something like that)
Arroma said:
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed
Click to expand...
Click to collapse
-fyi...the command 'adb devices' is for when your device is booted up to the android homescreen and 'fastboot devices' is obviously when you're in bootloader
-'fastboot oem unlock' is to unlock the bootloader
then, if you have the 4.3 factory image from google on hand...
-extract the initial zip, and you'll get like 5 files
-copy those 5 files to the same C:/Android folder from earlier
-make sure your nexus is in bootloader screen and then just double click the 'flashall' .BAT file (if you're running windows OS) and android will auto wipe and flash everything
-just let it sit and wait for your device to boot to setup screen

chrisbo4 said:
Okay, and the command prompt is where I had some trouble too. Unfortunately all of the tutorials I read assume that that the user already knows how to use a command prompt, which I didn't. So you'll want to make sure your SDK manager has "platform-tools" & "USB drivers" up to date. Also make sure that your factory image has been extracted and placed in the platform-tools folder. I used 7-zip to extract.
When you're in the command prompt, type "cd android-sdk-windows", then "cd platform-tools". From there you're ready to use fastboot. You can type "fastboot devices", and you should (if everything is installed correctly) see your devices serial number displayed. From there you can type the necessary commands to restore your device.
Click to expand...
Click to collapse
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed

Arroma said:
i do see the serial, but now im unsure of what commands to use, the guide said to do oem fastboot unlock, but it failed
Click to expand...
Click to collapse
The command you'll want to use if you want your bootloader unlocked is "fastboot oem unlock" Just a hint, every command should begin with "fastboot". If all you want to do is restore the factory image, I can help you with those commands as well.

You're limited to Fastboot commands when your device is booted to the boot loader. ADB commands only work if you can get booted into Android. You'll have to recover your tablet strictly using fastboot commands. Wugfresh's root toolkit should work now that you have the device drivers loaded. First step is to unlock the boot loader. Then proceed with flashing the factory image.

wugfresh doesnt work, it always fails to unlock, even using the commands, says Unknown Error

Arroma said:
wugfresh doesnt work, it always fails to unlock, even using the commands, says Unknown Error
Click to expand...
Click to collapse
read my earlier post, forget using the damn toolkit

@jt.one I agree using a toolkit is a waste of time, especially when the OP has already accessed fastboot. He's practically done.

mandad since
jt.one said:
then, if you have the 4.3 factory image from google on hand...
-extract the initial zip, and you'll get like 5 files
-copy those 5 files to the same C:/Android folder from earlier
-make sure your nexus is in bootloader screen and then just double click the 'flashall' .BAT file (if you're running windows OS) and android will auto wipe and flash everything
-just let it sit and wait for your device to boot to setup screen
Click to expand...
Click to collapse
Right so, i did everything you said, and it was working, until somewhere along the middle it failed cause its still locked, but i cant unlock it cause it always fails to unlock due to an unkown error ):

After sending fastboot devices, and getting a serial number, send fastboot oem unlock. Then flash a factory image. Here's a good tutorial on how to flash Android 4.3..

Arroma said:
Right so, i did everything you said, and it was working, until somewhere along the middle it failed cause its still locked, but i cant unlock it cause it always fails to unlock due to an unkown error ):
Click to expand...
Click to collapse
even though you did 'fastboot oem unlock'..... your bootloader refuses to unlock?
now that is strange...

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jt.one said:
even though you did 'fastboot oem unlock'..... your bootloader refuses to unlock?
now that is strange...
Click to expand...
Click to collapse
i dont understand either, errors everytime ):

You don't see a fastboot response like this?
Then you'll need to tell us specifically, every error message that pops up.

exglynco said:
You don't see a fastboot response like this?
Then you'll need to tell us specifically, every error message that pops up.
Click to expand...
Click to collapse
i do see that, and i use the power button for yes, here ill copy and paste what i saw on the internet some guy is having the same problem im having, only noone replied to his thread
"My problem is that I cant unlock my bootloader.
This is what I tried:
fastboot oem unlock
This is the result:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
On my device in fastboot it just adds the text "unlocking now......" and nothing happens. If I try to reboot with i.e fastboot reboot-bootloader the device screen is just black, im not sure its even on."
-cant give credit to the guy cause i cant post links yet,
sorry on not being clear enough, i really appreciate your help

Arroma said:
i do see that, and i use the power button for yes, here ill copy and paste what i saw on the internet some guy is having the same problem im having, only noone replied to his thread
"My problem is that I cant unlock my bootloader.
This is what I tried:
fastboot oem unlock
This is the result:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
On my device in fastboot it just adds the text "unlocking now......" and nothing happens. If I try to reboot with i.e fastboot reboot-bootloader the device screen is just black, im not sure its even on."
-cant give credit to the guy cause i cant post links yet,
sorry on not being clear enough, i really appreciate your help
Click to expand...
Click to collapse
You're device wouldn't boot prior to unlocking the bootloader, right? I would try flashing the factory images, then unlocking the bootloader... if that;s possible.

chtfte was
chrisbo4 said:
You're device wouldn't boot prior to unlocking the bootloader, right? I would try flashing the factory images, then unlocking the bootloader... if that;s possible.
Click to expand...
Click to collapse
im not sure i understand, i cant flash anything because its still locked

Arroma said:
im not sure i understand, i cant flash anything because its still locked
Click to expand...
Click to collapse
I apologize, just a crazy idea I had.

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated ​

Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk

Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )

Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid

Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk

I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?

Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet

Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

Bootloop Nexus 4 - Broken Stock Recovery - Bootloader won't unlock

I made sure the drivers are google drivers. I have done this before millions of times.
I swapped cables.
I tried everything.
I always get an OKAY, but no erases. I read that new Android Bootloaders need stock recovery to erase the data and other partitions after an oem unlock, in order to complete successfully.
Only issue is, stock recovery is broken with a red triangle and a dead android robot.
Bootloader version is MAKOZ30f.
'fastboot oem unlock' results in OKAY (as mentioned earlier) then I reboot boot loader and get it back on locked status again! Like NOTHING ever happened.
Is Debugging enabled? No. Because it was fully stock before this (friend's phone). Is that the issue? If so? How can I fix it when I can't get into recovery or even the system!
Hmm... What else?
That's mostly it.
I've tried NRT with no luck. It booted a modified boot.img and attempted to flash stock recovery 5.1.1 to no avail. The phone rebooted back into a bootloop, I shortly saw the unlocked white lock with the Google logo splash, but that was it then bootloooooop.
I have a fair bit of experience with android devices over the years. I am not a newbie, so I do have an intermediate level of knowledge with rooting, recoveries, Custom ROMs and the like.
Thank you guys in advance, I hope this is solvable! Because this is the first bootloop device that has actually gotten to me!
Tl;dr: Nexus 4 stuck in a bootloop. Recovery is broken (red triangle). Bootloader will not unlock (resets to 'locked' after bootloader reboot). Restarting after a bootloader unlock attempts just results in system bootloop again.
Help is gravely needed.

andezzat said:
I made sure the drivers are google drivers. I have done this before millions of times.
I swapped cables.
I tried everything.
I always get an OKAY, but no erases. I read that new Android Bootloaders need stock recovery to erase the data and other partitions after an oem unlock, in order to complete successfully.
Only issue is, stock recovery is broken with a red triangle and a dead android robot.
Bootloader version is MAKOZ30f.
'fastboot oem unlock' results in OKAY (as mentioned earlier) then I reboot boot loader and get it back on locked status again! Like NOTHING ever happened.
Is Debugging enabled? No. Because it was fully stock before this (friend's phone). Is that the issue? If so? How can I fix it when I can't get into recovery or even the system!
Hmm... What else?
That's mostly it.
I've tried NRT with no luck. It booted a modified boot.img and attempted to flash stock recovery 5.1.1 to no avail. The phone rebooted back into a bootloop, I shortly saw the unlocked white lock with the Google logo splash, but that was it then bootloooooop.
I have a fair bit of experience with android devices over the years. I am not a newbie, so I do have an intermediate level of knowledge with rooting, recoveries, Custom ROMs and the like.
Thank you guys in advance, I hope this is solvable! Because this is the first bootloop device that has actually gotten to me!
Tl;dr: Nexus 4 stuck in a bootloop. Recovery is broken (red triangle). Bootloader will not unlock (resets to 'locked' after bootloader reboot). Restarting after a bootloader unlock attempts just results in system bootloop again.
Help is gravely needed.
Click to expand...
Click to collapse
Stock recovery will give you the laying down Android with a red exclamation, once it times out press PWR+VOL UP to get to the recovery menu.
The bootloader probably won't unlock because it can't wipe (a requirement with the fastboot command), or it is locked in the Security settings of the latest stock image. Beginning with Lollipoop, if you are locked you have to tell Android it can be unlocked before doing it, it is a security measure.
You will need to reflash the full stock image, if NRT is failing do it manually, and do it from Linux if possible (no driver issues like Windows), you can get the images here: https://developers.google.com/android/nexus/images
And remember, first boot on Lollipop on the N4 can take 10-15 minutes or more well caches are being built and the OS is settings up (easily 5 times longer than a boot on KitKat), give it time, unless it restarts (a true bootloop) just let it sit. Patience is a real virtue here...
Note, you could have a corrupt or defective flash RAM chip, if that is the case, a full factory flash -MAY- fix it, but no guarantee... If the flash ram is bad, they you might be SOL.

Oh my god. Thank you so much. I am so stupid. I thought stock recovery is broken. But it's not. That's the normal way it should display. And you are right. Holding power then tapping vol up will show the menu
I am such a fool, I've always used custom recoveries, and forgot totally how stock recoveries work ^_^
I am now trying an adb sideload (the factory reset from recovery isn't working, lots of errors).
Gonna try a couple things.
And no I can't flash the images, cause I need to unlock the bootloader (if done through fastboot). Which is my main issue.
Hoping sideload really works!
BUT THANK YOU AGAIN SO MUCH ^_^

Okay. Now I am getting failure to mount /cache and stuff. Lots of problems with the cache partition.
I attempted 2 factory resets. I am now restarting and will report on how it goes. Gonna let the phone take its sweet sweet time booting.
If nothing else works, it really might be a hardware defect, and I really might be SOL @acejavelin
*sigh*
Oh well, all phones come to an end :/

Oh and great work Google on your 'extra precaution' with the whole bootloader unlock thing. Really? Nexuses/Nexii were MADE to be easily unlock-able. If this wasn't a problem... I might have actually been able to format the /cache/ partition, or try something with custom recovery that'd fix this phone quickly. *sigh*

andezzat said:
And no I can't flash the images, cause I need to unlock the bootloader (if done through fastboot). Which is my main issue.
Hoping sideload really works!
BUT THANK YOU AGAIN SO MUCH ^_^
Click to expand...
Click to collapse
When you do "fastboot oem unlock" are you getting a confirmation screen on the device and selecting Yes, or does that screen never pop-up?
Also, for the cache issue, in fastboot try "fastboot format cache" instead of the erase command.
And be aware that on first boot, I have had several Nexus/GPE Lollipop devices not show the setup screen or launcher (just a blank wallpaper) even after waiting 10-15 minutes, a simple reboot and more patience usually corrects this.

I did confirm, and it says unlocked on the phone. After restarting the bootloader it goes back to locked.
Cache: not supported in locked device.
I really cannot do a thing without unlocking the bootloader
Phone is still bootlooping. I gave it lots of time *sigh*

andezzat said:
I did confirm, and it says unlocked on the phone. After restarting the bootloader it goes back to locked.
Cache: not supported in locked device.
I really cannot do a thing without unlocking the bootloader
Phone is still bootlooping. I gave it lots of time *sigh*
Click to expand...
Click to collapse
I forget if unlocking the bootloader forces a reboot or not... If it doesn't, unlock and without rebooting try formatting cache or "fastboot boot recovery.img"" of latest twrp image.
Sent from my Nexus 4 using Tapatalk

That usually just says the device is locked, and that cannot be done on a locked device.
No it doesn't force a reboot!
I will try formatting cache partition again directly after unlocking bootloader (at least attempting). I'll report back if anything is successful.
I've tried flashing recovery as well, but just says cannot do while phone is locked. Will also try again.
Thank you for your help. I appreciate it.

acejavelin said:
I forget if unlocking the bootloader forces a reboot or not... If it doesn't, unlock and without rebooting try formatting cache or "fastboot boot recovery.img"" of latest twrp image.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

andezzat said:
Click to expand...
Click to collapse
After you unlock, do NOT try to FLASH recovery, try to boot it...
fastboot boot <path\recovery.img>
If the bootloader is unlocked, you should be able to push the recovery image over and boot it (not flash it), this will run a temporary copy that you can use to try to format the cache partitions, it doesn't write to the flash partitions to boot it, it all happens in RAM, so even if the flash is corrupt, you -MIGHT- be able to get TWRP loaded and format things to get them working again.
But to be honest, if you can't write recovery, or any other partition (or so it appears), this one might be done... but I don't stick a fork in it until there is nothing more to try.

I didn't notice the boot it part. Okay I am in TWRP now. I can't wipe cache. It is unable to mount cache, data usb-otg, and storage.
Where do I go to format not wipe?

Sideload gives me error: protocol fault (no status).

andezzat said:
I didn't notice the boot it part. Okay I am in TWRP now. I can't wipe cache. It is unable to mount cache, data usb-otg, and storage.
Where do I go to format not wipe?
Click to expand...
Click to collapse
Wipe in TWRP formats, except internal storage and data since internal storage is actually /data/media.
This is bad, if you can't mount cache or internal storage, your flash ram is likely bad.
andezzat said:
Sideload gives me error: protocol fault (no status).
Click to expand...
Click to collapse
Most likely you need a newer adb to use sideload in TWRP... There is a minimum revision of adb required, version 1.0.32 or higher.
Sent from my Nexus 4 using Tapatalk

That was useful! I got adb 1.0.32 but now instead, I get total xfer: 0.00x
Is that it? EOL for this phone? :'(

I don't know if this will help you, OP but here goes - try selecting the partition in TWRP, changing the partition type to something else and then changing it back to ext4. See if that works.
PS: I remember that my N4 refused to boot up to system after I flashed a factory image - it only booted up to recovery which I promptly restarted. Turns out you have to wait till the recovery reboots itself.

Nothing is working right now. I tried changing formats and everything. It's just unable to mount any of the partitions. And now they're all stuck on 0mb size.

I have an otg usb. It won't even detect or mount it at all. I can't even choose it instead of internal storage. This phone is beyond gone :/

I get constant ERROR=8 from e2fsck whenever I try to resize or repair. Probably has something to do with the phone not being REALLY unlocked.

I'm starting to wonder if this might be a corrupt image of your radio or the bootloader... Flashing it (if it's possible) might be risky in your situation but at this point in time I don't know if you can do much else than try.

[solved] Can't unlock bootloader / flash recovery

EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
The phone is working perfectly again.
Also, if this problem appeared when you tried flashing OOS 3.0, check out this guide.
I did a lot of google research, found a lot of stuff and I'm still stuck at my problem.
Some background information:
I wanted to flash the new Oxygen OS 3.0 Community Build, decided to perform a clean install (full wipe with system, cache, dalvik and data).
Went into TWRP, wiped phone, installed OOS 3.0 - worked.
Made my initial setup, then I wanted to boot into recovery - didn't work.
Then I booted into fastboot, tried fastboot oem unlock, it said:
fastboot oem unlock
...
OKAY [ 0.014s]
finished. total time: 0.014s
Click to expand...
Click to collapse
Afterwards I checked fastboot oem device-info:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.080s]
finished. total time: 0.080s
Click to expand...
Click to collapse
That means still locked.
The phone won't boot up by itself.
I had to go in fastboot, and then use "fastboot continue" to get into the OS.
At the beginning, I forgot to enable the 'Allow OEM unlock' option in developer settings, it is now enabled but effect remains the same.
My question:
How do I fix my obviously broken recovery? How can I reflash it with a locked bootloader or how do I even unlock the bootloader.
PLEASE do not link me to the unbrick guides - the device is NOT bricked - it boots up with fastboot continue and also shows up as ONE A2003 when connected to pc.
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Thanks in advance for your help & ideas!

Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS

Tierri said:
Hi man, what a mess did you did
I have been in that situation. (Stock in fastboot/boot logo with bootloader locked and oem unlocking disabled in seetings).
The only thing that worked for me was the naman bahlla tutorial to unbrick hard bricked devices. (The 3rd method).
The link is this one: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Anyway you can ask naman bhalla help in that thread. He will help you.
TS
Click to expand...
Click to collapse
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
hum. Ask Naman Bahlla for help.

GerRudi said:
Thanks for your reply.
I've seen the guides from Bhalla, but I don't think that fits for me...
because the device still boots up with a little trick, so apparently only the recovery is broken.
It does not show up as an unknown devices or qualcom device or anyting in device manager.
In fastboot, nothing shows up in Device Manager.
When booted, it shows up normally as ONE A20003
Click to expand...
Click to collapse
When you try to flash a recovery, what error message do you get? Curiosity question.
But I'm gonna have to echo Tierri to use that unbricking method. I get you're not bricked, but that will work to fix your issue. To get the Qualcomm device thing to show in device manager, power down your phone completely. Then connect the USB cable and press VOL UP (don't press power). You should hear the Windows connection chime. Also make sure you're booted up with Windows Device Driver Signature check turned off.
EDIT: I've followed these directions in the past: http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543

I did the same thing.
Only way is boot to system (fastboot continue) backup all files from internal memory to pc,
Restore device completly as Tierri said using method 3 unbrick guide.
Unlock bootloader in system (oos 2.2.1 or 2.2.0).
and flash oos 3.0 beta with twrp from that thread: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Thanks for all your replies!
As you all suggested, I decided to go through the Bhallas unbricking guide on the OnePlus forums.
This seemed to be the quickest solution out there.
I'll update the Original post with the solution, thanks.
If mods see this, thread can be closed, tagge the thread as solved.

The real op oem fix
follow these steps:
1. launch your cmd
2. plug out your phone
3. power it off
4. power into fastboot
5. plug it into the pc
6. type these commands
"adb start-server"
"fastboot devices" (your device should show in fastboot)
"fastboot oem lock" (this will reboot your phone and reset everything make sure you backup if you need to)
7. skip all OP setup steps(skipping these steps saves your time cause this process will have to be done twice also put into DEV mode and allow usb debugging)
8. once you on your homescreen power off your OP
9. plug it out of the pc
10. put it back into fastboot
11. type these commands before plugging back into pc
"adb kill-server"
"adb start-server"
12. plug it back into the pc and type these commands
"fastboot devices"
"fastboot oem unlock" (sometimes it will prompt you in some kind of asian language asking if you want to reset all your data just click the first option this will also reset your phone again)
that should fix the OEM boot unlocker now
i made this solution my self after troubleshooting like crazzy cause i had the same problem like you but didnt have to do all the extra bs with download random crap that does not really help
~xjinx216

is your bootloader unlocked now after following naman's process? please help, i've been having the same problem for ages.

I'm having this issue as well. Tried every driver and just can't seem to unlock bootloader. Adb seems to work, can boot into fastboot but then it always says fastboot cannot be detected when I try anything. Or it gets stuck on waiting for device. I just want to get this thing rooted????

Im having the same issue and my device IS bricked (and im sure i may have somehow deleted my OS) And i can't do anything to fix it, but if i deleted/corrupted my OS can it still be oem locked?

Solution
GerRudi said:
EDIT:
Soulution
If you stumble upon this thread while searching for your problem...
There is no specific solution for this problem.
Allthough the phone isn't bricked, you still should do the unbreaking Method 3 in Naman Bhalla's thread on the OnePlus forums (LINK)
Click to expand...
Click to collapse
I had about the same problems with my phone (oem unlock shows okay but doesn't unlock, directly booted the not working recovery) i was then able to boot to system with "fastboot continue".
Solution i found (root needed): flash stock recovery (from oneplus 2 downloads section) in rom with "dd" command and do a oem unlock, it will then boot to stock recovery, where you have to confirm the unlock (works with all roms but only with stock recovery).
command used to flash recovery (in android terminal emulator, adb should work too): dd if="location of recovery.img to flash" of=/dev/block/bootdevice/by-name/recovery
You can also flash twrp on a locked bootloader like this (just make sure to have a stock recovery ready on the device).
You might want to include this in front page.

GerRudi said:
EDIT:
What works:
+ getting into the OS (via fastboot continue)
+ getting into fastboot
What doesn't work:
- unlocking via fastboot oem unlock
- flashing a recovery (device is locked)
- booting into recovery
Click to expand...
Click to collapse
I got into exactly the same situation now, the problem is that "Method 3 in Naman Bhalla's thread" is not working for me as it break on "sahara error". Actually the message says to restart phone and retry, but I'm always getting into this error again and again. I already tried to reinstall drivers many times and I'm running in testing mode... what else I can try to solve this? (Windows 10 Pro)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Recent Firmware Update Failed - Onn 7" Surf gen 2 10015685

Anybody else have the gen 2 7" Onn tablet from Walmart and get a recent firmware upgrade (within the past few weeks)?
I have two of these devices. I got them all set up and secured for my two young kids for Christmas presents. Between when I finished configuring them and Christmas morning, some kind of update was pushed out. Now every time I start them up, I get a notice to try to install a firmware upgrade. The kids can't bypass it easily and it has become quite the inconvenience. When I try to complete the update, it fails.
I'm running both the tablets with unlocked bootloaders and rooted with Magisk. I assume this is why the update fails. If it even is a real update. The link in the message goes to an RCA website that doesn't exist. I don't care about the update, but I hate that it tries to install it every time I boot up the tablets. I have disabled "Automatic System Updates" from Developer Options. I have the Google Play store disabling auto-updates as well. I don't want to re-lock the bootloader and have to then unlock it again, and re-install/configure the tablet from scratch again.
Anyone have any ideas on A) how to get the update to work or B) How to ignore the update and get it to stop bothering me? I'm happy to push a new system image if anyone has successfully figured out what can be updated.
Here's what is displayed on the screen and what the update process shows. My guess is the problem lies with the patched boot.img but I'm not ready to wipe it back to stock yet because I'm not good at pulling it back off. Luckily after failing to update I can reboot without trouble. Also I can dismiss this message easily, but my kids can't, and it seems to be unpredictable when it will actually pop up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.

Okiera29 said:
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Click to expand...
Click to collapse
From the error messages I get I'm guessing it's a problem with the boot.img as it's patched by Magisk. I can reflash the stock boot.img but then I loose root. If it does update, I don't have root and am not skilled enough to pull the new updated boot.img without root.
If anyone out there has a good tutorial on doing that I'd be happy to try to get the new updated image files to flash.

I'm having a related issue with the same tablet (10015685-E): I got the request to update the firmware, accepted, it appeared to install over the course of ~5 minutes, and after reboot, it is now stuck in an infinite loop in which it boots to the onn logo screen, goes black, and repeats. I assume it's crashing during boot.
I am able to enter recovery mode (see attached pic), but doing a cache wipe and factory reset from the recovery screen did not remedy this sad state of affairs.
I'm happy to load a stock ROM if that would restore functionality, but I don't have one. Any advice welcome. Thanks.

chromoly said:
I'm having a related issue with the same tablet (10015685-E): I got the request to update the firmware, accepted, it appeared to install over the course of ~5 minutes, and after reboot, it is now stuck in an infinite loop in which it boots to the onn logo screen, goes black, and repeats. I assume it's crashing during boot.
I am able to enter recovery mode (see attached pic), but doing a cache wipe and factory reset from the recovery screen did not remedy this sad state of affairs.
I'm happy to load a stock ROM if that would restore functionality, but I don't have one. Any advice welcome. Thanks.
Click to expand...
Click to collapse
Do you have the stock ROM? You can try to just flash the boot.img which isn't altered during a factory reset. It would reverse the update but it appears the update isn't working anyway.

PleaseBeNicetoMe said:
Do you have the stock ROM? You can try to just flash the boot.img which isn't altered during a factory reset. It would reverse the update but it appears the update isn't working anyway.
Click to expand...
Click to collapse
I don't; I'd appreciate a link to the stock ROM or boot.img. Thanks.

chromoly said:
I don't; I'd appreciate a link to the stock ROM or boot.img. Thanks.
Click to expand...
Click to collapse
You can try my files from here
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com

PleaseBeNicetoMe said:
You can try my files from here
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
Click to expand...
Click to collapse
Thanks. I got your files and tried a couple of things, neither of which worked:
I tried loading your stock image via ADB, but got "Signature verification failed. Error 21" after loading.
I tried flashing just magisk_patched boot.img via ADB in fastboot mode, but got "Download is not allowed on locked devices".
So perhaps the device has to be unlocked before #2 will work. Any thoughts on #1?
Thanks again.

chromoly said:
Thanks. I got your files and tried a couple of things, neither of which worked:
I tried loading your stock image via ADB, but got "Signature verification failed. Error 21" after loading.
I tried flashing just magisk_patched boot.img via ADB in fastboot mode, but got "Download is not allowed on locked devices".
So perhaps the device has to be unlocked before #2 will work. Any thoughts on #1?
Thanks again.
Click to expand...
Click to collapse
Did you try flashing the boot.img this way with the vbmeta.img first?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot boot.img
fastboot reboot

For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
I appreciate the help.
Code:
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.001s
$ fastboot erase cache
erasing 'cache'...
FAILED (remote: Erase is not allowed on locked devices)
finished. total time: 0.000s
$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
$ fastboot flash boot ../magisk_patched_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (9152 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.000s

Ok, here's one. I have the same tablet, not rooted, not modified, just stock. The update fails because it says update.zip isn't found after the download... Anyone have a way to fix? After the error, the whole tablet locks up and I have to force reboot...

chromoly said:
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
I appreciate the help.
Code:
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.001s
$ fastboot erase cache
erasing 'cache'...
FAILED (remote: Erase is not allowed on locked devices)
finished. total time: 0.000s
$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
$ fastboot flash boot ../magisk_patched_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (9152 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.000s
Click to expand...
Click to collapse
The stock boot.img should be in the STOCK ROM .zip file in my GDrive folder above. I reuploaded it just in case.
My guess is the bootloader is locked. Did you unlock it before? Try running
fastboot flashing unlock
Follow the prompts. If that worked then try flashing vbmeta and the other steps from above. That's my only idea right now.

chromoly said:
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
Click to expand...
Click to collapse
If you did not unlock your bootloader before all this happened, then I believe you will not be able to flash via fastboot commands. You can try to use the SP Flash Tool to install the earlier stock ROM. If you look through my thread from earlier, you will find a full dump of the original pre-update ROM
Try this post... Hang on, that was for the A variant. Look for a post by Fred, he dumped the entire ROM with scatter file(needed for SP tools to function properly) You may still need my super.img referenced below
Do not use the one from Tytydraco as it is for the A variant of the tablet and will cause some screwy issues(personal experience on my E variant) If you are looking for the super.img you can use the one I pulled from my tablet.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com

Okiera29 said:
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Click to expand...
Click to collapse
We're you ever able to find a work around? I may have fixed it, at least this works for me because I don't care about the update ever. I don't know your level of expertise with these. I'm definitiely just proficient enough to be dangerous. I can give more details than this if you need it.
You'll need a rooted tablet with Magisk and the Terminal Debloater (Terminal Emulator) module installed.
Start your Terminal Emulator app (I use Termux), type su (grant superuser if you haven't already) and start the Debloater by typing "debloat"
From the menu I choose 1 - System Apps and for me on the second menu #13 is Firmware Update
Choose that to uninstall, restart the tablet, and the popup error is gone!
This works for me for my 7" version. I have a 10" version too that doesn't have the same app, but it's called Wireless Update, and I uninstalled that using the same process successfully.
It's a great way to ge tall those pesky Walmart apps off too, PLUS I disabled the extra Walmart nav button (It didn't disappear but nothing happens when tapped, so it's one less thing to help my kids escape from when they get stuck in it).
Hope this helps a bit.

PleaseBeNicetoMe said:
We're you ever able to find a work around? I may have fixed it, at least this works for me because I don't care about the update ever. I don't know your level of expertise with these. I'm definitiely just proficient enough to be dangerous. I can give more details than this if you need it.
You'll need a rooted tablet with Magisk and the Terminal Debloater (Terminal Emulator) module installed.
Start your Terminal Emulator app (I use Termux), type su (grant superuser if you haven't already) and start the Debloater by typing "debloat"
From the menu I choose 1 - System Apps and for me on the second menu #13 is Firmware Update
Choose that to uninstall, restart the tablet, and the popup error is gone!
This works for me for my 7" version. I have a 10" version too that doesn't have the same app, but it's called Wireless Update, and I uninstalled that using the same process successfully.
It's a great way to ge tall those pesky Walmart apps off too, PLUS I disabled the extra Walmart nav button (It didn't disappear but nothing happens when tapped, so it's one less thing to help my kids escape from when they get stuck in it).
Hope this helps a bit.
Click to expand...
Click to collapse
Worked like a champ on both tablets. I only use them for reading, light gaming and watching youtube in bed. So like you, the updates are not imperative for me.