So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
Cant find valid operating system
The device will not start
Click to expand...
Click to collapse
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you
When you say 'adb', do you mean you're trying to use the command 'adb' when you're in fastboot? At the risk of stating the obvious, you need to use 'fastboot' command when you're in fastboot mode. 'adb' is only used when you're in recovery or in the actual android system. Otherwise you may wish to try a different fastboot version (sometimes that matters).
Javi22 said:
So I was stupidly trying to relock bootloader, and somehow I ended up hardly bricked
Please tell me If I can do anything...The problem is:
I can get into fastboot, but when connect to PC, it recognizes some device, but is not working properly, adb is not finding the device
Not problem of the drivers or the cable, because I have managed to connect to adb before, and also trying right now with other phone. Adb recognizes as soon as I enable USB debugging
Thank you
Click to expand...
Click to collapse
TOOL_ALL_IN_ONE_1.1.1.3.zip it's the solution,Block again from here and you can start over
Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
So my problem now is to unlock the bootloader
Javi22 said:
Ok thank you for the answers. I missconfused about adb and fastboot. So yes, fastboot is working. But If I try to unlock bootloader in order to flash the image, it is not working. I tried these 2 commands:
So my problem now is to unlock the bootloader
Click to expand...
Click to collapse
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:
Badger50 said:
Get rid of minimal adb, and use the most recent platform-tools version 28.0.3 :good:
Click to expand...
Click to collapse
Thank you! But still the same...:
Code:
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot devices
711KPDT0682490 fastboot
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>fastboot flashing unlock_critical
FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
C:\Program Files (x86)\platform-tools_r28.0.3-windows\platform-tools>
Javi22 said:
Thank you! But still the same...:
Click to expand...
Click to collapse
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.
Badger50 said:
Then either you have a Verizon variant phone, and/or USB debugging and OEM unlocking is not enabled in developer options.
Click to expand...
Click to collapse
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk
Javi22 said:
But there is no system installed, I erased by accident...:S
Any clue what I can try?
Gesendet von meinem Pixel 3 mit Tapatalk
Click to expand...
Click to collapse
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota
Badger50 said:
Try side loading the OTA through stock recovery.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thanks but I can not get into recovery, the same screen:
Javi22 said:
Thanks but I can not get into recovery, the same screen:
Click to expand...
Click to collapse
Can you get into fastboot mode? If so you can then run deuces bootloop tool.
https://www.google.com/url?sa=t&sou...AxAB&usg=AOvVaw02czE3zeVK5sKbCe6V9L2v&cf=1
Related
A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!
I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Any other suggestions..?
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?
that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..
tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7
i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow
LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
nvrpunk said:
When removing TWRP and flashing my phone back to factory images, I received a size issue on the main image. I then manually flashed each .img using fastboot. Lastly, assuming it was good, I was an idiot and locked the bootloader.
Is there any way to recover from this using adb and sideloading? I have the factory recovery image working, locked bootloader but nothing else. Any help would be greatly appreciated
Click to expand...
Click to collapse
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
ulxerker said:
try to enter bootloader via adb reboot bootloader or key combination and issue fastboot oem unlock.
Click to expand...
Click to collapse
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
ulxerker said:
try it with nexus root toolkit
or
download latest OTA image and adb sideload OTA.zip in recovery.
Click to expand...
Click to collapse
Thanks, I am going to try the sideload of the OTA.zip And see if that works.
nvrpunk said:
This does not work.
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I'm curious if you did anything other than what you listed, because Allow OEM unlocking that was set from Developer Options should still be one given what your described actions.
I'm trying to unlock the bootloader of my Nexus 5x, because I want to downgrade to 6.1 after proximity sensor issues. I tried "fastboot oem unlock" and "fastboot flashing unlock", but it looks like the bootloader auto-locks after reboot, and so I can't flash anything.
Did this happen to someone?
Do you have "Secure boot- enable (no rpmb)" on fastboot screen?
This is my fastboot screen
View attachment 3984342
You can't unlock bootloader because probably you have replacement emmc memory/motherboard without flashed rpmb partition. You can't do enything with that, but on this forum there is a topic, where someone wrote how to work around this problem.
Wuzimu said:
You can't unlock bootloader because probably you have replacement emmc memory/motherboard without flashed rpmb partition. You can't do enything with that, but on this forum there is a topic, where someone wrote how to work around this problem.
Click to expand...
Click to collapse
I sent my phone to LG support for an hardware problem, that's probably the cause. Thank you very much for your help
Here you go:http://forum.xda-developers.com/nexus-5x/help/bootloader-relocks-reboot-t3466854
unlock bootloader problem
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
mohitkhurama93 said:
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Update your platform tools, make sure USB debugging is enabled, then try again.
Sent from my Nexus 5X using Tapatalk
I cant flash everything on fastboot mode
i have usb enabled and bootloader unlocked latest
status: Bootloop, no recovery
only fastboot mode
help for a fix ... I bricked the tab
TRIED TO RETURN TO STOCK WITH FLASH ALL.BAT BUT ALL PARTITIONS END WITH UNKNOWN COMMAND
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Alessandro999 said:
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Click to expand...
Click to collapse
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
parakleet said:
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
Click to expand...
Click to collapse
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Alessandro999 said:
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Click to expand...
Click to collapse
Good job
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
xxnirvana69xx said:
I've got the lastest sdk tools and google usb driver installed and still get a fail when trying to run fastboot flashing unlock. I also have allow oem unlocking checked. Is there something I'm missing?
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
7xxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
sorry delete!!! try fastboot flashing unlock_critical
lucky_strike33 said:
did you go to developer and tick on to unlock bootloader?
Click to expand...
Click to collapse
Sure did. OEM unlocking is ticked.
lucky_strike33 said:
sorry delete!!! try fastboot flashing unlock_critical
Click to expand...
Click to collapse
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
xxnirvana69xx said:
Same thing.
C:\Android>fastboot devices
7xxxxxxxxxxxxxxxx5 fastboot
C:\Android>fastboot flashing unlock_critical
...
FAILED (command write failed (No error))
finished. total time: 0.003s
Click to expand...
Click to collapse
Try a different cable?
Unfortunately I am at work and only have the C to C cable that was in the box.
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Az Biker said:
My sdk/platform tools files are the same ones I've used with my 6P since 11-2015, and unlocking the 2 XL bl worked on the first attempt.
my process:
pow button + vol down
open cmd prompt in platform tools folder
fastboot devices (recognized my device)
fastboot flashing unlock
use vol up to select UNLOCK MY BOOTLOADER
power, to confirm
erases everything,
restarts
profit
Click to expand...
Click to collapse
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
xxnirvana69xx said:
Tried with a slightly older version I had for my og pixel and it worked. Wonder what was up with the other version.
Click to expand...
Click to collapse
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
canemaxx said:
I have the latest adb and fastboot files and can not get my device to be recognized by adb can anyone help me with this?
Click to expand...
Click to collapse
Pm instead
xxnirvana69xx said:
Found this to possibly get you an older version of the platform tools...
"Well, you could use direct link, like
Click to expand...
Click to collapse
I started off with what I was using with my pixel XL and that didn't work and I have installed about 10 different version thus far and still nothing
I basically ended up using another cable, different version of adb, and another computer. Hard to tell what the problem exactly was since I changed 3 things at the same time between it not working and working. My guess is the cable and/or the computer.