Hello i know i installed android 9.0 Pie and i didnt know i cant do it because the modem.img...
I have Telcel Carrier Mexico TELMX, i was reading a lot about this, my question is.. I really have to wait for a TELCEL MX android 9 update to flash the Pie Modem and restore all this??
XxeAgLeAnGeLxX said:
Hello i know i installed android 9.0 Pie and i didnt know i cant do it because the modem.img...
I have Telcel Carrier Mexico TELMX, i was reading a lot about this, my question is.. I really have to wait for a TELCEL MX android 9 update to flash the Pie Modem and restore all this??
Click to expand...
Click to collapse
Depends. What firmware specifically did you flash? What is your variant? XT1789-?? Have you tried doing a factory reset from recovery?
41rw4lk said:
Depends. What firmware specifically did you flash? What is your variant? XT1789-?? Have you tried doing a factory reset from recovery?
Click to expand...
Click to collapse
I installed: NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And my variant is XT1789-05 from Telcel Carrier Mexico, and yes i did a factory reset from recovery
note: when i installed this 9.0 firmware, worked data, but no wifi signal, so i decided to return to stock Android 8 firmware of my device but i lost imei, wifi, data and no baseband
XxeAgLeAnGeLxX said:
I installed: NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And my variant is XT1789-05 from Telcel Carrier Mexico, and yes i did a factory reset from recovery
note: when i installed this 9.0 firmware, worked data, but no wifi signal, so i decided to return to stock Android 8 firmware of my device but i lost imei, wifi, data and no baseband
Click to expand...
Click to collapse
Once you upgrade your modems to pie, you can't go back to oreo modems. So you need to be back on pie to get baseband back.
41rw4lk said:
Once you upgrade your modems to pie, you can't go back to oreo modems. So you need to be back on pie to get baseband back.
Click to expand...
Click to collapse
i suppose have to wait until motorola launch my modem model, is correct?
XxeAgLeAnGeLxX said:
i suppose have to wait until motorola launch my modem model, is correct?
Click to expand...
Click to collapse
Not necessarily, you said that mobile data worked with retail, so that means the modem was okay. Typically if the modem is all wrong then you just lose baseband altogether. I think if you post your variant and carrier here, someone might know the eact firmware you need. There is retrb, amx,retail, etc. You just need the right one, but you're stuck on pie now so that's that. Anyway, someone in that other thread should know which one will work for you. I'm not well versed in all the -05 carriers so I simply don't know. Sorry.
41rw4lk said:
Not necessarily, you said that mobile data worked with retail, so that means the modem was okay. Typically if the modem is all wrong then you just lose baseband altogether. I think if you post your variant and carrier here, someone might know the eact firmware you need. There is retrb, amx,retail, etc. You just need the right one, but you're stuck on pie now so that's that. Anyway, someone in that other thread should know which one will work for you. I'm not well versed in all the -05 carriers so I simply don't know. Sorry.
Click to expand...
Click to collapse
thats rare, because when i installed android 8 oreo again i missed everything, then i installed back android 9 and didnt boot, so, now dont know, i read that the update was ok on Mexico with the same carrier, meaby he didnt flash modem. I really apreciate your help and thanks amigo
XxeAgLeAnGeLxX said:
thats rare, because when i installed android 8 oreo again i missed everything, then i installed back android 9 and didnt boot, so, now dont know, i read that the update was ok on Mexico with the same carrier, meaby he didnt flash modem. I really apreciate your help and thanks amigo
Click to expand...
Click to collapse
The oreo firmware that you're flashing that is the full name of the package? Maybe we can get an idea of what you need.
Has anyone tried blankflashing to restore an oreo/nougat bl, and thus pre-pie stock modem?
I see no reason it should not work. You can enter EDL mode to blankflash from TWRP if unlocked. I'd try the nougat blankflash first, then oreo. If it works, try flashing your stock flashall. Maybe your imei will come back, maybe not.
R-T-B said:
Has anyone tried blankflashing to restore an oreo/nougat bl, and thus pre-pie stock modem?
I see no reason it should not work. You can enter EDL mode to blankflash from TWRP if unlocked. I'd try the nougat blankflash first, then oreo. If it works, try flashing your stock flashall. Maybe your imei will come back, maybe not.
Click to expand...
Click to collapse
i really dont understand blankflashing, what it do ??
now my Motorola is hard brick, i tried to install Lineage OS nash and then only black screen, when i connect dont recognize my phone, i tried installing qualcom drivers but i think my pc dont install correctly because dont appear on devide administrator, and then, when i connect it doesnt recognize to blankflash now i have to recover from hard brick and then blackflash, sorry for the inconvenience
ok now is recognized Qualcomm HS-USB QDLoader 9008 (COM5) but when i try to black flash it says this:
C:\Users\eagle\Downloads\unbrick\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
FAILED: qb_flash_singleimage()->device_open()->error opening device
do you know why?
XxeAgLeAnGeLxX said:
ok now is recognized Qualcomm HS-USB QDLoader 9008 (COM5) but when i try to black flash it says this:
C:\Users\eagle\Downloads\unbrick\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ 0.000] Opening device: \\.\COM5
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
FAILED: qb_flash_singleimage()->device_open()->error opening device
do you know why?
Click to expand...
Click to collapse
1st.) you need to go into each file in your blankflash dir and go to properties and unblock each one.
2nd.) sometimes its finicky, try holding vol down, than plug in your usb cord while still holding the button start the blankflash.
3rd) If you have any motorola drivers installed to your pc, uninstall them. (This is most likely your error) Once uninstalled, reboot the pc and try again.
jbats said:
1st.) you need to go into each file in your blankflash dir and go to properties and unblock each one.
2nd.) sometimes its finicky, try holding vol down, than plug in your usb cord while still holding the button start the blankflash.
3rd) If you have any motorola drivers installed to your pc, uninstall them. (This is most likely your error) Once uninstalled, reboot the pc and try again.
Click to expand...
Click to collapse
Ok i explain what happened, first my device was not recognized, i tried usin other ports and then was recognized like Unknown Device, i updated to qd loader 9005, and it is all time, when i disconnect my phone it still appearing on device manager, but looks like blank flash detect my phone because when it didnt, never started, but now yes..
So, question:
how unblock each one? what do you mean
system permissions? only special permissions is not activated
i tryed holding power+vol down but the same happens
i uninstalled motorola drivers and reboot pc, also disabled Driver Enforcement
XxeAgLeAnGeLxX said:
Ok i explain what happened, first my device was not recognized, i tried usin other ports and then was recognized like Unknown Device, i updated to qd loader 9005, and it is all time, when i disconnect my phone it still appearing on device manager, but looks like blank flash detect my phone because when it didnt, never started, but now yes..
So, question:
how unblock each one? what do you mean
system permissions? only special permissions is not activated
i tryed holding power+vol down but the same happens
i uninstalled motorola drivers and reboot pc, also disabled Driver Enforcement
Click to expand...
Click to collapse
In win10 you have to unlock it from permissions not sure what win version your using. You are using the N blankflash as well right?
If you haven't already, you need to install the qualcomm diag drivers so that your phone can communicate with your pc. The error you have is error opening device, it seems like it can't pass data back and forth. Here is a general guide that has worked for most. It has the drivers and blankflash that has been used numerous of times successfully. I don't know all the win10 nuances, I hate it. This has been used on win7 and win10 and the drivers are win signed so you don't need to worry about driver enforcement.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
jbats said:
In win10 you have to unlock it from permissions not sure what win version your using. You are using the N blankflash as well right?
Click to expand...
Click to collapse
yes i am using windows 10, i tried both, the oreo and blankflash_from_NDX26.183-15_17
41rw4lk said:
If you haven't already, you need to install the qualcomm diag drivers so that your phone can communicate with your pc. The error you have is error opening device, it seems like it can't pass data back and forth. Here is a general guide that has worked for most. It has the drivers and blankflash that has been used numerous of times successfully. I don't know all the win10 nuances, I hate it. This has been used on win7 and win10 and the drivers are win signed so you don't need to worry about driver enforcement.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
okey i will try this thanks a lot, yes i am on windows 10, but if i cant to do this i really will install windows 7 to recover my phone, but first i will do all this options that you are giving me
XxeAgLeAnGeLxX said:
okey i will try this thanks a lot, yes i am on windows 10, but if i cant to do this i really will install windows 7 to recover my phone, but first i will do all this options that you are giving me
Click to expand...
Click to collapse
win 10 works fine. You just need to make sure you follow the steps exactly for it to work. It does take a few attempts sometimes to flash.
jbats said:
win 10 works fine. You just need to make sure you follow the steps exactly for it to work. It does take a few attempts sometimes to flash.
Click to expand...
Click to collapse
i did it, i used windows 7 and happened like first, detected 1 time like unknown device, and then, on blank flash only says waiting device, then i reset my windows 10 pc because i damage the so xD, and it doesnt detect anything doing that, im tired i dont know, i begin to think that is a different hard brick? only dont detect anything i really do step by step and nothing..
ok i tried more and the same but now it says waiting for device only, i installed adb and qualcom drivers but same.
Related
Hello guys,
After an update to android 7.0 my cell phone started to show difficulties to load. When I connect it on it gives the following message: Caution: High temperature of the device.
This happened after I updated the firmware to the latest version. I wonder if it is to restore the system and go back to version 6.0 of android?
Thank you all,
Best regards
Lando
I have a feeling you'd need to unlock the bootloader. Even so it may not allow you to install MMon it...
Usually the newer firmware replaces the bootloader that rejects older versions of the OS to be flashed.
Help
ultramag69 said:
I have a feeling you'd need to unlock the bootloader. Even so it may not allow you to install MMon it...
Usually the newer firmware replaces the bootloader that rejects older versions of the OS to be flashed.
Click to expand...
Click to collapse
Yes, actually I already unlocked but it did not work. When I try to flash the ROM it says that the version is impractical with the CPU. And nothing truth is not because I've tried more than 5 old roms.
Please if anyone knows how I do this downgrade help me, because I have to have to try several times to load the phone with it turned off.
Many thanks to any help!
landognr said:
Yes, actually I already unlocked but it did not work. When I try to flash the ROM it says that the version is impractical with the CPU. And nothing truth is not because I've tried more than 5 old roms.
Please if anyone knows how I do this downgrade help me, because I have to have to try several times to load the phone with it turned off.
Many thanks to any help!
Click to expand...
Click to collapse
Boot latest twrp
wipe everything on phone in twrp (tick all boxes)
Flash the correct (2.4ghz or 2.15ghz) android 6.0 rom from the asus website. You will need to transfer the zip file to your phone from computer while in recovery. Sometimes you have to reboot twrp after wiping to see the storage on your computer.
Be careful as wiping you phone will remove the os and will result in soft brick if u don't flash the android 6.0 rom.
I have reverted to android 6.0 twice on the sd821 variant but still only do this if you are confident.
I am not responsible if you brick your phone
Brick
Huffy1 said:
Boot latest twrp
wipe everything on phone in twrp (tick all boxes)
Flash the correct (2.4ghz or 2.15ghz) android 6.0 rom from the asus website. You will need to transfer the zip file to your phone from computer while in recovery. Sometimes you have to reboot twrp after wiping to see the storage on your computer.
Be careful as wiping you phone will remove the os and will result in soft brick if u don't flash the android 6.0 rom.
I have reverted to android 6.0 twice on the sd821 variant but still only do this if you are confident.
I am not responsible if you brick your phone
Click to expand...
Click to collapse
Hello friend,
Unfortunately at the time of doing the procedure by an oversight on my part I forgot to do the full wipe. I circled the correct ROM for my phone, but did not do the wipe.
The phone rebooted, hung up and did not call anymore. I can not believe it looks like it gave soft brick due to this my carelessness.
It does not go into fasboot or recovery mode. It gets totally off and when I connect to the pc it recognizes as Qualcomm hs-usb qdloader 9008.
I'm desperate, have I lost my phone? Is there any way to fix this friend? Please ask if anyone knows any procedure to correct it.
Thank you from the heart.
=(
landognr said:
Hello friend,
Unfortunately at the time of doing the procedure by an oversight on my part I forgot to do the full wipe. I circled the correct ROM for my phone, but did not do the wipe.
The phone rebooted, hung up and did not call anymore. I can not believe it looks like it gave soft brick due to this my carelessness.
It does not go into fasboot or recovery mode. It gets totally off and when I connect to the pc it recognizes as Qualcomm hs-usb qdloader 9008.
I'm desperate, have I lost my phone? Is there any way to fix this friend? Please ask if anyone knows any procedure to correct it.
Thank you from the heart.
=(
Click to expand...
Click to collapse
Hi sorry I'm having trouble understanding what your stuck at. You saying the phone doesn't boot at all?
Huffy1 said:
Hi sorry I'm having trouble understanding what your stuck at. You saying the phone doesn't boot at all?
Click to expand...
Click to collapse
Exactly! My phone doesn't boot, just recognizes how QUalcomm HS-USB QDLoader 9008 in my PC. He's dont boot or fastboot mode and dont recovery. Could you help me please?
landognr said:
Exactly! My phone doesn't boot, just recognizes how QUalcomm HS-USB QDLoader 9008 in my PC. He's dont boot or fastboot mode and dont recovery. Could you help me please?
Click to expand...
Click to collapse
Ok restoring your phone with the Qualcomm loader is a very lengthy and complicated process. When the phone is completely off. Hold down the volume up button and power button for a while until the Asus logo appears on the screen. Then open cmd in your android-sdk folder and type "fastboot devices." Let me know if it detects the phone
Huffy1 said:
Ok restoring your phone with the Qualcomm loader is a very lengthy and complicated process. When the phone is completely off. Hold down the volume up button and power button for a while until the Asus logo appears on the screen. Then open cmd in your android-sdk folder and type "fastboot devices." Let me know if it detects the phone
Click to expand...
Click to collapse
Hello friend,
Unfortunately this procedure dont work, my device dont turn on. With power + vol up or power + vol down or both at the same time dont work, because he gives no sign of life. All I can do is connect the PC and recognize how Qualcomm hs-usb qdloader 9008 in device manager. You know others procedure to do?? Thank you
landognr said:
Hello friend,
Unfortunately this procedure dont work, my device dont turn on. With power + vol up or power + vol down or both at the same time dont work, because he gives no sign of life. All I can do is connect the PC and recognize how Qualcomm hs-usb qdloader 9008 in device manager. You know others procedure to do?? Thank you
Click to expand...
Click to collapse
What phone version do u have? S821 or s820?
Huffy1 said:
What phone version do u have? S821 or s820?
Click to expand...
Click to collapse
I think s820, my phone is CPU 2.15GHz version. Thank your repply
landognr said:
I think s820, my phone is CPU 2.15GHz version. Thank your repply
Click to expand...
Click to collapse
Ok well unfortunately my phone is s821. You need someone here that has a s820 to factory reset then backup their phone. Then you can use the Qualcomm loader to restore your phone.
Huffy1 said:
Ok well unfortunately my phone is s821. You need someone here that has a s820 to factory reset then backup their phone. Then you can use the Qualcomm loader to restore your phone.
Click to expand...
Click to collapse
Ok man, but where can i find files to do a factory reset?
im searching in.web but i cant find. Please bro help me, i dont know what do. You are my last hope to solve this, thanks
landognr said:
Ok man, but where can i find files to do a factory reset?
im searching in.web but i cant find. Please bro help me, i dont know what do. You are my last hope to solve this, thanks
Click to expand...
Click to collapse
Like I said as this is such an uncommon phone it probably doesn't exist. You need someone willing to upload a backup of their phone 2.15ghz for u to restore.
Huffy1 said:
Like I said as this is such an uncommon phone it probably doesn't exist. You need someone willing to upload a backup of their phone 2.15ghz for u to restore.
Click to expand...
Click to collapse
Ok Man, but can you send me the step by step of how you managed to solve your problem, regardless of whether rom is different? I know you have nothing to do with it, but I have spent all my savings on this device and need to work out a way to recover it.
Thanks Huffy :good:
landognr said:
Hello guys,
After an update to android 7.0 my cell phone started to show difficulties to load. When I connect it on it gives the following message: Caution: High temperature of the device.
This happened after I updated the firmware to the latest version. I wonder if it is to restore the system and go back to version 6.0 of android?
Thank you all,
Best regards
Lando
Click to expand...
Click to collapse
Did you success?Have you unlock the bootloader of your phone?unlock is necessary!(even though somebody say it work on locked phone)
Here come the tip from Taiwan forum~
link
samson1357924 said:
Did you success?Have you unlock the bootloader of your phone?unlock is necessary!(even though somebody say it work on locked phone)
Here come the tip from Taiwan forum~
link
Click to expand...
Click to collapse
Yes, The bootloader was already unlocked before the problem happened on my phone. I dont think you really understood my problem. What I need is to recover the bootloader from my device.
You said: wonder if it is to restore the system and go back to version 6.0 of android?
So I give you the way to downgrade~It’s not difficult.
I don't know that you had brick your phone......
samson1357924 said:
You said: wonder if it is to restore the system and go back to version 6.0 of android?
So I give you the way to downgrade~It’s not difficult.
I don't know that you had brick your phone......
Click to expand...
Click to collapse
Will QuickCharge 3.0 work again if you return to Android 6 (given that it was removed in Android 7)?
AWT86 said:
Will QuickCharge 3.0 work again if you return to Android 6 (given that it was removed in Android 7)?
Click to expand...
Click to collapse
It was never removed it works fine on Android 7.0. Sometimes you have to factory reset your phone to get it working after an upgrade.
You do have to use the supplied ASUS charger though which is really annoying to get qc3.0 speeds. Other qc certified quick charge 3.0 will only charge at normal speeds. Something Asus have blocked themselves.
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
dmilz said:
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
Click to expand...
Click to collapse
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Robert1852 said:
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Click to expand...
Click to collapse
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
dmilz said:
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
Click to expand...
Click to collapse
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Ooh ok.. i see.. hope you will find a way out
Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Xceeder said:
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Click to expand...
Click to collapse
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Robert1852 said:
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Click to expand...
Click to collapse
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Puddi_Puddin said:
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Click to expand...
Click to collapse
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Robert1852 said:
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Click to expand...
Click to collapse
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Puddi_Puddin said:
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Click to expand...
Click to collapse
When it's in the bootloader menu it shows up as "Android Bootloader Interface", when it's in EDL mode it shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)". It connects fine with the pc and flashes everything without problems as far as I can see. Yeah it says "FAILED (remote: oem unlock is not allowed)" probably because the allow oem unlock option in the settings isn't checked.
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
ZVNexus said:
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
Click to expand...
Click to collapse
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Robert1852 said:
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Click to expand...
Click to collapse
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Puddi_Puddin said:
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Click to expand...
Click to collapse
Tried everything it says in the guide about the drivers (even the last part about installing the certificates) but it just keeps showing up as qualcomm hs-usb qdloader 9008, even though I'm pretty sure they are installed correctly. It just won't show up as Qualcomm 9008, as it is supposed to, whatever I try. But it looks like these drivers are only for the EDL mode, and as far as I know it is normal for the phone to show up as Android Bootloader Interface when it's in the bootloader menu. And you can't use fastboot from EDL mode... Will try it later again on a different pc though, really hope you are right about the drivers after all
Hi Robert,
I am having same problem with my oneplus3. I also tried both unbrick methods and tried different oxygen ROMs.
Are you able to fix your phone?
Thanks in Advance,
Anil
Have you tried this http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
Hi
Go back to an older Version...3.xx
worked for me
be warned ..3.xxx formats internal memory
I also have the same problem, I'll try to restore to old version too.
Do you also have artifacts on the screen?
Iused another phone, to check wether its the fault of pc, but it detected other phone but not thiss one. Please give a solutuin i lost all my data while doing factory reset.
fluid1998 said:
Iused another phone, to check wether its the fault of pc, but it detected other phone but not thiss one. Please give a solutuin i lost all my data while doing factory reset.
Click to expand...
Click to collapse
Seems to be issue related with drivers install it again.
Not_James_Bond said:
Seems to be issue related with drivers install it again.
Click to expand...
Click to collapse
no it didnt work:crying:
I had this Problem aswell many times....i guess u are using windows 8 or 10?
So Adb is giving u the "no device found" message?
What helped my is just trying out all sorts of stuff, reinstalling drivers, trying other drivers like adb universal drivers or lenovo drivers or zuk drivers..... reinstall them and try again.
Also try this one:
google for disabling driver signature verification...(cant post links cause i am a new user)...
and try to directly use the right command for adb...dont rely on the command for finding ur device...i once had a long night where my zuk z2 was bricked after flashing baseband and i had the same problem u had....it never found my device but when i just straight up used the command to unlock my bootloader it suddenly worked.
Also restart ur pc after every driver install.
fluid1998 said:
Iused another phone, to check wether its the fault of pc, but it detected other phone but not thiss one. Please give a solutuin i lost all my data while doing factory reset.
Click to expand...
Click to collapse
are you on h2os?
or stock or any other rom?
temporary solution may be that to use twrp instead
Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!
If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.
It was a t mobile damn never go for a t mobile again REALLY
paxar331 said:
If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.
Click to expand...
Click to collapse
It was a t mobile damn never go for a t mobile again REALLY
Pocketjam347 said:
It was a t mobile damn never go for a t mobile again REALLY
Click to expand...
Click to collapse
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I
I don't understand one part
Awesomeslayerg said:
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I
Click to expand...
Click to collapse
I tried this method 2 days ago but for some reason when I try STEP 7: It says "Extracting kdz to ..." so I tried to wait a WHILE but after 4 hours of wait nothing happened so I was unable to do the next steps
Does it matter if the Phyton says that it was the end of its life?
Thank you so much for your post tho I believe you helped other people
Don't throw it away, I think there's a fix with QFIL.
I'm having a similar problem, but in my case I managed to accidentally erase laf_b from QFIL and this has corrupted my GPT. Now the QFIL partitioner can't see my partitions. Can you help? I may need a flat pack or something? I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't get into fastboot to install TWRP and Lineage OS, so I ended up trying to erase laf_a and laf_b like it says to do in the V40 Qfil guide. Big mistake. Qfil and windows both recognize it as a 9008 device on Com3, but can't access the partitions.
I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error
THE KHAMELEON said:
I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error
Click to expand...
Click to collapse
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.
lefttobleed said:
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.
Click to expand...
Click to collapse
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon
THE KHAMELEON said:
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon
Click to expand...
Click to collapse
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.
lefttobleed said:
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.
Click to expand...
Click to collapse
To be honest I think it could be me just having the files in the wrong place or something else I'm doing wrong. All I get is Sahara error
Pocketjam347 said:
Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!
Click to expand...
Click to collapse
Same problem with my phone.
I also try these things.
If you solved that problem then please share with me.
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).