OFFICIAL FXZ IS AVAILABLE: http://motofirmware.com/files/category/9-ghost/
note: all you really need are boot, system, modem, and fsg. epecially if you're coming from 4.4. everything else is optional.
note: unlocked devices can downgrade to 4.4, most likely 4.2.2 also; just be sure not to flash downgraded motoboot/gpt if you've upgraded to 4.4.2 motoboot/gpt.
----------
rsd lite notes:
two processes you may want to comment out or delete are the recovery flashing and the wiping of userdata.
to comment out an operation, add "!--" to the beginning, and "--" to the end of an operation.
examples:
<step operation="flash" partition="recovery" filename="recovery.img" MD5="9A3EA0D90080200826EE7B50164012BF" />
<step operation="erase" partition="userdata" />
<!--step operation="flash" partition="recovery" filename="recovery.img" MD5="9A3EA0D90080200826EE7B50164012BF" /-->
<!--step operation="erase" partition="userdata" /-->
you can comment out other processes in this way as well.
or you can just use fastboot and flash what you want.
----------
fastboot notes:
you can look at the xml file to determine fastboot commands to use:
fastboot <operation> <partition> <filename>
examples:
xml:
<step operation="flash" partition="system" filename="system.img" MD5="" />
fastboot command:
fastboot <operation> <partition> <filename>
fastboot flash system system.img
xml:
<step operation="erase" partition="cache" />
fastboot command:
fastboot <operation> <partition>
fastboot erase cache
Way to go Q9Nap
Sent from my XT1060 using XDA Premium 4 mobile app
Q9Nap said:
*edit*
removed for now, i'm now noticing that active notifications aren't working for some reason. i'm guessing it's because the gpt size specification for system partition isn't enough room for the 4.4.2 system image.
Click to expand...
Click to collapse
OH THE HUMANITY!!!!!!!!!!!!
So out of curiosity, while waiting for your fix or the official release ...
As someone who used to have a Nexus, why exactly does this process take so long? Is it just because we lack google release of full images?
For that matter I want to make sure this fxz (a new term to me) is what I think it is: This will let me flash my current XT1060, with unlocked bootloader, frozen bloat, and Xposed Framework, and what? My data will be retained? I'll still have to rebuild my whole phone?
I promise I won't clutter the thread with back and forth Q&A. If there is a better thread explaining it that I haven't found please just point me there, or give me enough tid-bits for me to perform better searches. Like I said, I'm used to dealing with and playing with my GNex so dealing with a non-nexus while wanting to retain motorola's extra's is a new to me. If it weren't for those I'd be AOSP by now
jumperalex said:
OH THE HUMANITY!!!!!!!!!!!!
So out of curiosity, while waiting for your fix or the official release ...
As someone who used to have a Nexus, why exactly does this process take so long? Is it just because we lack google release of full images?
For that matter I want to make sure this fxz (a new term to me) is what I think it is: This will let me flash my current XT1060, with unlocked bootloader, frozen bloat, and Xposed Framework, and what? My data will be retained? I'll still have to rebuild my whole phone?
I promise I won't clutter the thread with back and forth Q&A. If there is a better thread explaining it that I haven't found please just point me there, or give me enough tid-bits for me to perform better searches. Like I said, I'm used to dealing with and playing with my GNex so dealing with a non-nexus while wanting to retain motorola's extra's is a new to me. If it weren't for those I'd be AOSP by now
Click to expand...
Click to collapse
fxz: Fastboot Xml Zip
fxz contains full images of device partitions and is used to restore to out-of-the-box condition. it is similar to factory images for nexus devices. depending on how you flash, either with fastboot or rsd lite, you can choose whether or not to wipe data
fastboot: the command "fastboot erase userdata" will wipe data; don't use the command if you want to keep data
rsd lite: the xml may contain the following line: <step operation="erase" partition="userdata" />
if it does, you can disable it by changing it to: <!--step operation="erase" partition="userdata" /-->
or just deleting the line altogether.
Q9Nap said:
fxz: Fastboot Xml Zip
fxz contains full images of device partitions and is used to restore to out-of-the-box condition. it is similar to factory images for nexus devices. depending on how you flash, either with fastboot or rsd lite, you can choose whether or not to wipe data
fastboot: the command "fastboot erase userdata" will wipe data; don't use the command if you want to keep data
rsd lite: the xml may contain the following line: <step operation="erase" partition="userdata" />
if it does, you can disable it by changing it to: <!--step operation="erase" partition="userdata" /-->
or just deleting the line altogether.
Click to expand...
Click to collapse
OK last two questions for clarity then ban me if I ask another:
so you said don't issue "fastboot erase userdata" to keep my data. That is functionally then like when I would flash a new AOSP release without doing a factory reset. All the other partitions get written and userdata is left untouched. Right?
Does that mean when I flash gpt it isn't touching the userdata partition? That was the bit that I think had me squinting. If I understood what was being said in other threads about the problems with trying to flash back and forth between 4.2.2, 4.4, 4.4.2, pre-camera, post-camera, etc it is playing with partitions sizes. That got me worried it was also going to muck about with the userdata partition ... read: erase it.
jumperalex said:
OK last two questions for clarity then ban me if I ask another:
so you said don't issue "fastboot erase userdata" to keep my data. That is functionally then like when I would flash a new AOSP release without doing a factory reset. All the other partitions get written and userdata is left untouched. Right?
Does that mean when I flash gpt it isn't touching the userdata partition? That was the bit that I think had me squinting. If I understood what was being said in other threads about the problems with trying to flash back and forth between 4.2.2, 4.4, 4.4.2, pre-camera, post-camera, etc it is playing with partitions sizes. That got me worried it was also going to muck about with the userdata partition ... read: erase it.
Click to expand...
Click to collapse
gpt.bin has nothing to do with userdata.
you can read this post and further in the thread for more clarification: http://forum.xda-developers.com/showpost.php?p=50555443&postcount=16
link is back up, please read the op FULLY before flashing.
Q9Nap said:
link is back up, please read the op FULLY before flashing.
Click to expand...
Click to collapse
Worked great even without erasing userdata. I can't speak as for root or rw protection as i flashed twrp and a new bootlogo immediately after flashing. Thanks for the hard work Also, does anyone know if the entitlement hack for wifi hotspot that worked on 4.4 works on 4.4.2?
-Edit-
Was on wifi so i didn't realize, no data connection (or mobile connection at all) after flashing. Solution ideas?
StATicxTW0T said:
Worked great even without erasing userdata. I can't speak as for root or rw protection as i flashed twrp and a new bootlogo immediately after flashing. Thanks for the hard work Also, does anyone know if the entitlement hack for wifi hotspot that worked on 4.4 works on 4.4.2?
Click to expand...
Click to collapse
you can flash the vzw removal package in the same folder as the fxz. it removes all vzw bloat and branding and unlocks tethering. if you want' to unlock tethering only, you can copy the framework-res.apk from that zip to your framework on device and make sure permissions are set to rw-r-r.
as for dymmeh's xposed module, which i used to modify the framework-res.apk, not sure whether it is updated for use on 4.4.2 or not.
*edit*
btw, were you on full 4.4 before flashing? also what partitions did you flash?
Thanks for this, I'll try this out later once I have a better grasp on what I'm doing. I've got a Dev edition with TWRP.
Q9Nap said:
btw, were you on full 4.4 before flashing? also what partitions did you flash?
Click to expand...
Click to collapse
I was on eclipse 3.1.2, and i flashed whatever was in the zip, so boot, modem, and system
-Edit- I restored from a nandroid from before i flashed this, and no signal on that either, should i try flashing gpt?
I got a little carried away and deleted a system app I shouldn't have without backing it up. Version from 4.4 wouldn't work. Thought I'd have to wait until the SBF came out, but then I saw this... Flashed system.img and I'm back in business! On a Developer Edition.
Thanks much!!
Q9Nap said:
gpt.bin has nothing to do with userdata.
you can read this post and further in the thread for more clarification: http://forum.xda-developers.com/showpost.php?p=50555443&postcount=16
Click to expand...
Click to collapse
HA! yeah i read that the yesterday, but your comments put it into perspective. Thanks so much for the help.
StATicxTW0T said:
I was on eclipse 3.1.2, and i flashed whatever was in the zip, so boot, all three modem files, and system
-Edit- I restored from a nandroid from before i flashed this, and no signal on that either, should i try flashing gpt?
Click to expand...
Click to collapse
-edit- my bad, had to flash fsg.mbn as well, sorry about that You should edit the zip to flash that, i'm pretty sure it's part of the modem so i don't think data will work without it
StATicxTW0T said:
-edit- my bad, had to flash fsg.mbn as well, sorry about that You should edit the zip to flash that, i'm pretty sure it's part of the modem so i don't think data will work without it
Click to expand...
Click to collapse
yeah, good idea. i deleted the previous one and am uploading the new one now. the op has changed, so please read carefully before flashing, especially if you plan to use rsd lite.
OK so I did it. I used the rsd script as a guide but also, as now recommended, flashed fsg.mbn. I also flashed the verizon debloat script I was coming from an OTA'd 4.4 install that was pushed on my first boot of the phone. So a "stock" 4.4 all be it with unlocked bootloader, SuperSU, Xposed framework, and TiBU killed bloat. As you can guess I had to reinstall SuperSU binary (and clear out SuperUser), and reinstall Xposed. After that my phone was back up and running as if I never did a thing. But now I'm on 4.4.2 Oh yes and Gravity Box seems to be working just fine on 4.4.2, but I haven't checked out every single option, just the mod I personally used.
Thanks for your work Q9
okay, I'm paranoid. If I install this I can easily revert to the official 4.4 without issue if for some reason I don't way to stay on 4.4.2? my goal is to not update anything that will prevent me from downgrading to 4.4 or 4.2.2 camera fix like I currently can.
thanks.
edit: I think I got it, I'll be able to safely down grade as long as I don't install motoboot or gpt.bin? and in this case motoboot isn't an issue because it's not included?
edthesped said:
okay, I'm paranoid. If I install this I can easily revert to the official 4.4 without issue if for some reason I don't way to stay on 4.4.2? my goal is to not update anything that will prevent me from downgrading to 4.4 or 4.2.2 camera fix like I currently can.
thanks.
edit: I think I got it, I'll be able to safely down grade as long as I don't install motoboot or gpt.bin? and in this case motoboot isn't an issue because it's not included?
Click to expand...
Click to collapse
correct, i was on the initial release gpt and motoboot when i first flashed this, and active notifications didn't work. that may not be an issue with the 4.4 gpt and motoboot. stay away from gpt i you can, but if you have weird issues like with active notifications, might as well flash it, especially if you're on an unlocked bootloader.
i finally gave in and did full fxz to 4.4 and flashed the update. i'll probably be able to downgrade to 4.4 or 4.2.2 if i ever want to, as long as i don't try to flash the downgraded gpt or motoboot. but 4.4.2 runs noticeably quicker, and i don't think i'll ever want to downgrade anyway.
Success! I installed everything but gpt.bin and successfully upgraded to 4.4.2, All seems to be running well. At one point I even reverted to 4.4 with a nandroid and all went well.
This is the first time I used fastboot to flash and came across an error that didn't appear to effect the flash but am curious as to what it is...
Error:
(bootloader) Variable not supported!
Is this normal or did I do something wrong during the flash process?
Thanks again!
edthesped said:
Success! I installed everything but gpt.bin and successfully upgraded to 4.4.2, All seems to be running well. At one point I even reverted to 4.4 with a nandroid and all went well.
This is the first time I used fastboot to flash and came across an error that didn't appear to effect the flash but am curious as to what it is...
Error:
(bootloader) Variable not supported!
Is this normal or did I do something wrong during the flash process?
Thanks again!
Click to expand...
Click to collapse
Completely normal, i've not idea what the hell it is but i've had it every time i've flashed anything in fastboot on this phone as well as on a droid 3 and razr maxx hd
Related
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
ricm68 said:
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
Click to expand...
Click to collapse
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
garyd9 said:
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
Click to expand...
Click to collapse
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
garyd9 said:
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
Click to expand...
Click to collapse
I flashed the one found at the post: [RUU] att ruu 1.58.502.1 posted
Hmm.. Not sure what to suggest in that case. I'm not very familiar with the whole RUU thing myself...
Sent from my Nexus 7 using Tapatalk
Download the ota update. Extract the firmware.zip from it but don't extract firmware.zip. boot to fastboot.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Do it again
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
Fastboot flash recovery twrp.img
Fastboot erase cache
Load recovery
Wipe, advanced wipe
Select dalvik, cache, data, system, internal. Wipe.
Put Rom on ext sd card or
Adb push Rom.zip /sdcard/
Install zip this will obviously erase everything on your phone.
Click thanks.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
You don't need to repair. You just need to troubleshoot. You are throwing the baby out with the bath water, if you go for a hardware repair for what is likely a software issue that is easy to resolve.
You also need to provide more details, and be specific as possible. Namely:
What recovery and version number?
S-on or off?
What exactly have you tried to flash?
Did you factory reset in bootloader?
Do you have working adb?
What happened when you ran the RUU?
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You wont need the whole thing but some of it might pertain to you
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back.
Click to expand...
Click to collapse
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
ricm68 said:
They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Click to expand...
Click to collapse
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
redpoint73 said:
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
Click to expand...
Click to collapse
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
ricm68 said:
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
Click to expand...
Click to collapse
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
I did the factory reset from within cyanogenmod and it didn't wipe it. It restarted back to cyanogenmod. I copied andoid revolution to my internal memory and try to install from there.
ricm68 said:
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
Click to expand...
Click to collapse
You need to try the things I've suggested. I've made some definitive recommendations, and you seem to have ignored them. Honestly, I don't see a point in trying to help anymore, if you don't read what I'm taking the time to post; or you don't try what I've suggested.
Worst case is RUU and start over (install custom recovery again, etc.). But again, I have no idea what happened when you tried to RUU since you still haven't answered that.
You aren't going to make any progress, if you keep ignoring the advice that is given to you.
I'm doing what you told me!!!
I reinstalled twrp and tried but it failed again. Believe me, I've been doing what you suggested.
Can you please give me the steps to RUU and what ruu file to download and use. I really appreciate all you're doing for me and the time you are taking to help.
Sent from my One M8 using XDA Premium 4 mobile app
I was able to install cyanogen mod again and I am using the phone but I want to install sense again.
Sent from my One M8 using XDA Premium 4 mobile app
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!
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
This place has gotten a bit messy with all of the threads out there and it's especially confusing for those who are new to unlocking and rooting. Or, heck, to those who weren't around as the threads were being written and referenced. I've reposted my consolidated step-by-step list half a dozen times so far - and the steps seem to be working for folks - so I'm going to post it here. You're still going to have to visit the original threads, but hopefully this will serve as a clear outline for you.
Maybe we can also try to keep general unlocking and rooting questions ("I don't know where to start, help me!") to this thread to avoid cluttering up the other ones. Reserve questions in those threads for those specifically related to the OP ("I received ABC error after doing XYZ, what does it mean?"). If anyone sees general unlocking or rooting questions in other threads, maybe direct them here as a place to start. Make sense?
A list of FAQs can be found here in the second post.
Many thanks to @tenfar and @DrakenFX (among others with their help and suggestions!) for the tools and files they provided to make all of this happen.
Unlocking and Rooting your Axon 7
This set of steps has worked successfully for multiple folks (including myself) on the US/NA variant (A2017U) and stock B29. Folks with EU/global variant (A2017G) may have issues and as of right now, should proceed with caution. If you see any problems and/or have a different variant and need additional (or different) steps added, let me know. I will update the thread as necessary.
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Backup your boot and recovery (just in case) using the tool found here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Using the same tool as above, flash TWRP (recovery) found in that thread. You do not need to flash the boot image!
Unlock the bootloader: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash the bootstack and ROM for your variant: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Boot phone, set it up, whatever
Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, fully functioning TWRP (no data encryption issue), and a rooted phone. You will no longer be able to receive OTAs!
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
What does disemmcwp do and why should I do it?
disable emmc (internal storage) write protection is what allows changes to system (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
I only see B27 files and not B29. Help!
If you're in any of the threads referenced in the OP that only have files marked as B27, you can use those even if you're on or upgrading to B29. If the thread has B29 files, use those.
Fastboot can't find my device.
If fastboot oem lock returns <waiting for device> or fastboot devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (in this case, v9)
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
xtermmin said:
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
Click to expand...
Click to collapse
Excellent point. Done!
It would be nice if someone can post a video on YouTube. That would make it that much easier.
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Also it would be nice a guide how to go back to stock and update to latest OTA.
Sent from my ZTE A2017G using Tapatalk
tasar said:
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Click to expand...
Click to collapse
Yes you must disable your screen lock due to the encryption issue in MiFavor. If you do not disable your screen lock and restore your data, your pin/password/pattern would become wrong and your only option would be to factory reset. Fingerprint would still work but I wouldn't risk it.
dejikocv said:
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
Click to expand...
Click to collapse
razorsbk said:
Also it would be nice a guide how to go back to stock and update to latest OTA.
Click to expand...
Click to collapse
I've updated the OP with the relevant information. I haven't done it myself so I can't say what the exact screens are, but the steps should be pretty close and you should be able to figure it out.
If no one confirms (or corrects) the steps as I've written them, I'll go through the process before installing CM and update the steps to more accurately describe the process.
@rczrider
I'll updating my sticky thread/guide/info to direct everyone who want to unlock/root their devices, here to your thread....instead of having an outdated one with old info.
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
kodrnusa said:
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
Click to expand...
Click to collapse
This will be very helpful
Do I have to rollback to B20 or B27 to unlock bootloader?
@rczrider
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Orlando1193 said:
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Click to expand...
Click to collapse
I was under the impression that @DrakenFX's StockSystem zip would overwrite boot, but I could be wrong in that. Have you tried doing the same process, but manually replacing recovery using @tenfar's tool and your own original recovery image?
If you don't have your original recovery, it (among other files for B20 and B27) can be found here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
baconboy said:
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Click to expand...
Click to collapse
Correct, no updates at all for the moment. As it stands, I believe we would need a modified/merged full zip that included the OTA's content. You definitely won't be able to receive OTAs officially.
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Great thread. Just wish this post was up 2 days ago. I just flashed B29 to my Axon from B20_Boot (which I now have read was a bad move. I just found out call audio & mic arent working). Good thing you put this post up. I have been scrambling through the threads to figure a solution. Just gonna flash back to B20 stock using TWRP :good:
Kevinkuensken said:
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You probably haven't enabled OEM Unlock in Developer Options.
ntzrmtthihu777 said:
Ok. I've put together some packages to help people who unlocked their bootloaders
and got stuck on version 10.0.13, 10.0.14, or 10.0.16, or who unlocked
(or will unlock) on version 10.0.19 and wish to get whatever the next OTA version is.
reserve.10.0.*.HD61CB.7z has all the files needed to re-insert your reserve.img where
it should be and correct its permissions. It should allow you to OTA ifyou don't root
after this (this uses a temporary root), or if you unroot before trying to take it. Pick
the version that matches whatever version you are currently on.
Files:
reserve.10.0.13.HD61CB.7z
SHA256: 047c18bc7cf29aef556ed023a061276ff940201d5184355da977a911ccb43931
reserve.10.0.16.HD61CB.7z
SHA256: 0b180e338e889aee149672ba026fb02c16f56d1dfad9351dd9e9f3fabee7d310
reserve.10.0.19.HD61CB.7z
SHA256: 34f92a7f114d3bb4dd8e7cf5aee47ad3909f79fa8ccc97fdaa417ef422dc21ed
reserve.10.0.25.HD61CB.7z
SHA256: 85157f6f9f386c2d87235762862fbd5c6f844ab9f750fc5637b87a2fc0c25815
Instructions:
0. This script starts at the normal system screen.
1. Unzip.
2. If you're on windows, extract the contents of platform-tools_r29.0.5-windows.zip
into the root of the same folder. If you're on linux, adjust your $PATH variable in shell.
3. Run fix-reserve.sh or fix-reserve.bat for linux or windows respectively.
4. Follow the instructions in the prompt. (when it says 'when you're booted' that
means booted and unlocked (pin, pattern, whatever. userdata needs to be decrypted
at this point)).
5. It will reboot you. Magisk manager will still be installed but you will otherwise
not be rooted. The magisk_patched.img in this folder will root you permanently
if you would like.
Click to expand...
Click to collapse
Hope this helps! This has been tested to work on a device unlocked on 10.0.13,
and there is little reason to believe it won't work on others. Also, if you use the
msm tool for these devices, and wish to unlock and continue to get OTA updates,
you must use this package, as MSM relocks you, and will destroy reserve.img again.
Those of you who have used this, please keep an eye out for updates from TMO
and report back whether you were able to update.
Confirmed that it works with brand new OTAs. Several members of the TG group
took the update from 10.0.16 and 10.0.19 without issue after restoring reserve with
these packages.
Thanks for this. So just to be clear, I should be able to run the second part (fix reserve) only and this should put back the .img file so I could theoretically receive the OTA? Is the first part necessary at all? I am on 10.0.16 and would just like to receive the OTA directly. Of course, I would unroot first.
No, you need to do the whole thing.
js042507 said:
Thanks for this. So just to be clear, I should be able to run the second part (fix reserve) only and this should put back the .img file so I could theoretically receive the OTA? Is the first part necessary at all? I am on 10.0.16 and would just like to receive the OTA directly. Of course, I would unroot first.
Click to expand...
Click to collapse
The first part is necessary if you are on any other version than 10.0.19. You would need a reserve.img dumped from 10.0.16
to ota to 10.0.19, and since most people unlocked before 10.0.19 came out, we're not likely to get ahold of reserve.img for
those versions.
Does the first part perform a clean wipe or just force the OTA to apply even with the file mismatch?
dstryrwiz said:
Does the first part perform a clean wipe or just force the OTA to apply even with the file mismatch?
Click to expand...
Click to collapse
First part does not wipe at all, just an overwrite. It fastboot flashes all the non-device-specific partitions as dumped
from a phone which was updated from 10.0.13 to 10.0.19, so after the first bit, and then restoring the reserve.img, your
phone should in theory be exactly how it would be if you hadn't unlocked, except its unlocked. Confused yet?
ntzrmtthihu777 said:
First part does not wipe at all, just an overwrite. It fastboot flashes all the non-device-specific partitions as dumped
from a phone which was updated from 10.0.13 to 10.0.19, so after the first bit, and then restoring the reserve.img, your
phone should in theory be exactly how it would be if you hadn't unlocked, except its unlocked. Confused yet?
Click to expand...
Click to collapse
Understood. Just to be clear though, this overwrite doesn't result in a replacement of the data partition with a blank partition, correct?
I understand that it's technically not a wipe, but I just want to be certain by doing this process that I won't end up losing all my files and need to restore all my apps again. If I need to, it's fine, just want to know that will happen before I do this process if it will.
dstryrwiz said:
Understood. Just to be clear though, this overwrite doesn't result in a replacement of the data partition with a blank partition, correct?
I understand that it's technically not a wipe, but I just want to be certain by doing this process that I won't end up losing all my files and need to restore all my apps again. If I need to, it's fine, just want to know that will happen before I do this process if it will.
Click to expand...
Click to collapse
Well, standard disclaimers apply for any sort of flash operation on your phone, but no, it should
not delete anything in userdata. The first script pack should not touch it at all, and the second one
doesn't do anything other than push a file and correct permissions and selinux context.
excellent. thanks
Everything worked for me. Also looks like the Magisk patch works as well. So far no issues. Hopefully this will work with the next OTA update.
Very nice! I will probably take a shot of rooting my phone next weekend. Just got done setting my replacement phone up, and not in a rush during the week to do it again.
Update worked perfectly for me. Thanks for this!
directions are very unclear in batch for update part, says it was finished with the Super (after parsing all 12 parts) and then nothing and now when i closed out to try to do the reserve to the boot loader im getting into qualcoms crashdump mode and its saying corrupted force dump kernel_restart. Please advise.
Keepinitgreen said:
directions are very unclear in batch for update part, says it was finished with the Super (after parsing all 12 parts) and then nothing and now when i closed out to try to do the reserve to the boot loader im getting into qualcoms crashdump mode and its saying corrupted force dump kernel_restart. Please advise.
Click to expand...
Click to collapse
No, it was 'finished' with super. there are more images after that.
Can you get into either fastboot or fastbootd mode?
ntzrmtthihu777 said:
No, it was 'finished' with super. there are more images after that.
Can you get into either fastboot or fastbootd mode?
Click to expand...
Click to collapse
My apologies brother, did not realized there were more to flash. Just completed part one now to do the reserve.
Keepinitgreen said:
My apologies brother, did not realized there were more to flash. Just completed part one now to do the reserve.
Click to expand...
Click to collapse
It happens. I amended the first post to say it would reboot on its own, I thought I had,
but it was only on the second part.
ntzrmtthihu777 said:
It happens. I amended the first post to say it would reboot on its own, I thought I had,
but it was only on the second part.
Click to expand...
Click to collapse
All good man! Appreciate this dope workaround. I have intermediate experience with terminal so it's a lot of guess work haha
ntzrmtthihu777 said:
The first part is necessary if you are on any other version than 10.0.19. You would need a reserve.img dumped from 10.0.16
to ota to 10.0.19, and since most people unlocked before 10.0.19 came out, we're not likely to get ahold of reserve.img for
those versions.
Click to expand...
Click to collapse
Is this still the case? And if so, would it be useful to have access to somebody with a locked HD1925 running 10.0.16?
@ntzrmtthihu777 , I wonder how hard it would be to modify all future snatched OTAs to completely ignore reserve.img? I did see one line in the last one mentioning a specific reserve size.
jhofseth said:
@ntzrmtthihu777 , I wonder how hard it would be to modify all future snatched OTAs to completely ignore reserve.img? I did see one line in the last one mentioning a specific reserve size.
Click to expand...
Click to collapse
You would need root at a minimum, and likely a functional TWRP as well. Once you modify the OTA, it will fail the signature check.