Related
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.
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?
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
back2nature said:
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
Click to expand...
Click to collapse
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Click to expand...
Click to collapse
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
back2nature said:
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
Click to expand...
Click to collapse
Sorry, I'm just now seeing this. Did you ever make any progress? Yes, I think there are some reliable methods to create debrick.img/debrick.bin files, there is one such method posted here at XDA in a random post in a thread here but I can't remember exactly what thread it is.
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.
Hi, guys, I am really needing help.
I have bougth a chinese android tablet model tb128fu. I was worried with the safety of the tablet's ROM, I was suspecting it was a shop ROM. So, I downloaded LMSA (Lenovo Rescue and Smart Assistant) to flash an another ROM (even I have read in LMSA app that flashing ROM mustn't be done in chinese devices - I was very stupid) and it bricked my tablet. Tablet entered into a reboot mode loop: any chosen option was conducting to lenovo's logo and, after it, reboot menu again.
I have posted a question about it here in forum and people suggested to use ROM2box app. I tried to use it and I think it would solve my problem, but during ROM flashing in ROM2box my pc turned off (due to a residencial blackout) and now my tablet is completely died. VOL UP and DOWN and power off buttons are not working, and the screen doesn't show anything, in any situation (even during battery charging).
Please, help me!!! I think I have lost my tablet.
In PC's devices manager tablet is showed as Qualcoom HS-USB QDLoader 9008 (COM3). Does it help anything to solve my problem?
I have also tried to flash some chinese ROM in tablet using QFIL, but all times it shows the follow error:
"Download Fail:Sahara Fail:QSaharaServer Failrocess fail"
I am thankful anyway. Thank you for your attention.
Re-flash tablets Stock ROM.
BTW:
Tablet isn't hardbricked but softbricked, IMO
With the "hardbrick" usually a part of the low-level firmware is damaged, e.g. the bootloader, the "radio firmware" or other firmware, which is necessary for the operation of the SoC (System-on-Chip). To re-install this firmware, special hardware (usually JTAG) is required, as well as expert knowledge and corresponding image files are often not publicly available (at least not officially). It's like "shooting" the BIOS/EFI on a PC.
With a "softbrick," only the operating system is damaged, e.g. the Android kernel or the system libraries. You can reflash the device.
xXx yYy said:
Re-flash tablets Stock ROM.
BTW:
Tablet isn't hardbricked but softbricked, IMO
With the "hardbrick" usually a part of the low-level firmware is damaged, e.g. the bootloader, the "radio firmware" or other firmware, which is necessary for the operation of the SoC (System-on-Chip). To re-install this firmware, special hardware (usually JTAG) is required, as well as expert knowledge and corresponding image files are often not publicly available (at least not officially). It's like "shooting" the BIOS/EFI on a PC.
With a "softbrick," only the operating system is damaged, e.g. the Android kernel or the system libraries. You can reflash the device.
Click to expand...
Click to collapse
Ah, ok. I am really sorry for my mistake. It's clear now what is the difference between hard and soft brick.
May you help me to reflash my device? I have no idea how to do that.
Thank you for you reply
joaovitorjvbjvb said:
Ah, ok. I am really sorry for my mistake. It's clear now what is the difference between hard and soft brick.
May you help me to reflash my device? I have no idea how to do that.
Thank you for you reply
Click to expand...
Click to collapse
I might try the website linked below -- there's also a "How to Flash" tutorial step-by-step guide in the page
DISCLAIMER: I am not completely sure if it will help or make this worse! Being that your device is a Chinese variant and you've already bricked it messing with it because it is that variant, there's no guarantee the files and steps below will do any better or not make things worse. I also have not personally vetted the validity or accuracy of the site. Proceed at your own risk!
Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File)
Download the official Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File) for your Lenovo Mobile. We also provide all other Lenovo Stock Firmware for free.
firmwarefile.com
simplepinoi177 said:
I might try the website linked below -- there's also a "How to Flash" tutorial step-by-step guide in the page
DISCLAIMER: I am not completely sure if it will help or make this worse! Being that your device is a Chinese variant and you've already bricked it messing with it because it is that variant, there's no guarantee the files and steps below will do any better or not make things worse. I also have not personally vetted the validity or accuracy of the site. Proceed at your own risk!
Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File)
Download the official Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File) for your Lenovo Mobile. We also provide all other Lenovo Stock Firmware for free.
firmwarefile.com
Click to expand...
Click to collapse
OWWWW DUDE!!!
I am really thankful . Thank you very much )
Using your download link I got it! I could flash ROM (using QFIL) in my tablet again. My tablet is finally back. Thank you!!!