Success is disgusted by some people, and will not share any files for free in the future.
Once again you proved it bro. Amazing job will test now and confirm.
Working perfectly tested and rooted. Steps are easy to follow.
1) Download the ENG firmware and flash it following the steps.
2) Then follow this post and the commands to extract asuskey4 and add ISN to the asuskey4.
3) Flash WW ROM back to the phone.
4) Use Unlock tool and then done.
by far one of the best contributions of the forum, I don't usually comment, but I had to thank you
This is huge! The answer everyone with Tencent WW phones were looking for! Thank you
Could anyone please elaborate step 1 (flashing the ENG firmware provided)?
My phone enters edl mode and I see port 9008 in the device manager.
What should I do next?
arjun_m4 said:
Working perfectly tested and rooted. Steps are easy to follow.
1) Download the ENG firmware and flash it following the steps.
2) Then follow this post and the commands to extract asuskey4 and add ISN to the asuskey4.
3) Flash WW ROM back to the phone.
4) Use Unlock tool and then done.
Click to expand...
Click to collapse
yes,very easy
Can NOT flash ENG firmware..
Method # 1 : "0-update_image_EDL.bat" does not even start
Method # 2 : ERROR_UNSUPPORTED_TYPE
Method # 3 : Download Fail:FireHose Fail: FHLoader Fail: process fail
SOS guys! I am in deep sh*t!!
I cant find the SSN in the device.txt ... Only ISN is available .. ?
JazonX said:
I cant find the SSN in the device.txt ... Only ISN is available .. ?
Click to expand...
Click to collapse
You can see SSN on our phone when you boot up ENG firmware just type urself to the editor.
Find the address mentioned and start typing from first 0 u will see the HEX changing and then verify it's correct and save
aimsjahan said:
Can NOT flash ENG firmware..
Method # 1 : "0-update_image_EDL.bat" does not even start
Method # 2 : ERROR_UNSUPPORTED_TYPE
Method # 3 : Download Fail:FireHose Fail: FHLoader Fail: process fail
SOS guys! I am in deep sh*t!!
Click to expand...
Click to collapse
Can you check if your phone is being recognized as EDL maybe the drivers are installed wrong. I can verify that the files provided works 100% and you have to use left side type c of the Asus not the bottom.
JazonX said:
I cant find the SSN in the device.txt ... Only ISN is available .. ?
Click to expand...
Click to collapse
SSN can be seen on the homepage of the mobile phone after flashing the ENG firmware, or on the packaging box of your mobile phone.
Asuskey4 software download link please
Thanks, @johnny886! Btw, can you change your post to "General" instead of "Question", and pin it to this forum so people would use it as a reference in the future?
arjun_m4 said:
Can you check if your phone is being recognized as EDL maybe the drivers are installed wrong. I can verify that the files provided works 100% and you have to use left side type c of the Asus not the bottom.
Click to expand...
Click to collapse
My ROG5 is being shown in Device Manager as Qualcomm 9008. So I guess it has entered in EDL mode.
aimsjahan said:
My ROG5 is being shown in Device Manager as Qualcomm 9008. So I guess it has entered in EDL mode.
Click to expand...
Click to collapse
Could you reinstall the drivers I have faced issues like this before with other Qualcomm devices. Reinstall Qualcomm drivers it should work. And remember to install with disable signature enforcement.
Akkaya34 said:
Asuskey4 software download link please
Click to expand...
Click to collapse
I think you haven't figured out how to do it. Please read the steps carefully before proceeding. . .
arjun_m4 said:
Could you reinstall the drivers I have faced issues like this before with other Qualcomm devices. Reinstall Qualcomm drivers it should work. And remember to install with disable signature enforcement.
Click to expand...
Click to collapse
Appreciate your response mate! I will try again after reinstalling QCOM drivers. Could you please share that driver you are using?
Also, my PC does NOT detect ROG5 when using the official USB-C on both end cable. I have to use another cable with USB in one end and USB-C in the other end. Do you think that might be an issue?
With lost imei , imei=0 , I correct imei , SN in asuskey4 but it not unlock
nguyenhung9x2018 said:
With lost imei , imei=0 , I correct imei , SN in asuskey4 but it not unlock
Click to expand...
Click to collapse
The asuskey4 should contain SSN and ISN then only it will unlock. Make sure it's there and how come you lost your IMEI I tried this for 2 separate devices and I didn't face any issue.
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 am a little new and don't really know about this subject but :
I purchased a new phone : a Gome K1.
This is not tablet but phone. This is a new brandt. This a MTK (MT6757).
For the story, it came to me with chinese ROM, all menus in chinese
I asked to the seller to give me a ROM with playstore and french. They done it.
I flashed their new ROM with a proprietary flash tool. Now I have a android 6 ROM with Playstore, french menus. Well !
But I'd like to know if there is a way to root it, and install a TWRP :
The ROM came with bootloader locked and no recovery. It is entirely blocked.
No way to unlock bootloader via the general way (fastboot oem unlock --> unknown command)
I read some articles that deal with spflashtool and porting TWRP, but I'm new to this and I don't think I will be able to make all these steps correctly to flash a TWRP ...
Does someone has an idea ?
Is my post on the good topic ?
Up, does someone have an idea of how to root it ?
Hello,i also have a Gome K1 phone and I am also interested at rooting it.
There is an ' OEM unlocking option' under the developers option in the settings, have you tried that yet?
If you managed to import twrp and rooted the phone can you pls send here the steps, Thanks
Hello, happy to not be alone with this phone ...
Yes I tried everything, after enabling unknown source, OEM unlocking and USB Debugging developer options :
- All root apks
- all existing root kits using ADB
- Method with a linux distro to access Phone filesystem as root ( cannot see my phone ... )
Now I'm trying to use SP flashtool last version, but even that cannot correctly access the phone to Readback my recovery : there is BROM error, so I think that phone is not compatible with the phone (seen on a forum ...)
So if someone has an idea, he is welcome
Inveds said:
Hello,i also have a Gome K1 phone and I am also interested at rooting it.
There is an ' OEM unlocking option' under the developers option in the settings, have you tried that yet?
If you managed to import twrp and rooted the phone can you pls send here the steps, Thanks
Click to expand...
Click to collapse
When I contacted them, they send me a non rooted custom ROM which embed Google Apps and All language, AND another flash tool.
This flash tool seems to be based on SP flash tool. It seems to have restrictions (no readback ability ...).
I'm not able to backup anything with this tool or with SP flash tool.
Whis spflashtool, when clicking ReadBack, I power off my phone, and plug USB cable.
It begins the process but I immediatly encounter a BROM error :
ERROR: status_brom_cmd_send_da_fail (0xC0060003)
I read a post which indicate to try to plug usb cable when pressing Power plus Volume Up, but I don't think it can work, because I know that their tool works without that operation.
So now I'm still stuck here. Does someone have an idea ?
Hi
On the Russian forum 4pda, the topic GOME K1 we are also discussing and trying to solve the problem of a locked bootloader. So far no results. ROOT is also not yet possible to get.
I've also ported twrp for GOME K1, but there's no point in installing it until the bootloader is unlocked. Otherwise we will get a brick.
Hi
In Developer options there is a setting to unlock bootloader, it's the third toggle down.
Hope this helps.
Amagram said:
Hi
In Developer options there is a setting to unlock bootloader, it's the third toggle down.
Hope this helps.
Click to expand...
Click to collapse
No, it's not working. This switch does not affect the boot loader state.
vsxby said:
Hi
On the Russian forum 4pda, the topic GOME K1 we are also discussing and trying to solve the problem of a locked bootloader. So far no results. ROOT is also not yet possible to get.
I've also ported twrp for GOME K1, but there's no point in installing it until the bootloader is unlocked. Otherwise we will get a brick.
Click to expand...
Click to collapse
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
z2x said:
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
Click to expand...
Click to collapse
Thank you, but I already have this tool. As I wrote before flashing TWRP we need to unlock the bootloader. While this is not impossible to do. But one of our users on 4pda is going to ask the manufacturer to unlock bootloader. In case of success, I will inform you.
If you want to experiment and flash TWRP with a locked bootloader, I can give you the TWRP I made, but I warn you, it's not safe.
Bro,Can you upload the firmware and tools to google drive or something like? It will be very helpful for dealing with this mediatek replica phone(aus6757_66_m),i got some possible factory test MTK AOSP,but the link expires ：（
@Vortex said:
Bro,Can you upload the firmware and tools to google drive or something like? It will be very helpful for dealing with this mediatek replica phone(aus6757_66_m),i got some possible factory test MTK AOSP,but the link expires ：（
Click to expand...
Click to collapse
It's link GD to multi firmware and tool
vsxby said:
Thank you, but I already have this tool. As I wrote before flashing TWRP we need to unlock the bootloader. While this is not impossible to do. But one of our users on 4pda is going to ask the manufacturer to unlock bootloader. In case of success, I will inform you.
If you want to experiment and flash TWRP with a locked bootloader, I can give you the TWRP I made, but I warn you, it's not safe.
Click to expand...
Click to collapse
Ok, hope manufacturer will accept to give bootloader unlock procedure
z2x said:
Ok, hope manufacturer will accept to give bootloader unlock procedure
Click to expand...
Click to collapse
We were unable to contact the manufacturer and the moderators of the official GOME forum do not have this information. At the moment, there are no solutions to this issue.
z2x said:
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
Click to expand...
Click to collapse
could you please post here what is the procedure you took to flash the rom. Seller sent me with multi language rom. i want to downgrade the rom to its original one. I used your tools in the windows 10 lap. and also in the windows 7 lap but it was useless. I am going to try the procedure in the windows 8.1 lap. can you tell me exactly how you flash your phone with that tool ?
Hey Bro,
I get my new Gome K1 with Global ROM
but have some issues with my new Gome K1 >> the GPS doesn't work proper for Google Maps / Waze, it doesnt show accurate position most of the time, but it seems work well with "offline GPS" (but offline GPS most of the time not able to find location that I ahead for meeting). Any recommendation/solution?
Thanks in advance
Hi, is there any modem file for this phone ? MDDB....
original eom (china rom).
Hello every one i buy thise phone and come with multilanguage firmware but i like the origin one, can anyone help me the link of the firmware of origin!!
vsxby said:
We were unable to contact the manufacturer and the moderators of the official GOME forum do not have this information. At the moment, there are no solutions to this issue.
Click to expand...
Click to collapse
After some time ... is there any news about his root? I wouldn' t like to change the rom, but just do the root thing would be useful ..... tks
i've disabled the google app in the settings and now the phone is stuck on boot logo... any ideas how to fix this?
---------- Post added at 06:51 PM ---------- Previous post was at 06:30 PM ----------
driska said:
i've disabled the google app in the settings and now the phone is stuck on boot logo... any ideas how to fix this?
Click to expand...
Click to collapse
found the answer on 4pda, can't post link.
visit this link https://halabtech.com/remove-rmm-prenormal-a320f-j701f-etc/
use miracle box to remove rmm state ...
put phone itno download mode and connect with computer via usb . then open miracle box
go to samsung tab ... then select Reset Reactivation / EE Locks
then click start .. wait for 1 minute .. ist done ...
then flash Stock ROm or Custom Rom
tools link http://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/
Thank you very much I used miraclebox to remove rmm and root my oreo 8.1 j7 pro (j730gm, same exynos chipset) without problem
I got 'open port' error in miraclebox at first but it was solved after installing virtual serial port driver
A720F not work
bluechipmunk1225 said:
Thank you very much I used miraclebox to remove rmm and root my oreo 8.1 j7 pro (j730gm, same exynos chipset) without problem
I got 'open port' error in miraclebox at first but it was solved after installing virtual serial port driver
Click to expand...
Click to collapse
Hi, how do you create a virtual serial port?
I just googed virtual serial port driver, installed and it worked
full tutorial please?
It works!
This method actually worked in removing the rmm state in my J701F.
Do I have to download stock rom or it's optional?
virtual serial port
bluechipmunk1225 said:
I just googed virtual serial port driver, installed and it worked
Click to expand...
Click to collapse
link pls
If i got one of these 'miracle box' things, would this work on my SM-G960W(samsung galaxy s9, snapdragon, Canada, Koodo)?
FalsAlarm said:
If i got one of these 'miracle box' things, would this work on my SM-G960W(samsung galaxy s9, snapdragon, Canada, Koodo)?
Click to expand...
Click to collapse
you just have to take the risk
qasimsansi3 said:
visit this link https://halabtech.com/remove-rmm-prenormal-a320f-j701f-etc/
use miracle box to remove rmm state ...
put phone itno download mode and connect with computer via usb . then open miracle box
go to samsung tab ... then select Reset Reactivation / EE Locks
then click start .. wait for 1 minute .. ist done ...
then flash Stock ROm or Custom Rom
tools link http://www.techeligible.com/2018/04/03/download-miracle-2-58-with-loader/
Click to expand...
Click to collapse
is it mandatory to flash firmware after removimg rmm from miracle
abd96iq said:
is it mandatory to flash firmware after removimg rmm from miracle
Click to expand...
Click to collapse
yes
It works
It works for me very well, even my smj701d was not shown in the list from miracle box. I choose a similary one and
when done my bootloader option was visible.
Guess everyone can try it too, i really guess there is nothing can happen.
meyshah said:
A720F not work
Click to expand...
Click to collapse
You managed to bypass rmm state prenormal? If so, please tell us how!
For those interested, this is exactly engineering rom, with added modified patched boot, so it is rooted with magisk. v23
This is the detailed install procedure:
You need to download the following:
1. YU_Yutopia_YU5050_V1_24.12.15 rom, link give below.
2. Qfil tools
3. Qualcomm driver.
How to Flash:1. Extract All Files From Zip File.,
2. Install Qualcome drivers (search through the web), Install QPST Tool and Run Qfil.exe File
3. Select the flat build option after the tool is open
4 . After that click on the select programmer’s path to browse and select the file “prog_emmc_firehose_8xxx.mbn”.
5. Then click on load.xml and select the “rawprogram0” file.
6. Then select the file patch0.
7. After selecting all the files with the flash tool, the phone has to be connected to the tool
8. For that, turn off the phone and press the Volume Up and Volume Down buttons simultaneously.
9. And then connect the data cable with the phone
10. After connecting, click on the select port in the tool and select Qualcomm HS-USB QDLoader 9008
11. Then click on the download button.
12. Keep the up and down buuton pressed until start downloading some files, the you can remove you fingers.
13. Wait until flashing finishes.
14. After First boot download Magisk apk, (I ve downloaded magisk v23, & its working perfectly).
No need to flash GAPP, its already present. Infact, the bootloader is locked & dont know how to unlock it, there is no option in developer mode to enable unlocking it. The rom is fast, not laggy, battery discharge is very good.
Download link:
1.37 GB file on MEGA
mega.nz
YU5050_SW_V46_User.zip | by kurdiak for Yutopia
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Attached files are screen shots of Qfil file setting & rom.
{Mod edit: Quoted post has been deleted}
I didnt understand what you mean. can you clarify your question.
kurdiak said:
{Mod edit: Quoted post has been deleted}
I didnt understand what you mean. can you clarify your question.
Click to expand...
Click to collapse
Sorry sir a simple typos.... (Due to autocorrect)
Real question...will flashing this firmware with flat building, nullify my phone's imei number.??
More over will i be able to write or rewrite imei on this rooted magisk phone without bootloader unlocked? As given in this procedure(of yu 5050)
CHAMPIONGAMERS said:
Sorry sir a simple typos.... (Due to autocorrect)
Real question...will flashing this firmware with flat building, nullify my phone's imei number.??
More over will i be able to write or rewrite imei on this rooted magisk phone without bootloader unlocked? As given in this procedure(of yu 5050)
Click to expand...
Click to collapse
No it will not nullify imei numbers, but it is safer to back up your imei (although i did not, and i have no problem with imei no.) As it is rooted already, you can do whatever you want. the only problem with this rom is that I could not unlock bootloader.
kurdiak said:
No it will not nullify imei numbers, but it is safer to back up your imei (although i did not, and i have no problem with imei no.) As it is rooted already, you can do whatever you want. the only problem with this rom is that I could not unlock bootloader.
Click to expand...
Click to collapse
Thank you a lot sir for ur kind replay...
Sir please please can u give me an easy procedure to restore or change (qcn) IMEI number if something goes wrong..cause i tried to repair imei of yu4711 through shell terminal but unable to do so without super su....
So please please gimmi a good easy procedure to change or repair imei if something goes weong...thanks in advance sir...and happy rakhi
CHAMPIONGAMERS said:
Thank you a lot sir for ur kind replay...
Sir please please can u give me an easy procedure to restore or change (qcn) IMEI number if something goes wrong..cause i tried to repair imei of yu4711 through shell terminal but unable to do so without super su....
So please please gimmi a good easy procedure to change or repair imei if something goes weong...thanks in advance sir...and happy rakhi
Click to expand...
Click to collapse
I used mobile unkle tools, I had lost my imei on another phone, and I could retain my imei using that tools easily. so if you take a picture shot or write down your number, you can rewrite it again. I dont write my imei no, because i had it on my phone box already written.
kurdiak said:
I used mobile unkle tools, I had lost my imei on another phone, and I could retain my imei using that tools easily. so if you take a picture shot or write down your number, you can rewrite it again. I dont write my imei no, because i had it on my phone box already written.
Click to expand...
Click to collapse
Sir yu 5050 is a qualcomm smartphone...as probably mobile unkle tools won't work...btw can i change the root provider from magisk to supersu without bootloader unlocked??...
CHAMPIONGAMERS said:
Sir yu 5050 is a qualcomm smartphone...as probably mobile unkle tools won't work...btw can i change the root provider from magisk to supersu without bootloader unlocked??...
Click to expand...
Click to collapse
I dont know. The most important thing for me is root, wether its magisk or supersu.
with this rom, my battery issues become much better, it can withstand a good period of time, the rom is smooth.
hello there . my flex ribbon cable appear to be broken . i wonder if someone knows the edl point for this device . thanks
Hi all,
I need a N976V U7 (USB only) DEAD-BOOT file / DEAD-FIX file / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer
The SM-N976V is a Verizon variant of the Note 10+ 5G positioned for the US market.
PLEASE PLEASE PLEASE !!!
Thank you.
Network_Pro said:
Hi all,
I need a N976V U7 (USB only) DEAD-BOOT file / DEAD-FIX file / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer
The SM-N976V is a Verizon variant of the Note 10+ 5G positioned for the US market.
PLEASE PLEASE PLEASE !!!
Thank you.
Click to expand...
Click to collapse
you dont need that as far as you can get into EDL mode you can flash with miracle tool box
So the Miracle Tool support SM-N976V SW Rev . bit7 (U7) ? I didn't find it specifically mentioned anywhere. In the EDL mode the Qualcomm sm8150 requires the firehose programmer. For other models this file seems to available so there is hope that for this model it can also be obtained from GSPN USA probably or from a guy who knows a guy who knows a guy who passed by a Samsung building once wink wink.
Network_Pro said:
So the Miracle Tool support SM-N976V SW Rev . bit7 (U7) ? I didn't find it specifically mentioned anywhere. In the EDL mode the Qualcomm sm8150 requires the firehose programmer. For other models this file seems to available so there is hope that for this model it can also be obtained from GSPN USA probably or from a guy who knows a guy who knows a guy who passed by a Samsung building once wink wink.
Click to expand...
Click to collapse
am telling you from experience it happened to my device i bricked it and i used miracle tool crack with just stock rom i did the EDL i just selected scatter file etc and i flashed and that was it
Anyways Good luck unbricking
Which update was it? I think the problem is the bit7 / U7 the firehose for that is another one if it worked for previous versions.
Gudaji said:
am telling you from experience it happened to my device i bricked it and i used miracle tool crack with just stock rom i did the EDL i just selected scatter file etc and i flashed and that was it
Anyways Good luck unbricking
Click to expand...
Click to collapse
Gudaji please give more info how did you do it exactly? Which 'scatter' file did you write to the device ?
Network_Pro said:
Gudaji please give more info how did you do it exactly? Which 'scatter' file did you write to the device ?
Click to expand...
Click to collapse
Okay,
I unpacked the firmware got the scatter file put the device in edl mode (with pins) and flashed the device .
But make sure you watch legit tutorials on YouTube how to get miracle tool box crack
Gudaji said:
Okay,
I unpacked the firmware got the scatter file put the device in edl mode (with pins) and flashed the device .
But make sure you watch legit tutorials on YouTube how to get miracle tool box crack
Click to expand...
Click to collapse
I've deleted your other post in this thread for the same reasons I already provided you here:
[RELEASED] TWRP FOR REDMI 12C/Poco C55
So I've started development for device trees, TWRP and custom for Redmi 12C (earth) and by the end of may we should also have a rom and custom recovery for our Redmi 12C. So stay tuned
forum.xda-developers.com
Please read my message as a friendly warning!
Regards
Oswald Boelcke
Senior Moderator
Which firmware and which scatter file? It won't work with wrong ones. More specifics please.
Did you have a pre-made scatter file, that you have made before bricking/EDL ?
It is important to be precise.
Network_Pro said:
Which firmware and which scatter file? It won't work with wrong ones. More specifics please.
Did you have a pre-made scatter file, that you have made before bricking/EDL ?
It is important to be precise.
Click to expand...
Click to collapse
Your stock rom it is in your stock rom just unpack it or use ODIN to unbrick
Odin does not see the phone because the phone is in 9008 EDL mode and the driver for that one is from Qualcomm. Odin wants a mode and driver from Samsung. For the Samsung download - Odin mode to work, the later Boot stages need to load. Those are messed up by wrong etoken bypass for the wrong Update version or wrong BL or tripepd knox erasure of the entire flash or something of that sort.
In the stock ROM I do not know which file you can call a scatterfile? Is it the PIT file which is used for formatting?
This is the 'stock ROM' correct ? https://samfw.com/firmware/SM-N976V/VZW/N976VVRU7HWB2
Well for sure the Miracle Box has a huge collection of loaders in the distribution, as well as XML files. Very interesting.
@Gudaji, it seems, however that with U7 there may be needed a new loader. The update "bit" is somehow set inside the CPU, which, from my understanding, prevents older loaders from working?
Network_Pro said:
Well for sure the Miracle Box has a huge collection of loaders in the distribution, as well as XML files. Very interesting.
@Gudaji, it seems, however that with U7 there may be needed a new loader. The update "bit" is somehow set inside the CPU, which, from my understanding, prevents older loaders from
Click to expand...
Click to collapse
First of all do you have miracle tool box?
If so go to the Qualcomm tab and you will se flash tab under and then you select the files from your “extracted” firmware and flash while in EDL mode
The "Miracle Box Update 3.39 to 3.40 only for PS" informs me there is a new version and does not start. Maybe I do not have the right one.
Network_Pro said:
The "Miracle Box Update 3.39 to 3.40 only for PS" informs me there is a new version and does not start. Maybe I do not have the right one.
Click to expand...
Click to collapse
There is a bypass for it but you have to look for it
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Network_Pro said:
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Click to expand...
Click to collapse
Reply in my pm asap
Network_Pro said:
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Click to expand...
Click to collapse
First off how did you brick your device
Spammed the download mode with some wrong files. older etoken bypass, vbmeta disabled, KG disabled , eng. files, modem from other model, boot from other model, twrp recovery not sure which exactly was a successful flash and which were rejected due to checksum mismatch.
Network_Pro said:
Spammed the download mode with some wrong files. older etoken bypass, vbmeta disabled, KG disabled , eng. files, modem from other model, boot from other model, twrp recovery not sure which exactly was a successful flash and which were rejected due to checksum mismatch.
Click to expand...
Click to collapse
hayahe sorry your mobile is dead kek
MIRACLE TOOLBOX IS YOUR 1 AND ONLY SOLUTION IF YOU DONT WANT TO PAY ANYONE IVE GIVEN YOU GUIDE IN YOUR PM SO GOODLUCK KEK