Related
I discovered a forum pertaining to the G5 a few days ago for methods of rooting the device (http://forum.xda-developers.com/tmob...-h830-t3384526). To the best of my abilities, I believe I followed each step correctly. After I used the LGUP tool to install the file while the device was in download mode, it began boot-looping on the initial boot screen with an error message displaying "boot verification failed". I found a post on the same forum from someone who was experiencing the same error on their device. Tungkick posted a response that provided a solution to the issue; "IF Boot Verification Failed error > download stock full flash again>> enabable usb debugging + oem unlock> adb reboot bootloader> fastboot oem unlock> then up file tot add twrp again." I downloaded the stock file and used LGUP to flash it to the device.
I believe I made the mistake of selecting "upgrade" instead of "refurbish" before I initiated the flash. When the file finished installing, the screen on my device went black. Since then, I've been incapable of booting my phone up. When I connect it to my laptop, the Device Manager reads it as: "Qualcomm HS-USB QDLoader 9008". I researched some methods but wasn't successful in finding one that fixed my phone. Although, I could've found a site that provided a solution but I might've failed to follow the instructions properly. I assure you I gave my best effort to fix this issue myself, but I'm desperate to seek help from anyone at this point.
I would sincerely appreciate any feedback that would assist in resolving this issue. Here are the Web addresses:
(1) http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
(2) http://www.androidbrick.com/unbrick-...-qhsusb_dload/
(3) http://www.androidbrick.com/ultimate...oad_qpst_qfil/
Unfortunately your phone is done. None of those links work for the G5, or the G4 even.
If you purchased it from a retailer, send it to LG for a warranty replacement. Be 'mysterious' and ignorant about how it happened. Will take about 1.5 weeks to get it back. They just reflash the phone and you're as good as before. Or, show it to T-Mobile and they will send a refurbished replacement out, for either $5 or $20, depending on your phone insurance.
It's quite odd that this happened according to your description. From your profile, you have the H830, right? Do you know if you were on 10A or 10D?
From the beginning, did you select OEM unlock in Android developer settings, and then unlock the bootloader? If not, that will lead to that type of error you got. The instructions are all over the place and the tutorials are not always as complete as they should be.
I don't think refurbish vs upgrade makes a difference--one will wipe the /data, the other won't. If you have the right stock KDZ file, LGUP (you used LGUP, not LGFlash right?) will simply return you to stock so you can try again.
That error occurs if you try to flash an older firmware version OR flash a different model KDZ. Neither of those should occur with LGUP as it has safeguards.
waylo said:
Unfortunately your phone is done. None of those links work for the G5, or the G4 even.
If you purchased it from a retailer, send it to LG for a warranty replacement. Be 'mysterious' and ignorant about how it happened. Will take about 1.5 weeks to get it back. They just reflash the phone and you're as good as before. Or, show it to T-Mobile and they will send a refurbished replacement out, for either $5 or $20, depending on your phone insurance.
It's quite odd that this happened according to your description. From your profile, you have the H830, right? Do you know if you were on 10A or 10D?
From the beginning, did you select OEM unlock in Android developer settings, and then unlock the bootloader? If not, that will lead to that type of error you got. The instructions are all over the place and the tutorials are not always as complete as they should be.
I don't think refurbish vs upgrade makes a difference--one will wipe the /data, the other won't. If you have the right stock KDZ file, LGUP (you used LGUP, not LGFlash right?) will simply return you to stock so you can try again.
That error occurs if you try to flash an older firmware version OR flash a different model KDZ. Neither of those should occur with LGUP as it has safeguards.
Click to expand...
Click to collapse
Yeah, I was on 10D. OEM unlock and USB debugging were enabled; the bootloader was unlocked, as well. This is all a mystery to me, honestly. I've never experienced an issue like this before. I appreciate you taking the time to help
Hmm, weird scenario then, as it seems like everything went exactly the way it was supposed to. Good luck with the replacement, it's not that hard, just annoying.
If you're happy with the G5 you have, send it through LG. If you'd prefer to get it a tad sooner and don't mind playing the refurb lottery, go through T-Mobile.
waylo said:
Hmm, weird scenario then, as it seems like everything went exactly the way it was supposed to. Good luck with the replacement, it's not that hard, just annoying.
If you're happy with the G5 you have, send it through LG. If you'd prefer to get it a tad sooner and don't mind playing the refurb lottery, go through T-Mobile.
Click to expand...
Click to collapse
Thanks, man. Take care
If your bootloader was unlocked already then you should have twrp still, try booting into that with a button combo or thru adb terminal you'll need a file called no dm-verify zip witch you can find on the fourms, be sure to wipe your caches as well. I believe this is your problem is you may have forgot to flash this and that's why your not booting. And I would try to flash the 10d fluence ROM as well and follow his instructions on how to do so it may solve your boot loop and you won't have to wait for another phone.
I made a stupid mistake trying to flash a H850 build on H830 devices via TWRP.
I ended up with a dead device with 9008 driver communication only. Now, I've managed to get MSM8996 programmer file in order to flash bootloaders back to the device via QPST utility and all I'm missing is rawprogram0.xml file that contains the exact start_byte_hex values of each one of the bootloader files in order to be successfully downloaded to the phone.
I would highly appreciate some help from anyone with a rooted LG G5 to get the exact start_byte_hex of each one of the phone's partitions in order to build my own rawprogram0.xml file or alternatively just get the complete LG G5 rawprogram0.xml file from someone who already have his hands this file
I'll post here all revive steps and tools used once I'll have all files needed and get a successful revive results on my device.
Crossdead said:
If your bootloader was unlocked already then you should have twrp still, try booting into that with a button combo or thru adb terminal you'll need a file called no dm-verify zip witch you can find on the fourms, be sure to wipe your caches as well. I believe this is your problem is you may have forgot to flash this and that's why your not booting. And I would try to flash the 10d fluence ROM as well and follow his instructions on how to do so it may solve your boot loop and you won't have to wait for another phone.
Click to expand...
Click to collapse
Dude, I concur with your method entirely haha.
I wanted to root my phone and install a custom recovery simultaneously (idiotic decision, I guess). So I just waited until someone posted a forum with the files that were compatible for the G5's most recent update. Ironically, the files didn't install properly or something, so my phone went into a bootloop. The same developer who posted that forum with the root and recovery files, provided a solution to the issue. Which was, initially, flashing the stock files to the device, then proceed with installing the root/recovery files.
I then flashed the stock files to the device and simultaneously at completion, my phone powered off. Still, my phone is incapable of communicating with my laptop because something is wrong with the drivers on the LG and I've only been able to find outdated and ineffective solutions for it. Thank you for lending a hand though, man. If you have any alternatives, please let me know.
motman said:
I made a stupid mistake trying to flash a H850 build on H830 devices via TWRP.
I ended up with a dead device with 9008 driver communication only. Now, I've managed to get MSM8996 programmer file in order to flash bootloaders back to the device via QPST utility and all I'm missing is rawprogram0.xml file that contains the exact start_byte_hex values of each one of the bootloader files in order to be successfully downloaded to the phone.
I would highly appreciate some help from anyone with a rooted LG G5 to get the exact start_byte_hex of each one of the phone's partitions in order to build my own rawprogram0.xml file or alternatively just get the complete LG G5 rawprogram0.xml file from someone who already have his hands this file
I'll post here all revive steps and tools used once I'll have all files needed and get a successful revive results on my device.
Click to expand...
Click to collapse
Same here, man! I thought I was so close to fixing it but the QPST tool would always display an error indicating that there was an issue with the rawprogram0.xml file. I don't believe I used MSM8996 programmer file, though... Would you mind posting a link of the download, please? Thank you for posting.
Colbyfales_25 said:
Same here, man! I thought I was so close to fixing it but the QPST tool would always display an error indicating that there was an issue with the rawprogram0.xml file. I don't believe I used MSM8996 programmer file, though... Would you mind posting a link of the download, please? Thank you for posting.
Click to expand...
Click to collapse
Here you go, I guess that you will have to use the lite version
https://www.mediafire.com/?epv3qq83ag2vqar
motman said:
Here you go, I guess that you will have to use the lite version
https://www.mediafire.com/?epv3qq83ag2vqar
Click to expand...
Click to collapse
I found a way to create the required rawprogram0.xml and patch0.xml files from a working phone via Python script.
Python should be installed on your computer in order to run this tool. All we need is someone with a working phone who will be willing to run this tool and create the required files...
Tool:
https://www.mediafire.com/?jh2owbccrfj6rne
Script description:
http://forum.xda-developers.com/showthread.php?t=1884417&page=2
motman said:
I found a way to create the required rawprogram0.xml and patch0.xml files from a working phone via Python script.
Python should be installed on your computer in order to run this tool. All we need is someone with a working phone who will be willing to run this tool and create the required files...
Tool:
https://www.mediafire.com/?jh2owbccrfj6rne
Script description:
http://forum.xda-developers.com/showthread.php?t=1884417&page=2
Click to expand...
Click to collapse
I'm on it. I'll keep you apprised throughout the process.
Colbyfales_25 said:
I'm on it. I'll keep you apprised throughout the process.
Click to expand...
Click to collapse
Cool
Colbyfales_25 said:
I'm on it. I'll keep you apprised throughout the process.
Click to expand...
Click to collapse
Ever get a chance to make any progress with this?
SophiaNOTLoren said:
Ever get a chance to make any progress with this?
Click to expand...
Click to collapse
Unfortunately, no. I had access to Ubuntu's OS but wasn't successful finding another G5. Theoretically, using the Python rawprogram0.xml and patch0.xml scripts, along with an operable G5, It's plausible to recover the phone. I essentially just went into a retail store and told them that the phone had spontaneously shut-off and wouldn't reboot. They provided a replacement and that was the end of it.
So i got on of these but sprint model well g5
i have a full dump from before my phone bricked
but not through the script from lgups partition dump how can i push these back to mine or make a partition xml from my dump or even a sdcar debrick img? lol Im not picky any of these would suit me. lol Not askin to much
Colbyfales_25 said:
Unfortunately, no. I had access to Ubuntu's OS but wasn't successful finding another G5. Theoretically, using the Python rawprogram0.xml and patch0.xml scripts, along with an operable G5, It's plausible to recover the phone. I essentially just went into a retail store and told them that the phone had spontaneously shut-off and wouldn't reboot. They provided a replacement and that was the end of it.
Click to expand...
Click to collapse
Ah, that's a shame. I bought mine on eBay, and I'm on Metro not TMobile proper, so sadly that avenue's not much use for me.
for UFS Chip only can use Nuprog to rewrite full flash to chip direct or use cm2 dongle with Open memory tool plugin and can flash it in 9008 port
Device Found!
Initialize ...
Handshake passed!
BB_IDC_CPU : SnapDragon 820 [MSM8996]
ID_BLOCK_S : B861DCBB
ID_BLOCK_I : 009470E1
ID_BLOCK_E : 2A703DB9
ID_BLOCK_L : C4CF6F2386EC1D32B0AF58AB5E37F2A3
ID_BLOCK_L : 527BBE85A099E0CC4DA13129613BB67A
Pickup loader from firmware package
Loader Sent! Initializing ...
Running FireHose on BBID : MSM8996 , FLASH : UFS , mVER : 1
ExtInfo : 0x0000C000/0000C000/00001000/00001000/00001000
UFS Device : SAMSUNG KLUCG4J1CB-B0B1 0800
UFS SectSize : 0x1000
UFS LU0 Size : 0x00000007602F0000 : 29,50 GiB
--------------UFS Device Info--------------
UFS Total Active LU: 0x6
UFS wManufacturerID: 0x1ce
UFS Boot Partition Enabled: 0x1
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x800f
UFS LUN Enable Bitmask: 0x3f
UFS bConfigDescrLock: 0x0
Boot Ok!
Flash Chain : 74
Flashing now
Flashing : persist.img
Flashing : cache.img
Flashing : devcfg.mbn
Flashing : devcfg.mbn
Flashing : dynamic_nvbk.bin
Flashing : reserve1.bin
Flashing : reserve2.bin
Flashing : config.bin
Flashing : userdata.img
Flashing : gpt_main0.bin
Flashing : gpt_backup0.bin
Flashing : xbl.elf
Flashing : gpt_main1.bin
Flashing : gpt_backup1.bin
Flashing : xbl.elf
Flashing : gpt_main2.bin
Flashing : gpt_backup2.bin
Flashing : gpt_main3.bin
Flashing : gpt_backup3.bin
Flashing : rpm.mbn
Flashing : rpm.mbn
Flashing : tz.mbn
Flashing : tz.mbn
Flashing : hyp.mbn
Flashing : hyp.mbn
Flashing : sec.dat
Flashing : pmic.elf
Flashing : pmic.elf
Flashing : NON-HLOS.bin
Flashing : adspso.bin
Flashing : mdtp.img
Flashing : emmc_appsboot.mbn
Flashing : emmc_appsboot.mbn
Flashing : logo.bin
Flashing : boot.img
Flashing : boot_aging.img
Flashing : system.img
Flashing : recovery.img
Flashing : BTFM.bin
Flashing : keymaster.mbn
Flashing : keymaster.mbn
Flashing : cmnlib.mbn
Flashing : cmnlib.mbn
Flashing : cmnlib64.mbn
Flashing : cmnlib64.mbn
Flashing : apdp.mbn
Flashing : msadp.mbn
Flashing : gpt_main4.bin
Flashing : gpt_backup4.bin
Flashing : md5.img
Flashing : gpt_main5.bin
Flashing : gpt_backup5.bin
Click to expand...
Click to collapse
MA7MOD_GSM said:
for UFS Chip only can use Nuprog to rewrite full flash to chip direct or use cm2 dongle with Open memory tool plugin and can flash it in 9008 port
Click to expand...
Click to collapse
This is rather interesting. I have a working g5 (H830) and a bricked on stuck on qdloader mode.
Can you point me in the direction of reading the backup from the working one to resurrect the bricked phone?
Currently have access to Octoplus Jtag Pro box. I do have cm2 dongle as well.
Hit me up soon, i hope.
Best Regards
hiroprotagonist said:
This is rather interesting. I have a working g5 (H830) and a bricked on stuck on qdloader mode.
Can you point me in the direction of reading the backup from the working one to resurrect the bricked phone?
Currently have access to Octoplus Jtag Pro box. I do have cm2 dongle as well.
Hit me up soon, i hope.
Best Regards
Click to expand...
Click to collapse
Let’s start with cm2
MSM8996 & UFS & MemoryTool
-Connect Working H830 in edl mode by press down,up and connect usb setup Cm2 QLM driver
-Open Cm2QLM and chose Memory Tool
-Chose full files and Make read
-Connect dead H830 with memory tool and make restore readed files from first working h830
-Send Screen Shot
#MA7MOD_GSM
Hi, I'm trying to find the original stock rom for XT1922-5, my cell phone got stuck on the bootloader screen and it's always showing the messagem;
START UP FAILED:
YOUR DEVICE DIDN'T START UP SUCCESSFULLY
USE THE SOFTWARE REPAIR ASSISTANT ON COMPUTER
TO REPAIR YOUR DEVICE.
I've tried so many stock rom, and none of them worked out for my cell phone.
these are the bootloader info:
baseband:M8937_13.423.055.35R JETER_LATAMDSSDS_CUST
PRODUCT/VARIANT: JETER XT1922-5 32GB P4
IF ANYONE HAS THIS STOCK ROM AVAILABLE, COULD YOU PLEASE SEND THAT TO ME?, I'VE BEEN TRYING TO SOLVE IT FOR WEEKS AND NOTHING REALLY WORKED!
AND MY BOOTLOADER ISN'T UNLOCKED!
THANKS IN ADVANCE,
Welcome everyone!
This project has started, becouse we need real solution for the problem. The problem of hard bricked Moto devices. It is like a curse.
When my device bricked I have done solid research, I have gathered many informations and files essential to revive my cellphone but 5 years experience of linux, rooting, compiling kernels and roms weren't enough to make it work.
But nevermind. I am even more determinated and I am asking ALL of You guys here to help me. Together we will come to solution.
Here is what I got, happy reading :
DICTIONARY:
PBL - Primary bootloader of the chip - this is like BIOS for phone so it checks chip for damage and problems and then it tries to load SBL but if SBL is corrupted or checksum doesn't match, PBL invokes Qualcomm HS-USB QDLoader 9008 emergency mode. PBL is hard flashed into SoC and can't be corrupted by firmware.
SBL - Second stage bootloader wich is more advanced than PBL. It initializes phone hardware and ABOOT.
ABOOT - Application bootloader (HBOOT). You probably know this one well. Android botloader.
Full mmcblk0 backup - Backup of whole phone flash storage byto to byte.
blankflash - method of repairing msm phones in 9008 state
programmer.mbn - Special type of software programmer that is being sent to chip in Qualcomm 9008 emergency mode. There it comunicates with pc via firehose protocol. Each phone has set of their own programmers, they are unique to phone and other programmers don't work. These programmers are signed so tampering it results in not working one.
firehose protocol - it is used to tell programmer what operations it must do on chip.
singleimage.bin - this package contains instructions for programmer and set of files it need (for example to replace)
gpt_main0.bin - Partition layout
rawprogram0.xml - instructions for programmer
patch0.xml - I don't know yet
STAR.exe - Application for managing and editing contents of singleimage.bin aka blankflash files
QPST - Flash tool from Qualcomm it basic function is to handle blank-flashing in a better way, also it allows for in-depth debugging of the process
Qualcom Premium Tool - Program made by Mppg Myanmar that is capable of making unlocking bootloader, OEM locks, making backup/restore of chip firmware, handling blank-flashing in VERY specific way (creating instructions for programmer), reading eMMC structure from firmware (can generate gpt layout so very useful!!!), modyfing FW and removing Xiaomi account. It also contains ALL programmers
for more:
https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565
https://alephsecurity.com/
https://github.com/alephsecurity/firehorse
https://github.com/aravindvnair99/Motorola-Moto-E-XT1022-condor-unbrick
INFO:
1. What causes the brick
I bet 100$ that you hard-bricked your Moto Z Play by installing OTA updates after downgrading firmware. This is only known reason for me at the time of writing this. There is most probable reason why it happens, look:
There are two most common chips on which smartphones are built - Qualcomm and Mediatek. While Mediatek chips are "modification friendly" and simple, Qualcomm chips are somewhat more advanced and have many features that can be enabled or disabled during prorammming in factory. One of them is PBL signature checking. During programming of your phone, proper signatures of SBL are written to it. When someone tries to override default SBL with the new one, it checksums are compared with that stored. If they match, new one is flashed, if not, then update does not happen.
Ok, but what it has to do with brick?!
I explain:
1. You decide to downgrade your firmware
2. During flashing, everything goes "well" (Phone boots), but trully update is partial:
FW in chip is (obviously) more recent that the one you downgrade to, and SBL signature is different (updated), so when it is compared to the signature of SBL from FW you want to flash, it don't match. That don't rise error and flashing continues. Only partition that stays untouched is bootloader, but all other partitions get replaced by those in FW zip. SBL is still compatible with the new partition offsets and partition layout overall so phone functions normally.
3 When OTA is executed, it checks the version of currently installed firware. The most reliabe way to do it is to check checksum of SBL which is pretty logical becouse it's checksum is like "fingerprint" of firmware. Normally, if it would detect the old firmware, OTA would be stopped, but newer SBL tricks it and OTA installs anyway.
4 Results are horrible, becouse OTA does not check GPT table and flashes partitions in bad sectors, corrupting FW.
This causes bootloader to go into Qualcomm HS-USB QDLoader 9008 safe mode.
5 Viola! Hard brick!
2. How to fix it?
That is jolly good question! What we have to do is to reflash full chip firmware. Suprisingly I see some solutions, but those need to be developed:
A) SD-BOOT
It turns out that our fancy chip can probably boot from SD-CARD! The procedure works like this:
- When chip starts, one of the very first things it does is loading the memory, so it can actually work. The trick, is that chip loads it from specific disk, marked with exact name (I don't remember which, but I will do research). Speccially repared SD-CARD can appear with that name, so chip boots from it, not from internal memory. (This trick is proved to work on this model)
How to do it?
- Get full dd of working phone - it must be phone with the SAME chip and very likely the same model
- flash it to SD-CARD of 32GB or more, class 10 speed or higher, directly to card, not partition
- put card in phone, turn it on and wait
- you should see HBOOT
- select fastboot and flash new FW via it
- viola!
!!!THIS IS COMPLICATED PROCEDURE, I WILL MAKE DETAILED THREAD SOON, BUT FOLLOW IT ONLY IF YOU KNOW WHAT ARE YOU DOING!!!
B) FIREHOSE/SAHARA ATTACK
This could be achieved by sending payload via Firehose programmer that would allow to break verification of SBL or somehow allow SBL to be flashed. Now, PBL blocks attempts to update SBL. I have thesis that it is becouse PBL do not allows for SBL downgrade, so it's version must be higher, but we try to flash same version of SBL so it doesn't work. That thesis needs confirmation.
C) CRAFT BLANKFLASH
This would be last resort. It will work for sure, but this method needs knowledge and I don't know if it is doable.
STEP 1: Get white-listed blankflash checksums from OTA (we would need to reverse engineer those)
STEP 2: Break hash
STEP 3: Craft blankflash with needed hash
STEP 4: Flash
NEVER USE BLANKFLASH (ATTENTION!)
DO NOT try any blankflash files. They can make situation a lot worse and even physically (!) dmage your phone.
D) JTAG
Medusa Box etc.
E) Qualcomm Premium Tool
This can even work, but it is untested and there is a slight chance that can worsen state of phone (needs confirming).
The tool is very advanced and I need to gather info about usage, so very probable to be a good solution if we will learn how to use it!
E) METHOD 7
Interesting method from this guy: (7th option, I have contacted him if it is compatibile)
https://github.com/aravindvnair99/Motorola-Moto-E-XT1022-condor-unbrick/blob/master/Unbrick%20methods.md
3. DOWNLOAD
(Links will be aded *soon*)
XDA:DevDB Information
Unbrick Developement for Moto Z Play (addison) Full-Brick, Tool/Utility for the Moto Z Play
Contributors
Bobernator, Stayn, Artim_96, Camarda
Version Information
Status: Nightly
Created 2019-05-04
Last Updated 2019-05-14
I really hope we can get a fully working detailed method to unbrick this device, I'll follow this project and try to help what I can, my phone isn't bricked but I think that an unbrick guide is absolutely necessary.
By the way, did you tried the Qualcomm Board Diag method? Before the Moto Z Play I had a LG G3 and got it hard-bricked and my pc would recognize it as "Qualcomm HS-USB QDLoader 9008" too, using the Board Diag method I got to erase completely the emmc and flash each partition manually, that got it back to life again, of course theres a requirement and it's the AP Chipset files. I don't know if you already tried so you tell me
Stayn said:
I really hope we can get a fully working detailed method to unbrick this device, I'll follow this project and try to help what I can, my phone isn't bricked but I think that an unbrick guide is absolutely necessary.
By the way, did you tried the Qualcomm Board Diag method? Before the Moto Z Play I had a LG G3 and got it hard-bricked and my pc would recognize it as "Qualcomm HS-USB QDLoader 9008" too, using the Board Diag method I got to erase completely the emmc and flash each partition manually, that got it back to life again, of course theres a requirement and it's the AP Chipset files. I don't know if you already tried so you tell me
Click to expand...
Click to collapse
Hi! Really nice to read that . I didn't tried it but i will chec k it out in a while. Sorry for not responding immediatelly but this will change from now, I have XDA app so I stay updated.
Have you seen this post? There's apparently a new Oreo blankflash https://forum.xda-developers.com/showpost.php?p=79514510&postcount=419
echo92 said:
Have you seen this post? There's apparently a new Oreo blankflash https://forum.xda-developers.com/showpost.php?p=79514510&postcount=419
Click to expand...
Click to collapse
Website is legit, sounds like something good, but i will byte-compare it to my other blank flashes in collection. Maby it will worsen state of my device but I will try it.
Ps. I am working on a download section!!!
EDIT: DO NOT TRY IT YET. As you can see in the link this has been uploaded 2 days ago. Post has 1 day, so this is suspicous as hell.
Bobernator said:
Website is legit, sounds like something good, but i will byte-compare it to my other blank flashes in collection. Maby it will worsen state of my device but I will try it.
Ps. I am working on a download section!!!
EDIT: DO NOT TRY IT YET. As you can see in the link this has been uploaded 2 days ago. Post has 1 day, so this is suspicous as hell.
Click to expand...
Click to collapse
I understand the reason to be suspicious, since there's also no way to verify the origin of this blankflash. Also, is there a OPNS27.76-12-22-10 firmware? I thought OPNS27.76-12-22-9 was the last build?
I will answer this way:
Bobernator said:
I will answer this way:
Click to expand...
Click to collapse
That blankflash looks like it worked - seems your device is in fastboot mode despite the photo angle.
echo92 said:
That blankflash looks like it worked - seems your device is in fastboot mode despite the photo angle.
Click to expand...
Click to collapse
Yes, it worked! But do not make misteake and after you flash blankflash do not flash full firmware. Instead flash only recovery - TWRP and make backup of modemst1, modemst2 and FSG partitions, so you can revert your IMEI. After that full flash android 8 FW
Bobernator said:
Yes, it worked! But do not make misteake and after you flash blankflash do not flash full firmware. Instead flash only recovery - TWRP and make backup of modemst1, modemst2 and FSG partitions, so you can revert your IMEI. After that full flash android 8 FW
Click to expand...
Click to collapse
Can you see your recovery partition with the dummy bootloader from the blankflash? Do you have to flash the GPT/bootloader from firmware first?
Well, this is nuts @Bobernator, I'm really happy we have an unbrick method.
If MTP is still working, you can flash the file I attached to this post to automatically backup the required partitions, this can also be helpful in case anyone wants a full IMEI Backup, also, I tried this step:
fastboot flash fsg mmcblk0p29_fsg_backup
fastboot flash modemst1 mmcblk0p27_modemst1_backup
fastboot flash modemst2 mmcblk0p28_modemst2_backup
Click to expand...
Click to collapse
and it gives me permission denied when flashing modemst1 and modemst2, I think we should flash modem NON-HLOS.bin and erase modemst1 and modemst2, if you agree I'll update the zip I made to backup NON-HLOS.bin instead of modemst1 and modemst2
Quick question, is it worth mentioning only to perform steps 12 and 13 (flashing your FSG and modemst backups) if your device has no signal/IMEI issues after flashing the Oreo firmware? Just wondering since the firmware flash and subsequent boot may correctly rebuild the modemst files...
echo92 said:
Quick question, is it worth mentioning only to perform steps 12 and 13 (flashing your FSG and modemst backups) if your device has no signal/IMEI issues after flashing the Oreo firmware? Just wondering since the firmware flash and subsequent boot may correctly rebuilt the modemst files...
Click to expand...
Click to collapse
I don't know for sure but a backup is always recommended and more if it is the IMEI, then, you can flash all partitions and then before restoring the backup boot into the system and check by yourself if you're getting signal and its working... :good:
Stayn said:
I don't know for sure but a backup is always recommended and more if it is the IMEI, then, you can flash all partitions and then before restoring the backup boot into the system and check by yourself if you're getting signal and its working... :good:
Click to expand...
Click to collapse
Yup, an IMEI backup is always useful Just wanted to ask since it's not pointed out in the opening post's guide to check your IMEI/signal before committing to step 12/13. If it's working, no need for those two steps!
@echo92 I forgotten about IMEI totally so I can't tell you, but I can't confirm that's safe to flash gpt and bootloader from OREO fw (8.0). I did this way and everthing is working. Even OTA updates to most recent witouth problems! Here are the proofs (language is "Polish" if you want to translate):
Stayn said:
Well, this is nuts @Bobernator, I'm really happy we have an unbrick method.
If MTP is still working, you can flash the file I attached to this post to automatically backup the required partitions, this can also be helpful in case anyone wants a full IMEI Backup, also, I tried this step:
and it gives me permission denied when flashing modemst1 and modemst2, I think we should flash modem NON-HLOS.bin and erase modemst1 and modemst2, if you agree I'll update the zip I made to backup NON-HLOS.bin instead of modemst1 and modemst2
Click to expand...
Click to collapse
I really appreciate this! Thanks!
If you update your ZIP, I will attach it into the project today, and I will try to find out solution for you, becouse it looks if you can't restore IMEI now (correct me if I am wrong)
echo92 said:
Yup, an IMEI backup is always useful Just wanted to ask since it's not pointed out in the opening post's guide to check your IMEI/signal before committing to step 12/13. If it's working, no need for those two steps!
Click to expand...
Click to collapse
You are surely right. I will correct thread today.
Bobernator said:
I really appreciate this! Thanks!
If you update your ZIP, I will attach it into the project today, and I will try to find out solution for you, becouse it looks if you can't restore IMEI now (correct me if I am wrong)
Click to expand...
Click to collapse
Don't worry about the IMEI, I got it again after flashing my fsg backup, modem and erasing modemst1 and modemst2, now the problem is that on every ROM I get everytime a popup "com.android.phone" has stopped, till I remove the sim card, what could this be? This isn't my main phone so I'm not worried at all but this could happen to someone else
Dial *#06#, if you will get nothing or zero's that means it can be modem failure
Ps. Is your zip updated now?
Hello Guys,
I have the exact same problem. All started here with a changed screen that after update to 8 stopped working, so I did downgrade to 7, and the touch as back, than it started doing the OTA updates and I (dumb enough) accepted it, and now I have a bricked device.
***EDIT***
Now I could get access to the bootloader again, the flash blank worked but it had a catch, if I just executed the bat, it would not work, I had to open a CMD with admin rights, go to the folder and run the bat from there.
***EDIT 2***
So restored bootloader, and booted just like before it was corrupted, now it keeps asking for update, and I disabled it on the "Developer Menu", is that enough? Will not play with updates on this device anymore, android 7.1.1 with 2017 security updates will do it.
***EDIT 3***
Now I have a Mobile Network problem, it does recognize the SIM Chip, but won't get network access, I didn't backup before doing the Blank Flash, but it was not showing on the system before (because the downgrade from 8 to 6, and them upgrade to 7), is there a way to recover it or fix this no network registration possible?
the boot.img file was loaded into my phone in order to get root after that it could not detect imei numbers. Although they are in fastboot. I tried many different firmwares for this phone, but there is no result! I ask for your help. I was left without communication (sorry for not being very clear. I don't understand Russian and don't understand English at all, that's why I'm writing through a translator
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
twistedumbrella said:
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
Click to expand...
Click to collapse
Tell me where you can find the pure CN firmware? This phone was presented to me in this form already. And they told what happened to him. I doubt that ASUS support will help me, since in addition to everything according to the owner, the EMMCCDL_GUI utility was used. So I ask for help from knowledgeable people here.
And most importantly, what to flash and how?
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
twistedumbrella said:
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
did not help(
What? So no one will help ???
Return the phone or wait until the methods exist.
Those are the only quick answers left.
twistedumbrella said:
Return the phone or wait until the methods exist.
Those are the only quick answers left.
Click to expand...
Click to collapse
It was opened. This is not an option either
If you purchased it used and the seller refused a return, it sounds like they were trying to recover what they could by selling their problem to someone else. It's likely they knew there wasn't a self-service fix right now.
Just to be clear, what you need is a low-level EDL restore. As it stands, one of the files required is not available to the public. If you have a local repair shop, they may be able to do it (and will likely charge a fee).
Do NOT pay someone over the internet. It CANNOT be done remotely.
Dose anyone have the Raw firmware for Asus rog phone 5s or 5s Pro?
Same question here..
Does anyone have? My 5s pro is down T_T
Thanks anyway
wcx19911123 said:
Same question here..
Does anyone have? My 5s pro is down T_T
Thanks anyway
Click to expand...
Click to collapse
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
This thread by johnny886 has the entire firmware files. Follow the video in the first post so you minimize any issues.
You will need to download a few drivers.
I also posted some stuff related to any issues on a few of my threads and on johnny886 thread.
I hard bricked my phone, and managed to fix my phone only using his files.
Other people posted firmware threads as well but it isn't complete like this one is. The others are missing major components to actually fix the phone. The other threads also do not have software to save your phone imei, which if you don't save and you try to install firmware on your phone. You could end up permabricking your phone and no one can fix it at that point. This is because the phone doesn't have a serial or a lot of identifying information, so it will refuse to load the firmware.
Donlavon1 said:
Dose anyone have the Raw firmware for Asus rog phone 5s or 5s Pro?
Click to expand...
Click to collapse
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Trash.umu said:
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
This thread by johnny886 has the entire firmware files. Follow the video in the first post so you minimize any issues.
You will need to download a few drivers.
I also posted some stuff related to any issues on a few of my threads and on johnny886 thread.
I hard bricked my phone, and managed to fix my phone only using his files.
Other people posted firmware threads as well but it isn't complete like this one is. The others are missing major components to actually fix the phone. The other threads also do not have software to save your phone imei, which if you don't save and you try to install firmware on your phone. You could end up permabricking your phone and no one can fix it at that point. This is because the phone doesn't have a serial or a lot of identifying information, so it will refuse to load the firmware.
Click to expand...
Click to collapse
No firmware package is incomplete, but some of the older EDL restore packages don't have all the files to perform a full restore. There is a difference between flashing raw firmware and performing an EDL restore.
Raw firmware is like reinstalling Windows. It's a factory reset with the factory image. This fixes most OS issues, such as deleting important files.
EDL restore is like flashing the BIOS. It formats all of the partitions and does a clean install as if the phone never had any firmware at all.
It's important to know the difference, since flashing raw firmware is far less dangerous and much easier. It might be worth asking what the problem is before jumping right to EDL restore.
<Moderator Edit>: Post edited. I will PM you as to why shortly.
My rog phone 5s pro was hardbrick because I Flash the wrong firmware like rog phone 5 raw file.. then my phone detect on my pc only on edl mode qualcomm not turning on.. after few hours of research I revive my phone if someone softbrick rog phone 5 series.