I want to upgrade firmware from 6.0 to 7.0. there is a line in the command where it says erase data. Can I delete that command so that my data does not erase?
JulianCox said:
I want to upgrade firmware from 6.0 to 7.0. there is a line in the command where it says erase data. Can I delete that command so that my data does not erase?
Click to expand...
Click to collapse
There are a few options for updating (Non-OTA)
RSD Lite (using Windows XP/7)
Remove This line from flash_file.xml using Notepad++ then save
Code:
<step operation="erase" partition="userdata"/>
LMSA (Update option or Rescue)
The update option does not wipe dataFastboot.exe
Just do not use this command
Code:
fastboot erase userdata
LMSA is the easiest option if you have a Windows PC
sd_shadow said:
There are a few options for updating (Non-OTA)
RSD Lite (using Windows XP/7)
Remove This line from flash_file.xml using Notepad++ then save
Code:
<step operation="erase" partition="userdata"/>
LMSA (Update option or Rescue)
The update option does not wipe dataFastboot.exe
Just do not use this command
Code:
fastboot erase userdata
LMSA is the easiest option if you have a Windows PC
Click to expand...
Click to collapse
thanks mate
Related
Is there any way that we could remove a line or delete something out the script so that it doesn't clear data when running sbf. Friend needs help to unroot and get the kitkat update without wiping data. They are already on 9.30.1, just need to lose root and update. Thanks and have a great day.
Sent from my Droid Incredible 4G LTE
Yes, basically RSD Lite only wipes the user data with this line in the XML:
Code:
<step operation="erase" partition="userdata" />
If you have it in your file, just delete it and the user data in this partition should stay untouched. But you never know, so better have a backup anyway.
lem22 said:
Yes, basically RSD Lite only wipes the user data with this line in the XML:
Code:
<step operation="erase" partition="userdata" />
If you have it in your file, just delete it and the user data in this partition should stay untouched. But you never know, so better have a backup anyway.
Click to expand...
Click to collapse
Thank you a lot, ill be sure to test it.
Sent from my Droid Incredible 4G LTE
I can confirm this works, thank you!
Sent from my Dell Venue 8
ok,
i tried to update earlier, and the first update went through, but part 2 did not. i tried to go back to 100% stock and relock my phone, and i get this error: no valid piv block in SP for system piv validation failed (system) relock failure. and now it tells me there are no updates available, someone please help me moto x xt1060
Couple things, what build number (KXA21.12-L1.26, KXA21.12-L1.26-3, KXA21.12-L1.26-4, other) and what did you do or believe you had to do to return to stock? Were you previously running a custom recover (ie: TWRP)?
KXA21.12-L1.26-1, I was running twrp, flashed factory recovery, first update went through, second did not, then I flashed system and all, now I cannot get it to lock and it does not show an update available
The other thread has the solution, download the latest 4.4.4 rom from moto site, edit the xml file to NOT wipe your phone, use RSD lite to flash the phone, update as normal through settings.
Google this: VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip
unzip and edit xml file,
remove these:
<step operation="getvar" var="max-download-size" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
save file
boot to bootloader, start RSD lite, browse to the xml file and start it
I don't ever see an XML file, and I have never been able to get rsd to work, can you explain rsd to me
superkeest said:
The other thread has the solution, download the latest 4.4.4 rom from moto site, edit the xml file to NOT wipe your phone, use RSD lite to flash the phone, update as normal through settings.
Google this: VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip
unzip and edit xml file,
remove these:
<step operation="getvar" var="max-download-size" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
save file
boot to bootloader, start RSD lite, browse to the xml file and start it
Click to expand...
Click to collapse
loganehaynes said:
I don't ever see an XML file, and I have never been able to get rsd to work, can you explain rsd to me
Click to expand...
Click to collapse
You need to extract the archive, the xml file is inside the zip. I have taken the liberty of performing the google search for you:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
I assure you that there is an xml file in the archive that you will download.
And heres how to use RSD lite:
http://wccftech.com/steps-to-restore-moto-x-to-stock-firmware-with-rsd-lite-att-sprint-t-mobile-us-cellular-verizon/
Thank you, I will try it as soon as I can
RSDLite is the easy way, but you can fastboot flash all the partitions if you cannot get RSDLite working. I RSD'd back to KXA21.12-L1.26 and it ran through all the updates just fine. Here is a link to a zip with RSDLite and the Motorola USB driver required (CLICK HERE).
FYI... Moto didn't put an XML to use with RSDLite into some of the newer SBF/FXZ they had on the dev image site.
They did include a flash.bat which calls fastboot, and includes their tweaked version of fastboot inside the SBF/FXZ download.
Thank You
thank you all for your help! at the moment, my android is upgrading, optimizing app 24 of 73! if you were here, we would open a jar of shine and celebrate!
1. Download latest Firmware P605XXU1EPD4 with SamFirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
2. Model = SM-P605, Region = VNZ, [x] Auto, [x] Binary Nature, [x] Check CRC32, [x] Decrypt automatically.
3. Then click [Check Update] and after the file is found: [Download].
4. Unpack the .ZIP-file. Should GET 4 FILES
5. Boot into Bootloader mode by holding Vol Down + Power + Home at the same time, then press Vol up when the triangle appears
6. Right click on the Odin 3 Application file and run as administrator http://odindownload.com/Samsung-Odin/#.Vm3AglE1I-Q
7. Open BL_xxx on BL, AP_xxx on AP, CP_xxx on CP and CSC_xxx on CSC, leave UMS empty!
Make sure that under options only Auto Reboot, & F. Reset Time is ticked
This will delete everything!!!
8. Boot your device, no need to setup at this point.
9. Use Odin to flash CF-Auto-Root-lt03lte-lt03ltexx-smp605 file https://download.chainfire.eu/380/CF-Root/CF-Auto-Root/CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip
Make sure that under options only Auto Reboot, & F. Reset Time is ticked
The device will auto reboot, and you should see a red android pirate and some commands running
Don't worry if your device reboots a couple of times its normal
10. Use Odin to flash latest TWRP 3.0.2.0 https://dl.twrp.me/lt03ltexx/ in AP Slot with "Auto Reboot" UNCHECKED
11. Once completed do not let your device boot up
Hold Vol up + Home + power buttons to boot to TWRP recovery.
It will take a while so just wait.
BY NOW YOU HAVE A ROOTED STOCK ROM PD4 WITH TWRP recovery, and you may make a BACK UP - If TWRP offers to root, DO NOT DO IT
12. SD card fix
Launch your favorite file manager, like Root Explorer
Navigate to /system/etc/permissions/platform.xml (Do remember to backup “platform.xml” in safer place)
Open Platform.xml, then EDIT
Add the below Highlighted code lines and then save the file.
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
</permission>
<permission name=”android.permission.WRITE_MEDIA_STORAGE” >
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
</permission>
13. Screen mirror fix
Add "wlan.wfd.hdcp=disable" line to \system\build.prop file
14. Multiwindow
a. If you want all your aplications to open in multiwindow: multiwindow commander work perfectly
https://play.google.com/store/apps/d...ommander&hl=el
b. if you want 4 multiwindows then follow the direction in step 2 of that posting
http://forum.xda-developers.com/tab-4/themes-apps/mod-improve-multiwindow-mode-tab-4-t2996654
just com.sec.feature.multiwindow.quadview.xml is needed to /system/etc/permissions folder, and set their perms to rw, r, r or 644,
Thanks for this! That's sharing.
You hyperlinks (step 14) to external references don't work.
jpl69 said:
Thanks for this! That's sharing.
You hyperlinks (step 14) to external references don't work.
Click to expand...
Click to collapse
Thanks for bringing it to my attension,
link fixed.
hello,
i have the LTE version and had trouble doing this step:
10. Use Odin to flash latest TWRP 3.0.2.0 dl.twrp.me/lt03wifiue/ in AP Slot with "Auto Reboot" UNCHECKED
so the solution for me was, i used this version of TWRP (dl.twrp.me/lt03ltexx/twrp-3.0.2-0-lt03ltexx.img.tar.html) and voilá, works fine.
thx a lot for this!
BuZZ-t-HaRd said:
hello,
i have the LTE version and had trouble doing this step:
10. Use Odin to flash latest TWRP 3.0.2.0 dl.twrp.me/lt03wifiue/ in AP Slot with "Auto Reboot" UNCHECKED
so the solution for me was, i used this version of TWRP (dl.twrp.me/lt03ltexx/twrp-3.0.2-0-lt03ltexx.img.tar.html) and voilá, works fine.
thx a lot for this!
Click to expand...
Click to collapse
Thanks for bringing it to my attension, that is what I meant, the link was wrong.
link is fixed now.
hi alex,
no problem!
another question: what does step 12 do exactly? do i have to do this step? until now i didnt have done this step, i have no problems reading and writing to my sd card.
{Moderator Announcement: Thread closed!}
Obsolete
Refer to this guide for root. It's free.
(ROOT) ZTE Blade Z Max Z982 Free Non-UAT 2/21/19
My phone is B25 Not B20. Do you got one for my specific firmware?
The patched boot and recovery are from b20. They are working fine on my b25 system image.
Any ideas how to get the UAT for free?
Here is the MetroPCS B25 full partition update.zip designed to be flashed via recovery
https://www.androidfilehost.com/?fid=11410963190603910728
Here is some early production firmware use at your own risk
https://www.androidfilehost.com/?fid=11410963190603910729
Pulled these from a paid site to update my device, and maybe get a firehose for you guys in the process but no luck.
xxMoon said:
Using Win7 64
Here are the files you will need and may need before hand:
Need
Z982 Firmware B20 (It has the rawprogram0.xml file)
QDLoader Drivers
ADB Drivers
Patched Boot
Patched TWRP Recovery
ZTE Tool (Puts unrooted devices in EDL Mode while in DFU mode)
Uni Android Tool (This is the pay to play part :crying::crying::crying: )
ZTE DFU Drivers
Computer Prep:
1. Unpack the Z982 firmware to a folder on your desktop.
2. Install QDloader drivers
3. If you havnt already, install the adb drivers.
4. Install ZTE Tool
5. Install UAT (You need to subscribe to use thier program:crying::crying::crying
6.Put both boot.img and recovery.img into the folder where you unpacked your firmware and overwrite the existing stock ones.
7. Install ZTE DFU Drivers
8. Reboot you computer and press F8 to show the boot options.
9. Select "Disable Driver Signature Enforcement" or something like that.
Computer Prep Complete
Phone Prep
1. Unlock Developer Options and enable OEM Unlock and USB Debugging.
2. Backup all the files and apps you wish to keep to some place other than on internal storage.
3. Power off phone
4. Boot into DFU Mode by pressing Vol+, Vol-, and power.
Phone Prep Done
Watch Video
https://drive.google.com/file/d/1yvrb0nP7fEfTRAN3pQxuJAXHbvVZ8OdL/view?usp=sharing
After you flash your phone will try to boot. It probably will probably boot loop. The reason being, your current system in encrypted. So here is a list of what you have to do next.
1. Disconnect your phone from the computer.
2. Press and hold Vol+ and power until the phone restarts and vibrates. Then release power while continuing to hold vol+.
3. You will boot into TWRP. Swipe to allow modifications.
4. Select Wipe
5. Select Format Data
6. Type yes and then blue checkmark.
7. Back out and select reboot then system.
Mission Accomplished
The phone will do a the intial setup and you will have to open magisk manger which will then prompt you to install it.
Click to expand...
Click to collapse
why not using [adb reboot edl] command to boot directly into edl mode instead of using zte tool.
messi2050 said:
why not using [adb reboot edl] command to boot directly into edl mode instead of using zte tool.
Click to expand...
Click to collapse
That's what I did and can you help me with the UAT I don't have $50 for subscription. Do you know any way to get it for free? Plz help me
Chickenaa said:
That's what I did and can you help me with the UAT I don't have $50 for subscription. Do you know any way to get it for free? Plz help me
Click to expand...
Click to collapse
you just need the firehose from uni however i have no idea about where you can ind it, sorry..
messi2050 said:
you just need the firehose from uni however i have no idea about where you can ind it, sorry..
Click to expand...
Click to collapse
And how you get that FIREHOSE?
Chickenaa said:
And how you get that FIREHOSE?
Click to expand...
Click to collapse
no idea
It seems from what I could find online the file we need from uni is called 8936_020.ufl
I'm not 100% certain though
I think we have to make one.
https://cellphonetrackers.org/wp-content/uploads/8x60_msimage.mbn_.txt
How to generate the 8660_msimage.mbn
8660_msimage.mbn is released in SW by default, actually, it includes the all the boot images and partition table there. MPRG8660.hex will download this image and reset to mass-storage mode. If customers have different HW settings, such as GPIO/DDR, the default 8660_msimage.mbn may not work for them, so customers need build their own 8660_msimage.mbn by themselves with following ways.
1. Have the QPST 2.7.366 or higher version installed.
2. Make a local folder, copy sbl1/sbl2/sbl3/rpm/tz images to this folder.
3. copy the emmcswdownload.exe from C:\Program Files\Qualcomm\QPST\bin to this folder.
4. Prepare the partition_boot.xml as below and copy the partition_boot.xml to the same folder as above.
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
5. Run the emmcswdownload.exe tool to create OEM boot image with a command below.
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M
6. The 8660_msimage.mbn will be generated in the folder.
Additionally, I dumped the usb packets going from uni to my phone while flashing splash.img. It has the loader and the splash.img in it. But it needs to be pulled out. If anyone is capable, try it. uni_usb_dump_z982.7z
The firmware you provided only have Sbl1, it doesn't have sbl2 or sbl3. Can you help me? And one more thing do you have root on your Z982 because I think I found where the firmware is in the phone and we can copy it and keep it. I can't do it because it gives me access denied of course I don't have root but I think a person with root can do it.
The Z982 has 1 sbl. "SBL1"
Did you already root your phone?
Yep
Can you try something for me real quick? Plz
How to get the partition_boot.xml? Plz help me I need my phone root as fast as possible
Chickenaa said:
How to get the partition_boot.xml? Plz help me I need my phone root as fast as possible
Click to expand...
Click to collapse
I have just about as much an idea on how to do it as you do.
Earlier someone posted -In unzipped ROM folder right clck on file "flashfile.xml" open with Notepadn and delete this line (near the end) and save.
<step operation="erase" partition="userdata"/>
Tried it today during upgrade to February update. It still erased the data. One needs to also delete the following line line in the fastboot commands for it to work.
fastboot erase userdata