Related
After trying to unlock my phone and flashing stock rom through CWM I accidently downloaded the rom for the at&t model. I own the sprint model. After flashing the incorrect boot img and radio img the fastboot just spat out errors so closed the CMD and booted up the phone. No longer does the USB work i have tried several computers none detecting it in either bootloader or within the android os. The android os doesnt even ask to mount it it just charges. Any help would really be aprreciated!
kambokid said:
After trying to unlock my phone and flashing stock rom through CWM I accidently downloaded the rom for the at&t model. I own the sprint model. After flashing the incorrect boot img and radio img the fastboot just spat out errors so closed the CMD and booted up the phone. No longer does the USB work i have tried several computers none detecting it in either bootloader or within the android os. The android os doesnt even ask to mount it it just charges. Any help would really be aprreciated!
Click to expand...
Click to collapse
OK firstly never close CMD when it is doing stuff that can cause damage to your PC, device etc. It can cause serious damage
I haven't tried this myself but you could try using a different USB connector. If that still doesn't recognise your device then it is a hardware problem or you have messed up you device.
If it works then download the sprint version and flash.
Hope this helped,
UselessSniper001
Wait what ?
So you wanted to unlock to flash stock ROM with cwm recovery but you used fastboot to flash boot radio etc .img's ?
UselessSniper001 said:
OK firstly never close CMD when it is doing stuff that can cause damage to your PC, device etc. It can cause serious damage
I haven't tried this myself but you could try using a different USB connector. If that still doesn't recognise your device then it is a hardware problem or you have messed up you device.
If it works then download the sprint version and flash.
Hope this helped,
UselessSniper001
Click to expand...
Click to collapse
Ive already tried several different USB cables. Thanks for the suggestion though.
albundy2010 said:
Wait what ?
So you wanted to unlock to flash stock ROM with cwm recovery but you used fastboot to flash boot radio etc .img's ?
Click to expand...
Click to collapse
It was a fastboot image.
Transfer a stockish ROM (can be deodexed & rooted, doesn't really matter) via WiFi and flash in CWM.
polobunny said:
Transfer a stockish ROM (can be deodexed & rooted, doesn't really matter) via WiFi and flash in CWM.
Click to expand...
Click to collapse
CWM Is no longer there after i restored it I was able to flash a stock ICS through normal recovery but the usb is still not working.
From a powered off state, if you hold VOL down and then press POWER, can you access download mode?
If yes, and you connect it to your computer (I'm going to assume you are using a windows computer), can you hear the device connected sound? It should get detected.
Hi. After using this method to fix dozens of G4's and 5X's, I bumped on one bootlooping V10. As there's no modified kernels that would boot V10 on only 4 cores, I present to you:
V10 kernel that will resurrect your bootlooping beauty!
Requirements and Guide:
1: Working ADB and Fastboot
2A: If you already checked OEM unlock in developer options, try booting to fastboot using this method:
Remove battery from phone
Insert USB cable from PC to phone (with battery removed)
On your phone screen there should now be battery icon with question mark inside
Hold volume down, and while holding, insert the battery in the phone, you should be inside fastboot
From there, unlock bootloader, if you haven't already, and flash 4cores kernel for your version of phone and software
- or -
2B: If you previously didn't enable OEM unlocking, AND/OR you can't boot directly to fastboot:
You must be able to boot the phone at least for 30 seconds to do this
Go to developer options and check OEM Unlocking and USB Debugging
Go to LG site and follow instructions on how to unlock bootloader
After unlocking bootloader, while still on fastboot screen, flash my custom 4cores kernel
Code:
fastboot flash boot boot.img
NOTE: As of now, I only modified 30b and 20e versions for H960a variant, and 20e for H901... It might work on others versions, but I'm not sure. I tested 30B and 20e for H960, H901 is untested at the moment. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash software version that has 4cores kernel...
Now you have a kernel with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
NOTE: For anyone that didn't have OEM unlock checked at the time of bootloop, I guess you have trouble booting your phone to tick that option. You have few options, and here are only few of them... You can try refrigerator or freezer for 30 minutes to 1 hour, and try to boot your phone. In most cases it will boot long enough to go to developer options and tick the boxes, and then boot to Fastboot. Also, you can try hairdryer for around 10 minutes, it is also confirmed that this method has worked for some people...
If this method helps fixing your phone, feel free to hit thanks button
Donations are not expected or required, but are welcome:
Donate Me!
EDIT:
Added TWRP booting on 4 cores!
Credits:
Big thanks to following people for making this method possible:
@XCnathan32
@steadfasterX
@XeniX_Force
@rudi666
stojshic said:
Hi. After using this fix for few G4's and 5X's, I bumped on V10 with the same problem, but as I found out, no one still made modified kernel that would boot on 4 cores only, so, here it is:
Requirements and Guide:
Working ADB and Fastboot
Unlocked device with access to fastboot (if that's possible on V10?)
- or -
You must be able to boot the phone at least for 30 seconds to do this
Go to developer options and check OEM Unlocking and USB Debugging
Go to LG site and follow instructions on how to unlock bootloader
After unlocking bootloader, while still on fastboot screen, flash my custom 4cores kernel
Code:
fastboot flash boot boot_30b.img
NOTE: As of now, I only modified 30b kernel for h960a variant... It might work on others versions, but I'm not sure. I tested it on my V10 with 30B software installed. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash 30B, and after that flash this kernel.
Now you have a kernel with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
NOTE: Considering you have bootlooping phone, I guess it's the question how to enter fastboot, as to my knowledge LG disabled booting directly to fastboot. If you know the way to boot directly to fastboot, than you are fine (and please share how), and for everyone else, you must manage to boot the phone somehow. You can try refrigerator or freezer for 30 minutes to 1 hour, and try to boot your phone. In most cases it will boot long enough to go to developer options and tick the boxes, and then boot to Fastboot. Also, you can try hairdryer for around 10 minutes, it is also confirmed that this method has worked for some people...
If this method helps fixing your phone, feel free to hit thanks button
Donations are not expected or required, but are welcome: Donate Me!
Credits:
Big thanks to following people for making this method possible:
@XCnathan32
@steadfasterX
@XeniX_Force
Click to expand...
Click to collapse
this kernel is from V10 or from G4? i mean my V10 is work perfect with Nougat but i want to do as much as i can to keeping it so, can i flash this on H960A International Model? i have unlocked bootloader and i can boot into fastboot...
sun_is_shinning said:
this kernel is from V10 or from G4? i mean my V10 is work perfect with Nougat but i want to do as much as i can to keeping it so, can i flash this on H960A International Model? i have unlocked bootloader and i can boot into fastboot...
Click to expand...
Click to collapse
It's modified V10 kernel that utilizes only 4 cores. You can't use G4 kernel on V10. If you have 30b software on your H960A, you should be safe to boot in fastboot and flash this kernel. After that, you can install cpu-z and verify that only 4 cores are online
Sent from my ZTE Axon 7 using Tapatalk
stojshic said:
It's modified V10 kernel that utilizes only 4 cores. You can't use G4 kernel on V10. If you have 30b software on your H960A, you should be safe to boot in fastboot and flash this kernel. After that, you can install cpu-z and verify that only 4 cores are online
Sent from my ZTE Axon 7 using Tapatalk
Click to expand...
Click to collapse
very very thanks...its working!!! NOW I ONLY HAVE 4 CORES active and the crappy ones is gone!
EDIT: i lose root when flash this, and need to flash TWRP again and supersu again, but root is not working now...i try it twice but nothing, it keep giving error!
can you help?
DISCLAIMER TO THIS THREAD: If you flash this Kernel you will lose the hability to flash SuperSU, and so you wont be able to have root on your device.
P.S.: Dev should put a SELinux Permissive right in Kernel and some add ons like KCAL display calibration and core control. This only disable the little cores and the battery will be more hungry now...
i know this only are made to rescue your V10 from bootloop but i think it deserve some devlopment because this can be a great Kernel.
Thanks for suggestion. For now, this is, like it is stated, pure stock kernel with disabled cores, for those in bootloop. I will think about modified versions in the future, but until further testing, it's going to stay stock...
Sent from my ZTE Axon 7 using Tapatalk
stojshic said:
NOTE: As of now, I only modified 30b kernel for h960a variant... It might work on others versions, but I'm not sure. I tested it on my V10 with 30B software installed. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash 30B, and after that flash this kernel.
Click to expand...
Click to collapse
Great work. 30b KDZ is easily available here. I think one should flash it and use this boot image instead of asking for developing a boot image for their specific firmwares.
However, I would suggest to kindly release a custom boot image for H901 20e. Because H901 (Tmobile) is also bootloader unlockable and its 20e KDZ is also easily available here. This way both unlockable variants of V10 i.e. H960A and H901 will be covered. :angel:
NOTE: Considering you have bootlooping phone, I guess it's the question how to enter fastboot, as to my knowledge LG disabled booting directly to fastboot. If you know the way to boot directly to fastboot, than you are fine (and please share how).
Click to expand...
Click to collapse
I myself booted to fastboot easily on a bootlooped LG V10 H961N (HongKong) by:
1. Turning the phone off.
2. Pressing Vol down.
3. Connecting the phone with computer with data cable.
4. Releasing the Vol down upon seeing the phone booted into fastboot.
Dont know if the same would work on other variants or not.
rizkhan999 said:
Great work. 30b KDZ is easily available here. I think one should flash it and use this boot image instead of asking for developing a boot image for their specific firmwares.
However, I would suggest to kindly release a custom boot image for H901 20e. Because H901 (Tmobile) is also bootloader unlockable and its 20e KDZ is also easily available here. This way both unlockable variants of V10 i.e. H960A and H901 will be covered. :angel:
I myself booted to fastboot easily on a bootlooped LG V10 H961N (HongKong) by:
1. Turning the phone off.
2. Pressing Vol down.
3. Connecting the phone with computer with data cable.
4. Releasing the Vol down upon seeing the phone booted into fastboot.
Dont know if the same would work on other variants or not.
Click to expand...
Click to collapse
Yeah, I heard about that way of booting, but never managed to boot to fastboot using that method. I will edit my post to include it... Also, thanks for the link for the software, will edit that kernel soon, and post 4cores version of it here...
Sent from my ZTE A2017U using Tapatalk
I never had bootloop on my h960a. how is that possible?
stojshic said:
Yeah, I heard about that way of booting, but never managed to boot to fastboot using that method. I will edit my post to include it... Also, thanks for the link for the software, will edit that kernel soon, and post 4cores version of it here...
Click to expand...
Click to collapse
Someone whom I know has h901 software on his vs990. I asked him to follow this procedure. And he also successfully booted into fastboot mode and shared this image with me which I have uploaded here. Means its working on other models too.
rizkhan999 said:
Someone whom I know has h901 software on his vs990. I asked him to follow this procedure. And he also successfully booted into fastboot mode and shared this image with me which I have uploaded here. Means its working on other models too.
Click to expand...
Click to collapse
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
stojshic said:
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
Click to expand...
Click to collapse
Awesome work.:good::victory:
stojshic said:
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
Click to expand...
Click to collapse
Can we also get the TWRP recoveries with big cores disabled?
For H901 it is available here and here. And for H960A it is available here.
I would really be grateful.
rizkhan999 said:
Can we also get the TWRP recoveries with big cores disabled?
For H901 it is available here and here. And for H960A it is available here.
I would really be grateful.
Click to expand...
Click to collapse
I'll try to make them one of these days. I'm really busy ATM, but will try to find some time to modify the images
Sent from my ZTE A2017U using Tapatalk
I can get into fastboot, but any fastboot commands like
Code:
fastboot flash boot boot.img
or
Code:
fastboot boot recovery twrp.img
or
Code:
fastboot boot twrp.img
fail with unknown command error. My bootloader is unlocked so it can't be that. Any ideas on how to flash this with that it mind?
galaxymover said:
I can get into fastboot, but any fastboot commands like
Code:
fastboot flash boot boot.img
or
Code:
fastboot boot recovery twrp.img
or
Code:
fastboot boot twrp.img
fail with unknown command error. My bootloader is unlocked so it can't be that. Any ideas on how to flash this with that it mind?
Click to expand...
Click to collapse
with the phone off, volume up key pressed connect the phone into pc and keep pressed the volume up key, then go to "minimal adb and fastboot" - its a cmd dedicated to use for this - and there do the follow command:
adb devices
(you should see yours saying conected, then do the follow)
adb reboot fastboot
(and now you are in fastboot, if you want to boot in bootloader do the command bellow)
adb reboot bootloader
- and thats it. if you are trying to flash TWRP you need to download the img of TWRP in some thread in V10 section and put it on the root of the fastboot tool you are using and to install it when in fastboot do the follow command:
fastboot flash recovery (name-of-twrp-file).img
and you done.
sun_is_shinning said:
with the phone off, volume up key pressed connect the phone into pc and keep pressed the volume up key, then go to "minimal adb and fastboot" - its a cmd dedicated to use for this - and there do the follow command:
adb devices
(you should see yours saying conected, then do the follow)
adb reboot fastboot
(and now you are in fastboot, if you want to boot in bootloader do the command bellow)
adb reboot bootloader
- and thats it. if you are trying to flash TWRP you need to download the img of TWRP in some thread in V10 section and put it on the root of the fastboot tool you are using and to install it when in fastboot do the follow command:
fastboot flash recovery (name-of-twrp-file).img
and you done.
Click to expand...
Click to collapse
I tried doing those commands and got the same error that I mentioned in my previous post.
galaxymover said:
I tried doing those commands and got the same error that I mentioned in my previous post.
Click to expand...
Click to collapse
Do you see the device when execute "fastboot devices" command? Also try it on linux after installing "adb" or "android-tools". Because it may be drivers issue on windows. If nothing works, flash a different KDZ. May be this firmware has some limitations in its fastboot.
EDIT: Also check if you have unlocked the bootloader or not. These commands will work if it is unlocked. Although commands should still be recognized but still, just a check.
---------- Post added at 11:05 AM ---------- Previous post was at 10:45 AM ----------
stojshic said:
I'll try to make them one of these days. I'm really busy ATM, but will try to find some time to modify the images
Click to expand...
Click to collapse
Thanks. I have TWRP with big cores disabled in my G4 H815. But when I boot into TWRP and execute cat /sys/devices/system/cpu/cpuX/online from its terminal, I see that only the online file of cpu0 core has the value of 1, while the online files of all the rest cpu cores has 0 value. So if TWRP works on only 1 core by default (just like Download Mode), we may not have to make a TWRP with big cores disabled! But the question is that does TWRP really work on only 1 core by default, as also seem to be the case with that TWRP on my phone?
I would also request you to kindly make a custom boot image with big cores disabled for H901 with 30b firmware from its KDZ. I have attached its boot.img herewith, after extracting it with this tool, so that you may not have to download the whole 30b KDZ for that.
I am sorry to bother you so much but the reason why I am requesting for a 30b custom boot image in presence of 20e for the same model (H901) is that 20e is on ARBv1 while 30b is on ARBv2, and I cannot flash 20e over 30b using LGUP.
hi all, so with htis methode even with the h961n we can getout from the bootloop?, does the undercloked way helps? thanks a lot!!
rizkhan999 said:
Do you see the device when execute "fastboot devices" command? Also try it on linux after installing "adb" or "android-tools". Because it may be drivers issue on windows. If nothing works, flash a different KDZ. May be this firmware has some limitations in its fastboot.
EDIT: Also check if you have unlocked the bootloader or not. These commands will work if it is unlocked. Although commands should still be recognized but still, just a check.
Click to expand...
Click to collapse
While I can see the device in
Code:
fastboot devices
, I cannot see it in LGUP/LG Bridge/LG PC Suite. I will fire up a Linux VM and see if that helps. Also, I have definitely unlocked the bootloader.
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!
Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.
My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.
[READ FIRST] {BLU G90 PRO} I am new to all this, I started learning about rooting a week ago. If you can help, please explain in detail. TL/DR at bottom
[CAUSE] I'm not sure but I attempted root by useing migisk and lateset firmware boot.img provided by xda.
[PROBLEM] My phone constantly bootloops. I cannot access recovery mode as it just reboots. adb won't work as the phone does not connect to the computer. I can go to fastboot mode though.
[ATTEMPTS] I have let the battery die which did nothing, I tried to let the phone charge but it does not go up that much, but fastboot mode at least lets it chare a little. I have tried to reflash the stock boot.img but adb doesn't work. (see video).
[RESOURCES] I have all files assosiated with this. I now have stock firmware as well. Willing to wipe phone completely. I am bootloaded.
TL/DR: ****ed up root with wrong boot.img in magisk. Bootlooped and low battery..
[VIDEO]
I_like_root_pls said:
[READ FIRST] {BLU G90 PRO} I am new to all this, I started learning about rooting a week ago. If you can help, please explain in detail. TL/DR at bottom
[CAUSE] I'm not sure but I attempted root by useing migisk and lateset firmware boot.img provided by xda.
[PROBLEM] My phone constantly bootloops. I cannot access recovery mode as it just reboots. adb won't work as the phone does not connect to the computer. I can go to fastboot mode though.
[ATTEMPTS] I have let the battery die which did nothing, I tried to let the phone charge but it does not go up that much, but fastboot mode at least lets it chare a little. I have tried to reflash the stock boot.img but adb doesn't work. (see video).
[RESOURCES] I have all files assosiated with this. I now have stock firmware as well. Willing to wipe phone completely. I am bootloaded.
TL/DR: ****ed up root with wrong boot.img in magisk. Bootlooped and low battery..
Click to expand...
Click to collapse
How to root/alternate for twrp? BLU G90 PRO
I have spent 2 days trying to figure out how to root my g90 pro. I can't find twerp for it and every possible guide I find destroys my sanity when I find out it won't work. I have magisk as a zip file on my phone right now, is there an alternate...
forum.xda-developers.com
[CAUSE] You not know how using fastboot mode:
Code:
fastboot devices
If okay so you can using:
Code:
fastboot flash boot boot.img
But the boot.img file is in the folder platform?
[PROBLEM] You need better file patched. Maybe your pacthed_boot.img is wrong! So you can flash TWRP but need modified vbmeta file. I can help with that file!
[ATTEMPTS] two ways: 1- charge battery for using with fastboot. 2- Using SPFT for flash stock ROM or stock boot.img only.
[RESOURCES] You know use SPFT for flashing stock ROM?!
Created 2 posts with same device?? daaammm
Look this guy!: https://forum.xda-developers.com/t/...310ww-mt6765-android-10.4163497/post-84082633
LMFAO I FORGOT THE ./
but your post also made alot of things click for me. I was feeling down cause I though I ****ed up my first phone before a week even passed. Thanks for the help! Feeling alot better now!
also I got the recovery mode to pop up and I'm downloading verified stock firmware rn. Will update
Everything is fixed! I used spft and installed the stock rom! Everything is backing up now from my cloud account.
Now I want to root even more and I got a bit more experience. I saw your post mentioned a program bprd. Should I use that instead of the twrp build I found for this?
Also thanks!
I_like_root_pls said:
program bprd
Click to expand...
Click to collapse
Where did I write that?
Now understand: You have 2 ways for flash only recovery.img(TWRP or PBRP).
Using SPFT;
Using adb-fastboot.
Obviously if you want ROOT without Custom Recovery you should use magisk to create patched_boot.img and flash with 2 same ways.
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.