Related
I have tried absolutely everything i can think of to restore my razr m. I'm using a macbook pro. I've tried using RSD lite in crossover, and in parallels, both windows 7, and windows xp. No matter what, my device is never recognized in fastboot mode and never pops up in RSD lite. I can use fastboot from the sdk directly in OSX. the device is recognized, but thats basically useless since the bootloader is locked, and I cant flash the system partition. Yes, I have installed the moto USB drivers, multiple times. I don't have access to any other computer and I'm in desperate need of help. please give me any suggestions you have
Get to a windows computer man. The motorola usb drivers need to talk directly to the hardware, not through another layer like parallels or other emulation software.
NRGZ28 said:
Get to a windows computer man. The motorola usb drivers need to talk directly to the hardware, not through another layer like parallels or other emulation software.
Click to expand...
Click to collapse
i literally can't until at least this weekend :/ im trying to flash the files using fastboot, but I get this error when attempting to flash system.img.ext4
sending 'system' (835010 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.107s
any work arounds for this?
ahhhzombies said:
i literally can't until at least this weekend :/ im trying to flash the files using fastboot, but I get this error when attempting to flash system.img.ext4
sending 'system' (835010 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.107s
any work arounds for this?
Click to expand...
Click to collapse
No man.. no workaround as long as the bootloader is locked. Otherwise we wouldn't need safestrap.
NRGZ28 said:
No man.. no workaround as long as the bootloader is locked. Otherwise we wouldn't need safestrap.
Click to expand...
Click to collapse
my buddy brought over his windows laptop, flashed without a hitch thanks for the help, and I'm installing your rom right now BTW
Hehe.. there ya go. See ? It pays to have a Windows laptop around
NRGZ28 said:
Hehe.. there ya go. See ? It pays to have a Windows laptop around
Click to expand...
Click to collapse
does it have to be a windows computer? just wondering because I only have a mac, and linux installed in my pc lol
looks like you need the new fastboot; try the linux one from this zip:
http://forum.xda-developers.com/showpost.php?p=37155367&postcount=190
Hi everyone,
In the past days I tried to unlock and root my Nexus 10, and looks like something went very wrong.
Right now, I'm stuck with the bootloader screen; the tablet boots into bootloader and I can only go to "bootloader" (power + vol up + vol down) or "download" (power and vol up).
The bootloader screen reads:
PRODUCT NAME: mantra
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION : MANTAMD003
CARRIER INFO: NONE
SERVIAL NUMBER: XXXXXXXXX
LOCK STATE: UNLOCKED
REBOOT MODE FLAG: NONE
I've tried using different tools, including "Wugs Nexus Root Toolkit" and command line fastboot.
Some fastboot commands seem to work - e.g.:
fastboot devices (it does recognise my device)
fastboot -w (the messages on the screen seem to suggest it's all ok)
fastboot getvar all:
(bootloader) product: manta
(bootloader) variant: wifi-only
(bootloader) serialno: XXXXXXXXX
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMD03
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000
The problem is with commands like:
fastboot flash bootloader bootloader-manta-mantamd03.img
(or any flashing command for what it matters).
None of them works; after waiting for a long while, the error returned is "Too many links".
I have googled the command, but I haven't found anything meaningful. ADB doesn't work - I must use fastboot to unbrick the device.
Any suggestions?
Andres
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
faiyo said:
I haven't unlocked & rooted yet.. just started looking at it today. It seems you can already get into bootloader. Shouldnt you be flashing a recovery in download mode?
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
Also the toolkit has an option for bricked devices. I'd look into that as a last resort.
Click to expand...
Click to collapse
Hi, thanks for the suggestion.
I've tried to flash a recovery image already - that didn't work. That's why I tried flashing anything. I've also tried the "Back to stock" option in the toolkit, and it hangs when trying to flash anything to the tablet...
Andres
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Have you tried using Wugs to Flash the Stock ROM and Unroot? I have been unable to get ADB to find my Nexus 10, even though it's been listed in the Device Manager of Win 8 with each of the 4 suggested drivers suggested. After getting stuck in a Bootloop I was still able to use the 'Back to Stock' option to recover my Nexus 10.
Good luck.
faiyo said:
I was still curious so i went googling. I think u should try a different cable and another usb port and different computer. It has fixed this issue for some people. Others said to try odin but what you're doing should really work. Otherwise there is a hardware failure and replacement parts dont seem to be an option... except at best a pogo connector cable in case the microusb jack is borked. I hope someone else chimes in for you. I haven't had any experience with this device. Maybe take some comfort in the asus nexus 10 coming out in a few months?
Click to expand...
Click to collapse
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
4ndres said:
Hi all,
thanks for your suggestions/comments. I did quite a lot of reading while trying to get this sorted, and the suggestion to check different cables/ports was popping up a lot.
I was on holiday - I tried all ports of the laptop, and 2 cables, with no success. Let me stress that with my first 2 cables the table was recognised - I couldn't just write (anything).
I didn't have access to more cables/computers and I though that I had done my homework with 2 cables/3 USB ports.
I was wrong; once I was back home I managed to sort it out in few minutes with a third cable.
I hope that my error does help anyone else reading this.
Right now I would like to know if there is some kind of cable that I can buy and know that it will work... Does anyone have any suggestions?
Click to expand...
Click to collapse
Definitely stick to non-counterfeit OEM samsung cables as best as you can. In the past few years, Samsung/Apple have bastardized and corrupted the usb standard. It's usually only noticeable for charging, though in any practical use we find one usb cable is actually better than another It's really disappointing.
Flash the factory image via fastboot. And never use toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app
Hi Guys,
I was hoping to upgrade to Paranoid Android today but didn't get so far.
I went into Clockwork Recovery and did a Factory Reset. I then proceeded to wipe the Dalvik Cache and other Cache. Then after that I set it to format the SD Card.
I noticed that while in recovery I couldn't get my SD card to mount in Windows 7. I booted up the Nexus 7 toolkit and chose a sideloading option for the Paranoid Android zips while the Nexus 7 was in CM Mod. I was staring at a frozen screen so I held the power button and down volume for ten seconds.
After a while it got to the point where the Nexus 7 would not boot. It would not show me the Google logo and when plugged in the Battery Recharging graphic did not come on.
After a while I somehow got it to boot up again. I went back into Recovery Mode and tried the sideloading again. I was still looking at a frozen screen so I did the ten second power button reset.
Now it's bricked. There's no Google logo, no option to go into Bootloader or Recovery. There is no graphic indicating that the Nexus 7 is recharging.
It's been hours. I even went so far to open up the back cover, unplug the battery, and then plug it back in. There's nothing.
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
I thought out of everything I did that unplugging and replugging the battery would have reset the system and allowed me back into Recovery Mode.
Not so....
So, I have to ask: Did I kill my Nexus 7?
Is there any way to bring this thing back? I figure I will leave it charging in a 2A Charger overnight. I need some feedback though because I did some research and have seen that a lot of people are had this problem.
ev1lchris said:
When I plug it into my laptop Windows detects it as "ADX" but doesn't have a driver to load for it.
Click to expand...
Click to collapse
Did you mean ADB drivers? I can't find anything on ADX. I would try uninstalling and reinstalling the drivers and toolkit as a quick step, I'd also consider other toolkits as a possible solution.
I think he meant APX. APX=done. Only solution: take out phone and call ASUS for an RMA number.
I refuse to believe my Nexus 7 is done.
ev1lchris said:
I refuse to believe my Nexus 7 is done.
Click to expand...
Click to collapse
If you haven't already, do a search on APX mode/drivers. You should find that the only way to recover once in APX is if you have made a copy of a file prior to bricking. That file contains a device-specific number that is required to perform the recovery. Additionally, even with that number the process is quite daunting. Good luck should you soldier on.
PS- You should also know that while in APX mode your device is "on" & the battery is discharging to a non-rechargeable state.
Yup, had the same thing happened to my N7 today after it crashed and could not recover to save it. Plugged it on my laptop and it recognized it as an apx device something. I already called asus for rma and I'll be shipping out mine on monday.
There is hope.
Sent from my ZTE V970 using xda app-developers app
First thing I'm going to do once I get my N7 back, make an nvflash blob http://forum.xda-developers.com/showthread.php?t=2455927
I don't think I ever got the chance to flash anything new onto my Nexus 7. I just did a factory reset and formatted the SD card.
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
ev1lchris said:
It's ON IT BOOTED UP!!!!
SO HAPPY. LOL!!!!!
IT'S ALLLLIIIIIIIIIIIIIVVVVVEEEE!!!!
Click to expand...
Click to collapse
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Lucky! curious also on how you manage to get out of apx mode!
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
OffcerClancy said:
You returned from APX? This is a first; what did you do? Are you sure you were in APX?
Click to expand...
Click to collapse
thraizer said:
Lucky! curious also on how you manage to get out of apx mode!
Click to expand...
Click to collapse
ev1lchris said:
Just walk around constantly holding the power button. Go about your day, and it should come on all of a sudden.
I'm rocking Kit Kat 4.4 right now!
Click to expand...
Click to collapse
I think there's a bit of misunderstanding here about APX mode...
To put it simply... APX doesn't necessarily signify hardbrick.
APX is required for nvFlash operations, such as nvFlashing a new bootloader, should the original become erased/corrupted. Indeed, if that where to happen, the Nexus 7 would automatically default to APX mode... and await for somebody to perform such an nvFlash operation.
Currently the only way of performing nvFlash operations on the Nexus 7 is if the user had run the flatline procedure BEFORE damage had occurred to the bootloader. This procedure generates what are called 'wheelie blobs' on a per-device basis, and are unique to each Nexus 7... ie., they are not transferable. They are required to resurrect a dead Nexus 7 with a corrupted, damaged or erased bootloader.
However, you can electively get into APX mode, even with a functional bootloader. Indeed, the latter part of the flatline procedure requires it. How to do this is detailed here.
So, just because your Nexus 7 is in APX mode doesn't necessarily mean it's hardbricked or the bootloader is damaged/corrupted or erased... though, more often than not, that is exactly what it does mean.
Providing you haven't knowingly done anything that might affect the bootloader, pressing and holding the POWER BUTTON for a good 30 seconds or more, might just be sufficient to kick-start a seemingly dead Nexus 7 out of APX mode. I can't guarantee it will work of course... but it's got to be worth a shot.
And it seems to have worked for @ev1lchris.
Rgrds,
Ged.
Sound like by dumb luck he stumbled in and fell assbackwards out of APX mode.
I brick my N7 when flashing 4.3 vía fastboot, ASUS replace the motherboard and its all good now
Enviado desde mi HTC One mediante Tapatalk
After months of use it is non responsive and in APX mode again. However, I have to highly suspect that the battery is playing a role here.
I have a rubber band constantly pressing the power button.
Let you guys know what happens.
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
ChiquiNL said:
I had almost the same problem that is described below. I did not leave the link to the blog since I assume its not allowed.
How to brick your Nexus 7
I have been playing around with Ubuntu on my Nexus 7 for a while, and decided yesterday to go back to stock android 4.2.2, so I downloaded the images from developers.google.com/android/nexus/images and extracted the zip file to my PC.
Restoring android 4.2.2
included in the package is a flash-all.bat file which contains all the commands which need to run so i thought great – i’ll just run it, go make a cup of tea and job done.
*** DO NOT RUN THE BATCH FILE! ***
The batch file doesn’t actually check the status of the commands it sends! Here’s what happened to me:
C:\Program Files (x86)\Android\android-sdk\platform-tools>flash-all.bat
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.022s
erasing 'boot'...
OKAY [ 1.042s]
finished. total time: 1.043s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.861s]
finished. total time: 1.862s
erasing 'recovery'...
OKAY [ 0.975s]
finished. total time: 0.978s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.611s]
finished. total time: 1.613s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.114s]
finished. total time: 12.116s
sending 'bootloader' (2096 KB)...
OKAY [ 0.279s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.849s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.007s
< waiting for device >
^CTerminate batch job (Y/N)? y
It’s sent the reboot command even though the bootloader failed to flash! So now i have an expensive paperweight
BATCH FILE DEVELOPERS, please make sure that your code has at least a ‘pause’ statement before doing things like rebooting so users can check the output before proceeding!!!
Tags: google, nexus7
When I plug to the PC my Nexus 7 it wants to instal APX Drivers. I already read that this is as good as rubbish now but I just wanna make sure there is nothing I can still do.
Im preaty sure Im ****ed up though. Should I try contact Asus?
Click to expand...
Click to collapse
If you're still under warranty and you have tried all you can to revive the thing then yes you should call Asus and do a RMA.
Here's an update on my situation...
I installed a battery I bought off of eBay and.... nothing. Still dead.
I'm charging it and I'm going to continue to have the rubber band wrapped around the power button but I think it's pretty much dead.
Such an awesome tablet that I used and depended on every day.
I bought a refurb N7 2013 but I really would have liked to save my N7 and continued using it.
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: XXXXXXXXXXX
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: CVH7N15C14001695
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
sumitpetal said:
... can you guys help me to overcome this problem and install the new android os. Looking for your response.
Click to expand...
Click to collapse
Unlocking your device is failing because you haven't ever enabled Allow OEM Unlock or USB Debugging from within the OS. The only way you will be able to unlock the phone is to get it to boot into the OS first, and going into Developer Options to toggle these two settings on. You may be able to use the method linked above to briefly get your phone booted into the OS long enough so you can do this. If you are lucky enough to accomplish this, then you can disable the big cores using a custom kernel.
SlimSnoopOS said:
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hello SlimSnoopOS,
Thanks for giving the link. I checked it but in that links it showing the method to enable OEM and I am totally failed to boot into the OS. I got only Google Logo and it loop again and again. I tried fastboot flashing unlock but It showing me Remote: Device is locked.
Is there any way to installed the New OS or downgrade or repair current version with unlocked OEM Devices?
Looking for your response.
Thank you.
v12xke said:
Unlocking your device is failing because you haven't ever enabled Allow OEM Unlock or USB Debugging from within the OS. The only way you will be able to unlock the phone is to get it to boot into the OS first, and going into Developer Options to toggle these two settings on. You may be able to use the method linked above to briefly get your phone booted into the OS long enough so you can do this. If you are lucky enough to accomplish this, then you can disable the big cores using a custom kernel.
Click to expand...
Click to collapse
Hello v12xke,
Thank you for your response.
I am totally failed to go into the os. I am getting only Google Logo and its looping. so I am unable to go in to setting and enable OEM unlocking option in developer option.
do you have any other option to install, repair current version with Unlocked OEM devices ?
Thank You so much.
sumitpetal said:
Hello SlimSnoopOS,
Thanks for giving the link. I checked it but in that links it showing the method to enable OEM and I am totally failed to boot into the OS. I got only Google Logo and it loop again and again. I tried fastboot flashing unlock but It showing me Remote: Device is locked.
Is there any way to installed the New OS or downgrade or repair current version with unlocked OEM Devices?
Looking for your response.
Thank you.
Click to expand...
Click to collapse
You have to try either of those two methods (extreme heat or extreme cold) to see if you can get it to boot even for a couple minutes. Neither method is quick nor do you have time to mess around once the phone finally boots. You can only upgrade with a locked bootloader. So you are stuck unless you are under warranty or can try the fix.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You have to try either of those two methods (extreme heat or extreme cold) to see if you can get it to boot even for a couple minutes. Neither method is quick nor do you have time to mess around once the phone finally boots. You can only upgrade with a locked bootloader. So you are stuck unless you are under warranty or can try the fix.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hello SlimSnoopOS,
I found a video on youtube which fix the bootloop by opening the whole phone. can It possible ?
could you please check the video -> https://www.youtube.com/watch?v=-A-FQp1DP7A
can It be possible ?
Thank You.
sumitpetal said:
Hello SlimSnoopOS,
I found a video on youtube which fix the bootloop by opening the whole phone. can It possible ?
could you please check the video -> https://www.youtube.com/watch?v=-A-FQp1DP7A
can It be possible ?
Thank You.
Click to expand...
Click to collapse
I'm at work so I can't watch your video. I don't recommend opening up a device if you aren't technically sound enough to follow whatever the instructions are. So, try at your own risk and loss of warranty.
Sent from my Nexus 5X using Tapatalk
Hey man, here is what I did though my device was rooted/unlocked/custom kernal (EX)
- Put the phone on charge
- Switch on, let it bootloop, eventually it booted [takes a day at times]
- Backup if you need to (eg. ADB pull).
- I have EX manager so I enabled power save mode which disables the 4 big cores. As long as the phone doesn't reboot or die no bootloops.
boeder9 said:
Hey man, here is what I did though my device was rooted/unlocked/custom kernal (EX)
- Put the phone on charge
- Switch on, let it bootloop, eventually it booted [takes a day at times]
- Backup if you need to (eg. ADB pull).
- I have EX manager so I enabled power save mode which disables the 4 big cores. As long as the phone doesn't reboot or die no bootloops.
Click to expand...
Click to collapse
Hello boeder9,
Thanks for reply.
my device is not rooted and unlocked but let me try it, hope it works...!!
Thank you
sumitpetal said:
Hello v12xke, Thank you for your response.
I am totally failed to go into the os. I am getting only Google Logo and its looping. so I am unable to go in to setting and enable OEM unlocking option in developer option.
do you have any other option to install, repair current version with Unlocked OEM devices ? Thank You so much.
Click to expand...
Click to collapse
You will need to get into the OS somehow to toggle the dev settings. Otherwise you will not be able to unlock the bootloader. You will not be able to apply the fix (flash custom kernel) with a locked bootloader, and there is no way to unlock it unless your phone can boot. There are a few "tricks" to use with the heatgun/hairdryer that force the phone into limp mode so it will boot into the OS. Others have claimed that once booted, they have enabled "power savings" under settings>>battery and that prevents the phone from going back into the looping. Keep trying, and good luck with the hairdryer!
v12xke said:
You will need to get into the OS somehow to toggle the dev settings. Otherwise you will not be able to unlock the bootloader. You will not be able to apply the fix (flash custom kernel) with a locked bootloader, and there is no way to unlock it unless your phone can boot. There are a few "tricks" to use with the heatgun/hairdryer that force the phone into limp mode so it will boot into the OS. Others have claimed that once booted, they have enabled "power savings" under settings>>battery and that prevents the phone from going back into the looping. Keep trying, and good luck with the hairdryer!
Click to expand...
Click to collapse
Hi v12xke,
Thanks for the details, Let me try with hairdryer. Hope it works...!!!
Thank You so much once again.
SlimSnoopOS said:
Try the following thread then post after your attempts in there as well:
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Same problem... , i tried several flashes ... nothing!
but seems to me it's a fault on the software ... a bug or a glitch, because it came at the end of february! or a malware of some kind!
moshu_fc said:
Same problem... , i tried several flashes ... nothing!
but seems to me it's a fault on the software ... a bug or a glitch, because it came at the end of february! or a malware of some kind!
Click to expand...
Click to collapse
If it's a software issue best thing to do is completely wipe your phone. Easiest way is to install Twrp and wipe all incuding internal then flashing fresh stock image. I'm sure there is fastboot commands also to erase (or some other way if can't do neither.) This will remove every last thing from your phone so make sure if you are able to back up pics,docs,downloads,music etc. Last thing though don't think it's causes issues make sure your flashing the right version of February stock image Google finally labled them. Or March if it's out.
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6p
BL: angler-03.68
baseband: angler-03.81
product/variant: ANGLER-ROW-VN1
Serial Number: XXXXXXXXXXX
CPU: MSM8994 0x20001
eMMC: 64GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: ttyHSL0,115200,n8
Battery ok
Device is LOCKED.
Qfuse status: ENABLED.
off-mode-charge: ENABLED.
Download Mode: DISABLED.
Connect USB Data Cable
can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
Hello, you describe a cluster A57 failure, to fix it you need to boot into your phone enough time to enable USB debugging and OEM unlock then flash a modified kernel or a modified ramdisk
See this thread : https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/
To boot into your device you need to overheat the CPU so the software will shutdown the faulty A57 clusters to cool down the device as soon as it boot up enable USB debugging and OEM unlock before the A57 clusters goes online (because it will shutdown your device) once you succeed enable USB debugging and OEM unlock flash modified files and enjoy your working (but slower) N6P
I had that problem too, but wasn't able to live thinking that my phone was working with CPU issues, so I bought an other Nexus 6P from a guy on the internet, he was selling it because the screen was broken, I got it for real cheap ! I swapped the screen of my BLOD N6P to the one from the guy, it cost me 60$ to completely fix my phone (way less than buying a new phone or buying a new microprocessor)
Exodusche said:
If it's a software issue best thing to do is completely wipe your phone. Easiest way is to install Twrp and wipe all incuding internal then flashing fresh stock image. I'm sure there is fastboot commands also to erase (or some other way if can't do neither.) This will remove every last thing from your phone so make sure if you are able to back up pics,docs,downloads,music etc. Last thing though don't think it's causes issues make sure your flashing the right version of February stock image Google finally labled them. Or March if it's out.
Click to expand...
Click to collapse
Hy!
Already done that... Today It comes back from service, they told me they replaced the PCB ... so... it could be a hardware problem or a malware of some kind that ruins the memory... that's what i think about those problem, but i suspect google has something to do whit it!
So... i'll get back to you when I will have IT! :fingers-crossed:
bootloop can't unlock device
I have had exactly the same problem. I tried in vain using heat or cold to get the thing to boot, but independently found the method of leaving it on charge for a few days, occasionally it will get into the O/S.
So while in the O/S I enabled developer options and adb too (the second time) and unlocked the bootloader.
However it still claims to be "device is LOCKED" in recovery mode. This is really weird. I have also factory reset the phone but that hasn't helped.
Luckily I have read the other posts about power saving mode so I'll try that next, it will save having to flash a non-stock OS.
When people ask why unlocking the bootloader is important to me, this specific situation comes to mind. If you had unlocked your device you could have fixed this easily, mind you you would lose 4 cores.
Nexus 6P Huawei H1511 Bootlooping fix with OEM Unlock off
sumitpetal said:
Hello Friends,
I got the bootloop problem on my nexus 6p from the last few days.
I Google it to solve the problem with various methods but I am unable to solve the problem. I tried command fastboot flashing unlock but I am getting remote: device is locked. I am unable to unlock usb debugging and oem through fastboot command prompt. When I write command fastboot devices then I get the serial number and when I write the command adb devices then I failed to get the device. I am also unable to get recovery mode.
here is some details of my nexus 6P.
Can you guys help me to overcome this problem and install the new android os.
Looking for your response.
Thank You guys.
Click to expand...
Click to collapse
*** I ran into a similar catch-22 issue on my 6P (H1511) the dreaded bootlooping with OEM Unlock turned OFF. ***
*** Couldn't flash the phone because OEM Unlock was off, and couldn't turn OEM Unlock on because it was bootlooping. ***
*** You MUST be able to fix the bootlooping/freezing at least temporarily, in order to turn on OEM Unlock in Developer Options ***
I have tried the "squeezing" method to no avail.
Then tried the heating method, which worked to a point where it has reached the color circles while booting, but then it started looping again.
I figured there's nothing to loose, so I cranked up the heat on the digital heating plate to exactly 140 Celsius for about 10 minutes covered with a paper towel, with only the upper half of the phone's back touching the heating plate (no need to "cook" the lower part with the battery).
It was still looping after the circles appeared, BUT by leaving it to cool off for about an hour, it has finally booted up into the setup page, so I quickly went to Settings > About/Phone/Software Info > clicked the "Build" line 7 times to enable Developer Options, under which I enabled OEM Unlock and ADB Debug.
If it's still bootlooping, you may try to "freezing" method where you would put the phone into the deep freezer for about an hour.
However, heating has worked for me.
Following that, in FastBoot mode I entered the following 3 versions of the flash unlock commands (only one will work out of the 3 which is fine):
fastboot oem unlock
fastboot flashing unlock
fastboot flashing unlock_critical
Downloaded the latest full stock firmware directly from Google.
https://dl.google.com/dl/android/aosp/angler-opm6.171019.030.b1-factory-ab13a98b.zip
Unzip it, and run flash-all.bat
Once the flashing has finished, DO NOT let it boot up, instead hold down the Volume Down as it's about to reboot, which will kick it into bootloader/fastboot mode.
I have tried flashing the Osmosis zip to patch the boot but it didn't work, it was still bootlooping.
So I have flashed a pre-patched 4-Core Boot kernel to fix the bootlooping issue permanently.
For Android 8.1 OPM6.171019.030 flash this 4-Core Boot with the commands below:
https://androidfilehost.com/?fid=13356325061477269711
fastboot flash boot Huawei_H1511_6P_OPM6.171019.030_Boot_4Core.IMG
fastboot reboot-bootloader
At this point flash a 4-Cores patched TWRP, go into TWRP recovery (hold down Volume Down + Power for 10 seconds, Volume Down to "Recovery", Power) and first "format" Data, then "wipe" Cache, Dalvik-Cache, and Data.
Note, all information on your phone will be lost by the above format/wipe operation.
All done, hope this method may help some of you.
And here are some interesting FastBoot commands I've come across....
C:\ADB>fastboot flashing get_unlock_ability
(bootloader) 1
OKAY [ 0.018s]
Finished. Total time: 0.019s
C:\ADB>fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.87
(bootloader) version-bootloader:angler-03.79
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xdaa17ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:8XV5T15C11000453
(bootloader) kernel:lk
(bootloader) product:angler
all:
Finished. Total time: 0.172s
Instead of "fastboot getvar all", you can also use "fastboot getvar <variable>" (without the quotes and <>)
Any <variable> from the log above, between "(bootloader)" and the second ":"
For example:
fastboot getvar serialno
Enjoy!
My nexus 6P recently went through this bootloop,
Google screen coming up and stuck there, for 5 days, i was going through many possible solutions throughout the web, but they all said it must boot to OS to be able to unlock oem bootloader,
Finally stuck at extreme heat or cold, extreme heat did'nt work for me, but YES extreme cold did actually work, i kept it in the deep freezer for about half an hour, and then waited 2 min, and plugged the charging cable and powered ON the phone, to my astonishment, it did start and i was able to use the phone.
I have rebooted several times since then, it works fine for certain time, and then crashes and restarts all the time, i can still use th phone but its uncertain when it will restart again.
I tried to install new custom rom, but it still says DEVICE IS LOCKED and i cannot do anything else.
Hi,
I have oneplus 6T which has suddenly started giving qualcomm crash dump error after normal reboot. I have tried msm tool to flash. Tool shows success but when it boots the mobile at end , same crash dump appears again. have also tried multiple version of msm. Also visited service center but they are suggesting motherboard replacement.
Now i want to try manual flashing. Phone is in bootlocked state. also OEM is not unblocked. Is it possible tounlock OEM when my phone is not booting. also is it possible to change boothlocked state to unlock?
I can go to fastboot by pressing vol UP + DOWN and power button but on selecting recovery option it still goes to same crash dump state.
Please suggest what options do i have?is there any way to recover?
Thanks
If your device is a global model 6t then put it in fastboot mode manually then try "fastboot oem unlock* and see what happens.. Unlocking the bootloader won't fix a hardware issue but it won't hurt anything either. ?
Have you ever unlocked your bootloader and then locked it afterwards? If so I wouldn't recommend it again. I've seen a few people screw up their devices that way on here. I've never since Nexus S days when I began modding my phone's locked a bootloader. I always unlock and leave them unlocked.
**I'd either sell it as is online or get motherboard replaced then unlock bootloader and install whatever you'd I like but don't lock the bootloader after you unlock it. That's just my opinion. I've been on XDA a long time and had many devices over the years and I remember reading about people on 5 or 6 phone's I've had in my past screwing up their phones that way..
Edit added: ?
Thanks for responding
yes device is global model of 6T.
I have not unlocked /locked bootloader in past.
"fastboot oem unlock" gives error as "FAILED (remote: Flashing unlock is not allowed)"
flash713 said:
If your device is a global model 6t then put it in fastboot mode manually then try "fastboot oem unlock* and see what happens.. Unlocking the bootloader won't fix a hardware issue but it won't hurt anything either. ?
Have you ever unlocked your bootloader and then locked it afterwards? If so I wouldn't recommend it again. I've seen a few people screw up their devices that way on here. I've never since Nexus S days when I began modding my phone's locked a bootloader. I always unlock and leave them unlocked.
**I'd either sell it as is online or get motherboard replaced then unlock bootloader and install whatever you'd I like but don't lock the bootloader after you unlock it. That's just my opinion. I've been on XDA a long time and had many devices over the years and I remember reading about people on 5 or 6 phone's I've had in my past screwing up their phones that way..
Edit added:
Click to expand...
Click to collapse
Did you tried different older versions of MSM Tool?
Dafelleant said:
Did you tried different older versions of MSM Tool?
Click to expand...
Click to collapse
Hi,
yes tried couple of older versions too (listed below).
ANDROID+10+OOS+10.3.5+fajita_41_J.47_200717.zip
ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222.zip
6T_MsmDownloadTool_v4.0.59_OOS_v9.0.13.rar
Every time on completion of msm flashing in all the above versions, I still get qualcomm crash dump error.
My question is: Is it necessary for bootloader to be in unlocked state for msm tool to work? if no, is there any other command to unlock the bootloader on a bricked phone as "fastboot oem unlock" and "fastboot flashing unlock" fails with the message "not allowed".
thanks again for responding to the post.
ms2020 said:
Hi,
yes tried couple of older versions too (listed below).
ANDROID+10+OOS+10.3.5+fajita_41_J.47_200717.zip
ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222.zip
6T_MsmDownloadTool_v4.0.59_OOS_v9.0.13.rar
Every time on completion of msm flashing in all the above versions, I still get qualcomm crash dump error.
My question is: Is it necessary for bootloader to be in unlocked state for msm tool to work? if no, is there any other command to unlock the bootloader on a bricked phone as "fastboot oem unlock" and "fastboot flashing unlock" fails with the message "not allowed".
thanks again for responding to the post.
Click to expand...
Click to collapse
As far as I know no. Because in order to unlock your bootloader you must have access to the screen so that after you send the unlock command you can use your volume buttons to confirm and power button to select yes and then it does its thing...
flash713 said:
As far as I know no. Because in order to unlock your bootloader you must have access to the screen so that after you send the unlock command you can use your volume buttons to confirm and power button to select yes and then it does its thing...
Click to expand...
Click to collapse
Hi,
The only screen i have access to is "fastboot mode " which has options like start, power off, restart bootloader, recovery mode.
When i choose recovery it goes back to same qualcomm crashdump.
i have tried sending "fastboot oem unlock" from pc while i am in fastboot mode. but gives error as
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.005s
Thanks
Deleted.
None of what I had typed will work because your bootloader is blocked correct?
---------- Post added at 03:31 PM ---------- Previous post was at 03:13 PM ----------
ms2020 said:
Hi,
The only screen i have access to is "fastboot mode " which has options like start, power off, restart bootloader, recovery mode.
When i choose recovery it goes back to same qualcomm crashdump.
i have tried sending "fastboot oem unlock" from pc while i am in fastboot mode. but gives error as
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.005s
Thanks
Click to expand...
Click to collapse
I think the only thing that may work would be a programmer box (ex: Octopus, Mudusa..) and I'm not even sure if it would or not. I was just about to buy two before this stupid Corona bs hit and made me broker than broke. If you had one of these programmer boxes I'm talking about you may be able to fix it but I'm not 100% sure of it and they cost anywhere from $75-300 depending on which one you're looking at. They make many different programmer boxes and they all are compatible with and do slightly different things.. Sorry I couldn't be of any real help man. I hope you can get this fixed.
I'm quite sure the reason you're being denied when trying to send the bootloader unlock command is because your switch in developer options on your device isn't switched to enable bootloader unlock.
yes you are right ... got same error
fastboot boot twrp-3.4.0-2-fajita.img
downloading 'boot.img'...
OKAY [ 0.678s]
booting...
FAILED (remote: boot is not allowed in Lock State)
finished. total time: 0.697s
thanks for your reverts .
flash713 said:
Deleted.
None of what I had typed will work because your bootloader is blocked correct?
---------- Post added at 03:31 PM ---------- Previous post was at 03:13 PM ----------
I think the only thing that may work would be a programmer box (ex: Octopus, Mudusa..) and I'm not even sure if it would or not. I was just about to buy two before this stupid Corona bs hit and made me broker than broke. If you had one of these programmer boxes I'm talking about you may be able to fix it but I'm not 100% sure of it and they cost anywhere from $75-300 depending on which one you're looking at. They make many different programmer boxes and they all are compatible with and do slightly different things.. Sorry I couldn't be of any real help man. I hope you can get this fixed.
I'm quite sure the reason you're being denied when trying to send the bootloader unlock command is because your switch in developer options on your device isn't switched to enable bootloader unlock.
Click to expand...
Click to collapse
ms2020 said:
yes you are right ... got same error
fastboot boot twrp-3.4.0-2-fajita.img
downloading 'boot.img'...
OKAY [ 0.678s]
booting...
FAILED (remote: boot is not allowed in Lock State)
finished. total time: 0.697s
thanks for your reverts .
Click to expand...
Click to collapse
Have you tried formatting data and then reboot system? I know that sounds kinda dumb but if I were you I would definitely try that. It might boot up to system. To do this you can plug up to your computer and open command window and manually set phone in fastboot mode where you see the "START" screen. Then from PC terminal do: sudo fastboot -w (hit enter) and then once it wipes , push power button on your device which should still be at the screen that reads START. Your device should then reboot. I'd give that a try for sure if I were in same situation.
What did the service center quote you price wise on motherboard replacement?
The process looks doable I think..
https://www.ifixit.com/Guide/OnePlus+6T+Motherboard+Replacement/129570
I'm assuming motherboard is the mainboard. If so OnePlus has the 6t main board costing more than I paid for my mint 8gb 128gb OnePlus 6t.
https://www.oneplus.com/support/repair-pricing/details?code=9
If you end up trying everything and just can't get it fixed ...
If the cost to repair is two hundred plus dollars I would sell it online as is and add some money to it when you can and grab another used device from swappa.com . I paid $200 for my 6t near mint condition on swappa about 5-6 months ago.
Hmm, unlocking the BL is a mute point if you didn't open the developer options and check usb debugging and oem unlocking... So as the phone is borked at moment, I like the idea of reformatting but I wouldn't reboot after the format.. but have MSM ready to go and use the edl tab in twrp to start the msm...flash away..
tried the format with -w,
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
flash713 said:
Have you tried formatting data and then reboot system? I know that sounds kinda dumb but if I were you I would definitely try that. It might boot up to system. To do this you can plug up to your computer and open command window and manually set phone in fastboot mode where you see the "START" screen. Then from PC terminal do: sudo fastboot -w (hit enter) and then once it wipes , push power button on your device which should still be at the screen that reads START. Your device should then reboot. I'd give that a try for sure if I were in same situation.
What did the service center quote you price wise on motherboard replacement?
The process looks doable I think..
https://www.ifixit.com/Guide/OnePlus+6T+Motherboard+Replacement/129570
I'm assuming motherboard is the mainboard. If so OnePlus has the 6t main board costing more than I paid for my mint 8gb 128gb OnePlus 6t.
https://www.oneplus.com/support/repair-pricing/details?code=9
If you end up trying everything and just can't get it fixed ...
If the cost to repair is two hundred plus dollars I would sell it online as is and add some money to it when you can and grab another used device from swappa.com . I paid $200 for my 6t near mint condition on swappa about 5-6 months ago.
Click to expand...
Click to collapse
hi,
even though format didnt work tried with msm too after the command to format but same result.
formating throws error as
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
lilbrat said:
Hmm, unlocking the BL is a mute point if you didn't open the developer options and check usb debugging and oem unlocking... So as the phone is borked at moment, I like the idea of reformatting but I wouldn't reboot after the format.. but have MSM ready to go and use the edl tab in twrp to start the msm...flash away..
Click to expand...
Click to collapse
ms2020 said:
hi,
even though format didnt work tried with msm too after the command to format but same result.
formating throws error as
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
Click to expand...
Click to collapse
Well that's not good.. as flashing with msm wouldn't matter whether the bootloader is lock or not ... As it automatically relocks it anyways... Has me stumped..
Are you sure you didn't flash anything that wasn't specifically made for your model device? I mean after you started to fix the crashdump issue?
Want to hear something crazy.. Two days ago when we were first commenting about this crashdump deal, about an hour after we stopped chatting I took a shower, got out and went to grab my OnePlus 6t off the Dash ac charger and yep, you guessed it!!! Crashdump mode!!!! ?????
I swear man! And I wasn't messing with my device when it occurred either. I was not able to get out of it by manually holding power+ volume -&+ until I saw fastboot mode and then selecting start using power button like the three other times I've experienced this. So I went ahead and booted twrp, and did a clean install of OOS and formatted data and that worked. Is this **** contagious?! ? Tripped me out! Haha!!
I'd give the data format command: fastboot -w then run msm tool like the other user said to do. See if that works.
that sounds creepy.. you getting is 'crashdump':laugh:
i guess what is different in my case is i did not unlock oem. And so none of the commands are working. Phone was working fine and one morning fingerprint scanner did not reco. my finger so i thought of rebooting instead of other method to open and i get this error. i know there was no physical mishandling on my part so its difficult to believe that its a hardware failure and needs main board replacement as service center suggests. i have tried only msm tools (stated here in previous msgs) after service center gave a huge bill (230+)for repair.
and other commands as you stated but none of them have worked anyways so not sure if i did something wrong while self repair.
guess will do one more round format plus msm...
ms2020 said:
that sounds creepy.. you getting is 'crashdump':laugh:
i guess what is different in my case is i did not unlock oem. And so none of the commands are working. Phone was working fine and one morning fingerprint scanner did not reco. my finger so i thought of rebooting instead of other method to open and i get this error. i know there was no physical mishandling on my part so its difficult to believe that its a hardware failure and needs main board replacement as service center suggests. i have tried only msm tools (stated here in previous msgs) after service center gave a huge bill (230+)for repair.
and other commands as you stated but none of them have worked anyways so not sure if i did something wrong while self repair.
guess will do one more round format plus msm...
Click to expand...
Click to collapse
Far as I know fastboot and adb commands should still work but not commands like booting custom recovery...etc .. Also developer options and usb debugging needs to be set to "on" as well in settings. It sure seems like they would have made some alternate way to access these settings but if they did I've never heard of it. Tell you the truth I've never even used fastboot and adb on anything other than a device that is bootloader unlocked except to unlock the bootloader usually a a day or two after I get my device.. I really have no clue what works and doesn't with BL locked.
What mind boggles me is all over our OP6/6t forums you see people talking about this crashdump issue. And although I've been there 5 or 6 times on my 6t I've always been able to get out of it by holding down power + volume +&- until I see the fastboot screen then releasing. And I guess many people cannot do that. I wonder why? Maybe there are two different crashdumps...? Sure seems that way to me. I've always been able to hold my buttons down and get out of it by rebooting from fastboot mode. Many report they cannot do that. ?
(I wasn't even gonna mention crashdump. My luck my phone will go to it and I won't be able to get out of it like I've been able to before.) ?
Edit added:
sudo fastboot oem device-info
Use that command to show whether device is bootloader unlocked or not. See what it says if you type that in?
Maybe see what this shows afterwards as well:
sudo fastboot gatvar all
I believe your developer options and usb debugging was probably not flipped on as well, in settings?
bro fixed aleady? i got fix for you.
i have tried the commnads you have stated earlier.. still giving output here.
fastboot oem device-info
output below
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x31
(bootloader) cal_rebootcount: 0x31
OKAY [ 0.027s]
finished. total time: 0.028s
so it's locked
fastboot gatvar all gives the list of options that you can use with fastboot
most of the commands dont work and gives below error
FAILED (remote: Erase is not allowed in Lock State)
yes developer options and usb debugging was probably not flipped either
flash713 said:
Far as I know fastboot and adb commands should still work but not commands like booting custom recovery...etc .. Also developer options and usb debugging needs to be set to "on" as well in settings. It sure seems like they would have made some alternate way to access these settings but if they did I've never heard of it. Tell you the truth I've never even used fastboot and adb on anything other than a device that is bootloader unlocked except to unlock the bootloader usually a a day or two after I get my device.. I really have no clue what works and doesn't with BL locked.
What mind boggles me is all over our OP6/6t forums you see people talking about this crashdump issue. And although I've been there 5 or 6 times on my 6t I've always been able to get out of it by holding down power + volume +&- until I see the fastboot screen then releasing. And I guess many people cannot do that. I wonder why? Maybe there are two different crashdumps...? Sure seems that way to me. I've always been able to hold my buttons down and get out of it by rebooting from fastboot mode. Many report they cannot do that. ?
(I wasn't even gonna mention crashdump. My luck my phone will go to it and I won't be able to get out of it like I've been able to before.)
Edit added:
sudo fastboot oem device-info
Use that command to show whether device is bootloader unlocked or not. See what it says if you type that in?
Maybe see what this shows afterwards as well:
sudo fastboot gatvar all
I believe your developer options and usb debugging was probably not flipped on as well, in settings?
Click to expand...
Click to collapse
not yet..
gazitonmoy said:
bro fixed aleady? i got fix for you.
Click to expand...
Click to collapse