Related
Hey all! Think I managed to bugger it nice and good this time. I have the verizon variant of this phone and recently unlocked its bootloader. I followed netookska5's guide to unlocked and ended up on G710VM20g with root. All seemed well so I went on to start playing with the firmware, specifically prodding at the way force encrypt is implemented. I found the contents of the ramdisk in boot_a were easy enough to modify and boot from temporarily using fastboot but then hit a bit of a roadblock.
After a reboot I found the bootloader played the verizon boot animation but didn't seem to have any incentive to continue past flashing the dots. I rebooted into download mode and reflashed the vm20g kdz in lgup, and still faced the same problem. I tried crossflashing to the ulm11g kdz I used to unlock the bootloader and faced the same issue there. Flashing back to vm20g yielded an odd result where the bootloader still doesn't make it into the initial setup but anytime when force reset with pwr + vol down the factory reset "erasing" animation plays before the bootloader tries to start again, regardless of if there is any data on the userdata partition. Flashing individual partition images extracted from the kdz over qfil doesn't provide any differing results.
I can't get any logs to see what's actually happening as enabling adb in the ramdisk doesn't do anything because the bootloader uses the usb port as "LGE AndroidNet USB Serial Port" in windows and is just as unhelpful under linux. I'm downloading another kdz to test as the other two were both android 9, but aside that I'm mostly out of ideas. It doesn't seem worth attempting to get the kernel to output the console over this serial port as from what documentation I've found its not likely the serial will even support console output. Anyone have any ideas? I can get into download mode, fastboot, twrp, and su shell through twrp.
So as a follow up to this, the vm10i kdz also doesn't work. Got a dmesg from twrp and the official laf in download mode, both boot without any issue so nothings really jumping out at me so far.
laf_a dmesg https: //pastebin .com/cbMxFGm8
twrp dmesg https: //pastebin .com/0mtq3jF2
The download mode serial only responds to the dmesg command and only serves its own log. Haven't found a way to communicate with the boot_a serial yet. Going to flash to em20b and give lineageOS a shot.
orbitalm99n said:
Hey all! Think I managed to bugger it nice and good this time. I have the verizon variant of this phone and recently unlocked its bootloader. I followed netookska5's guide to unlocked and ended up on G710VM20g with root. All seemed well so I went on to start playing with the firmware, specifically prodding at the way force encrypt is implemented. I found the contents of the ramdisk in boot_a were easy enough to modify and boot from temporarily using fastboot but then hit a bit of a roadblock.
After a reboot I found the bootloader played the verizon boot animation but didn't seem to have any incentive to continue past flashing the dots. I rebooted into download mode and reflashed the vm20g kdz in lgup, and still faced the same problem. I tried crossflashing to the ulm11g kdz I used to unlock the bootloader and faced the same issue there. Flashing back to vm20g yielded an odd result where the bootloader still doesn't make it into the initial setup but anytime when force reset with pwr + vol down the factory reset "erasing" animation plays before the bootloader tries to start again, regardless of if there is any data on the userdata partition. Flashing individual partition images extracted from the kdz over qfil doesn't provide any differing results.
I can't get any logs to see what's actually happening as enabling adb in the ramdisk doesn't do anything because the bootloader uses the usb port as "LGE AndroidNet USB Serial Port" in windows and is just as unhelpful under linux. I'm downloading another kdz to test as the other two were both android 9, but aside that I'm mostly out of ideas. It doesn't seem worth attempting to get the kernel to output the console over this serial port as from what documentation I've found its not likely the serial will even support console output. Anyone have any ideas? I can get into download mode, fastboot, twrp, and su shell through twrp.
Click to expand...
Click to collapse
the ramdisk in boot is not the os ramdisk its the recovery ramdisk the , ramdisk in root of the /system partition
J0SH1X said:
the ramdisk in boot is not the os ramdisk its the recovery ramdisk the , ramdisk in root of the /system partition
Click to expand...
Click to collapse
huh, actually thinking about it this makes a world and a half more sense. In my head I was thinking about a linux kernel using an initramfs on a shared boot partition and then only later switching roots. Since the system_a image doesn't have the usual kernel headings and is just an ext4 image, I have to assume the bootloader loads the kernel from boot_a and then decides which partition gets put on the root? Thanks for the tip off though!
Somewhere between vm11g, em20b, and vm20g with a little fumblery inbetween I ended up in the initial setup again. Don't know what survived flashing but got fixed by a certain crossflash, gremlins probably
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
durrant111 said:
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
Click to expand...
Click to collapse
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
you can fomat data : - and power before click power
durrant111 said:
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
Click to expand...
Click to collapse
Boot to EDL mode by holding the vol - and power button while your G8 is plugged in your computer, after you hear a disconnection sound immediately press the vol + until you hear a connection sound from your computer.
Now, open QFIL then look for the abl a and b then flash your backed up abl_a nd abl_b accordingly and reboot. And you're good to go again.
I can help you. Do you fix problem ???
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Anybody?
Ratty696 said:
Anybody?
Click to expand...
Click to collapse
.
Ratty696 said:
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Click to expand...
Click to collapse
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
Used method in beginning of this thread. Tried flashing backup
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Ratty696 said:
Used method in beginning of this thread. Tried flashing backup
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Click to expand...
Click to collapse
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
armodons said:
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
Click to expand...
Click to collapse
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Ratty696 said:
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Click to expand...
Click to collapse
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Nobody able to help me?
Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
I'm new to the G8 (not LG), so just now browsing these posts.
First and foremost, this thread shouldn't be in this forum. This forum is for roms, kernels, recoveries and other development.
This thread is a question about a guide (which is in guides forum). This 'question' is not development of a rom, kernel or recovery, it's a question.
I'd suggest, if you want people to respond that can help, ask the question in it's individual guide thread, that's where the people that know the most about it will be. If you get no response in that thread, then maybe think about posting the question in the questions forum.
but here? in dev forum? absolutely the wrong place for a question about a guide.
cheers
Thread moved to Q&A section.
Thanks!
woodman
Senior Moderator
@durrant111
So to the original OP; 2 things; If your device isn't recognized when in fastboot mode, that's because you don't have the right driver installed in WinBlows.
You have to download the LG USB drivers, install them, then in device manager select the "! Android" and install the driver (usually says ADB) and then 'fastboot devices' will see the phone.
Second; if you ever get a message telling you that 'Data Overflow' then you are absolutely making a big mistake. When you did the backup of your abl(s) (and other partitions), you should have renamed then one by one, that way you don't make the mistake of naming the laf_a partition as the abl_a partition (or any name other than what ti should be). If you flash the wrong partition you run the risk of overwriting the nearby partition, which would make the device essentially unusable except only to qfil.
Lastly, yer lucky the device is VZW, as they make their kdz available and you can use use lg up to get back to stock. If it was Sprint or At&t you'd be scrambling to find a qfil or bkerler backup someone luckily made that you come across (a much more unlikely scenario).
Good luck, you've probably already moved on from this, but just in case, thought I'd mention the above.
cheers
Ratty696 said:
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Click to expand...
Click to collapse
Unfortunately at&t doesn't make their kdz available. You can be 99.9% positive the only thing this person that wants to charge you 30$ is going to give you is the partitions backed up by qfil or bkerler edl stuff.
With both at&t and sprint, because no kdz, you can only restore (if you didn't back up the files yourself originally), with someone elses backup, and then you have to use qfil or bkerler edl utilities to restore. If you look around in the G8 forums (or the tele group), there's a decent chance someone has already make their backup available.
cheers and good luck.
Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Yarib said:
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Click to expand...
Click to collapse
Lol no still haven't solved my problem. I need the abl_a and abl_b files for a lg g8 at&t. My phone only goes in fastboot or qfil and Fastboot says its a lmg850um because I tried using the files from my lg g8x and it didn't work. I have also now bricked my lg g8x it only boots into qfil. Any help would be great. My g8x is canada version
hey, i have a completely stock 9 pro, i was texting someone and sending them pictures from the night but while i was doing that the phone suddenly crashed to the lock screen over and over again. so i just hard rebooted it since it was completely unresponsive and just crashing on the lock screen and now it will not even boot up it just shows the oneplus log and a field to put in a password and after entering the password its looking to format the phone and probably factory reset the whole device i was hoping that there would be some way to use adb to get my photos back since i didnt get a chance to save or send them and it would be a real bummer if they were gone. not enough to pay 1000s of dollar but enough that i would spend time playing with adb to recover them. im very familiar with commandline and adb but i dont know of a way to get in without unlocking the bootloader first.... any help would be very much appreciated.
Can you manage to boot into fastboot and try some things there?
Setup platform tools (let me know if you do not have it setup) and then boot into fastboot. Connect your device to your computer and try out the following commands :
fastboot getvar current-slot
If this outputs something like :
current-slot: b
Then run the following command :
fastboot --set-active=a
otherwise, run the following command :
fastboot --set-active=b
After this is done, reboot your device by running :
fastboot reboot
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
I never set bios or lockscreen passwords, or encrypt data drives. You are the one most likely to be locked out, sometimes through no fault of your own. People will steal these devices regardless if they're locked or not; physical security is the only type of security that works.
wjcrabtree said:
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
Click to expand...
Click to collapse
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
ekin_strops said:
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
Click to expand...
Click to collapse
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
You can't do a factory reset from there?
It's rare but a SEU can corrupt any part of the flash memory. It causes no physical damage but the altered memory cells will need reset.
I think the best way to recover is MSM tool for youre specific model phone.
My phone power off by it self after watching a video on a received link with whatsapp.
Nothing workt beside MSM. I factory reset, downgrade rom. flash-reflash rom's.
MSM wipe all in youre phone.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Thank you so much!!
Sorry for the slow reply, but I haven't had time to deal with the problem because of work. I'll be looking into this today.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Ho Lee Sheet! I finally got around to dedicating serious time to working on this.
I had to jack-around with it quite a bit to get Windows 11 to load the proper drivers so that the phone would be recognized, but: BOOM! BACK IN BUSINESS!
Thank you so much for the guidance.
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
mbj731 said:
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Click to expand...
Click to collapse
Also, you need T-Mobile msm
oddlyspaced said:
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
Click to expand...
Click to collapse
I've tried that. Still no luck. Getting either "IMEI is incorrect" or "device doesnt match image" errors. Kind of odd getting different errors each time.
jamescable said:
Also, you need T-Mobile msm
Click to expand...
Click to collapse
I've tried them all just hoping one will work. Tmo-EU, Tmo, EU, Global etc etc
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
I use USB C to USB C 3.2 with no issues
Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
mbj731 said:
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
Click to expand...
Click to collapse
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Shooter7889 said:
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Click to expand...
Click to collapse
Yes, I had been running on A13 for a few days. Got the itch to root but as I said, I couldnt unlock bootloader (kept saying to flash token) so I decided to start the whole process over, unlock the bootloader and try to manually flash A13 instead of doing a local upgrade. (hadnt hit OTA for me yet)
During the process, theres a point where you have to boot in to fastbootD to flash critical partitions that wont flash in regular fastboot.... using the commands "fastboot reboot fastboot" wouldnt get me to fastbootD as I read it's supposed to. I think during all that and scrolling through the bootloader menu, I hit "recovery mode" which was apparently wiped because I just went straight to a black screen and thats where it's been ever since. I did all the button combos etc thinking it would just go back to bootloader but to no avail.
I wish there was a way to do manual commands in EDL or something. Maybe bootloader is there just that it's not responding to the hardware keys?
Oh. When u tried to unlock BL did u try "fastboot oem unlock? Yeh usually, eben if I mess up with msm or flashing imgs, it will kind of get stuck in edl, and I have to hold all three hardware buttons for some time b4 it will finally respond
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
kjslabber said:
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
Click to expand...
Click to collapse
I taped all the buttons down and I'll watch it for a while and see if it boots up. I have tried holding them for a very good while with no luck already though
Shooter7889 said:
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
Click to expand...
Click to collapse
I've tried the IND MSM gives me an "unsuspected target TMO" error or something like that. So at least some tools are seeing it as TMo... Tmo tools say the device doesnt match! I'll have to find another computer or 2 to try.. I was supposed to ship off my oneplus 7t tomorrow for trade in on this 9 pro but now I'm using the 7t again as it's my only working device. this has been a headache. lol
thanks for the feedback. I'm trying everything I can think of and researching too
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
mbj731 said:
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
Click to expand...
Click to collapse
Every one of us that's been at this long enough has gone thru this or a similar experience. It's a lot more headache but you also learn a lot more for the next time or to help others. Congrats on getting it up
mbj731 said:
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
Click to expand...
Click to collapse
You can use python3 to decrypt the .ops file, edit the first line parameters in the settings.ini, then python3 to encrypt the folder that was decrypted. Slow process but gives extra options.....
Hi there, I am encountering the following issue.
It is a hindi op9 pro
The situation:
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
Any ideas or advice? Plz help
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
it keeps on cycling back to 9008 so what you meant by xbl or abl is broken? Any solution ?
Renate said:
Can you locate the Firehose loader?
Click to expand...
Click to collapse
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
My msm tool from that
Renate said:
Have you tried various USB problem solving, different cables, different ports?
Click to expand...
Click to collapse
Yes I think it is no issues with my cable
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
FOR MORE DETAILS
I tried upgrading my device using fastboot firmware according to the following according to this article
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
when I reached to put commands in cmd and wrote
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
then reboot by
fastboot reboot fastboot
it gets stuck in edl mode and no anything showing just " Qualcomm HS-USB QDLoader 9008" showing in the device manager, appearing and disappearing about every five seconds
so the situation is
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in the device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Click to expand...
Click to collapse
Fastboot commands already worked and I used them to upgrade my phone according to the article above, so when finished, I put a reboot command, and then it got stuck on EDL mod, so I tried to repair it using MSM tool it always says Sahara communication failed, any way to fix it plz my phone is new
Click to expand...
Click to collapse
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Renate said:
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Click to expand...
Click to collapse
thank you but is there a video explaining it bcz I am a noob in this stuff plz.
or you can contact my device using TeamViewer and try to fix it plz.
I don't know your partitions well enough.
If it wants a two stage reflash with 1/2 by (abl) fastboot and 1/2 by (recovery) fastbootd then you need a working recovery and I'm not sure that you have one.
The original post didn't indicate that you were able to reach/use fastboot.
I jumped on this because it seemed to be about USB/Sahara which I know something about.
We need the advice of somebody who knows more about your model.
Sorry
Can you tell how you ended up in this state? If you are a noob, why did you start wipe stuff from your phone without knowing how to what you are doing?
I would guess you thought a custom rom sounded nice but you don't have a clue what to do when things are starting to go south..
Edit: We, as a community always try to help out as much as we can but (and there is a BIG but) you have to understand the basics before you even start to do stuff or you will learn the hard and in some cases expensive way.
Read and do research at least for a few month, like reading most of the threads here and try to figure out how things work.
recovered my noodlep a week ago using this:
How to recover your device after flashing incorrect DDR xbl images
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now... Even I was aware which DDR model was my device, yes.. I did it :D - flashed by mistake DDR4 xbl.img to my DDR5 noodlep...
forum.xda-developers.com
You may want to check it out....
Best luck. and don't worry. Just follow the steps and you'll recover your device.