Related
[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Sorry for my bad english! I hope someone can help me!
Here I put the files I've already uploaded! USE AT YOUR OWN RISK!
https://mega.co.nz/#F!VMQHFJxB!7aSAkqkYI1SX7GI_S5yItw
USE AT YOUR OWN RISK! YOU MUST HAVE UNLOCKED BOOTLOADER
How-to:
-Copy all the files from the IMG's And BIN folder and the TWRP Recovery "twrp-2.8.3.0-titan.img" to your "platform-tools" folder
-Copy the TWRP Backup to your SD Card Backup's folder
Enter to fastboot in your device and run this commands in order (I exclude "fastboot flash partition gpt.bin" and
"fastboot flash motoboot motoboot.img")
fastboot flash logo logo.bin <--- From Retail US Firmware
fastboot flash boot boot.img <--- From XT1064 Nextel México
fastboot flash recovery twrp-2.8.3.0-titan.img <--- Flash TWRP Recovery include in the Link
-Enter to TWRP Recovery using your device, Wipe System/Data/Cache and Restore the System Partition from the Backup.
-Power Off the Device and enter to Fastboot again.
fastboot flash recovery recovery.img <--- Original Recovery from Retail US Firmware
fastboot flash modem NON-HLOS.bin <--- Modem from XT1064 Nextel México
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn <--- From XT1064 Nextel México
fastboot erase cache
fastboot erase userdata
ejsmsupersoyelm said:
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Click to expand...
Click to collapse
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
reefuge said:
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
Click to expand...
Click to collapse
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
ejsmsupersoyelm said:
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
Click to expand...
Click to collapse
It's hard to say but motoboot.img and gpt.bin it's normally a one way upgrade only, if you flash newest, it can be hard to go back. Yes the should flash but you wont gain much and may lose OTA updates in future.
So there is no need to flash these for restoring TWRP back ups, I strongly suggest you leave yours alone.
ADB flashing really is just for OTA upgrades and using to get a custom recovery on phone, once you have a custom recovery you can make custom roms to flash from that.
Adb flashes system from OTA as 4 parts that combine into /system folder - so thats why you cant flash 1 big img via adb
again you need to learn how to make a flashable custom rom to use via TWRP, look for a guide there are many.
but i will give you a idea how to do
using your xt1064 mexcio TWRP back up - ALL you need for now is Boot.emmc.win and system.ext4.win nothing else
rename boot.emmc.win to boot.img and change system.ext4.win to system.ext4.tar and find a guide on how to extract the tar to a system folder ( I use cygwin )
then take a meta-info folder from a custom xt1064 rom and adjust the updater-script to work with your rom - zip these 3 files up into your new custom rom.
this is a very simple idea, there are more steps so search for a guide on here
I just need the motoboot.img file, would provide for me?
Hello ,
i am new to this fastboot thing because i had galaxy grand and restoring to stock rom was so easy and now i have moto g2 running CM12.1 + TWRP +unlocked bootloader
and now i want to restore to stock 5.0.2 .and restoring to stock will install stock recovery or not?? please tell me step by step instructions .
thanks
Recently i downgraded from cm12.1 to stock. Here is what i did.
Downloaded stock rom from one the xda threads.
Placed in internal storage
Used philiz recovery. Chose 'Clean for a new rom' or something like that.
Installed zip.
Wipe cache partition.
rahul.pipaliya007 said:
Hello ,
i am new to this fastboot thing because i had galaxy grand and restoring to stock rom was so easy and now i have moto g2 running CM12.1 + TWRP +unlocked bootloader
and now i want to restore to stock 5.0.2 .and restoring to stock will install stock recovery or not?? please tell me step by step instructions .
thanks
Click to expand...
Click to collapse
yes if you install stock rom stock recovery will also be installed and this is the link for mfastboot that will be required to flash stock rom http://goo.gl/lTYq4F
YOU WILL NEED A PC OR LAPTOP TO PERFORM THESE OPERATIONS
instructions :
1. download stock rom and mfastboot
2. unzip mfastboot and place it some were in your pc
3. unzip the stock rom and copy all the stuff to mfastboot folder
4. make a backup your internal storage will also be wiped
5. reboot your phone to bootloader mode
6. connect your phone to pc and go to mfastboot folder which you have unzip rom in it and right click mouse button in that folder and hit open command window hear
7. copy the bellow commands in that window one by one you need to hit enter for every each and every command
6.
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
now your done :laugh: enjoy stock
dj krishna said:
yes if you install stock rom stock recovery will also be installed and this is the link for mfastboot that will be required to flash stock rom http://goo.gl/lTYq4F
YOU WILL NEED A PC OR LAPTOP TO PERFORM THESE OPERATIONS
instructions :
1. download stock rom and mfastboot
2. unzip mfastboot and place it some were in your pc
3. unzip the stock rom and copy all the stuff to mfastboot folder
4. make a backup your internal storage will also be wiped
5. reboot your phone to bootloader mode
6. connect your phone to pc and go to mfastboot folder which you have unzip rom in it and right click mouse button in that folder and hit open command window hear
7. copy the bellow commands in that window one by one you need to hit enter for every each and every command
6.
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
now your done :laugh: enjoy stock
Click to expand...
Click to collapse
Why do we need such a long process. I installed stock rom through recovery mode.
Will be there any difference?
kishorebvs said:
Why do we need such a long process. I installed stock rom through recovery mode.
Will be there any difference?
Click to expand...
Click to collapse
that is flashable zip right hmm !! i prefer this method this is the actual method but you can ever go for that i prefer this because factory images will also be flashed in this method and even bootloader will also be updated and stuff like that. not sure what will be the difference between both may be nothing
and the main thing is he wanted to restore stock recovery so this is only way to restore stock recovery
Hi folks,
I made a mistake after unlocking my Moto G XT 1068.
After unlocking was confirmed i did not boot it back to system.
Instead I installed TWRP 2.8.5.0 thru fastboot .
Then i rebooted to TWRP.
Inside TWRP i flashed CM12.1 zip. Then got a list of errors (image1).
All errors mention "E:Unable to mount '/data'"
Tried mounting 'data' too but i get a vibrate when i select 'data' partition and it is not selected.
Same while trying to fix data partition or trying to change file system.
How to mount it thru terminal commands in TWRP? Or thru fastboot?
Can anyone help with this please?
I also downloaded the stock firmware for the XT1068 (614 MB size) . Will flashing that work ?
If yes, how to flash that using fastboot? Can i just try to flash that zip thru TWRP?
Kind help required.
regards,
Anoop
anoopgkris said:
Hi folks,
I made a mistake after unlocking my Moto G XT 1068.
After unlocking was confirmed i did not boot it back to system.
Instead I installed TWRP 2.8.5.0 thru fastboot .
Then i rebooted to TWRP.
Inside TWRP i flashed CM12.1 zip. Then got a list of errors (image1).
All errors mention "E:Unable to mount '/data'"
Tried mounting 'data' too but i get a vibrate when i select 'data' partition and it is not selected.
Same while trying to fix data partition or trying to change file system.
How to mount it thru terminal commands in TWRP? Or thru fastboot?
Can anyone help with this please?
I also downloaded the stock firmware for the XT1068 (614 MB size) . Will flashing that work ?
If yes, how to flash that using fastboot? Can i just try to flash that zip thru TWRP?
Kind help required.
regards,
Anoop
Click to expand...
Click to collapse
Try flashing stock with fastboot commands..!?
dj krishna said:
Try flashing stock with fastboot commands..!?
Click to expand...
Click to collapse
Hi,
Do you mean the commands for the partition, boot, system, modem, cache etc? Where can I get the set of commands?
I found one link showing the process using mfastboot. Are they similar?
But can I go ahead without resolving the mount problem? Any idea why that mount problem cropped up?
Sent from my GT-I9001 using XDA Free mobile app
anoopgkris said:
Hi,
Do you mean the commands for the partition, boot, system, modem, cache etc? Where can I get the set of commands?
I found one link showing the process using mfastboot. Are they similar?
But can I go ahead without resolving the mount problem? Any idea why that mount problem cropped up?
Sent from my GT-I9001 using XDA Free mobile app
Click to expand...
Click to collapse
yaa !! download mfastboot zip file extract it into your pc and download stock unzip it, and copy all the files to mfastboot folder which you have extracted
now in that mfastboot folder right click mouse button and hit open command window hear now copy this commands one after the other and make sure you hit enter for every single command
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
and make sure you download the stock firmware not the flashable zip :good:
good luck
SOLVED-Moto G 2014 flash problem
dj krishna said:
yaa !! download mfastboot zip file extract it into your pc and download stock unzip it, and copy all the files to mfastboot folder which you have extracted
now in that mfastboot folder right click mouse button and hit open command window hear now copy this commands one after the other and make sure you hit enter for every single command
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
and make sure you download the stock firmware not the flashable zip :good:
good luck
Click to expand...
Click to collapse
Thanks bro, it worked with textbook precision. Booted back to stock Lollipop.
smitharro said:
Here you can find stock firmwares of all Moto G variants (including the 2013 variants). So br sure to choose the right version!
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1
Click to expand...
Click to collapse
Thanks Harro, for the stock links, those worked when none others did . :good:
Will flash CM in some time.
Extract this zip and place all files in your minimal adb and fastboot folder .
Reboot in to twrp and wipe system , vendor , data , cache , dalvick cache.
Reboot in to fastboot mode.
Run Fastboot commands ,
Commands :
fastboot flash config config.bin
fastboot flash misc misc.img
fastboot flash modemst1 dummy.img
fastboot flash modemst2 dummy.img
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot flash cust cust.img
Reboot in to twrp recovery
Now flash Xiaomi.eu OREO rom.
Reboot system , your network must work now. Fixed my xiaomi.eu oreo network and calling issue. No more unknown baseband.
If you are already having fastboot rom then no need to download these files from this link. Just extract from fastboot rom and paste in minimal adb and fastboot folder.
Link for files :
https://drive.google.com/file/d/1-0i1QMO_2c6LVxEazcpPEC1cG3EOe7ie/view?usp=drivesdk
NOHLOS.bin
Edit : NOHLOS.bin file get corrupted so uploaded seperate. NOHLOS.bin link :
https://drive.google.com/file/d/1-2CevvtQZ_966UKh76fFvCWkKq6CTW3_/view?usp=drivesdk
sumit17 said:
Extract this zip and place all files in your minimal adb and fastboot folder .
Reboot in to twrp and wipe system , vendor , data , cache , dalvick cache.
Reboot in to fastboot mode.
Run Fastboot commands ,
Commands :
fastboot flash config config.bin
fastboot flash misc misc.img
fastboot flash modemst1 dummy.img
fastboot flash modemst2 dummy.img
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot flash cust cust.img
Reboot in to twrp recovery
Now flash Xiaomi.eu OREO rom.
Reboot system , your network must work now. Fixed my xiaomi.eu oreo network and calling issue. No more unknown baseband.
If you are already having fastboot rom then no need to download these files from this link. Just extract from fastboot rom and paste in minimal adb and fastboot folder.
Link for files :
https://drive.google.com/file/d/1-0i1QMO_2c6LVxEazcpPEC1cG3EOe7ie/view?usp=drivesdk
Click to expand...
Click to collapse
The solution you offer is definitely working. Thank you so much...
wrbn said:
The solution you offer is definitely working. Thank you so much...
Click to expand...
Click to collapse
Always Welcome Brother.
my redmi y2 0 imei
Sir can it fix null imei please give me any fix of 0 imei
bitturathi645 said:
Sir can it fix null imei please give me any fix of 0 imei
Click to expand...
Click to collapse
This can work if you do this. It's worth trying.
flash nhi ho rhi miui eu rom how it fixed
flashing error
bitturathi645 said:
flashing error
Click to expand...
Click to collapse
Whats error you are facing?
error 7
not install in correct device
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
my mobile show unknown efs and unknown imei
bitturathi645 said:
not install in correct device
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
my mobile show unknown efs and unknown imei
Click to expand...
Click to collapse
Redmi Y2/s2 device only.
Drivers installed in pc , check by command prompt in fastboot mode
Commands
Fastboot devices
You can contact in telegram group.
t.me/redmiS2G
Thank you
wrbn said:
The solution you offer is definitely working. Thank you so much...
Click to expand...
Click to collapse
Thank you so much I could repair it
file corrupted NON-HLOS.bin
LsoaresA said:
file corrupted NON-HLOS.bin
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-2CevvtQZ_966UKh76fFvCWkKq6CTW3_/view?usp=drivesdk
thank you, now it's working.
Why it still 0 my IMEI
sumit17 said:
Extract this zip and place all files in your minimal adb and fastboot folder .
Reboot in to twrp and wipe system , vendor , data , cache , dalvick cache.
Reboot in to fastboot mode.
Run Fastboot commands ,
Commands :
fastboot flash config config.bin
fastboot flash misc misc.img
fastboot flash modemst1 dummy.img
fastboot flash modemst2 dummy.img
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot flash cust cust.img
Reboot in to twrp recovery
Now flash Xiaomi.eu OREO rom.
Reboot system , your network must work now. Fixed my xiaomi.eu oreo network and calling issue. No more unknown baseband.
If you are already having fastboot rom then no need to download these files from this link. Just extract from fastboot rom and paste in minimal adb and fastboot folder.
Link for files :
https://drive.google.com/file/d/1-0i1QMO_2c6LVxEazcpPEC1cG3EOe7ie/view?usp=drivesdk
NOHLOS.bin
Edit : NOHLOS.bin file get corrupted so uploaded seperate. NOHLOS.bin link :
https://drive.google.com/file/d/1-2CevvtQZ_966UKh76fFvCWkKq6CTW3_/view?usp=drivesdk
Click to expand...
Click to collapse
Hi, I am very much familiar to flashing roms through twrp of each and every device I purchase from Xiaomi since 2015. In my entire 4years of experience I made a small mistake name of redmi y2(3+32) flashed with pie ROM of EU through twrp, network issue faced, decided to revert back to latest MIUI global stable ROM(through fastboot method) and processed here I made simple untimely mistake which is I blindly proceeded with the flashing process flash all lock.bat instead of not opting to flash all.bat, this is the mistake I made, after completion of fastboot flashing same network issue happened even in the global stable ROM also(no network signals), I decided to unlock the bootloader but not able to do it because once Sim card inserted and detected then only if any one can bind their existing mi account, no detection of Sim card, only showing that please insert Sim card and try in the mi unlock device(developer options). This is the story and state of my device redmi y2, how to get rid of this situation, if you can understand my problem please help.
Regards
Hola, tengo un Redmi S2 y no reconoce las SIM card ni tampoco la red WLAN, he flasheado varias Room y probado todos los metodos pero no logro darle señal. Que puedo hacer, ya lo doy por muerto...
Mr Seshu said:
Hi, I am very much familiar to flashing roms through twrp of each and every device I purchase from Xiaomi since 2015. In my entire 4years of experience I made a small mistake name of redmi y2(3+32) flashed with pie ROM of EU through twrp, network issue faced, decided to revert back to latest MIUI global stable ROM(through fastboot method) and processed here I made simple untimely mistake which is I blindly proceeded with the flashing process flash all lock.bat instead of not opting to flash all.bat, this is the mistake I made, after completion of fastboot flashing same network issue happened even in the global stable ROM also(no network signals), I decided to unlock the bootloader but not able to do it because once Sim card inserted and detected then only if any one can bind their existing mi account, no detection of Sim card, only showing that please insert Sim card and try in the mi unlock device(developer options). This is the story and state of my device redmi y2, how to get rid of this situation, if you can understand my problem please help.
Regards
Click to expand...
Click to collapse
use test points to unlock bootloader.
After searching in many forums, I managed to enable the Wi-Fi, bluetooth and infrared port of my Redmi S2 by flashing the persist.bin file .... The problem I have is that the cell phone was left with IMEI 0, someone could guide me how to recover, repair or write a new IMEI for my Redmi S2?
sumit17 said:
Extract this zip and place all files in your minimal adb and fastboot folder .
Reboot in to twrp and wipe system , vendor , data , cache , dalvick cache.
Reboot in to fastboot mode.
Run Fastboot commands ,
Commands :
fastboot flash config config.bin
fastboot flash misc misc.img
fastboot flash modemst1 dummy.img
fastboot flash modemst2 dummy.img
fastboot flash dsp adspso.bin
fastboot flash mdtp mdtp.img
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot flash cust cust.img
Reboot in to twrp recovery
Now flash Xiaomi.eu OREO rom.
Reboot system , your network must work now. Fixed my xiaomi.eu oreo network and calling issue. No more unknown baseband.
If you are already having fastboot rom then no need to download these files from this link. Just extract from fastboot rom and paste in minimal adb and fastboot folder.
Link for files :
https://drive.google.com/file/d/1-0i1QMO_2c6LVxEazcpPEC1cG3EOe7ie/view?usp=drivesdk
NOHLOS.bin
Edit : NOHLOS.bin file get corrupted so uploaded seperate. NOHLOS.bin link :
https://drive.google.com/file/d/1-2CevvtQZ_966UKh76fFvCWkKq6CTW3_/view?usp=drivesdk
Click to expand...
Click to collapse
bro can you give me name of the files that scare please
for example: v9.x.x.x or v10.x.x.x
also correct name Xiaomi.eu OREO?
Thank u so much thought it was dead tried a lot of other stable roms none worked.Thank you for sharing the solution.
To others who are trying follow the steps properly
---------- Post added at 01:51 PM ---------- Previous post was at 01:47 PM ----------
tomelich said:
bro can you give me name of the files that scare please
for example: v9.x.x.x or v10.x.x.x
also correct name Xiaomi.eu OREO?
Click to expand...
Click to collapse
Download any rom that has the android version 8.1
I used https://xiaomi.eu/community/threads/9-1-10.48651/
---------- Post added at 02:21 PM ---------- Previous post was at 01:51 PM ----------
To boot TWRP use this guide https://forum.xda-developers.com/redmi-s2/how-to/guide-to-flash-twrp-unofficial-root-t3854906
Disclaimer: I am not responsible for the results of any of these operations.
Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just faced, then solved the problem and I want to share the solution that could maybe help other persons.
This was how it happeded:
While I was flashing the phone, I erased the partition called "persist" accidently. When I was trying to flash the persist partition, the phone returned a message said that you can't flash the controlled partition. I suddenly relized something bad happened. Then I reboot the phone and find that many sensors stopped working. But the worst thing is the carrier network signals lost. I want to contact the service center at first. But I think as long as the phone is unlocked, there are tons of possibilities to fix it, unless it's hard-bricked. So I wanted to try to fix the partition.
As we know, Xiaomi phones have backup partitions for most of the important partitions. For example, vbmeta and vbmetabak partitions. The vbmetabak usually is the backup of vbmeta. This persist partition also has a backup partition called "persistbak". This backup partition can be used to repair the persist partition. There are 2 ways to fix the persist partition. Choose the method you preferred.
1. This way is for users have erased the persist partition, but haven't modified/erased the persistbak partition. If you don't want to type commands just use method 2.
Go to fastboot, flash the twrp recovery first. Then hold the POWER and VOLUME UP to force the phone boot to twrp recovery. Connect the phone to your PC and open adb command window. Type the following commands in order:
adb shell
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition immediately. For example, the persist partition and persistbak partition correspond to mmcblk0p$$ and mmcblk0p%% respectively (persist---->mmcblk0p$$ and persistbak---->mmcblk0p%%). Run this following command to restore your persist partition:
dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partition block name.
Now the persist partition has been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
2. This way is for users that have erased persist partition and persistbak partition or can't restore the partition using method 1. Also, this method is a universal and easy way to fix both persist partition and persistbak partition. It doesn't need to type any command but only a swipe.
I have made the persist partition repair tool for both global version and Chinese version. Both of them are in attachments. These tools make the repair process very easy. Both flashable zip files are tested on my Redmi Note 8 and they work fine.
I have also posted them to Mi Community.
Flash the repair tool in attachment. Choose the right file and flash it.
Now the persist partition and persistbak partition have been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
If you think it's useful, please click the "Like" button.
Yuki1001 said:
Disclaimer: I am not responsible for the results of any of these operations.
Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just faced, then solved the problem and I want to share the solution that could maybe help other persons.
This was how it happeded:
While I was flashing the phone, I erased the partition called "persist" accidently. When I was trying to flash the persist partition, the phone returned a message said that you can't flash the controlled partition. I suddenly relized something bad happened. Then I reboot the phone and find that many sensors stopped working. But the worst thing is the carrier network signals lost. I want to contact the service center at first. But I think as long as the phone is unlocked, there are tons of possibilities to fix it, unless it's hard-bricked. So I wanted to try to fix the partition.
As we know, Xiaomi phones have backup partitions for most of the important partitions. For example, vbmeta and vbmetabak partitions. The vbmetabak usually is the backup of vbmeta. This persist partition also has a backup partition called "persistbak". This backup partition can be used to repair the persist partition. Here is a way to fix the persist partition.
This way is for users have erased the persist partition, but haven't modified/erased the persistbak partition.
Go to fastboot, flash the twrp recovery first. Then hold the POWER and VOLUME UP to force the phone boot to twrp recovery. Connect the phone to your PC and open adb command window. Type the following commands in order:
adb shell
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition immediately. For example, the persist partition and persistbak partition correspond to mmcblk0p$$ and mmcblk0p%% respectively (persist---->mmcblk0p$$ and persistbak---->mmcblk0p%%). Run this following command to restore your persist partition:
dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partition block name.
Now the persist partition has been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
2. This way is for users that have erased persist partition and persistbak partition or can't restore the partition using method 1.
Find someway to download the fastboot ROM for your device. Exract the tgz file and open the folder called "images". Copy the "persist.img" to the adb tool folder. Because of the limitations of Xiaomi, you can't flash the persist partition or the persistbak partition directly. Copy the persist img file to the internal storage or sdcard on your phone. Now reboot to twrp recovery, connect the phone to your PC. Use these command to make a file that you can dd it to the persist partition and the persistbak partition:
adb shell
simg2img /sdcard/persist.img /sdcard/persist333.img
Now you have a file that can dd to the persist/persistbak partition. Then type these following commands in order:
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition and the persistbak partition immediately. Type these following commands in order:
dd if=/sdcard/persist333.img of=/dev/block/mmcblk0p$$
dd if=/sdcard/persist333.img of=/dev/block/mmcblk0p%%
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partitions block name.
Now the persist partition and persistbak partition have been fixed/restored. Reboot your phone to system and check the whether sensors and carrier network etc. all work fine.
If you think it's useful, please click thanks button.
Click to expand...
Click to collapse
Does this fix "device storage corrupted" error?
Actually I have this error but my sensors, carrier, wifi ... Etc all working great this error still appears. Anyway I think magisk hide config props module damaged my device's persist when I changed the fingerprint then I came back to stock rom and this error happened so my question is: is this process risky Or could cause losing mac or imei? And am I going to lose widevine l1?
I'm thinking about backing up my current persist before proceeding do you think it's a good idea?
[email protected] said:
Does this fix "device storage corrupted" error?
Actually I have this error but my sensors, carrier, wifi ... Etc all working great this error still appears. Anyway I think magisk hide config props module damaged my device's persist when I changed the fingerprint then I came back to stock rom and this error happened so my question is: is this process risky Or could cause losing mac or imei? And am I going to lose widevine l1?
I'm thinking about backing up my current persist before proceeding do you think it's a good idea?
Click to expand...
Click to collapse
Yes. It can fix "find device storage corrupted" . You won't lose your imei or mac. At that time I erased the persist partition by a command "fastboot erase persist" accidently. I have tried both method 1 and 2, and the error is no longer appeared.
About backing up, the persistbak partition is a backup partition for your current persist partition. So if you failed, just restore the persistbak to the main persist partition. And you can also export the raw image of your current persist partition. Of course, the error will appear if you restore the corrupted persistbak.
Update: I have uploaded the persist partition repair tool for both global version and Chinese version. Both of them are in attachments. These tools make the repair process very easy. Both flashable zip files are tested on my Redmi Note 8 and they work fine.
realgordboy said:
Good work.
Just one query. In your original post, you mention simg2img command. I'm wondering if that is actually needed or wanted, given that the fastboot ROMs contain persist images that are not sparse.
Click to expand...
Click to collapse
Yes. You are right. I have been flashed my redmi note 5's persist partition and its a sparse img file. Look like this img file is a raw img not sparse file. Thanks for the tip. I have changed the content of method 2. And it's really easy to flash both persist and persistbak using my repair tool.
realgordboy said:
Looks like we both had the same good idea. I made a zip for my Redmi Note 8T, that does more or less the same, restoring both persist and persistbak to "pristine" condition.
My fix : https://forum.xda-developers.com/redmi-note-8/how-to/fix-persist-partition-getting-mangled-t4112133
Click to expand...
Click to collapse
Yes. That's a good work. Thanks for sharing. I really have the same idea to you. I will test your file later with replacing your persist.img in the zip file.
realgordboy said:
Are you serious?
Of course I tested it. In fact I tested it extensively, and the script has error checking for every single action command
The persist image, as I explained in my post is from the Global Note 8T 11.0.4.0 ROM. It will only probably work on the Note 8T.
It would of course work on just about any similar phone, if you replace the persist image with your own.
Click to expand...
Click to collapse
OK. Thanks for the reply I will test your zip file tomorrow. It should be a good work. Just technical discussion, nothing else.
realgordboy said:
Your original method 2 used 'dd'. Are you saying 'dd' is wrong?
Are you saying that in addition to the incorrect use of simg2img, your entire method was faulty?
And just what exactly is the difference between 'dd' and 'package_extract_file'?
These are not questions that require an answer, because one of us already knows the answers, and checks their 'advice' before posting.
Click to expand...
Click to collapse
I don't think dd is wrong if the img is a raw image. It should can be dd to the partition. I'm sorry if I said something wrong and don't be angry please. Just discussion, nothing else. I will test your file with my persist.img tomorrow.
Hi! Thanks for the input! Would I lose L1 widevine DRM validation with this method?
CesarPedetta said:
Hi! Thanks for the input! Would I lose L1 widevine DRM validation with this method?
Click to expand...
Click to collapse
Is your persist partition broken? If so just flash it. Don't think too much. The phone works normally is the first thing. And sorry, I don't know if it will effect the widevine DRM security level. Don't use it like a toy. Persist means "persist", its data should not be changed after shipping. Only flash it when your persist partition is broken or cannot works properly.
hello,
i have Mi 9T pro i have bug with light and proximity sensor, after flash persist.img with orange fox my sensor work but for few moment and stop work again look at the evidence
thx 4 the tutorial
can I flash this two files on my poco F2 Pro ? I have problem with persist image, lost my fingerprint sensor..
Is there an chance to get the the persist partition file for Willow please?
I tried to restore from bak files, didn't work.
autobrightness is not working for me. after ive flashed fastboot rom .. i noticed that my screen was very bright at nigth. so checked brightness.
manually brightness works ok up and down.. but in auto only works on high settings but it wont go down. or seems to go down but brightess doesnt change..
enter cit presing kernel verion did a test on light sensor. flux sensor goes up and down depending of light but the brightness value doesnt change down only up high.
WinBug2 said:
Is there an chance to get the the persist partition file for Willow please?
I tried to restore from bak files, didn't work.
Click to expand...
Click to collapse
Just download the fastboot ROM which version you are using. Extract it and you can find persist.img in images folder.
Hi, thanks for sharing.
im using mi note 10, im losing the /persist partition directory, somehow it losing after flashing custom rom, how to get it back? Im editing your file and change to my phone original persist.img, and flashing on twrp it end to fastboot bootloop. My sensor are working, but after loosing my /persist directory the fingerprint scanner "cant add fingerprint, try again" Error.
I check at miflash, theres no option to install/create persist.img partition at promram0.xml line to fix this (somehow im suprising about this, because at my old whyred phone theres an option to create the partition), Could you help me solving this?
Yuki1001 said:
Disclaimer: I am not responsible for the results of any of these operations.
Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just faced, then solved the problem and I want to share the solution that could maybe help other persons.
This was how it happeded:
While I was flashing the phone, I erased the partition called "persist" accidently. When I was trying to flash the persist partition, the phone returned a message said that you can't flash the controlled partition. I suddenly relized something bad happened. Then I reboot the phone and find that many sensors stopped working. But the worst thing is the carrier network signals lost. I want to contact the service center at first. But I think as long as the phone is unlocked, there are tons of possibilities to fix it, unless it's hard-bricked. So I wanted to try to fix the partition.
As we know, Xiaomi phones have backup partitions for most of the important partitions. For example, vbmeta and vbmetabak partitions. The vbmetabak usually is the backup of vbmeta. This persist partition also has a backup partition called "persistbak". This backup partition can be used to repair the persist partition. There are 2 ways to fix the persist partition. Choose the method you preferred.
1. This way is for users have erased the persist partition, but haven't modified/erased the persistbak partition. If you don't want to type commands just use method 2.
Go to fastboot, flash the twrp recovery first. Then hold the POWER and VOLUME UP to force the phone boot to twrp recovery. Connect the phone to your PC and open adb command window. Type the following commands in order:
adb shell
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition immediately. For example, the persist partition and persistbak partition correspond to mmcblk0p$$ and mmcblk0p%% respectively (persist---->mmcblk0p$$ and persistbak---->mmcblk0p%%). Run this following command to restore your persist partition:
dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partition block name.
Now the persist partition has been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
2. This way is for users that have erased persist partition and persistbak partition or can't restore the partition using method 1. Also, this method is a universal and easy way to fix both persist partition and persistbak partition. It doesn't need to type any command but only a swipe.
I have made the persist partition repair tool for both global version and Chinese version. Both of them are in attachments. These tools make the repair process very easy. Both flashable zip files are tested on my Redmi Note 8 and they work fine.
I have also posted them to Mi Community.
Flash the repair tool in attachment. Choose the right file and flash it.
Now the persist partition and persistbak partition have been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
If you think it's useful, please click thanks button.
Click to expand...
Click to collapse
not to hate or dislike or be rude or anything... but people will lose Widevine L1 support by this method... so if anyone doesn't want HD videos on netflix etc, go ahead with this method.. otherwise don't even touch persist partition.
Thank you so much, flashing the zip worked !
Where can i find repair_persist-willow.zip ? From gingko not work.