Hi, my friend failed to resize the partition on his Pixel 1 OG to install OxygenOS. Now the only thing he could boot into was fastboot. He tried to unlock the bootloader (It was unlocked before he tried to resize partition, but after it bricked, the bootloader got locked for some reason) using the "fastboot oem unlock" command but since it was a Verizon model, the command returns: "bootloader: oem unlock is not allowed". I will provide some screenshot below.
I also provide the result of the "fastboot get-var all" command and there is no partition size. Usually there should be something there but not this time.
The recovery is gone and the only thing that actually work is the "Show barcode" option in fastboot.
When my friend chose the Reboot or Recovery mode, the Google logo appear for a >0.6 second then turn it self off.
Also tried booting into EDL mode but didn't seems to work. It might required a EDL cable.
Any help would be appreciated since my friend is pretty much desperate at this point since quaratine prevent him from getting a step out of his house lol.
He also send me his Pixel through mail lol.
How to resize partition guide (Might be helpful if i provide a link here?)
http://lunarixus.party/oxygenosguide/part1.html
any help?
Please...
Sounds creepy
But nothing can you do on locked condition
Sent from my Pixel using XDA-Developers Legacy app
plokyz said:
Sounds creepy
But nothing can you do on locked condition
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
D*mn, thats kinda sad. But the Pixel XL could boot into EDL mode but not on the Pixel OG. I think I need to find a way to boot this into EDL mode. Can you help me?
enderzip said:
D*mn, thats kinda sad. But the Pixel XL could boot into EDL mode but not on the Pixel OG. I think I need to find a way to boot this into EDL mode. Can you help me?
Click to expand...
Click to collapse
I have the SAME issue that you do, and have been looking for a while.
Like literally the same thing happened to me as well, except my Bootloader is unlocked.
Voltz100999 said:
I have the SAME issue that you do, and have been looking for a while.
Like literally the same thing happened to me as well, except my Bootloader is unlocked.
Click to expand...
Click to collapse
I wish I have a unlocked bootloader . If I did, I will boot it into TWRP and try to repair the damaged file system. But that was far from what I currently can do.
enderzip said:
I wish I have a unlocked bootloader . If I did, I will boot it into TWRP and try to repair the damaged file system. But that was far from what I currently can do.
Click to expand...
Click to collapse
I would expect you to not be able to boot into TWRP, because I can't, even with an unlocked bootloader.
Voltz100999 said:
I would expect you to not be able to boot into TWRP, because I can't, even with an unlocked bootloader.
Click to expand...
Click to collapse
Did you get the WriteFailed error? Maybe fastboot were unable to detect the partition?
enderzip said:
Did you get the WriteFailed error? Maybe fastboot were unable to detect the partition?
Click to expand...
Click to collapse
Yes, fastboot cannot see a partition size for both boot slots.
Voltz100999 said:
Yes, fastboot cannot see a partition size for both boot slots.
Click to expand...
Click to collapse
Thats strange...
enderzip said:
Thats strange...
Click to expand...
Click to collapse
Yes, but that's what it was. Couldnt flash boot either. I just replaced it with an XL, as from what I've seen there's no hope for it.
Related
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
tom_clegg said:
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
Click to expand...
Click to collapse
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Fstop said:
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Click to expand...
Click to collapse
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
GXGOW said:
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
where do i find the files for mac with fast boot adb etc.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
Hmmm no recovery? When u hold down volume + power ?
Did u find the fastboot & adb tools for Mac?
What happens when u hold volume key up + power button at same time after turning device off?
What happens if u $fastboot devices -
Can u issue cmd "$fastboot oem unlock"
Know its frustrating but have to keep trying till u get in. Just have the rom files unzipped on your Mac ready to flash 1+1 when u get in. Its how I did it. When I wasn't able to but into recovery. Get on fastboot go thru OEM unlock, then flash 1+1. Follow the install script manually. Open script w plain text reader & just issue cmds following script. I don't trust scripts I + automation to get things unstuck.
tom_clegg said:
where do i find the files for mac with fast boot adb etc.
Click to expand...
Click to collapse
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Heisenberg said:
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Click to expand...
Click to collapse
would u be able to do a short one for mac that would help a lot with the commands
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Heisenberg said:
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Click to expand...
Click to collapse
is it just ./ then the command?
can i message you somehow maybe so it is quicker
tom_clegg said:
is it just ./ then the command?
can i message you somehow maybe so it is quicker
Click to expand...
Click to collapse
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Heisenberg said:
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Click to expand...
Click to collapse
fine then
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
tom_clegg said:
fine then
Click to expand...
Click to collapse
Don't get an attitude because I'm trying to help you help yourself.
tom_clegg said:
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
Click to expand...
Click to collapse
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Heisenberg said:
Don't get an attitude because I'm trying to help you help yourself.
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Click to expand...
Click to collapse
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
tom_clegg said:
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
Click to expand...
Click to collapse
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Heisenberg said:
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Click to expand...
Click to collapse
it says device tampered true
unlocked false
charge screen enabled false
tom_clegg said:
it says device tampered true
unlocked false
charge screen enabled false
Click to expand...
Click to collapse
Ok, try the unlock command again. What recovery did you previously have installed?
Heisenberg said:
Ok, try the unlock command again. What recovery did you previously have installed?
Click to expand...
Click to collapse
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
tom_clegg said:
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
Click to expand...
Click to collapse
You definitely can't boot into recovery? Most times not being able to get into recovery it's a case of user error. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Hi,
I have come here seeking help for repairing my Nexus 5 which is stuck in bootloop. The phone wasn't rooted with possibly no custom recovery and it's bootloader is locked. And I am not sure which firmware was on it. And I also don't know what was done to it for it to become "bricked" as it was given to me in that state.
I can access the Bootloader Mode (a.k.a. Fastboot) but when I try to enter the Recovery Menu it gives me an Android logo with the red triangle with "No Command." written underneath it. And since the bootloader is locked, I am unable to flash a Stock ROM on the phone.
I have somehow managed to "temporarily" unlock the bootloader by entering the following command.
Code:
fastboot oem unlock
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
So I tried entering that command then I immediately entered the following commands to flash the stock 6.0.1 recovery.img
Code:
fastboot erase flash
fastboot flash recovery recovery.img
But in vain, as it still gives me the "No Command." Android logo when I run the Recovery Mode. I have also tried the same procedure with the TWRP recovery.img but with the same results.
I have also tried launching the flash-all.bat from the stock 6.0.1 right after running the bootloader unlock command mentionned previously. But it fails as i guess the flash-all.bat is programmed to reboot the bootloader before flashing. Thus re-locking the bootloader right before attempting to flash it.
I have come here seeking for help as I believe XDA is the most active Android community online.
If my post is somehow against any forum rules here, please be indulgent as this is my first time posting on XDA.
Thanks in advance.
At first, fastboot erase flash is not a working fastboot command. It is used to erase a partition: boot, cache, data...
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
NexusUser5 said:
But, as mentioned, it is temporary as whenever the phone is rebooted it automatically gets locked again.
Click to expand...
Click to collapse
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Primokorn said:
Is your bootloader relocked after typing this?
fastboot oem unlock
fastboot reboot-bootloader
In the stock Android, press Volume up when you see "No Command".
Click to expand...
Click to collapse
Yes the bootloader gets re-locked. And pressing Volume Up doesn't work either.
JonesL said:
Sounds like the EMMC is dying. http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301 you can try using the tool here, test the EMMC and RAM, it'll pretty much confirm it.
Click to expand...
Click to collapse
I've tried the tool and I can't get it to work properly as it gives me an error saying "partition.txt does not exist. Please extract the file from the total binary image."
UPDATE: I just got it to work. The SDRAM test passed but EMMC test failed. So that means it's hard-bricked right? And is changing the motherboard the only way to fix it?
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
audit13 said:
I have a phone that does exactly the same thing. Swapped out only the motherboard and everything is fine again.
Click to expand...
Click to collapse
I suspect a hard-brick, so I am strongly considering it. Would you know if motherboards are carrier specific? Meaning if I get a motherboard from another carrier's Nexus, would it end up changing the carrier of my phone?
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
audit13 said:
Any motherboard from any carrier will work as long as the model numbers match. In Canada, every N5 carried by all carriers is the d820.
Click to expand...
Click to collapse
Thanks a lot for your help, very much appreciated.
Hey guys, so I recently tried re-locking my bootloader in hopes it would just factory reset my device so I could start fresh.
I used
Code:
fastboot oem lock
to lock the bootloader but now I'm stuck at the fastboot screen with this message:
Code:
"ERROR: Slot Unbootable: Load Error"
I cannnot boot into recovery or anything.
Not sure if this means anything but when I use:
Code:
fastboot flashing unlock_critical
I get:
Code:
FAILED (remote: Device already : unlocked!)
But when I try flashing or changing boot slots it says its locked?
Update: I tried using https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 Skipsoft's tool to unlock the bootloader but it says its already unlocked... but when I try to check if it is locked with the same tool it says it locked...?
Anyways I want to see if I can get this fixed, if not I'll try to get it RMA'd. But I really want to fix it. Thanks!
QUICK UPDATE:
Google Issued an RMA on Jan 25th
Jan 31, Received new sealed Pixel 2
VmX5 said:
Hey guys, so I recently tried re-locking my bootloader in hopes it would just factory reset my device so I could start fresh.
I used
to lock the bootloader but now I'm stuck at the fastboot screen with this message:
I cannnot boot into recovery or anything.
Not sure if this means anything but when I use:
I get:
But when I try flashing or changing boot slots it says its locked?
Update: I tried using https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 Skipsoft's tool to unlock the bootloader but it says its already unlocked... but when I try to check if it is locked with the same tool it says it locked...?
Anyways I want to see if I can get this fixed, if not I'll try to get it RMA'd. But I really want to fix it. Thanks!
Click to expand...
Click to collapse
What version?
D3RP_ said:
What version?
Click to expand...
Click to collapse
Thanks for replying,
I was running Android 8.10 the Januaray update, I had the default recovery, and the latest version of ADB.
For Skipsoft's program it was the latest version on their website.
I would try to flash the factory image using the flash-all batch script in an unlocked state.
enzyne said:
I would try to flash the factory image using the flash-all batch script in an unlocked state.
Click to expand...
Click to collapse
I'm not sure how to get to that unlocked state, the device can't flash anything with the bootloader locked.
VmX5 said:
I'm not sure how to get to that unlocked state, the device can't flash anything with the bootloader locked.
Click to expand...
Click to collapse
Just go into the bootloader then run the flash-all from Google factory image
ahoslc said:
Just go into the bootloader then run the flash-all from Google factory image
Click to expand...
Click to collapse
I have, the script ends up saying operation is not allowed in locked state
VmX5 said:
Hey guys, so I recently tried re-locking my bootloader in hopes it would just factory reset my device so I could start fresh.
I used
Code:
fastboot oem lock
to lock the bootloader but now I'm stuck at the fastboot screen with this message:
Code:
"ERROR: Slot Unbootable: Load Error"
I cannnot boot into recovery or anything.
Not sure if this means anything but when I use:
Code:
fastboot flashing unlock_critical
I get:
Code:
FAILED (remote: Device already : unlocked!)
But when I try flashing or changing boot slots it says its locked?
Update: I tried using https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 Skipsoft's tool to unlock the bootloader but it says its already unlocked... but when I try to check if it is locked with the same tool it says it locked...?
Anyways I want to see if I can get this fixed, if not I'll try to get it RMA'd. But I really want to fix it. Thanks!
Click to expand...
Click to collapse
Try Deuces Tool. May work.
I had all sort of weird fastboot failures when my Pixel 2 was connected to a USB Type C port, when I changed to a Type A port, fastboot started working again. Maybe it's your case as well?
D3RP_ said:
Try Deuces Tool. May work.
Click to expand...
Click to collapse
Thanks for replying,
I've tried that, it's a great script btw. But still doesn't work, still can't flash with bootloader locked.
paulomario77 said:
I had all sort of weird fastboot failures when my Pixel 2 was connected to a USB Type C port, when I changed to a Type A port, fastboot started working again. Maybe it's your case as well?
Click to expand...
Click to collapse
Thanks for replying, Good suggestion but can't be. On my laptop there are 2 USB 3.0 ports and 1 USB 2.0 port the Pixel only connects when I use the USB 2.0 port and won't work when I use the USB 3.0 port.
VmX5 said:
Thanks for replying,
I've tried that, it's a great script btw. But still doesn't work, still can't flash with bootloader locked.
Thanks for replying, Good suggestion but can't be. On my laptop there are 2 USB 3.0 ports and 1 USB 2.0 port the Pixel only connects when I use the USB 2.0 port and won't work when I use the USB 3.0 port.
Click to expand...
Click to collapse
Hmm. Try
Code:
Fastboot flashing lock_critical
It will wipe your device if it works. But you'll be unbricked.
D3RP_ said:
Hmm. Try
Code:
Fastboot flashing lock_critical
It will wipe your device if it works. But you'll be unbricked.
Click to expand...
Click to collapse
Already tried that, I'll get this message:
Code:
FAILED (remote: Device already : unlocked!)
Which is kinda weird...
VmX5 said:
Hmm. Try
Already tried that, I'll get this message:
Which is kinda weird...
Click to expand...
Click to collapse
Can you boot TWRP? Or do you at least have it installed?
D3RP_ said:
Can you boot TWRP? Or do you at least have it installed?
Click to expand...
Click to collapse
Didn't have it installed, kinda hoped default recovery was enough.
And can't boot into TWRP, says XXX Failed in locked state.
Anyways thanks for the help so far man, I spoke to a Google rep and said they'd RMA it. I just dropped it off at the post office. I'm kinda disappointed I couldn't fix this one by myself but whatever. Thanks man.
VmX5 said:
Didn't have it installed, kinda hoped default recovery was enough.
And can't boot into TWRP, says XXX Failed in locked state.
Anyways thanks for the help so far man, I spoke to a Google rep and said they'd RMA it. I just dropped it off at the post office. I'm kinda disappointed I couldn't fix this one by myself but whatever. Thanks man.
Click to expand...
Click to collapse
Oh aw, well alright. At least you're gonna have a working phone again, and this time it won't be locked
D3RP_ said:
Oh aw, well alright. At least you're gonna have a working phone again, and this time it won't be locked
Click to expand...
Click to collapse
Haha yea, Now just gotta wait about a week
But thanks for all the help man! Really appreciate it!
Tried rooting my pixel 3 with XDA instructions. Phone bootlooped and went into recovery. Tried restarting, same issue. Tried factory reset, same issue.
I can still boot to fastboot, recovery, barcodes etc.
When the pixel 3 is in bootloader the device is not recognized by adb on mac or pc. Can someone help? Prefer to solve the issue through mac if possible but if PC is the only option I'll greatly appreciate your help too.
Solved
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
I'm love you??????
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Thank you thank you thank you. The last part still got me confused, because I actually pulled from the zipped image file I had. I had an image file on hand, but it just wouldn't work. And I had no idea about the radio, so I just skipped since it didn't seem all that pertinent. This is the second time I've had to get it back to stock, but I couldn't remember for the LIFE of me how I did it. Even though it was literally two hours before this time. Hey! I just don't know when to quit!
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
robertoancini51 said:
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
Click to expand...
Click to collapse
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Click to expand...
Click to collapse
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
robertoancini51 said:
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
Click to expand...
Click to collapse
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
bobby janow said:
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
Click to expand...
Click to collapse
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
bobby janow said:
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
Click to expand...
Click to collapse
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was included in that first time I saw it. lol. Slight panic but the Google helped me out of it. Even knowing what to do it can be a little finicky.
jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you tried flashing the factory image?
abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
What happened exactly? If your bootloader unlocked, and have fastboot access, then you should be able to fastboot the factory image.
LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
You using sudo for fastboot and adb commands?
How'd you install platform tools? I know for me the only thing that worked on Mac was using Homebrew . All other methods were finicky at best
so guys i found a phone from a trash and tried to fix it but i found lot of CRITICAL PARTITIONS and couple of missing partitions... also EDL mode is probably broken too because it automatically goes to bootloader
is there any chance of life on that phone?
Someone probably tossed in in the trash after they took the OOS12 OTA
All jokes aside, is the bootloader unlocked? It's likely fixable if it is
FoxyDrew said:
Someone probably tossed in in the trash after they took the OOS12 OTA
All jokes aside, is the bootloader unlocked? It's likely fixable if it is
Click to expand...
Click to collapse
yes bootloader is unlocked i can now boot to bootloader and flash some custom recoveries but still edl is broken somehow
mxmda said:
yes bootloader is unlocked i can now boot to bootloader and flash some custom recoveries but still edl is broken somehow
Click to expand...
Click to collapse
did you try to flash a recovery that has adb? than you can use adb command to ender edl "adb reboot edl"
FoxyDrew said:
did you try to flash a recovery that has adb? than you can use adb command to ender edl "adb reboot edl"
Click to expand...
Click to collapse
can you link me one?
mxmda said:
can you link me one?
Click to expand...
Click to collapse
https://mirrorbits.lineageos.org/recovery/instantnoodle/20220416/lineage-18.1-20220416-recovery-instantnoodle.img