Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
What made your device hard brick
Sent from my SM-N910G using Tapatalk
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
AlexanderDAB said:
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
Click to expand...
Click to collapse
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Update:
So far I have contacted Qualcomm, Intrinsyc (they sell Snapdragon development boards), and a Samsung retail outlet.
All have come back as a negative - the closest I could get was the Samsung retail outlet where a dude used to work in the repair centre and had access to the files then.
Unfortunately, Samsung revoked his permissions now that he only works in a retail outlet.
He knew what I was talking about, but due to Samsung and their encryption etc, he couldn't provide me with the files.
C_dog_1 said:
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
Click to expand...
Click to collapse
I have the same problem and also looking for a solution. I will contribute to this post as I find something.
There is a similar post here:
http://forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
---------- Post added at 07:10 PM ---------- Previous post was at 06:30 PM ----------
Try this manual.
http://dl-1.va.us.xda-developers.co....rar?key=yrJPiZgu63c6RxNIbU_xVA&ts=1474829412
I've found it earlier today but haven't had a chance to try it yet.
Says the file is gone
Sent from my SM-N930W8 using XDA Labs
It's just the pdf and .pit that i used here: http://forum.xda-developers.com/note-4/help/hard-brick-phone-off-long-help-fellow-t3468792
yashthemw said:
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Click to expand...
Click to collapse
it won't boot at all
i was messing around with the system on the factory binary firmware
yes, it is
nope, it will not boot
i have same problem does any one sucess with this process ?
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
Click to expand...
Click to collapse
can you get me a dude with an AT&T note 4?
same boat with my N910F
C_dog_1 said:
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
Click to expand...
Click to collapse
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Lofhario said:
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3488114
Tried this?
Reporting Via N910G.
Hi, got a Phicomm Energy M+ (E551). It turned off as the battery was empty, so I charged it overnight.
But:
-Switching it on only shows the phicomm logo
-Trying to enter recovery, shows phicomm logo for a second and then the screen stays lit. Nothing else happens.
-On Windows 7 device manager shows it as "RELINK HS-USB QDLoader 9008 (Com3)" (VOL Up+VOL Down + Power)
-fastboot/adb wont find it
-I tried this http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I dont have a emmc backup but an unzipped Stock ROM of the E551L which support told me to use. (put on SD card and reboot into recovery, but I cant get into recovery)
Hence I use the unzipped ROM with the Qualcomm FLasher :S (http://na.phicomm.info/release/E551L...TA package.zip)
-It starts the process but then says "Failed to enter EDL" (Emergency) mode
Another thing I stumbled across is :
E551L has Qualcomm MSM8916 and Android 4.4.2
E551M has Qualcomm MSM8915 and Android 4.4.4
Will I have to quire a deepflash cable or am I missing something here ?
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Click to expand...
Click to collapse
tried but not working
waiting for other solution
Related
Hi still looking for the spst tool, the links are dead,realy do need to program, i did have but have the tool but lost it as my hard drive crashed, ive got the manual, please please help,thanks john
Sorry, I'm not sure what link/files you are looking for. I can check my own system to see if I still have access to it/them, once I know...
klamation said:
Sorry, I'm not sure what link/files you are looking for. I can check my own system to see if I still have access to it/them, once I know...
Click to expand...
Click to collapse
He is referring to the tools from this thread: http://forum.xda-developers.com/showthread.php?t=1019223
Aka: KinTwoSetupTool.rar and KUSBDrivers.rar
Some people just now found the thread (only seems like a few noticed it originally) and are curious if they can find anything new (including me). But the links are long dead.
Also, a google search turns up nothing. Only results are the xda thread and Microsoft PMX SPST USB Driver on software informer (to which it says "We don't have this file but you can try googling it" in place of the download button)
Also,
SPSTUSBDriverInstall.msi
PB10ZUnPB20ZU (Lab) Vn.n.n.msi. (Vn.n.n is replaced with version numbers, thus "Vn")
InstallPMXMTP.msi
these files would be of use too (they may or may not of been part of the rar's, but they are pointed out as necessary in the pdf from the original thread)
OK - total noobie here.
Bought my first tablet - Acer A500 off craigslist for $100. Worked like a charm for six months then went to brick status - locked on Acer Screen. BOO! HOO!
I've read and done the factory reset with the paper clip, and the Power Volume+, with no results.
Then I said to myself - "Hey, there's got to be a EASY way to do this. Probably download some software to my PC, plug in via USB, probably some sequence to boot from PC, and I'll be done!"
WRONG!
Apparently, I've got to know my CPUID - is that an acronym for Confused Person Undoubtably and IDiot - cause I got NO CLUE on that one.
And I've got to get an EUU - European United Union?
And I've got to get a Russian DeCrypter?
And.... well, you get the idea.
So, I've decided to exercise my capitalistic privileges!
IF SOMEONE THINKS THEY CAN FIX THIS DANG THING - I'LL PAY YOU!
I figure it'll take me days to figure out what I need to do and download and do it. Or, I can just ship this to someone who wants to make a few bucks and we'll both be happy.
So, if someone wants to help me do some additional diagnostics and make a buck or two in the process - email me at my public site of
rainbow 4 jd @excite. com (obviously no spaces there in the actual email address).
rainbow4 said:
OK - total noobie here.
Bought my first tablet - Acer A500 off craigslist for $100. Worked like a charm for six months then went to brick status - locked on Acer Screen. BOO! HOO!
I've read and done the factory reset with the paper clip, and the Power Volume+, with no results.
Then I said to myself - "Hey, there's got to be a EASY way to do this. Probably download some software to my PC, plug in via USB, probably some sequence to boot from PC, and I'll be done!"
WRONG!
Apparently, I've got to know my CPUID - is that an acronym for Confused Person Undoubtably and IDiot - cause I got NO CLUE on that one.
And I've got to get an EUU - European United Union?
And I've got to get a Russian DeCrypter?
And.... well, you get the idea.
So, I've decided to exercise my capitalistic privileges!
IF SOMEONE THINKS THEY CAN FIX THIS DANG THING - I'LL PAY YOU!
I figure it'll take me days to figure out what I need to do and download and do it. Or, I can just ship this to someone who wants to make a few bucks and we'll both be happy.
So, if someone wants to help me do some additional diagnostics and make a buck or two in the process - email me at my public site of
rainbow 4 jd @excite. com (obviously no spaces there in the actual email address).
Click to expand...
Click to collapse
Eh, personally we like to keep things in the forums, as other people may want to chime in and offer some steps others haven't thought of.
For some info, I'll try to explain a couple of things;
1. UID number. This is a number specifically assigned to your CPU. (CUID) which allows us (with a secure bootloader key, SBK) do a low level NVFlash of bootloaders. The issue, is that the bootloader (the first thing that loads) is secure and prevents us from flashing things. Pretty much locked. Unless you have your SBK. Then we can get into what we call APX mode which allows us to bypass security (in easy english terms). And yes, we have a tool that converts UID to an SBK.
If you do not have your UID number, all is not lost. Rumor has it that after ICS, the UID sometimes is the serial number you'll find on your Ext SD cover. Now some people confirmed this, and some say no. But it's worth a shot to use that number when trying to run an EUU file. If not, you will have to install Ubuntu on your PC and use the Linux method of getting it. More later.
2. Also, an EUU which is basically nothing more than an Acer maintenance rom which you run from your PC, requires this UID number because it uses NVFlash. That's why it's important to have it.
3. A Decrypter (not Russian I can assure you ) is sometimes required to install factory roms and updates, as Acer delivers these encrypted. You shouldn't have to worry about this yet, as most of the things we have posted are already de-crypted. For reference, you will find the tool in the Themes and Apps Forum.
For starters, I would like to know which bootloader version you currently have installed. You will find this in the upper left corner when you start the tablet. Should be a series of numbers and letters. Use a magnifying glass if you can't read it... :laugh:
Followup to a bricked Acer A500 - and if anyone can repair?
Moscow Desire said:
Eh, personally we like to keep things in the forums, as other people may want to chime in and offer some steps others haven't thought of.
For some info, I'll try to explain a couple of things;
1. UID number. This is a number specifically assigned to your CPU. (CUID) which allows us (with a secure bootloader key, SBK) do a low level NVFlash of bootloaders. The issue, is that the bootloader (the first thing that loads) is secure and prevents us from flashing things. Pretty much locked. Unless you have your SBK. Then we can get into what we call APX mode which allows us to bypass security (in easy english terms). And yes, we have a tool that converts UID to an SBK.
If you do not have your UID number, all is not lost. Rumor has it that after ICS, the UID sometimes is the serial number you'll find on your Ext SD cover. Now some people confirmed this, and some say no. But it's worth a shot to use that number when trying to run an EUU file. If not, you will have to install Ubuntu on your PC and use the Linux method of getting it. More later.
2. Also, an EUU which is basically nothing more than an Acer maintenance rom which you run from your PC, requires this UID number because it uses NVFlash. That's why it's important to have it.
3. A Decrypter (not Russian I can assure you ) is sometimes required to install factory roms and updates, as Acer delivers these encrypted. You shouldn't have to worry about this yet, as most of the things we have posted are already de-crypted. For reference, you will find the tool in the Themes and Apps Forum.
For starters, I would like to know which bootloader version you currently have installed. You will find this in the upper left corner when you start the tablet. Should be a series of numbers and letters. Use a magnifying glass if you can't read it... :laugh:
Click to expand...
Click to collapse
First - thanks for the reply - it was VERY NICE OF YOU.
And just so you know - I spent $100 on ebay and bought a replacement! So, now I can totally devote myself to learning what (if anything) can be done to unbrick my old one.
1. There is no external markings on this tablet AT ALL. No stickers, no nothing.
2. When I open up the SD card slot - I do get a SNID of 13001360415
3. When I do Power Volume+ slide - I get "erasing user data" and immediately below it "erasing cache"
4. It then goes to ACER logo screen and stops.
Logic tells me that A) the motherboard (or whatever passes for a motherboard on this tablet) might be bad. It's trying to go through its boot sequence and there's a physical fault or B) the motherboard could be good, but the inherent "boot disk" software is now corrupted - its locking up - and never getting to the OS software.
Or I could be wrong.
In either case - I feel like I have insufficient knowledge to properly diagnose AND determine if this is repairable at all. And that being said, IF someone has experienced this before, gone through the trial and error, and can say.... "Hey, I've fixed twenty of these, no problems" - I will happily defer to their experience.
Anyway - based on symptoms - if you think I have a fighting chance of salvaging this - I am game!
rainbow4 said:
First - thanks for the reply - it was VERY NICE OF YOU.
And just so you know - I spent $100 on ebay and bought a replacement! So, now I can totally devote myself to learning what (if anything) can be done to unbrick my old one.
Click to expand...
Click to collapse
Thanks for the comments!
$100... wow, I hate to say what I paid for my 501 new here in Moscow But now, I use my a701.
Typically, the a50x tablets have a reputation of being "bullet-proof", although lately, seems a rash of bricked tabs. Perhaps just due to old age.
You're correct about the motherboard, more specifically the emmc memory on it, is the likely culprit due to what you've stated. Or.... it could just be a corrupted file. Who knows until we investigate a little.
For starters, lets do some simple stuff first. Following is a link to some ICS update files. There are 4 of them. I have already de-crypted them. Now, download each to a individual folder on your PC. You will see they are numbered. This is to keep them separate so you know which is which.
Now, choose one of them (really doesn't matter which one, but maybe start with the highest number first). Rename it to "update.zip" (make sure it is not "update.zip.zip" as this is a common mistake. If your PC doesn't show the .zip extension, just rename it to update)
Now, copy it to your external SD card. Power on your tablet holding Vol+ (or minus) and PWR. Continue pressing until you see text about installing the update in the upper left corner, then release. We'll see if it installs all the way. If after 15 minutes it doesn't (it may stop at about 25%), then PWR off, and rename and copy the next update file, and try that one. Might have to try all 4, so make sure your tab is fully charged.
If none of these install all the way, then life becomes a little more difficult......
Links to my server (large files 300+mb)
http://d-h.st/Zf8
http://d-h.st/2cm
http://d-h.st/gw8
http://d-h.st/KXl
the JTiind
Moscow Desire said:
If you do not have your UID number, all is not lost. Rumor has it that after ICS, the UID sometimes is the serial number you'll find on your Ext SD cover. Now some people confirmed this, and some say no. But it's worth a shot to use that number when trying to run an EUU file. If not, you will have to install Ubuntu on your PC and use the Linux method of getting it. More later.
Click to expand...
Click to collapse
Can I get in on this conversation? For three days, I've been trying to revive my brother's A500. It seems like every option I come across requires the sbk, or the cpuid. I don't have the cpuid and can't figure out how to retrieve it since the tablet appears to be stuck in apx mode. The power button is illuminated and nothing comes on the screen. Windows device manager displays Acer USB Boot-recovery driver.
I've tried using AfterOTA v1.09 to flash recovery and bootloader files, but not sure if I've chosen the correct files to flash. I found a zip file here on the forums that contained ics_boot_unlk_v6_500.bin and recovery_thor17_403.img that I've attempted to use. AfterOTA just hangs on [2/3] flashing recovery...
Not knowing this all important UID, where do I go from here? Can I hear more about this Ubuntu method? Will that help in this case?
Thank you!
holtsclaw said:
Can I get in on this conversation? For three days, I've been trying to revive my brother's A500. It seems like every option I come across requires the sbk, or the cpuid. I don't have the cpuid and can't figure out how to retrieve it since the tablet appears to be stuck in apx mode. The power button is illuminated and nothing comes on the screen. Windows device manager displays Acer USB Boot-recovery driver.
I've tried using AfterOTA v1.09 to flash recovery and bootloader files, but not sure if I've chosen the correct files to flash. I found a zip file here on the forums that contained ics_boot_unlk_v6_500.bin and recovery_thor17_403.img that I've attempted to use. AfterOTA just hangs on [2/3] flashing recovery...
Not knowing this all important UID, where do I go from here? Can I hear more about this Ubuntu method? Will that help in this case?
Thank you!
Click to expand...
Click to collapse
Yep.... UID is all important. Uses what we call "NVFlash" to install bootloader and recoveries when all else fails. You UID is specific to each tab. No 2 are alike (as far as we know). With it, we can convert it to an SBK (Secure Bootloader Key). The stuff acer don't really wanna give us. This allows the use of NVFlash via APX mode (which you have already discovered.
Here is a link to getting your UID via various methods. The ones you want to pay attention to, are the links using Ubuntu (halfway thru the guide) Note that you may have to look at links within links to get all the methods people have tried, as some change a bit of the scripts here and there, but you should be able to figure it out.
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
http://forum.xda-developers.com/showthread.php?t=1751978
also of use, is a tool called "babsector". This tries to repair/workaround physical sectors on some tabs. But you shouldn't need that yet. So read that guide and check the links in it for using Ubuntu.Never had to use it myself, so not a lot of further advice on the technical aspect.
MD
rainbow4 said:
First - thanks for the reply - it was VERY NICE OF YOU.
And just so you know - I spent $100 on ebay and bought a replacement! So, now I can totally devote myself to learning what (if anything) can be done to unbrick my old one.
1. There is no external markings on this tablet AT ALL. No stickers, no nothing.
2. When I open up the SD card slot - I do get a SNID of 13001360415
3. When I do Power Volume+ slide - I get "erasing user data" and immediately below it "erasing cache"
4. It then goes to ACER logo screen and stops.
Logic tells me that A) the motherboard (or whatever passes for a motherboard on this tablet) might be bad. It's trying to go through its boot sequence and there's a physical fault or B) the motherboard could be good, but the inherent "boot disk" software is now corrupted - its locking up - and never getting to the OS software.
Or I could be wrong.
In either case - I feel like I have insufficient knowledge to properly diagnose AND determine if this is repairable at all. And that being said, IF someone has experienced this before, gone through the trial and error, and can say.... "Hey, I've fixed twenty of these, no problems" - I will happily defer to their experience.
Anyway - based on symptoms - if you think I have a fighting chance of salvaging this - I am game!
Click to expand...
Click to collapse
OH MY GOSH - IT WORKED! YOU ARE THE HERO OF ALL MANKIND!!
It took me a bit of minor tweeking - in that I had to rename the file BEFORE copying it to the SD Card - because I was getting some copying errors.
The version that took was #3 - what I mean by that is.... it was the third one in the Windows Explorer naming sequence. I don't know what the name of it is now, because I obviously updated the name to be "update.zip"
So..... it "took" and started giving me a working Android Robot - whereas the others had given me a Dead Android with the Information icon.
I waited through the process - it loaded the operating system and prompted me to select language, country, wifi, log in with google, AND I WAS UP AND RUNNING!
I am going to post these results as a specific FIX and encourage everyone to try it who has a bricked tablet!
:victory::victory::victory::laugh::laugh::victory::victory:
This DevDB project and it's related files are by Aravind V. Nair. I'm stating this because so many people are trying to impersonate me. For example, @Balaji Sriram More info: Balaji Sriram impersonating Aravind V. Nair
Most of you are probably facing battery issues. Please check what I have to say regarding that before proceeding. So many people have reported success after fixing the battery issue. Details are available at the bottom of the post
Click to expand...
Click to collapse
If your eMMC storage controller is corrupted, no method will work. You need to replace the motherboard. I'm sorry, I can't help you with that.
Click to expand...
Click to collapse
Big thanks to @ariel.buszczak for his continuous support in every way he could!
Big thanks to @waulliano for uploading the backup.img for XT1022! Download from here
Please upvote the TWRP time issue on GitHub here: TWRP 3.0.2-0 build to 3.1.1-0 build time miscalculation on so many devices.
Click to expand...
Click to collapse
Introduction?
Yes, of course. Hi there!
I have a bricked Motorola Moto E 1st Generation XT1022 condor. I watched so many threads on various forums to try and unbrick, but unfortunately all threads just got abandoned. Hence, I have come up with a DevDB project to try and unbrick Motorola Moto E 1st Generation XT1022 condor if possible. Please note, this project is only for Motorola Moto E 1st Generation XT1022, XT1021 and XT1025 condor. Between, I also have an unbricked working Motorola Moto E 1st Generation XT1022 condor along with the bricked one for test purposes.
This XDA DevDB project is aimed at developers mainly to gather all possible ways to unbrick a hard-bricked Motorola Moto E 1st Generation XT1022 condor, but not restricted to people who want to try their luck at unbricking their Motorola Moto E. Please don't post 3-line request like "my device is bricked, please help" as you will be ignored. If you can't do the research required to provide the right details plus finding the correct files required then, this DevDB project is not for you. The programs, its associated files & threads, etc are NOT going to be being actively developed very soon (July 10th 2017) as I get busy and involved with other things. But the thread remains open for user to post more information, additional files, updates from the public, etc. It's not here for lazy people to scream fix my device, can those type of users please speak to your retailer, cell phone service shop??
I will reiterate again, THIS IS A DEVELOPMENT THREAD AND NOT A REQUEST PAGE FOR "fix my device"
Click to expand...
Click to collapse
I haven't stopped working on this. I do update this XDA DevDB and my GitHub repository for the as I get time.
Please go through this DevDB post thoroughly.
Click to expand...
Click to collapse
Rules and regulations:
Please click the 'Follow Project' button to get notifications every time I update files or make any other changes instead of asking me manually via PM or in thread replies. I won't reply to unsolicited spam messages. So, DO NOT waste your time crafting them.
Click to expand...
Click to collapse
Obey all XDA rules posted here along with CODE_OF_CONDUCT.md posted by me here.
Click to expand...
Click to collapse
Please read through this post and also go through the README.MD file on my GitHub repository for this project carefully and thoroughly. They are created for a reason. I won't reply to unsolicited spam messages, tags, quotes, replies, etc. So, DO NOT waste your time crafting.
Click to expand...
Click to collapse
Warning: I am in no way responsible for your actions. You are on your own. Please undertake all actions at your own risk.
Click to expand...
Click to collapse
Please compress all files before uploading to the cloud after removing personal data. I'm not going to check otherwise.
Click to expand...
Click to collapse
Please attach error codes and other additional information is separate files to avoid clutter. I'm NOT going to check otherwise.
Click to expand...
Click to collapse
DO NOT share anything from this thread. DO NOT mirror anything without prior permission. I have recently busted so many people who have tried to do so despite my warning and even got them banned.
How can I get in touch with you?
My personal blog (All social media profiles link are available):
About Aravind V. Nair
Click to expand...
Click to collapse
Or
Just Search Google for 'Aravind V. Nair' and you can find me.
Click to expand...
Click to collapse
Or
My website: Get to know Aravind V. Nair
Click to expand...
Click to collapse
Or
XDA: Aravind V. Nair - XDA Developers
Click to expand...
Click to collapse
Where can I find the files and instructions?
Please check here: Motorola Moto E XT1022 condor files - GitHub (Aravind V. Nair)
How do I support you?
Hit the thanks button below and the 5-star button above to show your support. Also, you can 'star' and 'watch' my GitHub repository Motorola Moto E XT1022 condor files - GitHub (Aravind V. Nair).
Follow me on social media networking sites if you wish.
Donate to me if you wish by clicking here
What is the goal of this project?
The goal of this project is to gather all possible ways to unbrick a hard bricked Motorola Moto E 1st Generation XT1022 condor. Methods 3, 5, 6, 7 and 8 are perfectly working. Your mileage will vary with other methods. Please don't give up on first try. You need to try a lot of times and test your luck.
What is the proof that this has worked?
I have attached photos to this DevDB post. Please have a look at them.
Will this work for everyone?
As long as you haven't corrupted any of your phone's hardware, you do have chances of unbricking. If the NAND adapter or related parts are not functional, don't even expect to unbrick. A lot of you have tried weird files on the internet, so chances will reduce accordingly.
Where can I find the changelog?
I frequently update and patch things in my GitHub repository as I get time. Be sure to check the changelog here.
How do I find out which bootloader I have?
Sorry, I don't think that's possible when the phone is bricked. I'm not sure though. But definitely, your bootloader version would be the version from your last working stock OS (or custom OS, only if you flashed the motoboot.img or any other equivalent bootloader image).
If fastboot works,
Code:
fastboot getvar all
Can I restore factory aka original firmware if my bootloader is locked?
Yes, you can. However attempting to downgrade to an older version of Android may fail and isn't a good idea. Even with an unlocked bootloader, downgrading cannot be guaranteed. It's also important to be aware that flashing the wrong bootloader (motoboot.img) for your model can have serious consequences. Always identify your model of Moto E and verify the files before flashing.
If you downgrade your phone, it is advised to avoid all OTA updates. These updates can result in a hard-brick (phone will not turn on) if you have a newer bootloader than the one expected. For example, most of you had the Lollipop bootloader, but have downgraded to Android KitKat and thus bricking your phones.
How to disable OTA Updates?
Without root access
Settings > Apps > [swipe left to 'All'] > MotorolaOTA (or Motorola Update Services or something similarly named) > Disable
With root access
Google Play Store has many apps that will allow you to 'freeze' the OTA Update service. Titanium Backup is a common example.
Alternatively, with a 'root access' file explorer, you can delete or rename the following files:
/system/etc/security/otacerts.zip
/system/priv-app/3c_ota/3c_ota.apk
These additional files can be removed or renamed: (If you still get an OTA Update notification)
/system/priv-app/3c_checkin/3c_checkin.apk
/system/priv-app/3c_devicemanagement/3c_devicemanagement.apk
/system/priv-app/3c_notification/3c_notification.apk
I'm a developer or programmer or want to help. Could you please give some reference links?
Yes, of course. All contributions are welcome! Code, documentation, graphics or even design suggestions are welcome; use GitHub to its fullest. Submit pull requests, contribute tutorials or other wiki content -- whatever you have to offer, it would be appreciated!
Please feel free to get in touch with me. I'll always be available even after the deadline. Refer CONTRIBUTING.md on my GitHub repository for reference material and other things.
What are the possible methods of unbricking?
Refer Unbrick methods.md on my GitHub repository.
Where can I download the firmware files?
Check my GitHub README.md file for all files for all models or alterantively Moto E Factory Firmware Images by @lost101
Moto E won't power on. Only white light LED comes up when connecting powers source. Can I charge on AC, etc.
This has nothing to do with clearing cache, recovery and other nonsense. It is just a problem of overly discharged battery when the battery voltage drops below the 3.8 V, which is the minimum voltage of LiPo aka Lithium ion Polymer battery. Unlike other phones, all Motorola devices come with LiPo batteries.
When the battery reaches less than 0%, i.e., less than 3.8 V the phone will not allow it to turn on, as it is harmful for the battery and it might burst. So for these physical security reasons, the phone's adapter chipset/regulator stops the battery from charging. I faced the same problem many times while bricking and unbricking. One thing you could try is to jumpstart the battery by providing excessive power at your own risk, or consider replacing the battery. It is advisable, to never let the battery fall below 10 %. Below 0 %, the internal resistance or rather the impedance of the battery increases to a very very high constant, thus rendering the battery in a 'cannot be charged state'. I won't by trying to fix via firmware as it is very dangerous to charge a battery in such a state. We do not want another bomb apart from the already existing Samsung Galaxy Note 7, do we? :laugh:
Please check your battery voltage using a multimeter or voltmeter and contact me with the same. Please be very careful when removing the battery as Moto E has a loose pin and is easy to break. Caution advised!! For checking using multimeter, set to DC 20 Volts and use the correct input pins. For voltmeter, just use any DC voltmeter having a range of 0-5 Volts.
If the voltage is below 3.8 V, you have to replace the battery. If it is between 3.3 - 3.5 V, you have chances of resurrecting the battery. So try using a above 2 A charger (connecting to laptop won't work as that is just 0.5 A) and leave it like that for about 5 days continuous. Below 3.3 V, please replace the battery. It's not advisable to try and jumpstart.
For the prerequisites, you need a T4 Torx screwdriver and a new Moto E battery. Please buy genuine things. You could have a look at Amazon, Flipkart, eBay, IFIXIT, Snapdeal, etc and also offline stores. Search with the model number of the battery. For XT1022, XT1021 and XT1025, it is Motorola EL40 manufactured by SONY Electronics with a typical mAh of 1980 and minimum of 1860 mAh aka 1860/1980 mAh (min/typ) and 7.1/7.5 Wh (min/typ).
PLEASE DO NOT USE AC TO CHARGE DC BATTERIES DIRECTLY.
You have a high risk of causing serious damage. You might end up killing yourself! Please do not try this. To charge in this manner, you need a bridge rectifier. Noobs, please don't even venture here or think of making it. The battery will not get charged because AC supply changes its polarity after each half cycle. In India, it changes 50 times per second, Brazil 60. Therefore, the battery will be charged in one half cycle and discharged in the next half cycle. So basically, you are damaging the battery due to frequent charging and discharging cycles. Please do not try this!! There is high risk of fire damage and explosion. Those of you who already tried this, please discard the battery immediately to a recycling firm or any other relevant organisation for your country or city. It is not advisable to keep a spoilt battery at home. Using a resistor is not a good idea either as a resistor obeys Ohm's Law which states that the current flowing through any conductor, in this case the battery, is directly proportional to the potential difference across the terminals. So you wouldn't have a steady output. A diode would be preferable. Those who have no clue about these, please do not venture here. I reiterate, I won't be held accountable for any damage caused by you to yourself or your belongings or to anything else.
I was using the Moto E and it suddenly died. What do I do?
Step 1: Open up the phone as I have mentioned earlier. (If you read whatever I have written, you should be knowing what I'm talking about.)
Step 2: Detach the battery. Be very careful not to destroy any internal parts such as the connector which is very fragile.
Step 3: Connect the official charger. (Other chargers didn't work for me always during my testing.)
Step 4: Wait for the screen to say 0% or battery not connected or even if the screen turns on, consider yourself lucky.
Step 5: Attach the battery and reassemble the phone without removing the Moto charger.
Step 6: Go to fastboot, unlock the bootloader and use my fastboot unbrick script for your OS (I have made for Linux, Windows and MacOS). Leave it on charger for a day or two after this.
Step 7: Voila!
This is caused due to undercharging, overcharging or excessive battery drain cycles. In case the phone doesn't power on after connecting battery, check that the EMF of the battery is above 2.9 V with a multimeter as mentioned before.
How to power on Moto E without charger and unbrick?
Safest way is to use the original Motorola charger. As far as I have seen, all the original Motorola chargers have the 4th pin available. For the geeks:
Pin 1: VDD (+5V)
Pin 2: D- (Data-)
Pin 3: D+ (Data+)
Pin 4: ID (ID)
Pin 5: GND (Ground)
The additional pin added to the conventional USB port is the ID pin added to the 4th electrical pin which allows to recognize the device. The technical name is micro USB - B for the one on the charger and mini USB - A for the one on the charger. You can bypass power using this concept. This too is strictly not for noobs.
Errors:
Code:
Preflash validation failed
Buy a new phone. I doubt anyone can help you now...
Code:
Not able to flash GPT / Motoboot
You are not using the right firmware. Try another firmware.
Code:
FAILED (blank-flash: sdl-transfer-image: sdl-hello: invalid HDLC frame)
or
Code:
FAILED (blank-flash: sdl-transfer-image: sdl-hello: error sending packet)
Your bootloader files do not match your bootloader version, use another bootloader.
Code:
Stuck on Opening device: . COM ??
or
Code:
Greeting device for command (Or any other) mode
or
Code:
Switch To FireHose (Or any other) mode
Press and hold power button until detection or until flashing begins.
I'm fed up!! Nothing is working for me!!
Calm down!! Replace your motherboard and/or battery and/or screen, whichever is spoilt. That's the easiest option. But it wouldn't be a good choice to buy new parts now. The phone is quite old. I suggest you buy a new phone instead. That would be a wiser idea. Methods 3, 5, 6, 7 and 8 are perfectly working. Your mileage will vary with other methods. Please don't give up on first try. You need to try a lot of times and test your luck. You are the one who brought your device to this condition. Only you can help yourself.
Does this project have a website?
Yes, a very basic one though. Check here.
Please go through this XDA DevDB main post and my GitHub repository for the same before commenting, messaging or posting.
XDA:DevDB Information
Unbrick hard bricked Motorola Moto E, Tool/Utility for the Moto E
Contributors
aravindvnair99, Thanks for all support!
Source Code: https://github.com/aravindvnair99/Motorola-Moto-E-XT1022-condor-unbrick
Version Information
Status: Stable
Current Stable Version: 309
Stable Release Date: 2018-05-29
Current Beta Version: 309
Beta Release Date: 2018-05-29
Created 2017-05-01
Last Updated 2018-05-29
Reserved
By @kyocell
I am currently getting some SAHARA Port errors I'm trying to install and uninstall drivers and trying.
Will keep updating if it works.
Edit- Fixed SAHARA Port errors but now experiencing different ones.
Edit2- Now experiencing some kind of SAHARA Protocol errors.
Fixed errors guide- If you get any kind of SAHARA Port error then follow this easy guide.
1) First off, delete all the preinstalled drivers
2) disable your machine's driver signature enforcement by doing this -
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
3) After you enter your machine with driver enforcement disabled, Now go to the folder "Drivers" and extract the Qualcomm drivers and install them.
4) Here comes the tricky part. Now open your "moto e unbrick folder". Provided by @aravindvnair99 at his GitHub page and open the folders patch0.xml , prog_emmc_firehose_8x10 , rawprogram0.xml and copy all the contents into a new folder called "unbrick".
5) Now install the QPST tool. (installer in the unbrick folder provided by @aravindvnair99 at his GitHub.
6) Once you have this installed, go to the location of the installation of Qualcomm--> QPST --> Bin --> and copy this folder we made called "unbrick" into "bin" folder.
7) Now run Qfil.exe file which is located in the "bin" folder as well.
8) Now, plug your moto e with USB to your pc. If any drivers start installing, let them install.
9) Now select the port. Then browse the path for Programmer. For this click browse --> locate to the "unbrick" folder and select on "All files (*.*)" located at the bottom right of the browse window (dropdown).
10) Now select the file "programmer_8x10.mbn" and click ok.
11) Now click on load XML and locate to the "unbrick" folder and select the "rawprogram0.xml" file then another browse box will open and this time select "patch0.xml" and click ok.
12) You are now all set!
13) Finally click the "download" box and watch your phone come alive!
Hope this guide was easy. @aravindvnair99 you can use these instructions for method 1 as they are more elaborated & also it will save up your time so that you wont have to type so much data instructions. Its all up to you! i only wanna help all those people with this 'Dead moto e' problem and show them that there is still hope!
Much love! Hope it helped!
<3
P.S @aravindvnair99 please correct me if i have told anything wrong anywhere.
Edit - The following error still persists for me
20:39:51: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
20:39:51: ERROR: function: sahara_main:854 Sahara protocol error
20:39:51: ERROR: function: main:265 Uploading Image using Sahara protocol failed
EDIT - FIX FOR THE SAHARA ERROR
1) right as you plug in your phone to your pc and hear that sound (when device is plugged in to pc) right away click the download button without any waste of time.
Reserved
Happy to see this thread. I also have a bricked Moto E XT1022. After searching in many websites , i found that only flashing emmc using EasyJtag box has sloved the problem. Can you do anything with that flash file which flash the bootloader.
arputhatonyking said:
Happy to see this thread. I also have a bricked Moto E XT1022. After searching in many websites , i found that only flashing emmc using EasyJtag box has sloved the problem. Can you do anything with that flash file which flash the bootloader.
Click to expand...
Click to collapse
@arputhatonyking Thanks for the positive response. Sorry to hear that you too have a bricked condor. Yes, for hard bricked only JTag seems to work now. I don't see any other methods. For soft bricked, it is easy to recover. I am trying to find a solution (if possible) using blankflash or any such similar flashing procedures.
Stay tuned as you might be of help to us.
aravindvnair99 said:
@arputhatonyking Thanks for the positive response. Sorry to hear that you too have a bricked condor. Yes, for hard bricked only JTag seems to work now. I don't see any other methods. For soft bricked, it is easy to recover. Me and @Balaji Sriram are trying to find a solution (if possible) using blankflash or any such similar flashing procedures.
Stay tuned as you might be of help to us.
Click to expand...
Click to collapse
Hope to get a successful one..
i flash emmc backuped from eazy jtag with old riff box 1 but, not enter to fastboot. need read from worked phone and try flash to dead one. i look it to ebay but not find with low price phone/ if find and buy one, i will try read it and post here. i have hard bricked XT1021. it flashed customer from XT1022 firmware, now it dead.
VIPER_GE said:
i flash emmc backuped from eazy jtag with old riff box 1 but, not enter to fastboot. need read from worked phone and try flash to dead one. i look it to ebay but not find with low price phone/ if find and buy one, i will try read it and post here. i have hard bricked XT1021. it flashed customer from XT1022 firmware, now it dead.
Click to expand...
Click to collapse
I didn't quite understand what you were trying to say. As far as I understood:
You should have never flashed wrong firmware even though the only difference is the modem files between XT1022 and XT1021. Sure, will wait for your reply. Thanks for your time @VIPER_GE :good:
has XT1021 flashed as XT1022, now it dead. flashed with customer. i try restore with emmc isp flashing with riff box but not work. need try with Z3X easy jtag, not have this one
VIPER_GE said:
has XT1021 flashed as XT1022, now it dead. flashed with customer. i try restore with emmc isp flashing with riff box but not work. need try with Z3X easy jtag, not have this one
Click to expand...
Click to collapse
Oh, okay. Now I understand. Thanks a lot for the clarification @VIPER_GE !
Actually, Riff Box is mainly for selected Samsung devices. Apart from those, only for the ancient (first few) Motorola and HTC devices. Z3X I heard works for recent devices. I am not sure though. Give it a try. There was another JTag thing. I don't remember the name now. It works for all devices having Qualcomm chipset. Let me see if I can find or remember it. I'll send you the link. Between, are you a technician or something? Or just another curious one like us?
just another curious one like us
Anyone know how to generate BlankFlash Files
Can anyone just give the method to flash in bootloader
And is the file listed in the thread is enough or need some more things to unbrick
https://www.youtube.com/watch?v=Qf7kG3qnyx0 https://www.youtube.com/watch?v=_KRFxtz4h24
Do you guys have jtag ?
i have only FIFF Box 1,
We need RawPatch And Programmer Files for QFIL Flash.
mannu233 said:
Can anyone just give the method to flash in bootloader
And is the file listed in the thread is enough or need some more things to unbrick
Click to expand...
Click to collapse
@mannu233 Some more things are required. You can try though with whatever is uploaded. I'm constantly updating the files. I'm working on this day and night. Waiting for @Balaji Sriram to join me soon.
If I replace the "prom_emmc" file in the "blankflash" folder, can I test if flashing works? Thank you!
aravindvnair99 said:
@mannu233 Some more things are required. You can try though with whatever is uploaded. I'm constantly updating the files. I'm working on this day and night. Waiting for @Balaji Sriram to join me soon.
Click to expand...
Click to collapse
cAN you please do me a favour that i wanted to know how to use these files i haven't got any clue how to use them
---------- Post added at 05:19 PM ---------- Previous post was at 05:05 PM ----------
Can someone list up all files whatever is founded in the thread it would be easy for those who are looking for the files
Hello folks,
I ran into a poblem with my old Samsung Galaxy Grand Prime Plus. 3 years ago I was messing up with the phone and I ran into an invalid IMEI problem. As I was a real newbie, I brought it straight to a friend of a friend of a friend who had a phone shop, and he fixed it for me.
Everything OK until last week, when I suddenly realized that probably the guy had flashed the wrong IMEI to it, mistyping 2 numbers of one of the two IMEIs.
Currently, I then have a perfectly working phone, but the IMEI is incorrect and I need to fix it.
I don't have the box anymore, but luckilly the numbers under the battery are perfectly clear and readable, although this is quite an old device.
As the shop of the guy who did the work is long gone, I started to look around for instruction on how to deal with the problem, and I followed all the possible tutorials, but apparently I'm not able to fix the issue.
I just know it can be done, as this was done to the very same phone in the past, creating the problem. I just do not happen to know how he did...
Here's what I tried so far:
1. APP: Mobileuncle Tools
Whenever I tap onto "IMEI Backup Restore (MTK)" I get an error message that says "No support".
2. APP: MTK engineering mode
I open the app, and whenever I tap onto "MTK Settings" I get an error message that says: "Cannot find EngineerMode App - Mediatek chipset is mandatory and stock ROM must be installed".
I tried both Mobileuncle Tools and MTK Engineering mode with 3 different ROMs downloaded from different sources, before and after rooting the device with Super SU, but to no avail.
3. With any xposed module
This could be a solution... but not a real one.
At least according to all the documentation I found (also here on the forum), any xposed module like "IMEI Changer", "chamaleon", "device changer", "hijack suite free" etc only mask the IMEI in front of other apps, but do not really change the IMEI of the phone.
So basically I would still have a phone with an illegal IMEI on it.
Not ideal: this is not what I am looking for.
4. IMEI Maker and IMEI Repair
I followed the tutorial I found here:
https://forum.xda-developers.com/showthread.php?t=2399037
I encounter no errors at all, and TWRP shows a clean log, nothing seems to be wrong. But after flashing the new IMEI, nothing changes: with *#06# I can still see the wrong IMEI there.
The file in data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 just remains the same, dating 2016, and does not get replaced by the new one.
I tried to replace the file manually, using ROM Toolbox Lite. At the beginning I could not delete the original MP0B_001 file, even after changin permissions to 775. It kept saying "File deleted" but the file remained there.
I then installed BusyBox Free, and it did the trick: now using ROM Toolbox Lite I definitely can delete the MP0B_001 file. The problem is that the original file keeps coming back again and again, after every reboot.
Nevermind if I place the new MP0B_001 file in the folder copying and pasting it or flashing it with TWRP, it will get overwritten by the old file with the wrong IMEI.
5. Flashing a Combination ROM
I didn't find a specific tutorial for this one, but I just tried to flash the combination ROM and see whether I could get any luck touching things in there.
No luck!
6. With SN write tool (windows software)
Here the big problem is, I can't find the BP file anywhere.
No AP_BP_database seems to contain the BP file for the MT6737T (that is the chipset of the G532F). As I am writing, I am thinking about trying to use a different BP file, from a different chipset. This will probably won't work, but after trying all of these, I mean, why not...
I also tried to look for the BP file into the folder /system/etc/mddb/ , as advised here: https://forum.hovatek.com/thread-11609.html . I looked for ir with any of the 3 different stock ROMs I tried to install. Yet again, absolutely nooooo luck here.
7. MTK Droid Root & Tools (windows software)
This won't even connect to the phone. That is, whenever I connect the phone to the PC, I get the following errors:
" --- Estructura de ROM desconocida, no se puede hacer backup ! "
That would be something like: "Unknown ROM structure, cannot perform backup"
The device gets recognized (hardware, model, build number...), so it should be a problem of drivers, cable or USB port. Also because I used the same setup to install all the stock ROM, TWRP, Super SU etc...
---------------------------
And here I am. After one week of try and fail, getting tired of all this!
I'm surprised on how persistent that wrong IMEI is, as I can't get rid of it in any way.
Do you have ANY kind of idea of what can I do?
As the points 1, 2, 4, 6 and 7 are specifically advised for MTK chipset. I'm starting to doubt that this is an MTK chipset altogether!!!
Thanks for your help
Peter
Update:
I tried with NCK Dongle AndroidMTK 2.5.6.2
Still no success (phone apparently not supported).
Hello everyone, I need help. As English is not my native language, please forgive me for grammar and spelling errors if there is any. I am a Chinese student and our school uses a modded version of the Lenovo TB-X605M for teaching, which has restricted recovery (unable to mount any storage device) , no recovery mode (you have to scan a QR code provided by the service provider to enter) and no developer options (which means I cannot use ADB).
Now I’d like to use it for more purposes, so I decided to flash it through EDL mode (9008).
I read from online that this tablet uses the programmer file “prog_emmc_firehose_8953_ddr.mbn”, but I can’t find this file, and I also can’t find ROM for fastboot flashing (where I can extract the file).
Does anybody have the programmer file or the ROM for fastboot flashing? In addition, will it be OK to use programmer files for the same SoC but designed for other OEMs? I need your help. Please comment below. Thank you very much.
Did you try all these? https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/msm8953
You might have a chance.
In any case, you need to start trying an EDL client (before you find a loader) to get the HWID and Hash.
Renate said:
Did you try all these? https://github.com/bkerler/Loaders/tree/main/qualcomm/factory/msm8953
You might have a chance.
In any case, you need to start trying an EDL client (before you find a loader) to get the HWID and Hash.
Click to expand...
Click to collapse
Thank you for replying.
No. I'd like to try it later as I don't want to risk too much.
For EDL Clients , will "QPST Tool" be OK? And does HWID and Hash do? I never read about them on Chinese Android forums. Anyway, I am going to check out if I can connect to it and try to find them in QPST Tool and write them down.
I've never mixed it up with any of those tools.
I keep it simple, just a bare EDL client.
With them it's not likely you can click a button and accidentally flash all the partitions on your device.
Finding a loader will be the toughest part. You should start now instead of waiting for something to flash.
Just querying for HWID/Hash has zero risk.
Trying out random Firehose loaders has a very small risk.
Renate said:
I've never mixed it up with any of those tools.
I keep it simple, just a bare EDL client.
With them it's not likely you can click a button and accidentally flash all the partitions on your device.
Finding a loader will be the toughest part. You should start now instead of waiting for something to flash.
Just querying for HWID/Hash has zero risk.
Trying out random Firehose loaders has a very small risk.
Click to expand...
Click to collapse
Thank you for your advice.
As I have said before, I have never heard of what is HWID and Hash and I don't know what they do. What I am going to do is to wipe userdata , and I have no idea whether I need to know about HWID and Hash to do this. I am going to try some loaders I found on a Chinese forum. I will start trying from some other Firehose files for the same SoC.
Moreover, I viewed the link in your first reply and found all these files are with the extension name .bin , instead of .mbn . Are they loaders? If they are , how should I use them?
I am just an ordinary student and I am not familiar with command lines. I seldom use it unless I can't do it with GUI.
The HWID tells your processor, the Hash tells you who signed it.
To get a loader to work the two must be compatible.
I am not responsible for the content on Chinese forums.