Checking the internet showed me that it will probably not give any stock image for the Huawei MediaTab M3. Also the repair service has not even listed the media tab till now???
So now I hope someone of you can help me. Would it be possible to upload a TWRP Backup of the media tab for me? I'm not sure what partitions I need but for sure I need the system partition. I hope someone can help me. I don't want to buy another one just to get this data.
Related
I think i have bricked mine and hoping the community can help me. I was installing a new rom ([VDT-ROM] V11.5 Super Lite) for my variant, and when i completed the installation, It somehow removed my recovery and couldn't boot. Now when i try to do a restore using the restore to stock procedures it will not let me because the current version says d80210f i believe. when it does allow me to get to restore that version, i am unable to get to the settings to apply root and recovery cause the screen when you touch it cant sense my finger and its acts Totally weird. I have read some ppl have had this issue but i am unable to find a way to fix this. SO please anyone that knows a way to help me get my d801 back to stock from the wrong version. if anyone needs more details let me know.
Hello,
I have this problem with my phone and i don't know how to fix it, the IMEI is Null and when i enter "*#0011#" the ServiceMode is Blank !!
I tried to use GS5_EFS_Backup but it doesn't work ! Also the phoe get hot a lot, and when i put it in charge the battery level of charge is stuck in 10% always.
My phone is rooted.
Help me Please.
Thank you
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
*Detection* said:
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
Click to expand...
Click to collapse
Thank you Detection for your answer. So where can i find another S5 EFS, and how can i restore it.
Help me Please because i tried already to take it to a repair shop but they don't know how to fix it, that's why I wanna try to repair it myself, and i think its one of the repair shops who wiped the EFS partition without making a backup (because i give to 3 repair shops and they don't know how to fix it).
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
*Detection* said:
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
Click to expand...
Click to collapse
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Nope, not if you've deleted the EFS partition - that contains the IMEI and Radios
Ok thank you, ill try to contact samsung after sales service.
Hi everybody,
I have same issue:
I needed to update SU-binaries and tapped accidentally on CWM/TWRP-Mode instead of normal. After this IMEI is null, Service Mode blank, sudden reboots and unable to install any Apps (always saying no free memory). uninstalling App causes reboot.
I have efs backup made with (PhilZ Touch) CWM, but I'm not able to fix the problem with it.
What I tried:
flashing Stock ROM + updating Bootloader in Odin
this Guide (except Samsung Tool and Terminal Emulator steps, as I can't install any App)
CWM script
I really don't know what else I can do. Does anybody have some other ideas?
Also backing up is not possible, now. EFS Professional says specified PIT file does not exist, even when I choose all partitions.
FIXED. Possible solution.
Fixed. Went to a shop to repair IMEI/EFS.
It seems there is something called "IMEI NV Generator", this should also do the magic and would have saved me some money.
samsung S5 Imei Proplem
zicozack said:
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Click to expand...
Click to collapse
I have the same problem after trying to change the original IMEI>>> any help please
Please take a look here and here.
Due to an error of magisk, I lost some of my partitions of my Pro 5. So now it's hard-bricked.
But luckily, the bootloader remains unlocked, so that means I still have chance to fix it.
I found a way to backup the default partitions from this url:
https://forum.xda-developers.com/meizu-pro-5/development/meizu-pro-5-backup-tool-st0rm77-t3460138
My Pro 5 is 64GB version.
Could anyone please backup the default partitions and share with me to save my phone? Thanks!
Same problem here. Please help us.
aegoyu said:
Due to an error of magisk, I lost some of my partitions of my Pro 5. So now it's hard-bricked.
But luckily, the bootloader remains unlocked, so that means I still have chance to fix it.
I found a way to backup the default partitions from this url:
https://forum.xda-developers.com/meizu-pro-5/development/meizu-pro-5-backup-tool-st0rm77-t3460138
My Pro 5 is 64GB version.
Could anyone please backup the default partitions and share with me to save my phone? Thanks!
Click to expand...
Click to collapse
Hello,
have a look at that : https://forum.xda-developers.com/me...-12-0-unofficial-t3478872/page56#post73263021
(the latest comments)
untick AUTH
Hi All,
My first post on XDA even though I've been around for long now. Faust, thanks for your excellent work.
Regarding the Token Sign Failed error message. It seems you just need to untick "Auth" in the top right corner in the multiupgrade tool.
It worked for me and I could complete the process as described in the PDF file.
After the process, the phone rebooted... I could see the Battery icon and Meizu logo!!! Then I landed on the "Upgrade Firmware" screen from meizu. Weird, I thought I just did it.
I took the update.zip file from the demo and flashed it. It passed the checking Firmware and installation process. The phone reboots... and bootloops on the meizu logo.
Fastboot is still on but BL is now locked. I am stucked. If anyone has another tip to share
GL
Hello everyone. Looking for help in backing up my Zenfone 3.
Reason is, I must send my phone for warranty due to a hardware issue and even though I asked ASUS NOT to update my firmware (still have the original firmware), I have a bad feeling it will get returned factory reset with the latest update.
The reason is not relevant to this thread, but no other firmware past the original firmware the phone came with works properly with the 2 SIM cards I'm using. I tried.
So, is there please an option to backup my Zenfone 3 that most importantly, will keep my original firmware I have now and I can restore it if my phone will come back with the latest firmware? Something like a clone that allows me to restore it exactly the way I have it now before I must send it.
Only other possible obstacle is that my phone is not rooted or bootloader unlocked and I don't wish to do so, as I had no need, and I'm not even sure if ASUS allows that if I need to have it warrantied.
Please help? Any software out there or method I can use to just purely clone/copy my phone and be able to restore it once I receive the phone back?
Hey there folks,
here I am now too on the forum, trying to find a solution for an old sticky problem.
So far a some people here on the forum a while ago have had the problem that when they flashed a custom OS on their Zenfone 3 while data roaming was turned off in the stock rom, they could never get it working unless reverting back to the stock OS and switching it on there before reinstalling the custom OS. Until then only normal calls and SMS work.
I'm having the same problem now and trying to avoid going back to stock, so I wonder if somebody has found another solution by now? Any help would be really appreciated, and I think a lot of other EU people who will run into this problem in the future will be grateful too if this could be solved easier somehow :fingers-crossed:
Update: I took a look at the firmware partition and there is a folder image/modem_pr which seems to include the configuration how the phone connects to mobile networks. I don't claim to have any special knowledge about it but i would expect this is where the stock rom most probably makes its change about data roaming.
So maybe, as long as what the firmware partition contains is generic firmware, could somebody who has data roaming working on their Zenfone3 send a copy of their /firmware/image folder so I can compare the two and hopefully find the missing puzzle piece to get data roaming working?
I would of course post the solution here for everyone in case I figure it out! Would be great if we can solve it
I have the same problem. Please help.
So, here's an update:
After going crazy searching for a possible fix I gave up yesterday and re-installed the stock rom in order to turn on data roaming (since my TWRP backup won't boot that is something I had been trying to avoid, because the only way I found to do this was to either install a recovery from somewhere on the internet that is claimed to be the original Asus recovery but has no way to be integrity-checked for possibly including malware, or to install software designed to bypass Google's SafetyNet and other system integrity checks. Nah.)
Today I took a look at comparing a TWRP backup of the modem partition (contents identical to the one that mounts as "firmware"), and the persist partition. I wrote a script that would calculate the md5 checksum for each file and then compare for any changes.
On the modem partition, only binary files named Widevine changed, for whatever reason :silly:
And here is a list of the files that were changed on the persist partition:
persist/coresight/qdss.functions.sh
persist/coresight/qdss.log
persist/coresight/qdss.log.old
persist/data/gxflag
persist/data/gxfp/0_0/105885283
persist/data/gxfp/0_0/105885284
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxflag
persist/data/gxfp/1_0/gxfeature_table
persist/data/gxfp/1_0/gxflag
persist/data/gxfp/calibration_data
persist/data/gxfp/calibration_data
persist/data/gxfp/gxflag
persist/data/gxfp/mptest/gxflag
persist/data/gxfp/raw/0_0/gxflag
persist/data/gxfp/raw/0_0/tpl_index_table
persist/data/gxfp/raw/1_0/gxflag
persist/data/gxfp/raw/1_0/tpl_index_table
persist/data/ifaa_fplist
persist/data/ifaa_fplist
persist/data/widevine/UZT8uT7lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX
persist/data/widevine/UZT8uT7++lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX.bak
persist/data/widevine/widevine
persist/dmclient/dm_client_info
persist/dmclient/dm_client_token
persist/dmclient/hash_sn
persist/rfs/msm/mpss/server_check.txt
persist/rfs/shared/server_info.txt
persist/sensors/error_log
persist/sensors/sensors_settings
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
persist/.twrps
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
Unfortunately, mostly binary files making it impossible for me to dig deeper into the changes. But maybe somebody spots something odd that could lead to the solution.
My next step will be to go abroad again in early March and see if the data roaming now works. If it does, I will restore a TWRP backup of all partitions I could back up before returning to stock. If it still works then, then the stock rom made its change somewhere on one of the partitions TWRP does not back up. If it stops working, then the answer lies hidden somewhere on the TWRP-backuped partitions.
Either way, I'm sure there must be a manual solution, what happens on the stock rom cannot be black magic
Will keep you updated.
Alright, it's the 1st of March and I'm back abroad! I finally have data roaming working and got a little further in my investigation: Restoring partitions one by one, i figured out that the change by the stock concerning the data roaming is made somewhere on the efs partition (which one of the two I can't say yet, as TWRP only lets me restore them both together). Now I haven't succeeded yet how to mount the efs.emmc TWRP backup or otherwise dump the contents of the efs partition, but if someone here knows I'll go dig deeper and track down the specific entry that is changed
Can you tell how to restore the original partition without flashing the asus rom? Thanks
If you ever had data roaming working and created a Nandroid (TWRP) backup at the time, you can simply restore the efs partitions from back then. Just be sure to use the latest TWRP version and make a fresh backup before you go, as there used to be a version some time ago that corrupted efs partition backups.
If you don't, well, as long as I can't read out my efs I can't tell you what to modify in there and how Maybe somebody
I think my only option is to flash the original Asus rom. It is waste time if only to turn on the data roaming.