Develop Bugs

System corrupted, laf removed, fastboot doesnt work, stock recovery is useless.

Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Screen right after fastboot boot:
[500] Fastboot mode started
[600] -- reset --
[610] -- portchange --
[710] fastboot: processing commands
fastboot erase aboot brings:
erasing 'aboot' ... on command prompt
and
[346290] fastboot: getvarartition-type:aboot
[346350] fastboot: erase:aboot
after those appear it just hangs like that
unplugging it after that command gives me:
FAILED (status read failed (Too many links))
finished. total time: 164.350s
on cmd
and
[514820] -- reset --
[514820] EP1/out FAIL nfo=40 p0=f90bao0
[514830] -- portchange --
[514840] usb_read(0) transaction failed
[514890] fastboot: oops!
[514940] fastboot: processing commands
Click to expand...
Click to collapse

Did you ever find a fix for this?

No, its either professional jtag, or maybe the MM stock ota update zip will fix it if it includes the linker. i havent found this ota on the Internets yet though.

i just had the same problem. any fixes?

flash laf via fastboot
sirbow2 said:
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Click to expand...
Click to collapse
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.

nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
thanks for the reply, but as i mentioned in my post, fastboot commands don't work. i wish it was that easy.

nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
I think you have a serious problem
You have to see google fix lg g3 on Qualcomm mode...I mean hard brick fix....
Download as instructed
I think it will be fixed
Recently I fixed lg g3 from only led blink no signal to pc and only vibrate and others

That doesn't work on tmobile G3s, thanks though. I did try it anyways btw.

Getting the update.zip from a friend. its in the SD card but its not showing up in MTP so were trying to figure that out. once i have the zip ill try flashing it. if it doesnt work, itll get a octoplus jtag flash.

Well the update did not like the fact that this phone was missing the linker bin or the previous root because it fails when checking the current system. Looks like octoplus is the only way cause i'm an idiot.
Anyone know where i can send this to get it done? i thought some people on ebay did it but i cant find them.

I have same problem, no download mode, system corrupted and recovery is useless.

mysteryjeans said:
I have same problem, no download mode, system corrupted and recovery is useless.
Click to expand...
Click to collapse
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.

sirbow2 said:
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
Click to expand...
Click to collapse
Finally I recovered it, I have to short testpoint then connect cable to PC, my device is dual sim therefore different logic board, see this http://forum.xda-developers.com/lg-g3/help/lg-d858-qualcomm-test-location-t3293440 for D856/7/8 testpoint to get device into Qualcomm 9008 mode, then I had flash F400K (yes korean rom) tot from thread http://forum.xda-developers.com/showthread.php?t=2785089 using BoardDiagv2.99 http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 to get it live and get into download mode.
Now finally flashed stock KDZ using this post http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
If I knew there is new tool to flash MM stock, I wouldn't brick my device. :silly:

Thats exactly what i tried but didn't work because D851

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks

Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.

BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked

Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem

droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.

BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...

after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool

LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....

try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash

Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.

Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?

I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.

I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?

droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?

Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]

How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?

had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again

Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.

Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse

Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

Question 11.2.4.4 Update Ended Badly - Assistance is Needed on This One

Had an 11.2.3.3 Global rooted via Magisk OP9 Pro that I wanted to update via OTA to 11.2.4.4, which was offered via system update. I used Magisk to restore images before update, did the update, and then went back to install to inactive slot. Rebooted and it was still on 11.2.3.3 so I tried again. Upon trying again, my phone got to a Qualcomm debug/error mode. I experienced this before when on a different boot slot for some other diagnosis of another issue in the past so I switched boot slots.
The other boot slot is stuck in fastboot mode I come to find so I check what it shows if I reverted back to the other boot slot, which was the Qualcomm error. Now instead of a Qualcomm error, it shows language options, one of which is English, and then gives me "boot reason", "wipe data and cache" and "advanced". I believe this is the OnePlus recovery menu, which I have not needed to use before and in the past, used TWRP on other devices.
Can't I just reflash a whole system image for 11.2.4.4 (it'd have to be the European one right now since Global isn't available) via fastboot and it should be fixed, albeit unrooted and I can just re-root? I'd like to try this, but there's no "flash-all.bat" and I don't know the proper flash order for the Euro images within payload.bin as there's no xml file (I looked up a guide for directions on how to flash without flash-all.bat that I have used on other devices). Oh, and I tried to fastboot a known good boot.img and on one of the slots, it works fine, but still wont boot. The other gives error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". I'm stumped.
Wondering if this has been experienced by anyone else before. Wiping my device is the last resort and shall be avoided at all costs after how much I have configured it to my liking.
I saw the following on another guide:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img

