Hi all,
I flashed some custom version of Android 7.0 Nougat in my phone and decided to return to Android 6 Marshmallow from a TWRP Back-up stored in my phone (but I also have these files off the phone).
It started infinty bootloop, flashed official OTA files from adb sideload sucessfully, but it stills in bootloop.
When in fastboot mode, status is : BOOTLOADER BHZ11E, Baseband M8994F, Carrier Info N/A, SECURE BOOT: enabled, DEVICE STATE: locked.
Nexus Root Toolkit , not working properly
LGUP worked, but I think the problem is EFS folder and files.
Am I correct ? Any sugestions?
these are the files that I saved off the phone:
24/08/2016 06:58 33.554.432 boot.emmc.win
24/08/2016 06:58 48 boot.emmc.win.md5
24/08/2016 06:58 5.632 data.ext4.win
24/08/2016 06:58 48 data.ext4.win.md5
24/08/2016 06:58 56 data.info
24/08/2016 06:58 1.572.864 efs1.emmc.win
24/08/2016 06:58 48 efs1.emmc.win.md5
24/08/2016 06:58 1.572.864 efs2.emmc.win
24/08/2016 06:58 48 efs2.emmc.win.md5
24/08/2016 06:58 27.160 recovery.log
rodrigoresende said:
Hi all,
I flashed some custom version of Android 7.0 Nougat in my phone and decided to return to Android 6 Marshmallow from a TWRP Back-up stored in my phone (but I also have these files off the phone).
It started infinty bootloop, flashed official OTA files from adb sideload sucessfully, but it stills in bootloop.
When in fastboot mode, status is : BOOTLOADER BHZ11E, Baseband M8994F, Carrier Info N/A, SECURE BOOT: enabled, DEVICE STATE: locked.
Nexus Root Toolkit , not working properly
LGUP worked, but I think the problem is EFS folder and files.
Am I correct ? Any sugestions?
these are the files that I saved off the phone:
24/08/2016 06:58 33.554.432 boot.emmc.win
24/08/2016 06:58 48 boot.emmc.win.md5
24/08/2016 06:58 5.632 data.ext4.win
24/08/2016 06:58 48 data.ext4.win.md5
24/08/2016 06:58 56 data.info
24/08/2016 06:58 1.572.864 efs1.emmc.win
24/08/2016 06:58 48 efs1.emmc.win.md5
24/08/2016 06:58 1.572.864 efs2.emmc.win
24/08/2016 06:58 48 efs2.emmc.win.md5
24/08/2016 06:58 27.160 recovery.log
Click to expand...
Click to collapse
Do you have TWRP 3.0.2-1?
Darke5tShad0w said:
Do you have TWRP 3.0.2-1?
Click to expand...
Click to collapse
I'm trying to reinstall TWRP using NRT but no success. Only fastboot, and sideload ADB.
Have you tried the method to download twrp 3.0.2-1 in PC and fastboot flash recovery?
@Spark007. This step is not working on locked bootloader.
@rodrigoresende Are you on stock recovery?
Try flash vendor from MM in fastboot.
rodrigoresende said:
I'm trying to reinstall TWRP using NRT but no success. Only fastboot, and sideload ADB.
Click to expand...
Click to collapse
Please answer my question if you used 3.0.2-1 .
3.0.2-1 has a efs restore problem, if that was the case it is an easy fix.
It's saying your bootloader is locked, so I don't imagine using fastboot to flash anything will work. I don't know if using LG's flash tool to flash the .tot would work to restore your EFS (assuming that is the issue), but it might be worth trying. How did you get TWRP on their with a locked bootloader?
*Edit- my apologies, I missed the part about you trying LGUP.
rodrigoresende said:
LGUP worked, but I think the problem is EFS folder and files.
Am I correct ? Any sugestions?
Click to expand...
Click to collapse
You might be screwed.
I believe the TOT file for LGUP doesn't flash the EFS partitions (EFS would contain information specific to phones)
Also the TOT file restores your phone to bootloader locked.
That then prevents you from booting a custom recovery to zero out the EFS partitions and have the phone recreate.
However, since your EFS partition is screwed, you cannot boot into Android to enabled OEM unlocking in the RPMB partition.
I would warn people only use the LGUP / TOT file solution as an absolute last resort
It locks your bootloader and IF it doesn't solve your booting problem (like in the case of corrupted EFS), then it also prevents you from fixing the problem through alternate means.
sfhub said:
You might be screwed.
I believe the TOT file for LGUP doesn't flash the EFS partitions (EFS would contain information specific to phones)
Also the TOT file restores your phone to bootloader locked.
That then prevents you from booting a custom recovery to zero out the EFS partitions and have the phone recreate.
However, since your EFS partition is screwed, you cannot boot into Android to enabled OEM unlocking in the RPMB partition.
I would warn people only use the LGUP / TOT file solution as an absolute last resort
It locks your bootloader and IF it doesn't solve your booting problem (like in the case of corrupted EFS), then it also prevents you from fixing the problem through alternate means.
Click to expand...
Click to collapse
Can you please explain to me what this problem is? Corrupted EFS?
bardhi92 said:
Can you please explain to me what this problem is? Corrupted EFS?
Click to expand...
Click to collapse
EFS has the IMEI, MAC, etc.
There was a bug in TWRP 3.0.2-1 where it generated filenames incorrectly.
There are 2 EFS partitions. Restoring using that version of TWRP would overwrite one of the EFS partitions with the other.
When your phone detects EFS corruption it won't boot.
However, if you write all zeros to the partition inside of TWRP, the phone will regenerate a good copy of EFS.
If you flash the TOT file, I believe it doesn't flash the EFS partition (TOT file from LG might, but one on here probably doesn't)
In that case, after you flash the TOT file, your phone will now be OEM locked, but you still have the corrupted EFS partition preventing you from booting, so you don't have the ability to OEM unlock under developer options, because you can't get to developer options because of aforementioned EFS problem.
If you can't OEM unlock, you can't boot into TWRP and write zeros to your EFS partition, which is all you needed to do originally to get your phone working again after hitting the TWRP EFS bug.
So by flashing the TOT file, you have converted the EFS problem from something fixable into something not fixable (unless someone puts together TOT file that flashes zeros to EFS partition)
sfhub said:
EFS has the NVRAM info for your phone, IMEI, etc.
There was a bug in TWRP 3.0.2-1 where it generated filenames incorrectly.
There are 2 EFS partitions. Restoring using that version of TWRP would overwrite one of the EFS partitions with the other.
When your phone detects EFS corruption it won't boot.
However, if you write all zeros to the partition inside of TWRP, the phone will regenerate a good copy of EFS.
If you flash the TOT file, I believe it doesn't flash the EFS partition (TOT file from LG might, but one on here probably doesn't)
In that case, after you flash the TOT file, your phone will now be OEM locked, but you still have the corrupted EFS partition preventing you from booting, so you don't have the ability to OEM unlock under developer options, because you can't get to developer options because of aforementioned EFS problem.
If you can't OEM unlock, you can't boot into TWRP and write zeros to your EFS partition, which is all you needed to do originally to get your phone working again after hitting the TWRP EFS bug.
So by flashing the TOT file, you have converted the EFS problem from something fixable into something not fixable (unless someone puts together TOT file that flashes zeros to EFS partition)
Click to expand...
Click to collapse
sorry,I am restoring EFS with TWRP 3.0.2-1 My phone can not be turned on "bootloop "always. give a little help,what should I do. thanks in advance
I'm sorry for my bad english
akins0405 said:
sorry,I am restoring EFS with TWRP 3.0.2-1 My phone can not be turned on "bootloop "always. give a little help,what should I do. thanks in advance
I'm sorry for my bad english
Click to expand...
Click to collapse
The way you can fix your EFS is to write Zeros into the EFS partitions and they will get recreated.
To do that you will need to boot into TWRP or into Android (with root)
If your bootloader is still unlocked do *NOT* install the TOT file using LGUP. This will lock your bootloader.
Instead follow this post:
http://forum.xda-developers.com/nex...-fatal-bug-t3453119/post68537146#post68537146
It is for 6p but should work for 5x as well (it was confirmed later in the thread)
If you cannot get to one of those two, you are probably out of luck unless someone creates a TOT file with blank EFS partitions for you.
sfhub said:
The way you can fix your EFS is to write Zeros into the EFS partitions and they will get recreated.
To do that you will need to boot into TWRP or into Android (with root)
If your bootloader is still unlocked do *NOT* install the TOT file using LGUP. This will lock your bootloader.
Instead follow this post:
http://forum.xda-developers.com/nex...-fatal-bug-t3453119/post68537146#post68537146
It is for 6p but should work for 5x as well (it was confirmed later in the thread)
If you cannot get to one of those two, you are probably out of luck unless someone creates a TOT file with blank EFS partitions for you.
Click to expand...
Click to collapse
man thank you so much,I have used 3-0-2-0 end resort EFS . My phone works.
>>>>>>>>>>>>>>>>>>>Thank you very much once again<<<<<<<<<<<<<<<<<<<<<<<
akins0405 said:
man thank you so much,I have used 3-0-2-0 end resort EFS . My phone works.
>>>>>>>>>>>>>>>>>>>Thank you very much once again<<<<<<<<<<<<<<<<<<<<<<<
Click to expand...
Click to collapse
In future only restore your efs if you really need to.
Darke5tShad0w said:
In future only restore your efs if you really need to.
Click to expand...
Click to collapse
ok, thanks for the advice. have a nice day:good:
Darke5tShad0w said:
Please answer my question if you used 3.0.2-1 .
3.0.2-1 has a efs restore problem, if that was the case it is an easy fix.
Click to expand...
Click to collapse
I'm not 100% shure, but I have an EFS back-up. I was trying customs roms of NOUGAT and decided to restore a back-up from TWRP when all the mess started.
sfhub said:
EFS has the IMEI, MAC, etc.
There was a bug in TWRP 3.0.2-1 where it generated filenames incorrectly.
There are 2 EFS partitions. Restoring using that version of TWRP would overwrite one of the EFS partitions with the other.
When your phone detects EFS corruption it won't boot.
However, if you write all zeros to the partition inside of TWRP, the phone will regenerate a good copy of EFS.
If you flash the TOT file, I believe it doesn't flash the EFS partition (TOT file from LG might, but one on here probably doesn't)
In that case, after you flash the TOT file, your phone will now be OEM locked, but you still have the corrupted EFS partition preventing you from booting, so you don't have the ability to OEM unlock under developer options, because you can't get to developer options because of aforementioned EFS problem.
If you can't OEM unlock, you can't boot into TWRP and write zeros to your EFS partition, which is all you needed to do originally to get your phone working again after hitting the TWRP EFS bug.
So by flashing the TOT file, you have converted the EFS problem from something fixable into something not fixable (unless someone puts together TOT file that flashes zeros to EFS partition)
Click to expand...
Click to collapse
Your're right, I flashed the TOT and now the device is locked. Is it possible to create a TOT file that will flash zeros to EFS? Who can help with this?
sfhub said:
EFS has the IMEI, MAC, etc.
There was a bug in TWRP 3.0.2-1 where it generated filenames incorrectly.
There are 2 EFS partitions. Restoring using that version of TWRP would overwrite one of the EFS partitions with the other.
When your phone detects EFS corruption it won't boot.
However, if you write all zeros to the partition inside of TWRP, the phone will regenerate a good copy of EFS.
If you flash the TOT file, I believe it doesn't flash the EFS partition (TOT file from LG might, but one on here probably doesn't)
In that case, after you flash the TOT file, your phone will now be OEM locked, but you still have the corrupted EFS partition preventing you from booting, so you don't have the ability to OEM unlock under developer options, because you can't get to developer options because of aforementioned EFS problem.
If you can't OEM unlock, you can't boot into TWRP and write zeros to your EFS partition, which is all you needed to do originally to get your phone working again after hitting the TWRP EFS bug.
So by flashing the TOT file, you have converted the EFS problem from something fixable into something not fixable (unless someone puts together TOT file that flashes zeros to EFS partition)
Click to expand...
Click to collapse
Please i beg !! please tell me how do i write zeroes to the EFS partition on a nexus 5x !!
i get the TWRP 3.0.2-1 bug and i need to fix it.
please help !!
much obliged !
diegoshock said:
Please i beg !! please tell me how do i write zeroes to the EFS partition on a nexus 5x !!
i get the TWRP 3.0.2-1 bug and i need to fix it.
please help !!
much obliged !
Click to expand...
Click to collapse
just try restor with twrp 3.0.2.0 Worked for me.my phone is now working properly.
rodrigoresende said:
Your're right, I flashed the TOT and now the device is locked. Is it possible to create a TOT file that will flash zeros to EFS? Who can help with this?
Click to expand...
Click to collapse
I'm sure it is. I don't have the tools to create TOT files. If someone has the tools it is probably just about assembling the files and probably creating some meta file to guide the install.
---------- Post added at 09:24 PM ---------- Previous post was at 09:23 PM ----------
diegoshock said:
Please i beg !! please tell me how do i write zeroes to the EFS partition on a nexus 5x !!
i get the TWRP 3.0.2-1 bug and i need to fix it.
please help !!
much obliged !
Click to expand...
Click to collapse
The link is in the above post, but if you have a 3.0.2-0 backup of EFS and TWRP still running, restoring using 3.0.2-0 would be easier.
i was playing the qpst tool and my imei and meid is gone, it seems like my qpst version is old to write imei to the mi6. but now i can not recover it to its original state. what should i do?
if i copy sdf and sde blocks back to the phone, will it fix it, or should i rewrite qcn file with the qpst tool (qcn file can also be corrupted because of the wrong version qpst tool).
i need to rewrite imei, meid to recover the phone. is there any other tool for it?
Bro, use QPST 460 ver. First dd modemst1, modemst2 and fsg partitions, restart the phone, then restore this xqcn: mega.nz/#!vQ1zyART!bXiW0JY1RGWRdHRZZGo4toUOSZiVqEJjMUdyrI8u97Q
magş said:
i was playing the qpst tool and my imei and meid is gone, it seems like my qpst version is old to write imei to the mi6. but now i can not recover it to its original state. what should i do?
if i copy sdf and sde blocks back to the phone, will it fix it, or should i rewrite qcn file with the qpst tool (qcn file can also be corrupted because of the wrong version qpst tool).
i need to rewrite imei, meid to recover the phone. is there any other tool for it?
Click to expand...
Click to collapse
Did you fix it?
Help
Hello does this solution work with such a small xqcn file ?
mekato said:
Bro, use QPST 460 ver. First dd modemst1, modemst2 and fsg partitions, restart the phone, then restore this xqcn: mega.nz/#!vQ1zyART!bXiW0JY1RGWRdHRZZGo4toUOSZiVqEJjMUdyrI8u97Q
Click to expand...
Click to collapse
Any solution ?
Hint* if you try to flash with Mi FLASH PRO tool in recovery mode it will read IMEI from the phone !!
So IMEI is still written on the phone but where and how to recover back ?!
Hi all !
So IMEI, Baseband unknown and MAC address is gone.
No any backup of it !
Have unlocked bootloader, twrp, xiaomieu rom and phone is rooted.
Following "web find" solutions when tried to backup or restore qcn with QPST (v. 2.7 474)
only getting:
"Memory backup failed"
"Disk error writing to file"
When tried to "dd if=/dev/zero of=/dev/block/sde 34 (sdf4, sdf5)
getting "no space left on device"
(no sense, only trying to wipe, not to write anything)
Also tried the same through terminal on twrp and getting same no space error !
Any idea why, or any other way to recover Imei ?
Thanks !!!!
Kiki.G said:
Hi all !
So IMEI, Baseband unknown and MAC address is gone.
No any backup of it !
Have unlocked bootloader, twrp, xiaomieu rom and phone is rooted.
Following "web find" solutions when tried to backup or restore qcn with QPST (v. 2.7 474)
only getting:
"Memory backup failed"
"Disk error writing to file"
When tried to "dd if=/dev/zero of=/dev/block/sde 34 (sdf4, sdf5)
getting "no space left on device"
(no sense, only trying to wipe, not to write anything)
Also tried the same through terminal on twrp and getting same no space error !
Any idea why, or any other way to recover Imei ?
Thanks !!!!
Click to expand...
Click to collapse
contact me to fix it: fb.me/HomXiaomiColombia
Hi, my oneplus 5t suddenly lost the baseband information and imei, results show null baseband and unknown imei. I don't have twrp backup so is there any solution of this problem? Thanknyoubin advance
Try to flash modem "fastboot flash modem NON-HLOS.bin" (Non-hlos.bin you can get in the FullRom zip, path: Rom.zip/firmware update) or flash full firmware from here https://forum.xda-developers.com/showthread.php?t=3728665, finaly you can use unbrick tool. If this can not solve your problem, you will need to wtite your IMEI and MEID manualy (find instructions by google).
Just wanted to add my 2c to this:
Had the same problem (no mobile data, nor Wifi, no IMEI). Was able to locate an old TWRP backup and copy that to my phone via TWRP and restore JUST the EFS partition. After that, everything worked
Hello XDA Forum
I have a little problem with my Red Magic 5G
I accidentally deleted the parameter files and also other important files out of stupidity and wanted to ask whether someone has a red magic 5g and can make a backup via twrp and send it to me? < I really don't know what to do anymore >
I have flashed new software with edl on it and installed all 3 rom versions but I still have the same problem non of them worked i can't even install custom rom anymore.
Best Regards
Akizuma
Has really no one a backup for me left for the red magic 5g ?
Hello, what parameters are missing in your red magic5g, can I help you? I use red magic5s
(I think everthing)
I need a twrp backup from a red magic 5g where everthing still works i destroyed to much,
Not even touch working anymore in twrp.
Edit ( I think not that 5s works on 5g or ? )
you don't need anything from someone else's device.
if you ****ed something up. then you need to use the unbrick tools. and set them up correctly and follow the directions to unbrick.
they will erase all your data. but form what I've read, you lost all that already.
there are unbrick tools for both devices. 5S or 5G on either forum for those devices make sure you're using the correct unbrick tool. 5g does not work correctly with 5S devices, and vice versa.
the unbrick tools will format and restore every single parition on the phone. restoring it to factory settings.
its very possible though if you were messing with partitions that you erased your IMEI.
if thats gone, its beyond the scope of the unbrick tools. you'll have to contact warranty services.
the unnofficial unbrick tools by Johnny in my opinion better.
just make sure your drivers are correctly installed, and up to date. .. this includes windows updates.
(recently there has been a google ADB driver that needs updating thats available through winodws update)
so make sure thats installed too.
set your phone to EDL mode and follow the direction on Johnny's thread.
it will restore your phone as long as you can get to Fastboot mode. (vol down and power)
PM me if you need more help. but that should be enough to get your back to stock.
Problem Fixed ! #closed
@Akizuma it would be kind to post what you did to fix the issue, so others in the future who are faced with the same issue can use your solution.
We are a community here to help others.
If we mention that our problems are sorted, without posting how, it only helps the direct user and other searching for solutions to fix their issues will continue.
Please post what it was you did to fix your issue. It would be very appreciated.
If you're having any of these issues, this option may be able to fix it.
Problem: black screen after boot up, touch not working (TWRP) or automatic booting in EDL mode
First download the Unbrick EDL Tool
(I chose EU)
Download here:
[Tool] Nubia Red Magic 5G Unbirck Tool
So.......It's finally here, the unbrick tool for RedMagic 5G. This tool can help you to unbrick the phone. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm...
forum.xda-developers.com
Then follow the instructions in the folder and install an operating system on it through edl mode
Then you start the installation again but this time you don't run it because I noticed that the tool doesn't flash important image files but skips them (you can even find it in the log)
First go to \ AppData \ Local \ Temp \ is-K4OSH.tmp \ NubiaEmergencyDownload \ software
(name can be different)
And copy
persist.img
boot.img
odm.img
recovery.img
system.img
vendor.img
And put it in a new folder
After that go to the bootloader again and unlock the oem via
(fastboot oem nubia_unlock NUBIA_NX659J)
Then execute following commands for the files like
(Command (Fastboot flash persist [file.img])
(Command (Fastboot flash boot [file.img])
(Command (Fastboot flash odm [file.img])
(Command (Fastboot flash recovery [file.img])
(Command (Fastboot flash system [file.img])
(Command (Fastboot flash vendor [file.img])
It can be that most of them give out an error, execute them anyway in case the folder still exists
Then the cell phone should start again normally.
P.s ( Sorry for my poor english ^^ )
System, Vendor, and odm, are all partitions flashed during the "super" partition.
this is why you didn't see them exactly written in the log they all go under "super" and get assigned a dynamic partition when flashed.
you cna see here how they changed the partitions and how they're written now.
Implementing Dynamic Partitions | Android Open Source Project
either way. thank you for your effort to your solution.