I have a sprint xt1526, is there a way to tell how chunks there are as far as the system partitions go? I want to flash a firmware, but im not sure about it.
I've flashed both 5.0.2 and 5.1 on my XT1526. 5.0.2 has 6, 5.1 has 7.
Related
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
1. Most likely. There have been many users reporting hard bricked devices when the did what you are telling. So you shouldn't risk it.
2. No, it is not necessary if you haven't changed the system a bit, and in such a case just unrooting would suffice. But as you were rooted and all, you may have altered it a little. So it is recommended to flash stock as it removes all chances of errors.
3. Working link:http://forum.xda-developers.com/showthread.php?p=54872420
Hope I helped!!!
Harsh862 said:
Hope I helped!!!
Click to expand...
Click to collapse
Thanks for the answers. I'll definitely have to go back to stock then if we want to upgrade. I hate losing all my settings and high scores, but if that's what has to be done, that's what we have to do.
However, the link for the firmware is for Brasil. So it won't work for me. I'm in the United States, and need the US retail global version for the XT1021. Maybe someone else has this? Thanks in advance!
Also, not sure if it makes a difference or not, but we are still on 4.4.3.
LeiraHoward said:
For reference: We have two Motorola Moto E (XT1021) devices in our family. Both have been unlocked, rooted, and have TWRP installed. They are running Android 4.4.3.
We would like to upgrade to later versions of Android. However, I am getting conflicting answers on a few issues:
(1) If we just return to the stock bootloader and allow the Motorola update process to continue, will it brick our devices? (Some say yes, some say no... any solid answers?)
(2) In order to upgrade to Lollipop, most of the walkthroughs I have seen say to restore to stock firmware. Is this actually necessary?
(3) If it IS necessary to restore to stock firmware, does anyone have a working link to a current XT1021 stock ROM? Unfortunately, I seem to have lost my copy, and every single link that I have found so far is to http://sbf.droid-developers.org/phone.php?device=34 , which is a dead link.
Thanks in advance for your assistance!
Click to expand...
Click to collapse
Que 1&2 are basically the same.
Here is a detailed explanation for both.
To update your OS via official OTA, you need unmodified system. The OTA doesn't simply copy files to the system, it patches those files so if a single file is modified the update won't be able to patch it and your phone will soft brick.
Now, to avoid that, it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.)
So you can just flash the system partitions and stock recovery. This will not remove your data & those high scores.
To flash just extract your rom and execute these commands ONLY.
Code:
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
You will have your stock recovery and unmodified system ready for update.
neo.ank said:
it is recommended to flash stock ROM before updating. Its safe but its a lot cause you just need unmodified system. OTA doesn't care about anything else.(stock recovery is needed too.).
Click to expand...
Click to collapse
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
LeiraHoward said:
Thanks. I guess I'm stuck because I do not have stock recovery files (I could have sworn I had them backed up but I can't find them anywhere) and I am unable to find them online at the moment (all credible links seem to point back to the dead droid-developers link).
If anyone has a copy of the stock files, I'd love to get them.
Click to expand...
Click to collapse
Stock recovery files are available on xda. Why are going to stock for lollipop upgrade. Use a lollipop flashable file which is given on this page. Don't screw up your device. Link-http://forum.xda-developers.com/moto-e/development/rom-motorola-stock-rom-t2935429
I've done some research and it looks as though the file I need is Blur_Version.21.12.34.condor_retuglb.retuglb.en.US which should be Android 4.4.3 for the XT1021 for the GSM phone in the US. But I am unable to find this rom anywhere. The only file I've been able to get is the 4.4.4 and I don't think that flashing just parts of that one to my device is a good idea. I'd still kinda like to keep my original settings... does anyone have the Blur_Version.21.12.34.condor_retuglb.retuglb.en.US file or a link to it? I have done SO many searches on this site but keep running into dead links. (Whatever happened to droid-developers anyway? ALL the links go to them and nothing works....)
Thanks!
Can anyone help? I have a canadian 925w firmware and want to flash over to international 925f so that I can update to the MM beta and figure out if I can do it with flashing pit files and boot loaders and modem? or is it just not possible?
Thanks
Not Possible. The update.zip will check to make sure bootloader/system/modem match. Bootloaders from other variants cannot be flashed. The only way this can happen is if someone dumps the entire MM system, and then uploads it as a ROM package which is flashable via TWRP. After that, we will need a compatible kernel that includes the audio changes required for T/W8 and we need the corresponding fixes for the system to also fix in-call audio. Even after all that, we could have issues with bootloader differences such as the fingerprint reader not working due to being on an older bootloader and what not.
TLDR:
Not possible. Sit tight and wait for official release from Canadian Carriers.
I'm trying to downgrade from Marshmallow (XOSP) to KitKat (BarRin).
After wiping and installing BarRin, the phone gets stuck on the LG Logo.
I figure it's because of how my phone is partitioned - I recall that KitKat has different partitions than Lollipop/Marshmallow, but I can't remember how to re-flash the partitions so that it can accommodate for KitKat.
ZV6 TOTs - http://forum.xda-developers.com/spr...mware-sprint-lg-g3-ls990-zv6-tot-ota-t2948063
^ not sure which ones i would need to flash
Flashing IMGs - http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
^ which one am I supposed to use?
If someone can point me in the right direction for these, that would be great. Thanks!
hi.
i am getting this mi box and the first thing i want to do with is to secure the DRM and keep a backup of it. So there are two builds which have enabled ADB, the MM 454 and the Nougat 1028, where we can create a backup.
Out of the box the mi box has the Android MM 6.0 os.
My question here is, do both of these builds are safe to flash without losing the drm?
Can i just use the MM 454? or should i flash and update to Nougat build 1028? or either of them is safe to flash from MM 6.0?
I need confirmation from you guys so that i won't make a mistake and lose the life of the box.
THANK YOU!
454 worked for me. It will wipe your system (factory reset), but then you can back up the Boot partition/image and DRM.
Follow the backup part of these instructions. It needs to be translated, but it is accurate. - http://daivietpda.com/2017/11/mdz-16-abhuong-dan-downgrade-from-nougat-7-0-to-6-0/
rygle said:
454 worked for me. It will wipe your system (factory reset), but then you can back up the Boot partition/image and DRM.
Follow the backup part of these instructions. It needs to be translated, but it is accurate. - http://daivietpda.com/2017/11/mdz-16-abhuong-dan-downgrade-from-nougat-7-0-to-6-0/
Click to expand...
Click to collapse
thanks sir @rygle. so which build of MM were you from when you flashed the MM 454?
So do you also mean that if for example i am in MM build 750 it is 100% safe to flash the MM build 454 and not lose the DRM?
im just thinking that it could also be a downgrade (from MM 750 to MM 454)and i will lose the drm.
claishem01 said:
thanks sir @rygle. so which build of MM were you from when you flashed the MM 454?
So do you also mean that if for example i am in MM build 750 it is 100% safe to flash the MM build 454 and not lose the DRM?
im just thinking that it could also be a downgrade (from MM 750 to MM 454)and i will lose the drm.
Click to expand...
Click to collapse
There is no issue about losing drm when staying within MM builds. The quandary is there exists only 1 userdebug build for MM, that being build 454. Xiaomi has instituted some protections that preclude flashing a lower build once a certain build level has been flashed. Sorry, don't have my notes accessible to cite which specific MM build employs this protection.
The occasions where losing DRM is a potential issue is after having upgraded to Nougat. Regressing to MM does expose the potential for inadvertently losing DRM unless you have backed up the partitions that contain DRM. You would need to flash the Nougat build 1028 which permits copying DRM partitions, which then can be restored onto MM.
Such manipulations are not possible once Oreo has been flashed as there is no userdebug build for Oreo.
In summary.....moving between MM builds does not put your DRM at risk
Moving from MM to Nougat exposes the chance you can cripple your DRM by user error.
Moving to Oreo does not allow recovery of saved DRM partition under any circumstances.
The saved DRM partitions work no matter you are running MM or Nougat. They are identical and interchangeable.
bigtalker said:
Such manipulations are not possible once Oreo has been flashed as there is no userdebug build for Oreo.
In summary.....moving between MM builds does not put your DRM at risk
Moving from MM to Nougat exposes the chance you can cripple your DRM by user error.
Moving to Oreo does not allow recovery of saved DRM partition under any circumstances.
The saved DRM partitions work no matter you are running MM or Nougat. They are identical and interchangeable.
Click to expand...
Click to collapse
Please tell me if i am understanding it correctly.
We can only flash an update.zip in a recovery of a userdebug firmware if we are switching between OSs (including switching between builds)
We can also flash an update.zip in a recovery of a NONE userdebug firmware, only if we are switching between builds.
Is that right?
Because i am thinking why it isnt possible to go back to Nougat or MM, given you already have a copy of the drm partition, if you can just flash the update.zip in the recovery to update or downgrade os.
sorry for being noob about this.
claishem01 said:
Please tell me if i am understanding it correctly.
We can only flash an update.zip in a recovery of a userdebug firmware if we are switching between OSs (including switching between builds)
We can also flash an update.zip in a recovery of a NONE userdebug firmware, only if we are switching between builds.
Is that right?
Because i am thinking why it isnt possible to go back to Nougat or MM, given you already have a copy of the drm partition, if you can just flash the update.zip in the recovery to update or downgrade os.
sorry for being noob about this.
Click to expand...
Click to collapse
You are so confused you are making me confused. I will not be responding further to your inane questions.
HTML:
bigtalker said:
You are so confused you are making me confused. I will not be responding further to your inane questions.
Click to expand...
Click to collapse
This is what i am thinking,
(just the same process with N to MM. Only you are coming from Oreo)
flash Nougat 1028 from Oreo.
dd flash rom3.img
flash mm454.
restore/dd flash 256mb.img
wipe and reboot.
Hello everyone.
I am a fan of Android customization, and that's why i installed LineageOS 16 on my Galaxy S7 G930F.
Everything is working fine, but i am now asking myself a question: is it possible to downgrade from that Custom 9.0 to Stock 7.0/6.0 ?
Now that we installed a custom ROM, the Bootloader should be modified, right ? The stock Bootloader blocks Odin from installing older firmwares, but is it now possible ?
I don't want to try, because i have important data on my phone, a really bad internet, and i just want to be sure if it's possible or not.
Thanks to everyone for helping me .
Soriahz said:
Hello everyone.
I am a fan of Android customization, and that's why i installed LineageOS 16 on my Galaxy S7 G930F.
Everything is working fine, but i am now asking myself a question: is it possible to downgrade from that Custom 9.0 to Stock 7.0/6.0 ?
Now that we installed a custom ROM, the Bootloader should be modified, right ? The stock Bootloader blocks Odin from installing older firmwares, but is it now possible ?
I don't want to try, because i have important data on my phone, a really bad internet, and i just want to be sure if it's possible or not.
Thanks to everyone for helping me .
Click to expand...
Click to collapse
Lineage OS does not in any way modify your bootloader. You can flash your stock firmware without any issue. If you intend on keeping the data from apps on lineage os, and using it on stock, it's not going to work.
If you're referring to internal storage, that doesn't need be wiped when returning to stock (unless it's encrypted), only the data partition, system, cache, and dalvik cache need it.
Be aware that if you flash stock firmware using Odin, it will wipe your internal storage unless you use a home csc file. Not all firmwares have them. If you made a backup with twrp, you can restore that without any problems, and avoid worrying about your internal storage.
Thanks for that answer. I read on internet that the bootloader after Android 8.0 was locked at version 4, and did not let older firmwares with different bootloaders being installed with Odin. Of course I can flash the 8.0, but 7.0 and 6.0 does not seem possible because of that "impossibility". We can't use 8.0 bootloader with 7.0/6.0 because some functions will not work suck as vibrator. Flashing a custom firmware made me think that this "lock" would me removed. I already tried downgrading in the paste being on stock 8.0 and I got a fail. Thank for that answer !