Followed this guide here after extracting the Europe full system image via Payload-dumper and it now boots somewhat, but after it looks like it's loading into OOS and boot is complete, I get a black screen instead of the lock screen. I get charging sounds when plugged into the computer, but just a black screen.
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Wondering if this has to do with the Europe 11.2.4.4 on my Global device. Going to try reverting to 11.2.2.2 Global full image now.

Geez, good luck

vibrantliker said:
Geez, good luck
Click to expand...
Click to collapse
Just tried flashing the older 11.2.2.2 images one at a time and now it's stuck in recovery...
The closest I can get it to full booting is with 11.2.4.4 Europe full image and I get a black screen only, after it boots up with the OnePlus logo. When plugged in, I get a charging sound every 10-20 seconds or so. Too bad there's no 11.2.4.4 full image for Global or I'd try that.
Also just tried fastboot boot 11.2.4.4_global_boot.img on this 11.2.4.4 Europe image and still no go. Boots and makes sounds, but black screen still.

Have you tried the MSM tool?

hadesflames said:
Have you tried the MSM tool?
Click to expand...
Click to collapse
I was considering it, but don't want to lose any data. Next step is to contact OnePlus technical support during normal hours and see if they can work with me to resolve this one. I believe I read here on XDA that people have contacted them and usually are able to resolve the issue. Trying to avoid clearing data as the device is fine as it boots, but I think the Europe image is conflicting somewhere and not allowing me into the system since it boots all the way to the lock screen, but I don't see a lock screen, just a blank screen with sounds after boot seemingly working, along with charging sounds (albeit, sounding every 10-20s like its periodically charging).
This is so odd though because I did everything as I should've and update seemingly occurred, but system version still showed 11.2.3.3. So I go back to system update and it said there was an issue and to restart again. Did that two times with magisk revert image and restore to inactive and it then stopped booting.

If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata

djsubterrain said:
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
Click to expand...
Click to collapse
Does stock recovery support ADB? At 8 pro you needed modified one..

pyry666 said:
Does stock recovery support ADB? At 8 pro you needed modified one..
Click to expand...
Click to collapse
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).

djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
Click to expand...
Click to collapse
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though

pyry666 said:
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
Click to expand...
Click to collapse
Yeah I'm working at the moment so not on my own PC, can't really test it out

djsubterrain said:
Yeah I'm working at the moment so not on my own PC, can't really test it out
Click to expand...
Click to collapse
Just tried. ADB with stock recovery is "unauthorized"..So modified is needed if one wants to use stock recovery with adb

djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
Click to expand...
Click to collapse
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).

bulletbling said:
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
Click to expand...
Click to collapse
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.

djsubterrain said:
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
Click to expand...
Click to collapse
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.

bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
Are there actual hw differences between AA and BA?

bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
There's a pinned post at the top of the forum with all the available latest roms. Not sure they've added Global yet tho. Best going there or Oxygen Updater (when the phone is working) than the download page tbh, OnePlus ALWAYS takes ages to add builds there

pyry666 said:
Are there actual hw differences between AA and BA?
Click to expand...
Click to collapse
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.

bulletbling said:
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
Click to expand...
Click to collapse
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..

pyry666 said:
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
Click to expand...
Click to collapse
I wish I could go without my phone for weeks until they post the latest firmware to see if that even works, but I can't so I guess I'll have to use the msm tool and wipe all of my internal storage of documents, including taxes, and various files and downloads I've amassed over the past half decade. This really sucks. All because of a simple OTA that should've never caused this. They really should prevent this from being possible with the OTA update tool built-in to their system.

No bootable a/b slot

Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.

glossallalia said:
Hi all,
I have a T-Mobile Revvlry that I’ve been trying to flash lineage os to. It was unlocked and now after so many tries, it is oem locked
I went through all the unlock bootloader process before and was able to flash but always no os installed are you sure you want to proceed.
Slots a and b were confusing and so I changed the slot to a for flashing but this time the bootloader screen changed along with the serial number and now it is oem locked and can do nothing now .
I tried to boot twrp but no success. How can I oem unlock?? I tried the command fastboot oem unlock and fastboot flash etc but it is denied and that I need a code. Which I do have but don’t know how to use it now.
Click to expand...
Click to collapse
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers

Thank you! Yes I did follow the preinstall instruction and used copy-partitions-20210323_1922.zip several times. But obviously messed it up somehow.
I was missing some of the things you mentioned so I’ll work on that and thanks again!

