Hi there
Thanks to all other guys here who have made helpful development to tame this beautiful =)
To crossflash models other than LG G8 please read post 3.
Before asking any question please read the troubleshooting section at the bottom of the page.
If you still need some specific help I would appreciate if you bring it up just in the thread instead of sending direct messages.
LG has made things difficult in flashing custom and even stock roms by this new OPID thing! It prevents us from crossflashing but we have been able to use TWRP and change the system and some other partitions to have a different rom. We had to make some changes into OP partition using HxD editor.
But now, through this tutorial, we're able to flash any rom without the need to change OPID in OP partition. Also, there is no need to root or unlock boot-loader.
I was successful to do this on some G8 (LMG820UM) but I AM NOT RESPONSIBLE FOR ANY HARM TO YOUR PHONE!
By continuing to read the following instructions you are actually accepting the risk.
IMPORTANT!
first, MAKE A FULL BACKUP OF ALL PARTITIONS; and I mean it!!!
at least, for your sake, make a backup of "modemst1, modemst2, fsg, fsc, ftm" partitions, for emergency.
Requirements
QPST and Qualcomm USB Driver (get)
LGE SM8150 Firehose (get)
LGUP 1.16.0.3 (get)
LGUP_Common.dll (get)
UI_Config.lgl (get)
LG Mobile Driver 4.4.2 (get)
Preparation
1. Install QPST and Qualcomm USB Driver.
2. Install LGUP.
3. Find the folder named "model" in the installation directory of LGUP, then Create a folder named "common" in the "model" folder.
4. Move "LGUP_Common.dll" and "UI_Config.lgl" into "common" folder. Change the attribute of "UI_Config.lgl" to read only.
5. Install LG Mobile Driver 4.4.2.
Steps
A)
1. Open QFIL.
2. Change "Storage Type" to UFS.
3. Select "Flat Build".
4. Browse for "LGE SM8150 Firehose" and pick it.
5. Now, connect the phone to PC and boot into EDL mode.
6. Open "Select Port" and select the phone, press OK.
7. In "Tools" open the "Partition Manager".
B)
!!!BE CAREFUL TO DO EXACTLY AS THE INSTRUCTIONS SAY OR YOU WILL BRICK THE PHONE!!!
1. Make a backup of and erase these 7 partitions: FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A, OP_B.
1.1. You have to left-click on a partition then right-click on it and select "Manage Partition Data".
1.2. In the pop-up window, you have 4 choices: I. Erase (to erase data on the partition), II. Read Data (to dump or back up the partition), III. Load Image (to restore the partition), IV. Close (to close the window).
1.3. First dump/back up the partition by choosing "Read Data" then Erase it.
2. Close the "Partition Manager" window.
3. Wait for 5 seconds then press Vol- and Power until it restarts.
3.1. Immediately after rebooting, Release the Vol- and Power buttons and press Vol+ to get into Download Mode.
Note: Do not let the phone to begin to boot! If it begins to boot, it may regenerate the SID and FTM partitions data and so you need to redo the whole step B.
C)
1. Open LGUP.
2. Pick your favorite KDZ.
3. Select "PARTITION DL".
4. Press Start. And a pop-up window will appear. In this window you can select which partitions to be flashed.
5. Here, uncheck these partitions: SID_A and SID_B. It will make it able to bypass the OPID Mismatched Error.
6. If you are in Sprint or other platforms you will get the message whether to change the model or not. Of course you know what to do =)
after completing the process it will boot up in some minutes and before starting the customization it will do one restart. just be patient.
ERRORS, QUESTIONS, TROUBLESHOOTING
1. Can I crossflash V50, V60, G8X or other LG devices using this method?
I did it on V50. Maybe it'll work on your devices maybe won't. There's one way to find out; make backup and give it a try.
2. SN is gone, zero, etc.
Restore your original FTM.
3. I can't get into recovery.
Restore the original FTM.
4. I got NT-Code error.
It's been discussed many times in the thread and some solutions have been presented (such as this one, thanks to @animo214 and this, thanks to @kt-Froggy as well as this one, thanks to @StvOchi ). However, you can ignore it if the phone got network.
Note: You need to disable verity on the phone in advance otherwise changes in cust_path_mapping.cfg won't be saved.
5. IMEI is lost, zero, null etc.
Restore LUN5 partitions. If you have no backup it should be repaired using Octopus box. Go to 16.
6. I got "permanently locked" error.
This is because of IMPL lock and you have to restore LUN5 partitions. In case of having no backup you should use Octopus box.
7. All partitions are deleted accidentally.
Follow this instructions.
8. I need to get into PDM mode.
Unzip and restore the attached PDM to FTM partition. Remember, you need to restore your FTM to get into OS.
9. Can I use another phone's LUN5 backup?
NO.
10. Can I use another phone's FTM backup?
Yes. All partitions can be restored from another phone's backup except LUN5 partitions.
11. My phone is stuck in boot-loop.
Restore the original FTM and if it doesn't help redo the whole crossflash process and use a different KDZ this time.
12. Which KDZ is the best (for any matter of use)?
I do not know.
13. Can I crossflash from any source variant to Korean variant or vice versa?
Yes it is possible but you may get error on opening stock camera application because of hardware differences. There are some methods to solve the issue which you can search and find them.
14. Can I downgrade using this method?
Yes.
15. I erased partitions (ftm, op_a, op_b, modem_a, modem_b, sid_a, sid_b) but it still does not let me to crossflash.
Redo the whole process and this time make backup of and erase these partitions too, on both sides A and B: vendor, product, system, boot and userdata. Do not make backup of userdata partition.
16. How can I write IMEI?
A) Dump modem_a and create a copy of it. Then open it in UltraISO and remove IMEIPROT files from image folder. Save and restore it in place of modem_a and modem_b partitions.
B) Make backup of FTM and then flash or restore the PDM file (attached) into your ftm partition. Restart the phone; you'll get into PDM mode.
C) Open Tutty (attached). Select "Serial" in protocol and the proper port of your phone's modem driver. Click open. To test if you have selected the proper port number type "at" and hit enter it should respond"ok". Type the code at%imei=# (replace # with your IMEI) and hit enter. It doesn't matter you get "error" or "ok" after that, just check if IMEI is written via this code at%imei=?. If IMEI is written so you'll have the right MEID and ESN too.
D) Restore the original ftm and modem_a in place of modem_a and modem_b. Restart the phone.
I've already tested this method on V30, V50 and G8. Remember, if the phone has IMPL lock it'll throw "perm. locked" error even if you have written the IMEI.
17. I have lost GPT files of my LG G8, G8X, G8S, V50, etc. and Qfil partition manager does not show anything in the list.
You need to flash GPT files to your device with fh_loader (see this, part C). For that matter use KDZ_Tools to Extract DZ from a KDZ of your device. Then extract the DZ using -c at the end of extracting command. For example: unkdz -f FILE_NAME.kdz -c. It will extract all files besides all GPTs.
18. Which are the LUN5 partitions?
SM8150 has 7 physical partitions known as LUNs which are numbered from 0 to 6. Each LUN is split into several partitions. In Qfil Partition Manager you can see all partitions except those of LUN3 and LUN6 which are hidden. The number of LUNs are shown under the first column named LUN. Therefore, all partitions in front of number 5 are LUN5 partitions.
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
LG K31 Crossflashing:
To crossflash LG K31 go to this guide. Thanks to @Wish39.
LG Stylo 6 Crossflashing:
To crossflash LG Stylo 6 using LG K71 Android 12 firmware see this. Thanks to @Wish39.
LG V50 Crossflashing:
I had two LG V50 (LMV450) to which I flashed Korean Andorid 12 using the method mentioned in the first post. I cannot guarantee that it will work on every V50. After corssflashing I found out that one of them had the problem of draining battery due to not getting into deep sleep mode. To overcome the issue, I reflashed it via "Chip Erase" this time, and then again reflashed it but in the same way mentioned for crossflashing in the first post. Of course, I had created backup and at the end I restored LUN5 partitions.
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
great, thank you
netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
You didnt follow preparation correctly I guess?
netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
What OPID does it get assigned once you boot the device? OPEN_CA?
AsItLies said:
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
Click to expand...
Click to collapse
Like the a11 korean one?
cloud1250000 said:
You didnt follow preparation correctly I guess?
Click to expand...
Click to collapse
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
i got the same problem, just 3 options
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
AsItLies said:
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
How to make it?srry i cant understand
alright, G8x Sprint succesfully crossflashed to OPEN CA
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
Sebastian Thiago said:
i got the same problem, just 3 options
Click to expand...
Click to collapse
Azs5165 said:
How to make it?srry i cant understand
Click to expand...
Click to collapse
Follow preparation.
cloud1250000 said:
What OPID does it get assigned once you boot the device? OPEN_CA?
Click to expand...
Click to collapse
AsItLies said:
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Azs5165 said:
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Click to expand...
Click to collapse
Follow the steps in part C.
netmsm said:
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Click to expand...
Click to collapse
curious how the sprint v50 will react to this.. I`ll try this guide when korean A11 gets release.. I'll let you know..
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
cloud1250000 said:
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
Click to expand...
Click to collapse
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
netmsm said:
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
Click to expand...
Click to collapse
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
cloud1250000 said:
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
Click to expand...
Click to collapse
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
netmsm said:
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
Click to expand...
Click to collapse
can you check which mcfg is used? (field test > mcfg status)
Related
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
https://www.dropbox.com/s/9pzf18wxtj7i40l/IMEI MAKER.zip?dl=0
& IMEI REPAIR.zip
SCREENSHOT
https://www.dropbox.com/s/4p2rwoi5oxpth15/IMEI REPAIR.zip?dl=0
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
https://www.dropbox.com/s/o0vs89lob4yf4pv/vlcsnap-2015-01-03-22h23m53s216.png?dl=0
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
https://www.dropbox.com/s/lbdzp9ko0t9yons/vlcsnap-2015-01-03-22h24m10s140.png?dl=0
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
https://www.dropbox.com/s/j0uss286iv94red/vlcsnap-2015-01-03-22h24m48s31.png?dl=0
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
http://www.dropbox.com/s/femtg309chk147v/vlcsnap-2015-01-03-22h25m03s169.png?dl=0
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
https://www.dropbox.com/s/y1ign53lmqrwubs/vlcsnap-2015-01-03-22h26m03s7.png?dl=0
https://www.dropbox.com/s/bsbd0s1jhjt4eww/vlcsnap-2015-01-03-22h26m07s44.png?dl=0
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
http://youtu.be/8DT-32tPbMY
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
didnt help..it didnt work
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
What You Did
How it didn't helped
Can you say something about it?
-Adarsh- said:
didnt help..it didnt work
Click to expand...
Click to collapse
Here We Are Taking About An Error Which Occurs Mainly After flashing stock Rom On Android One Devices And Yes We Cannot make phone calls in this situation too, So here a Guide to fix it
my imei was also gone that's why this guide
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
Got an error:
set_perm: some changes failed
E:Error in IMEI Repair.zip
(Status 7)
Installation Aborted
the_prodigal_coder said:
Wait wait wait... The IMEI is gone?? how can the IMEI be gone? it is how the telecom directorate (Govt.) monitors each phone... thats the reason a couple of years ago all cellular devices without an IMEI (chinese imports mainly) stopped working (they could no longer make calls, but it could be used as a media player).
Click to expand...
Click to collapse
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Help Needed !! IMEI Fix for Android One not working for me...
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Great Guide! Liked it..Step by Step guide!
But i dont understand why people flash so much..where there is Official Lollipop & CM12 Available for us! Flash Freaking People! :/
You Should Tick All W-R-T All The 9 Then Only It Will Work & Dont Forget To Reboot
SpiceAndroidOne said:
I was using CM11 sprout earlier and tried moving back to Stock. I lost my IMEI during this time. I have moved to stock kitkat by doing scatter loading of stock firmware. I have rooted my Android one with CWM recovery. I have used the above tools and generated the MTB_001 and created a zip and installed it with recovery. But, still i have my IMEI as invalid. I even tried replacing the MTB_001 file manually using ES_File explorer and giving permissions 777. Still no luck.
Can someone help me out on how to load proper IMEI as am completely blocked :crying::crying::crying::crying:
Thanks in Advance.
Click to expand...
Click to collapse
Installation aborted in canvas A1.
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
aryan9090 said:
When i m flashing the zip file it says installation aborted in canvas A1.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try to copy paste the IMEI file you just made manually to the directory which is in the main post. It works on my Sparkle V everytime(the copy-paste method).
Does not work for me... please help.....
Sagar Kapasi said:
Note :- THESE GUIDE IS EXCLUSIVELY FOR ANDROID ONE DEVICE's. & Of course A Rooted Android Device To Flash zip
& EVERY TIME YOU FLASH A ROM ie: Format /System Then IMEI WILL BE GONE SO i MADE FLASHABLE ZIP TO Flash everytime you loose your IMEI [ its better to flash a zip rather than going to "\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001" & Fixing Permissions Manually
You Can Use It Too, On Your Device If Your Partition Is Like This
"\data\nvram\md\NVRAM\NVD_IMEI\MP0B_001"
Here "MP0B_001" Is The IMEI File And Its Corrupt [GENERALLY AFTER FLASHING STOCK ROM]
Then Follow This Guide To Rectify That Problem.
LETS BEGIN
First Download These Files
IMEI MAKER.zip
SCREENSHOT
& IMEI REPAIR.zip
SCREENSHOT
So After Downloading The Above Files
Extract IMEI MAKER.ZIP
SCREENSHOT
Open IMEI MAKER FOLDER , HOLD "SHIFT & RIGHT CLICK" , Click On "Open Command Window Here"
SCREENSHOT
Now In Command prompt (CMD)
-Enter the following text:
imei.exe <15digit_IMEI_1> <15digit_IMEI_2>
(eg: imei.exe 123456789111111 123456789111111)
Then Press ENTER
SCREENSHOT
NOW YOU WILL SEE A FILE CALLED "MP0B_001_NEW"
Now Rename & Remove "_NEW" From It .
SCREENSHOT
NOW OPEN IMEI REPAIR.ZIP Using Winrar [Software For Pc] [ recommended ]
Inside That Archive Navigate To
data/nvram/md/NVRAM/NVD_IMEI
& DRAG-&-DROP The MP0B_001 File There, Which We Just Created [using IMEI Repair]
Now It Should Look Like This
"/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001"
SCREENSHOTS
Now Copy The Zip To Your SD CARD [REMEMBER NOT TO PUT IT DEEP INSIDE]
& FLASH IT USING ANY RECOVERY BUT CWM RECOVERY IS RECOMMENDED
& REMEMBER THIS TUTORIAL IS ONLY FOR ANDROID ONE DEVICES AND SIMILAR DEVICES HAVING PARTITION LIKE THIS
/data/nvram/md/NVRAM/NVD_IMEI/MP0B_001
I Uploaded A Video On Youtube For This,
Its only [2:19] Minutes So People Confused Can Watch This Video
Please Like This Video & Suscribe To My Channel
Share This Video
& Thnx For Watching [If Watched] LOL
DONT PRESS THNX IF I HELPED YOU :laugh:
Click to expand...
Click to collapse
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
deepak21 said:
I followed complete steps and it got installed successfully but the IMEI is still 0 !! Does this even works on Nexus 5? Please help.
Click to expand...
Click to collapse
did you replace the file and rename it (just asking).
Saurabh K said:
did you replace the file and rename it (just asking).
Click to expand...
Click to collapse
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
deepak21 said:
Yes, I did... I followed every step very carefully and there were no error message at all.. everything was successful.
Click to expand...
Click to collapse
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Saurabh K said:
Is your IMEI back ???? If not.......
try to flash the nvram.img using:
fastboot flash nvram nvram.img
I think that nvram partition may have some problem, just give it a try..and reply
Click to expand...
Click to collapse
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
I have the stock KITKAT 4.4.4 nvram image, but I dont know will it work. I will try to extract the image from stock 5.1 and reply soon...
---------- Post added at 09:09 AM ---------- Previous post was at 08:56 AM ----------
deepak21 said:
So far nothing worked, will try anything to get it back. Do I need to clear the cache as well ? Will I lose my data? Just asking
---------- Post added at 08:55 AM ---------- Previous post was at 08:00 AM ----------
Also, I don't have any nv backup with me... could you please share any nvram image or let me know where can I get it?
Click to expand...
Click to collapse
sorry, but i couldn't backup the 5.1 stock nvram but i will send you nvram.img from stock kitkat ROM. Flash and redo the procedure from scratch...and tell your device model also..
First point to note is that only full formatting makes the device lose IMEI,not normal data,system,cache formatting which is required for installing custom roms.When your partition table is messed up you get lots of errors when trying to wipe or mount any partition from custom recoveries,thus leaving you with only option to format before flashing stock rom through sp flash tools.It is after this flash that nvram loses your unique IMEI number.In my case I had backed up my stock rom through cwm recovery,now to restore my IMEI, I just extract the contents of /data/nvram/.....NVD_IMEI from my backup( three files in total) and push it to my to the same directory using adb push command,and it works for me.There is no need to push three cos only one file is relevant .But this is only temporary solution,cos after every reset you will lose your IMEI. It is better to backup the nvram partiton using dd command so that it could be flashed later,which would persist through installs.
tealio said:
I accidentally restored the EFS partition from one Nexus 5 to another and ended up with an IMEI of all zeros. It can happen. I was able to repair it with Qualcomm software, but the phone still doesn't see the network. Possibly an antenna issue...
Anyway, it can definitely happen. Also, it is illegal to change your IMEI (in the US at least). I would think it's OK to repair one however. I think the OP should specify that this method should only be used to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray. Check documentation for your model.
Click to expand...
Click to collapse
please brother how did you "repair it with Qualcomm software to restore an IMEI to the numbers listed on the device. These can usually be found inside the back cover and on the SIM tray"? please can you pm me or email: [email protected] the software and guide pleeeeeeeeeeeeeeeeeeeeaaaaaaasssssssssssseeeeeee
need to fix my htc mytouch 4G and my LG vu II
Thanks
Warning: Use this at your own risk. I’m not responsible for any damages that may happen due to using this guide.
Problem:
LG L90 stuck at LG Boot Logo;
Cannot enter download mode;
Stuck at factory reset screen (factory reset processing) and cannot enter recovery;
Cannot enter fastboot mode;
Cannot enter qhsusb mode, or Qualcomm 9008 mode;
Attention: All the unbricking process is made WITHOUT the battery in the phone.
If your device is recognized in device manager as qhsusb_bulk or Qualcomm HS-USB QDloader 9008 jump to part 2.
Part 1 – Put the phone in qhsusb mode:
1.1 Disassembly the phone: Vídeo
1.2 Find the Test Point;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Compatible whith the folloing models: D400h, D400hn, D405, D405h, D405n, D405tr, D410, D410h, D410hn, D415, D415rd)
1.3 Connect the usb cable to the device (don’t connect it to pc yet);
1.4 Prepare the Test Point wires;
(I personally use an usb extension)
1.5 Short the phone resistor;
1.6 Connect the usb cable to pc;
1.7 Wait until Windows to recognize the device;
1.8 Disconnect the Test Point;
Now you should have the phone in qhsusb mode (Device Manager shows “QHSUSB_BULK” or “Qualcomm HS-USB QDloader 9008”).
If the phone doesn’t get recognized repeat this steps again.
If you see “Qualcomm HS-USB QDloader 9008” in Device Manager jump to the part 2;
If you see “QHSUSB_BULK” in Device Manager follow the next steps:
1.1.1 Download L90_Drivers.zip; (https://3r0xub.s.cld.pt)
1.1.2 Install the DriverL90;
1.1.3 If Windows can’t install it properly, restart the pc and press F8 repeatedly, a boot menu will appear, select "Disable Driver Signature Enforcement". Then you need to repeat everything from the beginning (Step 1.1);
1.1.4 Even if you can’t install it properly, try to install the AlternativeDriver. Then you need to repeat the whole process from the beginning (Step 1.1);
Part 2 – Restore Phone files:
2.1 Unzip L90_Hardbrick.zip; (https://ntqyw2.s.cld.pt)
2.2 Start boarddiag (b2b.exe);
2.3 Choose “W7 G2MDS (MSM8226)” Chipset;
2.4 Choose Port according to the port you see in the Device Manager;
2.5 Select your “Target Dir”;
2.6 Check “AP check”;
2.7 Check “EMMC”;
2.8 Press “START” button;
2.9 After some time you should see “PASS” in AP and EMMC. Then you just need to check “RESTORE BOOT IMG” and flash the files in this order:
1- aboot;
2- BackupGPT;
3- boot;
4- laf;
5- PrimaryGPT;
6- recovery;
7- rpm;
8- tz;
9- sbl1;
After flashing all the files remove the usb cable, put the phone back together, and turn it on. Now you should have the phone working again.
If you get "device was not found in dload trying flash programmer" error, go to Device Manager, expand the COM ports section, right click on the QDloader 9008 device, select Update Driver Software, follow the steps and point to the DriverL90. Reboot your PC and try the steps again. (Thanks @krusli)
If the phone hangs on LG Boot Logo, do a factory reset.
Factory Reset
1. Turn off the device;
2. Press and hold Volume Down key + Power Key;
3. Release Power key when LG logo appear;
4. Press and hold Power key again;
5. Release all keys when Factory Data Reset menu appears;
After that, you have to offline flash a stock KDZ for your L90 variant
Sources:
4pda (http://4pda.ru/forum/lofiversion/index.php?t575959-4560.html)
Credits to @TreQUS
This is probably the last resort for those that cannot get into any mode or get their phone recognized in PC.
Too bad a complete disassembly is necessary since the test points are in the front of the motherboard.
Hi, help me pls
Hi, i am beginner and i don't know how i can connect 'this point' to GND in first picture and when i should 'disconnect' it. Pls help coz i reallly need it
Anyway thanks for this guide it's my problem coz when i upgrade kitkat 4.4.2 to lollipop on lg l90 it's stop in 2/2 steps (7% and 'blue screen' with some bad parts) and i can't go to recovery,download,s/w mode
justM4gic said:
Hi, i am beginner and i don't know how i can connect 'this point' to GND in first picture and when i should 'disconnect' it. Pls help coz i reallly need it
Anyway thanks for this guide it's my problem coz when i upgrade kitkat 4.4.2 to lollipop on lg l90 it's stop in 2/2 steps (7% and 'blue screen' with some bad parts) and i can't go to recovery,download,s/w mode
Click to expand...
Click to collapse
For me, the easiest way to connect 'this point' to GND is as I show in the third picture, you can also get a piece of wire and connect the GND to the resistor, something like this:
Atention, be carefull to not connect the wire anywhere else than those two points.
To know when you should disconnect the wire, just turn on your computer speakers, when you hear a sound like when you attach a flash drive, it's time to disconnect the wire.
Thanks it's work now all good i can see qualcomm, but It's not my problem coz when i start phone its still the same problem i mean when LG logo dissapear automatically running android update 2/2 part and after several seconds i have error on black screen. I think i need format but i don t know how to do it, i saw yestarday i can go into s/w mode but lg flash tool don t help too with installing new android, on computer i have 4.4.2 and lollipop for lg l90 and i just can see after installing 4.4.2 in s/w mode i have rooted device but nothing more it s still the same problem with update. I think error say something about fonts.
Edit:
I install 4.4.2 drivers in lollipop from this hardbrick.zip and that s why perhaps its not working, i install drivers from lollipop and now i don t see update but just logo and i can t get into recovery, i try install now original KDZ
Drivers i mean it s just what we see in RESTORE BOOT IMG and i changed these file to lollipop
This Works But...
This Works but now in "About Phone" shows V120b-OP1-HQ.
Formerly V20b-SCA-XXX and now the frontal camera doesn't work!
How to Fix this?
Thi_Memoria said:
This Works but now in "About Phone" shows V120b-OP1-HQ.
Formerly V20b-SCA-XXX and now the frontal camera doesn't work!
How to Fix this?
Click to expand...
Click to collapse
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Tanks
F. Gacrux said:
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Click to expand...
Click to collapse
Ok, I have the KDZ my unpacked device. and it contains these files; aboot abootb BackupGPT boot cust factory laf modem persist PrimaryGPT rct recovery rpm rpmb SBL1 sbl1b sDI system tz TZB all accompanied with a numbering system and divided 17 part example: system_933888 system_1197064 system_1201176 tz_150528 tzb_157696 etc ... What should I do?
Whats your variant and what kdz you are trying to flash (kk or ll)? If your bootloader is unlocked and you have TWRP installed, I can arrange the flashable zip for you, all you'll have to do it's to drag and drop the files into the zip.
The multiple system binaries can be merged in the LG Firmware Extract, there is a button to merge all in a single img file, this one can also be used to flash your system partition.
Tanks again
F. Gacrux said:
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Click to expand...
Click to collapse
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
F. Gacrux said:
Whats your variant and what kdz you are trying to flash (kk or ll)? If your bootloader is unlocked and you have TWRP installed, I can arrange the flashable zip for you, all you'll have to do it's to drag and drop the files into the zip.
The multiple system binaries can be merged in the LG Firmware Extract, there is a button to merge all in a single img file, this one can also be used to flash your system partition.
Click to expand...
Click to collapse
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Thi_Memoria said:
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Click to expand...
Click to collapse
Hi @Thi_Memoria sorry , I've been a little busy , and so I've not been able to watch this thread as much as I wanted.
Now that you have the phone working you have to flash (offline) the KDZ suitable for your device.
Here you can see how to flash your kdz: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Thi_Memoria said:
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Click to expand...
Click to collapse
Mine is also the brazilian variant D410hn.
The files you flashed to get access to download mode are from the Asian CIS D410 (dual-SIM without NFC).
I unlocked the actual D410hn bootloader and made the proper bootstack for our version.
Make sure to be using TWRP 2.8.7.0, I didn't tested in older versions or CWM.
Bootstack - this flashes all D410hn partitions, except system: http://www.mediafire.com/download/mzc4qt5a7r79rcl/Bootstack_D410hn_Lollipop_v20b.zip
If you are willing to return to Lollipop (boot/system). This is the flashable android zip to install system without KDZ: http://www.mediafire.com/download/i2ijgbwa07o2ugf/Flashable_D410hn_Stock_Lollipop_v20b.zip
Before flashing the big lollipop (second zip), wipe data/cache/dalvik/system, since it's a huge file, It takes around 10 minutes to flash. Also, after that flash SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip then reboot and check if everything is back to normal.
Solved?!
neverdies said:
Hi @Thi_Memoria sorry , I've been a little busy , and so I've not been able to watch this thread as much as I wanted.
Now that you have the phone working you have to flash (offline) the KDZ suitable for your device.
Here you can see how to flash your kdz: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
Ok I know about Flash KDZ Updater and I found out where the problem is! he is in MISC partition and CUST partition, I edited files CUST partition with Root Explorer and now is normal and front camera working now! I edited these files: cust.prop cust_grup_mapping.cfg and cust.prop of open_sca folder. Tanks for All!:good:
The flashable bootstacks I made for D410hn also flash CUST partitions, this would have solved your problem too. In fact flashes all partitions in kdz, except boot and system that are in another different zip. With those two files you can flash everything in TWRP just like lg kdz would do if you have your partition table ok.
Help
F. Gacrux said:
The flashable bootstacks I made for D410hn also flash CUST and MISC partitions, this would have solved your problem too. In fact flashes all partitions in kdz, except boot and system that are in another different zip. With those two files you can flash everything in TWRP just like lg kdz would do if you have your partition table ok.
Click to expand...
Click to collapse
So... I flash this Bootstack_D410hn_Lollipop_v20b and my imei is now "0"
i'm downloading the big zip now
Thi_Memoria said:
So... I flash this Bootstack_D410hn_Lollipop_v20b and my imei is now "0"
i'm downloading the big zip now
Click to expand...
Click to collapse
Weird, because I flashed kk and ll bootstack multiple times between kk, ll, cm11 and cm 12.1 flashes and my imei remains the same. Try to flash system and boot of the big zip.
Edit: Sorry for the wrong info, it doesn't flash misc partition since it do not exist in kdz, I see you modified some files in misc partition, this might be the cause for your lost imei.
For reference, my cust.prop at cust root folder is
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.lge.callduration=1
cust_group_mapping.cfg
ro.lge.cupssgroup=OP1-HQ
cust.prop at open_sca folder:
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust/OPEN_SCA
# Define target operator/country/region
ro.build.target_operator=OPEN
ro.build.target_country=SCA
ro.build.target_region=SCA
# Default language
ro.product.locale.region=BR
ro.product.locale.language=pt
ro.build.default_country=BR
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
# Define SWV from CUPSS : Important for releasing Event Version
# Define swversion property when release official version
ro.lge.swversion=D41020b
ro.lge.swversion_short=V20b
ro.lge.swversion_rev=0
#ro.lge.swversion_svn=0
# Define swv_date property when the version date need to fix as the specific date
#ro.lge.swv_date=DEC-05-2013
ro.lge.opensw=SCA-XXX
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define call duration feature
ro.lge.callduration=1
# Define handwriting
ime_handwriting_apply=false
ime_trace_apply=false
ime_trace_menu=false
# Define cust language set
ro.lge.custLanguageSet=true
# Cell Broadcast scenario
persist.sys.cust.cbinfo_not_bar=true
# Enable MLT at SetupWizard
persist.sys.mlt_swupdt=1
If nothing works, try to flash the foreign d410 lollipop bootstack: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632 you flashed another variant unbrick images I believe some "unique" partitions were overwritten by this flash and your phone no longer is a d410hn anymore at software level.
Nothing...
F. Gacrux said:
Weird, because I flashed kk and ll bootstack multiple times between kk, ll, cm11 and cm 12.1 flashes and my imei remains the same. Try to flash system and boot of the big zip.
Edit: Sorry for the wrong info, it doesn't flash misc partition since it do not exist in kdz, I see you modified some files in misc partition, this might be the cause for your lost imei.
For reference, my cust.prop at cust root folder is
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.lge.callduration=1
cust_group_mapping.cfg
ro.lge.cupssgroup=OP1-HQ
cust.prop at open_sca folder:
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust/OPEN_SCA
# Define target operator/country/region
ro.build.target_operator=OPEN
ro.build.target_country=SCA
ro.build.target_region=SCA
# Default language
ro.product.locale.region=BR
ro.product.locale.language=pt
ro.build.default_country=BR
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
# Define SWV from CUPSS : Important for releasing Event Version
# Define swversion property when release official version
ro.lge.swversion=D41020b
ro.lge.swversion_short=V20b
ro.lge.swversion_rev=0
#ro.lge.swversion_svn=0
# Define swv_date property when the version date need to fix as the specific date
#ro.lge.swv_date=DEC-05-2013
ro.lge.opensw=SCA-XXX
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define call duration feature
ro.lge.callduration=1
# Define handwriting
ime_handwriting_apply=false
ime_trace_apply=false
ime_trace_menu=false
# Define cust language set
ro.lge.custLanguageSet=true
# Cell Broadcast scenario
persist.sys.cust.cbinfo_not_bar=true
# Enable MLT at SetupWizard
persist.sys.mlt_swupdt=1
If nothing works, try to flash the foreign d410 lollipop bootstack: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632 you flashed another variant unbrick images I believe some "unique" partitions were overwritten by this flash and your phone no longer is a d410hn anymore at software level.
Click to expand...
Click to collapse
Nothing work... imei=0 imeisv=0
Thi_Memoria said:
Nothing work... imei=0 imeisv=0
Click to expand...
Click to collapse
I took a look into the unbrick images you used and I could identify that they came from the D410 (dual sim no nfc) v10d kitkat. I would try this two things:
1 - Flash D410 (dual sim no nfc) kitkat bootstack and CM11 (since it's a smaller file, just to test and see if you have you imei back).
If it don't work:
2 - Return stock lg recovery and flash KDZ via LG Flash Tools in emergency mode.
You can extract the binary from the KDZ (LG Firmware Extract, extrack kdz, then dz and extract the recovery_numbers.bin), name it recovery.bin, put in the root of your microSD and flash in terminal or adb with:
dd if=/storage/external_SD/recovery.bin of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or use Jrummy ROM Installer.
Then follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I have 2 L90 with the unlocked bootloader I made, I flashed the bootstacks hundred times to go between almost all custom roms available here in xda and stock and never faced this problem, probably something changed when you got the hard brick and flashed the d410 l90 variant unbrick images so you can never change your bootstack to d410hn again, I never flashed other variant files in my two L90 and they both are ok.
If nothing more works, unfortunately, I believe the only way is to make the test point again and redo the whole process :crying:
OK
F. Gacrux said:
I took a look into the unbrick images you used and I could identify that they came from the D410 (dual sim no nfc) v10d kitkat. I would try this two things:
1 - Flash D410 (dual sim no nfc) kitkat bootstack and CM11 (since it's a smaller file, just to test and see if you have you imei back).
If it don't work:
2 - Return stock lg recovery and flash KDZ via LG Flash Tools in emergency mode.
You can extract the binary from the KDZ (LG Firmware Extract, extrack kdz, then dz and extract the recovery_numbers.bin), name it recovery.bin, put in the root of your microSD and flash in terminal or adb with:
dd if=/storage/external_SD/recovery.bin of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or use Jrummy ROM Installer.
Then follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I have 2 L90 with the unlocked bootloader I made, I flashed the bootstacks hundred times to go between almost all custom roms available here in xda and stock and never faced this problem, probably something changed when you got the hard brick and flashed the d410 l90 variant unbrick images so you can never change your bootstack to d410hn again, I never flashed other variant files in my two L90 and they both are ok.
Click to expand...
Click to collapse
OK i am download this now and i have the cm11 installed on my device!
Thi_Memoria said:
OK i am download this now and i have the cm11 installed on my device!
Click to expand...
Click to collapse
Make sure to flash kitkat recovery if you are using kitkat bootstack.
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download either of the firmware from here
Download the support files (Firehose/rawprogram0.xml/patch0.xml) here
Extract the firmware and support files to the same folder so you can easily access them like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash individual partitions you can edit your rawprogram0.xml to only include the ones you want. (patch0.xml stays the same) I have linked below 2 examples, one of them flashes just a boot.img and one that just flashes the recovery.img. But you aren't limited to those.
Recovery
Boot
Mine just in case
Awesome, thanks for this post! it will really help us in upcoming projects!
Managed to revive my phone using the B12 files but it crashes after completing system.img, I think the problem is userdata.img, my phone boots but I lost the imei and I don't know how to get it back, I'm still trying.
ZTE 971 not recognized by either QPST or QFIL
Thanks for all the detailed instructions. But my ZTE 971 is not visible to either qpst or qfil eventhough the phone shows in windows 8.1. In the Developer Options menu, I noticed Select USB Configuration, RNDIS (USB ethernet) option cannot be enabled. I wonder if this has anything to do with it. OEM unlocking, USB debbugging are already selected. Any suggestions, please? Thanks.
ps. I live in Turkey. I got this phone last year from AT&T and have unlocked the sim.
My PC is not detecting my ZTE MAVEN 3
I have installed all drives but still facing the issue. I am using it on Windows 10.
I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.
Mega says that link for the driver is invalid, but the driver is included in your QPST download anyway.
000Nick said:
I flashed the B13 (ZPST tool shows my device as B13) with the QFIL like your guide says and it says all completed successfully and finishes, but now my phone went from only being able to boot EDL + FTM + Recovery, to now booting directly to EDL mode, which obviously means this guide completely screwed up my phone... Thanks.
Click to expand...
Click to collapse
solucionaste hermano
Mod edit:
you solved brother
Click to expand...
Click to collapse
it says qhsusb_bulk when I connect the the software is not working in the mobile and it is stuck at bootloader screen but I used the press both buttons to go to edl mode method and it said in the device manager a device connected with name : qhsusb_bulk
help pls
Hello All.
I am not able to get the following files
rawprogram.xml and patch.xml for LG G8xPlease help me to get this files ASAP as i have hard bricked the mobile, all partitions deleted