Related
steadfasterX said:
Well first of all your issue is not an UsU issue .
This thread is only about UsU so this is going more and more off topic .
I would suggest you open an own thread for your specific issue and we continue there.
You wrote you flashed all partitions of that kdz. Write down (in that new thread ) which partition names exactly.
Click to expand...
Click to collapse
Lets start from the beginning then, shall we;
I have a LG G4 H815 TWN variant. It was on LP for the longest time because it had root, and there was no chance for an official unlock.
My phone WAS on LL/LP because the phone suffers ILAPO but was recommended I upgrade, so I use a KDZ i found [H81520e_00_0818.kdz][9C861EA87A0E07C873A7835ABF21A5CE]. flashed through LGUP. (unsure where I originally found this file)
fine and removed the battery when it attempted to reboot the phone (still saw the LG logo)
I presumed all was fine then followed the guide to install UsU, which went fine (used option 3, files from PC)
Flashed a '4 core fix' version of TWRP
Formatted Data, after the phone showed 0 bytes free. After formatting, everything seemed fine.
Installed LOS 15.1 UsU version from SFXs website
Now here is where it went pear shaped.
Booting would always result in TWRP being launched, no matter what.
I was told it may have been ILAPO catching the boot of the new OS, so i should patch my boot.img.
I patched the boot.img, but accidentally flashed aboot due to unclear instructions and an incorrect guess on my behalf.
I was then told to use some specific QFIL guide to recover from my brick. The process succeeds.
But I am back to square one. Booting only to TWRP
Follow FAQ #20
-Downloaded this KDZ this time, instead of using my original KDZ from before
-Downloaded newest current version of FWUL (v3)
-Ran KDZ extract via SALT
-FASTBOOT flashed extracted files. (All finished OK)
Code:
fastboot flash factory factory.image
fastboot flash hyp hyp.image
fastboot flash modem modem.image
fastboot flash pmic pmic.image
fastboot flash rpm rpm.image
fastboot flash sbl1 sbl1.image
fastboot flash sdi sdi.image
fastboot flash sec sec.image
fastboot flash tz tz.image
-Rebooted. (boots only into TWRP)
- - - - - - - - - - -
SALT says the firmware is still: LGH815AT-00-V10f-TWN-XX-JAN-13-2016+0 - which to me looks like its still LP firmware.
- - - - - - - - - - -
I tried flashing a different OS (after formatting of course), for the sake of it, maybe it'd be different somehow, i tried; RR-O-v6.0.0-20180622-h815-Unofficial.zip
then flashed H815_UsU_baseband_flash-in-twrp.zip too.
still only boots to TWRP.
steadfasterX said:
Also let it bootloop and when back to TWRP :
adb shell
strings /dev/block/bootdevice/by-name/misc | head -n 6
Write the output in your new thread as well
Click to expand...
Click to collapse
Code:
BSP Forever
SM03s151212002753
0,1111111111111111
LGH815AT-00-V10f-TWN-XX-JAN-13-2016+0
LGH815AT
LGH815AT-00-V10f-OPT1-YT-JAN-13-2016+0
QFPROMalreadyblown
1,12,0212,21,2011,201,1,111,1,331122,10,0,1200,2,1,1,1,213,10222,0,2,2,0,2,2,2,2
"1","fff,fff,ffffffff,ffffffff,55"
not sure if this is the sort of stuff you wanted. I couldnt get adb shell to work from within TWRP so i just used the terminal from within TWRP and wrote out the output here instead.
I hope this is enough information for @steadfasterX
I thank him for all his time and effort on the unlock and also the time on the forums helping dummies like me.
tim455 said:
I hope this is enough information for @steadfasterX
I thank him for all his time and effort on the unlock and also the time on the forums helping dummies like me.
Click to expand...
Click to collapse
Flash this one in TWRP:
http://leech.binbash.it:8008/stock/LG/h815/
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
Wipe -> advanced -> select system and wipe it
Reboot -> recovery
Download & flash:
http://leech.binbash.it:8008/lineage/nougat/h815-UsU/
--> lineage-14.1-20190120-UNOFFICIAL-h815_usu.zip
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Flash this one in TWRP:
http://leech.binbash.it:8008/stock/LG/h815/
--> h815_20p_bootloader_29a_modem_TWRP-flashable.zip
Wipe -> advanced -> select system and wipe it
Reboot -> recovery
Click to expand...
Click to collapse
Thanks for the simple instructions. Turns out I couldn't follow them through to the end.
I wiped my system so it was clean prior to this, so I didnt mess anything else up. (I've done this before with no issue)
Flashed the bootloader/modem zip, then restarted (to recovery).
black screen, and a hard brick.
- - - - -
after that. I "played around" to see if i could maybe fix the issue myself and try again. using that same qfil guide as before. but this time, ran into an error..
Code:
COM Port number:4
Sahara Connecting ...
Download Fail:Could not connect to the COMPORT
Download Fail:Sahara FailValue cannot be null.
Parameter name: key
Finish Download
Device manager shows the little orange warning sign, but the drivers appear to be correctly installed.
EDIT: needed to be in unsigned driver mode. phone booting in TWRP again.
EDIT2: tried installing the LOS zip and get an error
E3004: This package is for device: g4,p1,h815,h815_usu; this device is []ro.product.name ----(a square box with a character it couldnt read)
I can try restoring an old backup I have if you think that would be wise, but I dont think I will play with it any more before hearing from you again. It's definitely the bootloader/modem zip thats causing the brick btw.
tim455 said:
Thanks for the simple instructions. Turns out I couldn't follow them through to the end.
I wiped my system so it was clean prior to this, so I didnt mess anything else up. (I've done this before with no issue)
Flashed the bootloader/modem zip, then restarted (to recovery).
black screen, and a hard brick.
- - - - -
after that. I "played around" to see if i could maybe fix the issue myself and try again. using that same qfil guide as before. but this time, ran into an error..
Code:
COM Port number:4
Sahara Connecting ...
Download Fail:Could not connect to the COMPORT
Download Fail:Sahara FailValue cannot be null.
Parameter name: key
Finish Download
Device manager shows the little orange warning sign, but the drivers appear to be correctly installed.
EDIT: needed to be in unsigned driver mode. phone booting in TWRP again.
EDIT2: tried installing the LOS zip and get an error
E3004: This package is for device: g4,p1,h815,h815_usu; this device is []ro.product.name ----(a square box with a character it couldnt read)
I can try restoring an old backup I have if you think that would be wise, but I dont think I will play with it any more before hearing from you again. It's definitely the bootloader/modem zip thats causing the brick btw.
Click to expand...
Click to collapse
I am soooo sorry dude.. I wrote the wrong file name. You have to flash ofc an UsU zip not the other.. I have corrected it above but here again:
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
That one does not cause a brick!
Your current state means you have to use SALT to flash UsU again. Afterwards you should be able to install the LOS zip without an issue
sorry again.. I am doing all this in parallel of my work and private life which both are continuously stressful since years and well yea I haven't thought before writing, that can even happen to me..
,.-
steadfasterX said:
I am soooo sorry dude.. I wrote the wrong file name.
sorry again.. I am doing all this in parallel of my work and private life which both are continuously stressful since years and well yea I haven't thought before writing, that can even happen to me..
Click to expand...
Click to collapse
It's okay dude. I can understand your mis-concentration due to stress. Don't worry about it. :good:
You're always helping others.
steadfasterX said:
You have to flash ofc an UsU zip not the other.. I have corrected it above but here again:
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
That one does not cause a brick!
Your current state means you have to use SALT to flash UsU again. Afterwards you should be able to install the LOS zip without an issue
Click to expand...
Click to collapse
I flashed UsU again via SALT (although it still said UsU was installed correctly) and got a weird message saying that something didnt work (attached)
tried to install LOS after, but was hit with teh same error message. had to reflash TWRP in order to get it to continue.
Installed LOS and.................. always boots to TWRP :\
I've attached logs again.
tim455 said:
I flashed UsU again via SALT (although it still said UsU was installed correctly) and got a weird message saying that something didnt work (attached)
tried to install LOS after, but was hit with teh same error message. had to reflash TWRP in order to get it to continue.
Installed LOS and.................. always boots to TWRP :\
I've attached logs again.
Click to expand...
Click to collapse
Yes that message is normal in your case . No need to worry.
So it let you flash LOS now without an error?
Well if you can come to IRC from Monday to Friday , 9am-5pm UTC+1 ..
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Yes that message is normal in your case . No need to worry.
Click to expand...
Click to collapse
great.
steadfasterX said:
So it let you flash LOS now without an error?
Click to expand...
Click to collapse
Yes. It now installs fine and finishes without any errors.
steadfasterX said:
Well if you can come to IRC from Monday to Friday , 9am-5pm UTC+1
Click to expand...
Click to collapse
Sure. Not really used to IRC. I'm taking a look now (even though its after those times) and just asking which channel should I join to talk to you about this? (what should I say or ask?)
tim455 said:
great.
Yes. It now installs fine and finishes without any errors.
Sure. Not really used to IRC. I'm taking a look now (even though its after those times) and just asking which channel should I join to talk to you about this? (what should I say or ask?)
Click to expand...
Click to collapse
All my main threads have a topic for
"support/irc "
like the SALT one:
https://forum.xda-developers.com/android/software-hacking/tool-salt-lg-revolution-t3717864
Sent from my OnePlus 6T using XDA Labs
I just got a Sprint LS991, i have a VS986 that i Was used to where all the way up to 2BA Firm ware i could go all the down to 13B firmware and root. Now with this LS991 i am at ARB4 right off the bat on ZVI firmware. I cannot even do the USU method to unlock the bootloader. I really want to Sim Unlock this device and gain root.
Is there any possibility of wiping out the partition that contains the ARB somehow so a downgrade can be preformed? Or any method of any way shape or form. I also have a H810 main board G4 with H811 stickers and firmware (Bootloader Unlocked) but it is stuck in a bootloop and i only got it to turn on once since that happened with the oven method and now its stuck at the boot screen only and freezes.
robles4242 said:
I just got a Sprint LS991, i have a VS986 that i Was used to where all the way up to 2BA Firm ware i could go all the down to 13B firmware and root. Now with this LS991 i am at ARB4 right off the bat on ZVI firmware. I cannot even do the USU method to unlock the bootloader. I really want to Sim Unlock this device and gain root.
Is there any possibility of wiping out the partition that contains the ARB somehow so a downgrade can be preformed? Or any method of any way shape or form. I also have a H810 main board G4 with H811 stickers and firmware (Bootloader Unlocked) but it is stuck in a bootloop and i only got it to turn on once since that happened with the oven method and now its stuck at the boot screen only and freezes.
Click to expand...
Click to collapse
you are out of luck dude. ARB is no partition - consider to read the technical details if interested ( https://bit.do/antirollg4 ).
It is a physical fuse and so irreversible (means it requires to replace parts on the mainboard to make it work again - nobody knows which/what though).
No root as you are on MM as well and you cannot downgrade due to ARB.
.-
I have the G710EMW variant. As the title states, I was trying to install Lineage OS following sirbow2's thread 'Lineage OS 16/17/GSI Install Guide for LG G7 ULM'. Using the universal unlock method, I unlocked my phone. Next step was installing 21d ULM firmware; this is where I am stuck. When I begin the installation using LGUP, the phone boots into the rooted fastboot mode instead of the download mode. I even tried switching slots but it still boots up in fastboot mode.
Also, when I am able to load the download mode, it stays at the download mode screen & doesn't actually proceed further & neither is the device detected in device manager when it is connected in the download mode.
I've rooted quite a few phones in the past but this one has troubled me a lot. It is very difficult to find time for all this when you're working a full-time job. Please help me fix this. I'm happy even just to return to the stock LG ROM (which reminds me that the same thing happens when I try using the LG Bridge tool).
Thank you!
use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.
sinkoo1979 said:
use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.
Click to expand...
Click to collapse
Already tried that method. Everything works fine until the phone boots to start installation. Ideally it should start in download mode but in my case, it boots into the rooted bootloader.
@Awesomeslayerg was kind enough to message me this link (https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841) which helped me fix my problem.
Not only was I able to revert to stock; I went ahead to install LineageOS 17 which is amazing!
Thank you, Awesomeslayerg.
This thread can be marked as fixed now.
Please Help!!!! New to all of this.
Firstly my phone hung and wouldn't turn on. Finally later at night after non stop trying I realised it open in recovery and fastboot mode.
Recovery had the following options: (Didn't try fastboot)
- Install from internal storage
-Install from ADB
-Wipe data and cache
-Advanced
-Exit
Tried all options finally did a wipe cache and partition in data and cache
I wanted to save my data so didn't try adb
later the next day when i tried again it wouldn't turn on at all. Brick mode.
Checked online came across. https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
used the Method 2. Managed to get recovery installed the OS as mentioned with the thread. Nothing dif.
It wouldn't boot completly. It would go to "installing Android aps" and then reboot.
It wouldn't open in recovery as well, just fastboot. The next day even the OS stopped loading it would brick again and only load fastboot "Device State: Locked"
Tried the above method again. Used the MSM tool few times but still doesn't go past. Will only boot in fastboot mode.
Can't find any other option.
Anyway to proceed?
orlan7 said:
Please Help!!!! New to all of this.
Firstly my phone hung and wouldn't turn on. Finally later at night after non stop trying I realised it open in recovery and fastboot mode.
Recovery had the following options: (Didn't try fastboot)
- Install from internal storage
-Install from ADB
-Wipe data and cache
-Advanced
-Exit
Tried all options finally did a wipe cache and partition in data and cache
I wanted to save my data so didn't try adb
later the next day when i tried again it wouldn't turn on at all. Brick mode.
Checked online came across. https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
used the Method 2. Managed to get recovery installed the OS as mentioned with the thread. Nothing dif.
It wouldn't boot completly. It would go to "installing Android aps" and then reboot.
It wouldn't open in recovery as well, just fastboot. The next day even the OS stopped loading it would brick again and only load fastboot "Device State: Locked"
Tried the above method again. Used the MSM tool few times but still doesn't go past. Will only boot in fastboot mode.
Can't find any other option.
Anyway to proceed?
Click to expand...
Click to collapse
Re-download everything and try again. If still not successful, try the later versions of the MSM Tool (search XDA for a thread containing all the versions) and with it the later versions of OOS.
If still not successful, it might be a hardware fault.
Tried to find the later versions of MSM tool. The one i used was 3.0.
I managed to find the updated OS.
I found a link for MSM tool 3.0.6 but it has limited download size of 1gb before you sign up & the file size is 1.5 GB. Will continue looking for another link.Hopefully it works.
orlan7 said:
Tried to find the later versions of MSM tool. The one i used was 3.0.
I managed to find the updated OS.
I found a link for MSM tool 3.0.6 but it has limited download size of 1gb before you sign up & the file size is 1.5 GB. Will continue looking for another link.Hopefully it works.
Click to expand...
Click to collapse
Check THIS thread.
TNSMANI said:
Check THIS thread.
Click to expand...
Click to collapse
I have. Even though it mentions MSM tool 3.0.6, on dowload it is 3.0.0. Even though still gave it a shot, but its the same output. Only fastboot with device locked.
I have searched through Xda as well as google for MSM tool higher than 3.0, been unlucky. Didn't come across any for OP3.
orlan7 said:
I have. Even though it mentions MSM tool 3.0.6, on dowload it is 3.0.0. Even though still gave it a shot, but its the same output. Only fastboot with device locked.
I have searched through Xda as well as google for MSM tool higher than 3.0, been unlucky. Didn't come across any for OP3.
Click to expand...
Click to collapse
I don't know which file you downloaded. The one downloaded by me last year and successfully used was Android 9 OOS 9.0.6. It contains version 4 of the Tool and OOS 9.0.6. Version 3 of the Tool will not work with OOS 9.0.6. The Tool is specific to the OOS version.
Prior to that I used version 3 of the Tool and OOS 3.1.2 from the Mega Unbrick thread you linked and that too was successful.
Be patient and try again. I have also noticed that sometimes for some people, a few repeated attempts are required before being successful.
Good Luck!
TNSMANI said:
I don't know which file you downloaded. The one downloaded by me last year and successfully used was Android 9 OOS 9.0.6. It contains version 4 of the Tool and OOS 9.0.6. Version 3 of the Tool will not work with OOS 9.0.6. The Tool is specific to the OOS version.
Prior to that I used version 3 of the Tool and OOS 3.1.2 from the Mega Unbrick thread you linked and that too was successful.
Be patient and try again. I have also noticed that sometimes for some people, a few repeated attempts are required before being successful.
Good Luck!
Click to expand...
Click to collapse
My Bad. Was under the assumption OS n MSM tool were seprate. Got it. many thanks.
Had to use the MSM tool more than 10 times, finally the phone started.
Thanks alot buddy. Appreciate your help and patience.
orlan7 said:
My Bad. Was under the assumption OS n MSM tool were seprate. Got it. many thanks.
Had to use the MSM tool more than 10 times, finally the phone started.
Thanks alot buddy. Appreciate your help and patience.
Click to expand...
Click to collapse
So it worked for a while. Was downloading all aps, restoring settings. Then switched off again. Turned on 3-4 times loaded and turned off again.
back to square 1
orlan7 said:
So it worked for a while. Was downloading all aps, restoring settings. Then switched off again. Turned on 3-4 times loaded and turned off again.
back to square 1
Click to expand...
Click to collapse
It might be worth getting a new battery to see if thats the problem
i am on PE and been on Linage and then Derp but for 2 weeks now ive tried to go back to factory and for the life of me nothing works ive tried the All N One Tool and MSM Tool and nothing i constantly end up back where i started.
Ive downloaded the latest os firmware from oneplus All N One Tool Downloads the firmware extrasts it the pops up a error saying flash all .bat is missing so dead end there.
could someone lead me in the right direction or explain to me if im doing something wrong.... thanks
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
this will be my last onepluse thatr for sure going back to Pixel 4 XL didnt have no issues going back to stock this is crazy
I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.
When u r stuck on pink TMobile screen, force reboot to bootloader by holding vol+, vol-, & power buttons for 10 sec. Once you see phone rebooting, let go of power button only to enter bootloader mode. Then type "fastboot reboot fastboot" on PC while USBC cable is plugged into phone. This will kick phone into fastbootD mode. Then fastboot flash all stock rom files.
When wifi and 4g not working, u did not enter fastbootD mode, so system did not flash right
SageChrono said:
I'm having the same issue, so I'm gonna piggyback this in hopes of a different direction.. Long story, short, I've spent hours trying to get back to OOS from crdroid 11. the link above got me back to booting up t-mobile and relocks the bootloader, but wifi radio doesnt work & restarting brings me to being stuck on the boot logo. none of the other MSMtools work, unlocked or TMO from the unbrick page.
what step am i missing after going through the tmo to int. guide? since that's the only thing that's working.. thanks in advance, i'm attempting round 2 in the meantime.
Click to expand...
Click to collapse
Above
HueyT said:
Above
Click to expand...
Click to collapse
i was just coming to edit my post. rookie mistake - i forgot to overwrite adb/fastboot tools everytime i moved the OS files to my adb folder lol... somehow i forgot a bunch of times
phone is booting up without that userspace error, so i may be back in good shape!
edit 2.0: all booted up with wifi/camera working again
well gonna try again for the 4th time this time im gonna use a different computer and see if that works..... UUUGGGG
well the 4th time fail to restore back to stock OOS.. its gotta be something im doing bc i even used a different computer. but gonna keep looking around for another route.
msmdownloaderTool says this (Device Not Match Image) the device seems to time out and disconnects from MSMDownloaderTool every time. any advice i have the global version 7T 1905
HueyT said:
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
Click to expand...
Click to collapse
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??
scoot0073 said:
this would not work for me im assuming bc i have the global HD1905 not the T Mobile branded. u can read above why it wouldn't work . but i seem to have made some progress using the All in One Tool i clicked on flash factory image tab and at first it keep error out saying no Flash-All.bat found after unzipping it. so i kelp looking around and finally foud a factory zip that had the Flash-All.bat file in it so tried again using the Allin One Tool clicked Flash Factory image and it unzipped it and flashed fine but now i cant boot to the OOS it just reboots to the " your bootloader is unlocked integrity screen and stays . but i can boot in fastboot mode and recovery which is now factory recovery. i noticed that it flashed the OOS zip on slot A so i think the reason its not booting up to OOS is bc i need it flased on both slots ??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
using the " All in One Tool "
Flashing is not allowed for Critical Partitions
is this normal error when flashing back to stock OOS ? when the flashing starts it says this for the first 4 or 5 flashing parts then it stats flashing as described in OP. then it reboots out of fastboot and boots to stock recovery then it finishes the flashing . then at the end it says to press any key to continue and the phone reboots and hangs at the screen that lets me know the bootloader is unlock screen. i flashed both a \b partitions and still does the same thing. its like the boot image is not flashing or im missing something else in the OP to get back to stock OOS.
anyone can help me please ?
"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts
HueyT said:
"Fastboot reboot fastboot" will enter fastbootD mode to allow flashing system parts
Click to expand...
Click to collapse
ok that command worked it successfully Flashed all partitions and when it it it finished it said to press any key to continue .... i did and it rebooted into stock recovery and finished the flashing . then it reboots to the Your Bootloader is unlocked warning and stays there . so i went into recovery and factory reset everything and still hangs at the bootloder unlocked warningthat was all on Slot b so i was like maybe i need to flash both Slots so i switched to slot a active and repeated the whole process above and still nothing hangs again at the bootloader is unlocked warning... ggggrrrrr
what gives..... this is all done using the All in One Tool ... i know im getting close to getting it back to Stock OOS as i made progress with your help.
i then downloaded the factory image from OnePlus site but that was a no go as the zip had only something called Payload which wouldn't flash ..
anymore knowledge u might can share and thank you very much for your help
Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot
HueyT said:
Go back to fastbootD and flash-all parts manually on A slot, then go to bootloader, type "fastboot set_active other" to go into B slot and repeat fastbootD flashing all parts again. Then go into stock recovery to format data and then reboot
Click to expand...
Click to collapse
that did it im back to all stock oos thank you so much buddy couldn't have doe it without your knowledge. crazy that none of the tools didn't work mine must have been a rare odd ball that i had to flash everything manually.
again thank you.
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Salilsarkar said:
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Click to expand...
Click to collapse
Many thanks! I was having issues downloading the stock firmware files needed for the MSM tool. I do have the downgrade zip and ota signed zip for my model, but extracting with payload dumper gives me only 7 image files so I think it's incomplete, and I would still need to download the full firmware files to be able to flash via fastboot.
If you try using fastboot to downgrade, you're very likely going to brick and have to use the MSM anyway.
blitzkriegger said:
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
Click to expand...
Click to collapse
I was able to flash to oos11 using twrp. Well, I was on crdroid and there are custom ROMs that require oos12 before It will work. So I went crdroid 8.6 to oos11 to oos 12 and then lineage 19
Well it was a ride for me lol. Took me a few hours to realize I can gain fastboot access via long pressing power button+volume up and volume down altogether. I was then able to reflash the modded magisk boot image to regain access to AOSPA.
The fun part came after trying to flash back to stock via MSM. First I figured out that instead of using the "vol up+vol- button approach then connect usb" way of trying to get MSM tool to connect to the EDL mode of the phone, an easier method is to use "ADB reboot edl" command.
Now as I previously used global stock OOS, I mistakenly used the MSM tool for the global region. However, this got me in a SHA-256 mismatch in the flashing process, causing a flash error which got me back to getting stuck at the bootloader again. Turns out the global MSM tool does not work for LE2120 model.
So at this point I had 2 options - either find a MSM tool that works, or try flashing back to stock via fastboot. The fastboot way would have worked but I ran into a problem - you have to flash to .img files partly via fastboot, then partly via fastbootd. And when on fastbootd my phone is not recognized by the PC (this is why trying to flash back AOSPA also failed, it can't continue the fastbootd part of the install as for some reason my pc loses connection with the phone on fastbootd).
My saving grace was I found out that for LE2120, the EU version of the MSM tool works. So long-story short I got back to stock OOS 12 again. It was a fun yet nerve wracking experience, and I learned a lot.
So the lesson of the story is, for anyone tinkering with this device, to learn the basics, from knowing your correct model number, knowing the proper button combinations to boot to fastboot/edl/recovery, knowing which tools to use, to knowing how to setup/troubleshoot your pc to ensure the phone communicates properly at every step!