sd_shadow said:
Did you follow the preinstall instruction and use copy-partitions-20210323_1922.zip?
if not that's what caused the problem.
You will need to use a blankflash to fix
Search for Channel blankflash there are some here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
but you may need a newer one
The device will need to be in Emergence Download Mode (EDL Mode)
Use
Code:
fastboot oem blankflash
or
boot twrp (use full twrp file name)
Code:
fastboot boot twrp.img
and use
Code:
adb reboot edl
EDL Mode is just a black screen, and
Windows device manager will see it as a Qualcomm device (attached)
If it says ..._bulk... you need the Qualcomm drivers
Click to expand...
Click to collapse
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers

glossallalia said:
Blankflash did work to blank the screen. But <adb reboot edl > came back with ‘no devices/emulators found’.
I do have the Qualcomm drivers
Click to expand...
Click to collapse
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.

sd_shadow said:
No, you only use "adb reboot edl" if "fastboot oem blankflash" didn't work.
Now use the blankflash file.
Click to expand...
Click to collapse
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!

glossallalia said:
Ok, when I do the blankflash, there is the blank screen, however I can't communicate with the device after that and if I have lineage.zip or copy-partitions-etc...zip, how could I flash it or what is the next step? I'm new at this - I started this a year ago, after, gave up for a while.
Thanks!
Click to expand...
Click to collapse
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.

sd_shadow said:
If you have run the blank-flash.bat and it worked the device will reboot to bootloader.
If the device remains in EDL Mode, the blankflash failed, you may need a newer version.
You may need to do some searching in the forums for a newer version.
Click to expand...
Click to collapse
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.

glossallalia said:
thanks - blank-flash.bat worked and i'm back to flashing again - I sideload copy-partitions-etc.zip and the lineage.zip and there is 'no os installed...' this happens every time, and before as well. When I 'start' from the fastboot flash mode, it starts to draw the lineage symbol, then goes back to bootloader.
Click to expand...
Click to collapse
what is the file name of lineage.zip?

sd_shadow said:
what is the file name of lineage.zip?
Click to expand...
Click to collapse
LineageOS17.1Modified.img.xz
I went to Motorola website and flashed the firmware to restore the phone to its original state. I'll try lineage again in future and thank you!

Question tried flashing a magisk boot img and now phone is stuck on black screen w/ logo. PLEASE HELP

So I tried flashing a boot img that was modded with magisk, and now the phone is stuck on a black screen with the oneplus logo. When I get into fastboot mode the computer does not recognize it when I type "fastboot devices". I want to flash it back to stock but I'm not sure how. I just got the phone not even an hour ago, and it's already ****ed up.
the command i used was:
fastboot flash boot_a '/media/boris/Downloads/lemonadep/magisk_patched-24306_C48.img'
target reported max download size of 805306368 bytes
sending 'boot_a' (196608 KB)...
OKAY [ 0.829s]
writing 'boot_a'...
OKAY [ 0.560s]
then I did the same with flash boot_b and it basically said the same thing. I am freaking out because if it can't recognize commands in fastboot mode, then I don't know what to do.
Any help would be GREATLY appreciated! I just want to flash to stock now so I can turn on the phone. At least the bootloader was unlocked without anything bad happening.
Thanks!

People need to stop flashing patched boot images, you're supposed to boot them instead and use them to direct install Magisk. This solves two problems - your phone won't brick, and you'll be able to restore the images with Magisk to take incremental OTAs.
You will likely need to use the MSM Tool to recover your phone. Check the How To Guide tag to find the one for your model.

On A12 when I try booting "boot.img" I get stuck in fastboot.. I always flash patched_boot.. But I ALWAYS use latest magisk canary download.. Also OP stated his command was
Fastboot flash boot_a "xxxxxxxxxxxxx"
you need to type fastboot flash boot "magisk_patchedboot.img

Shooter7889 said:
On A12 when I try booting "boot.img" I get stuck in fastboot.. I always flash patched_boot.. But I ALWAYS use latest magisk canary download.. Also OP stated his command was
Fastboot flash boot_a "xxxxxxxxxxxxx"
you need to type fastboot flash boot "magisk_patchedboot.img
Click to expand...
Click to collapse
Doesn't make any sense that you get stuck in fastboot when trying to boot the same image that you then flash... This is the proper way to install Magisk with the boot and direct install method and it works when it's done properly.

On The Go Repairs said:
u need to find download of whichever OS u we're on.. OS11.xxx or OS12(C48, or whichever it was) and get it on ur pc, there is thread in this forum that should have all stock boot and patch boot imgs of all different versions. So u don't have to download the whole zip and dump yourself. If u try rooting again u need to just "fastboot flash boot magisk_patchedboot.img." not _a and _b..
Click to expand...
Click to collapse

On The Go Repairs said:
So I tried flashing a boot img that was modded with magisk, and now the phone is stuck on a black screen with the oneplus logo. When I get into fastboot mode the computer does not recognize it when I type "fastboot devices". I want to flash it back to stock but I'm not sure how. I just got the phone not even an hour ago, and it's already ****ed up.
the command i used was:
fastboot flash boot_a '/media/boris/Downloads/lemonadep/magisk_patched-24306_C48.img'
target reported max download size of 805306368 bytes
sending 'boot_a' (196608 KB)...
OKAY [ 0.829s]
writing 'boot_a'...
OKAY [ 0.560s]
then I did the same with flash boot_b and it basically said the same thing. I am freaking out because if it can't recognize commands in fastboot mode, then I don't know what to do.
Any help would be GREATLY appreciated! I just want to flash to stock now so I can turn on the phone. At least the bootloader was unlocked without anything bad happening.
Thanks!
Click to expand...
Click to collapse
what rom are you on? OOS 12?
then you need to patch & flash boot. vendor_boot and reflash vbmeta

Thank you for the prompt responses! My computer can send commands to the phone now through fastboot mode, for a while it was going straight to fastboot mode but now after trying to flash stock, it again is stuck on the oneplus logo on boot. I am downloading the MSM tool now, hopefully it will work. And I was suprised that their isn't a United States version of the firmware, the closest match I have found is the "global firmware" so that's what I will use.
On my other phone (s10 lite) I was able to just flash a lineage recovery image, then install magisk through recovery. I wish it was this easy for oneplus but apparently it's way more complicated. I'm guessing the MSM tool is like Odin for samsung phones. I wish their was an official program that could factory reset the phone, the way samsung does it with odin, or how chrome can factory reset a google pixel straight off their website. oh well. I'm not going to give up just yet...

OnTheGoRepairs said:
Thank you for the prompt responses! My computer can send commands to the phone now through fastboot mode, for a while it was going straight to fastboot mode but now after trying to flash stock, it again is stuck on the oneplus logo on boot. I am downloading the MSM tool now, hopefully it will work. And I was suprised that their isn't a United States version of the firmware, the closest match I have found is the "global firmware" so that's what I will use.
On my other phone (s10 lite) I was able to just flash a lineage recovery image, then install magisk through recovery. I wish it was this easy for oneplus but apparently it's way more complicated. I'm guessing the MSM tool is like Odin for samsung phones. I wish their was an official program that could factory reset the phone, the way samsung does it with odin, or how chrome can factory reset a google pixel straight off their website. oh well. I'm not going to give up just yet...
Click to expand...
Click to collapse
MSM Tool factory resets the phone when it flashes. It's just like Odin only less complicated because once the device is in the right mode, you just click Start and don't have to deal with anything else (I would actually click Start before connecting the device though so it's looking for it, it only stays in edl mode for a few seconds before it tries to reboot so you can get a Sahara error if you aren't quick enough).
Global = USA basically.

I am unable to get the phone into EDL mode, or have it showup in device manager as qualcom whatever. I press both volume up and volume down with phone powered off, then plug in. I even set everything up on a new computer just so it wouldnt have any left over driver stuff from my samsung phone. No matter what I try, it does not show up under COM in the MSM tool. I'm kind of starting to freak out, cuz I just spent almost $450 on this phone, and right now it's useless. And originally it was running stock, (to the person who asked).

OK, it shows in my device manager properly as QUALCOM blah blah blah, but does not show in MSM tool. at least i'm making progress.
OK! I had to open the program while it was in EDL mode, now it shows properly and it is flashing. thank god! I just wish it wasn't so complicated to root this ************...

phone is now unbricked and I will be more careful with rooting from here on out. thank you for the help people! i'm going to try following the main root tutorial on the oneplus 9 pro forums and see how that goes. i tried booting (not flashing) with a magisk modded boot.img and it booted to a black screen (pretty sure edl mode interestingly enough), then I realized it wasn't the same version as what I was running, since the msm tool put it on an old version. i'm going to update to the latest before trying again.

So I followed this guide: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-48.4252373/
and I tried using the patched boot.img's linked on the page and they didn't work. Then I made one from scratch using the latest oneplus firmware and patched it myself, and voila! it worked! I'm pretty happy with this phone so far, although it's a pain in the ass to start over and set everything up again. Not having an sd card sucks, but oh well.. I will try flashing a custom rom at some point when I get bored.