rsd lite firmware help - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

hello everyone so i messed up bad. need rsd lite firmware to flash if anyone can share. all i have now is the abiliy to get into bootloader mode. Any help would be appreciated.

mikelikesbikes said:
hello everyone so i messed up bad. need rsd lite firmware to flash if anyone can share. all i have now is the abiliy to get into bootloader mode. Any help would be appreciated.
Click to expand...
Click to collapse
All factory images can be found here: http://motofirmware.center/files/category/23-droid-turbo/

having trouble getting rsd to recognize my device in bootloader, anyone recommend some drivers i can try? windows 8.1

mikelikesbikes said:
having trouble getting rsd to recognize my device in bootloader, anyone recommend some drivers i can try? windows 8.1
Click to expand...
Click to collapse
Install Motorola Device Manager from Moto's website. That will give you the drivers you need.
My advice is don't use RSDlite. To get it to work, you have to edit the xml file in the firmware that you're trying to flash to remove all the other devices that it inexplicably also includes. All RSDlite does is automate the fastboot flashing process. A better way to do it, in my opinion, is to edit the .bat file that comes with the factory images and manually input the fastboot commands that you see there. If you want more detailed directions, see my post here: http://forum.xda-developers.com/droid-turbo/help/turbo-firmware-t3254185

tried your tutorial. now for some reason i cant get fastboot to recognize my device. device manager now says "fastboot quark S" with the little triangle beside it. fastboot devices isnt showing my device is connected,but it did before i tried manually flashing like in the post you linked me to. i dont get it

TheSt33v said:
Install Motorola Device Manager from Moto's website. That will give you the drivers you need.
My advice is don't use RSDlite. To get it to work, you have to edit the xml file in the firmware that you're trying to flash to remove all the other devices that it inexplicably also includes. All RSDlite does is automate the fastboot flashing process. A better way to do it, in my opinion, is to edit the .bat file that comes with the factory images and manually input the fastboot commands that you see there. If you want more detailed directions, see my post here: http://forum.xda-developers.com/droid-turbo/help/turbo-firmware-t3254185
Click to expand...
Click to collapse
what do you mean by editing the .bat file that comes with factory images?

mikelikesbikes said:
what do you mean by editing the .bat file that comes with factory images?
Click to expand...
Click to collapse
I mean right click on the .bat file that is included in the .zip file of the firmware that you're trying to flash and select "edit." This allows you to see the commands that the .bat file does when you double click on it.
But you don't have to worry about that, because I already outlined the necessary commands in the post that I gave you a link to.

TheSt33v said:
I mean right click on the .bat file that is included in the .zip file of the firmware that you're trying to flash and select "edit." This allows you to see the commands that the .bat file does when you double click on it.
But you don't have to worry about that, because I already outlined the necessary commands in the post that I gave you a link to.
Click to expand...
Click to collapse
any idea why fastboot doesnt see my device now? it did before, but I get the yellow triangle in device manager. I have installed every driver i can find... including motorola device manager and ran it several times. Was on mofo'd 4.4.4. and for some dumb reason thought i could flash the lollipop bootloader so now i am stuck with bootloader, recovery, but no os. any advice would be great.
OK, so i finally got fastboot to recognize my device again. Trying to download stock firmware from Rootjunky. Am i correct that I extract the zip into the fastboot folder then issue the commands? I am about to pull my hair out...

mikelikesbikes said:
any idea why fastboot doesnt see my device now? it did before, but I get the yellow triangle in device manager. I have installed every driver i can find... including motorola device manager and ran it several times. Was on mofo'd 4.4.4. and for some dumb reason thought i could flash the lollipop bootloader so now i am stuck with bootloader, recovery, but no os. any advice would be great.
OK, so i finally got fastboot to recognize my device again. Trying to download stock firmware from Rootjunky. Am i correct that I extract the zip into the fastboot folder then issue the commands? I am about to pull my hair out...
Click to expand...
Click to collapse
Yep. That should be all you have to do.

Related

TWRP .img from phone?

I've recently dumped my desktop. I'm using my company's laptop despite of being very restricted.
So... because of this, i can't use adb or moto x toolkit to install TWRP. I had it installed on my phone but somehow i've messed it up. I've an unlocked bootloader, and my phone is rooted. Now i have only the .img file and no way to install it. I've tested some apps from the store, but none of them work.
Any way to install TWRP .img file from the phone itself?
pintasmapila said:
I've recently dumped my desktop. I'm using my company's laptop despite of being very restricted.
So... because of this, i can't use adb or moto x toolkit to install TWRP. I had it installed on my phone but somehow i've messed it up. I've an unlocked bootloader, and my phone is rooted. Now i have only the .img file and no way to install it. I've tested some apps from the store, but none of them work.
Any way to install TWRP .img file from the phone itself?
Click to expand...
Click to collapse
Since you say you are already rooted, try FLASHIFY from the market. It should flash TWRP Recovery for you (assuming you are indeed rooted already).
Good Luck.
if you can install the moto device drivers on the PC, you can then try to download and unzip this -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip and try mfastboot from there.
samwathegreat said:
Since you say you are already rooted, try FLASHIFY from the market. It should flash TWRP Recovery for you (assuming you are indeed rooted already).
Good Luck.
Click to expand...
Click to collapse
Thanks for your help. Tried it but it doesn't work.
KidJoe said:
if you can install the moto device drivers on the PC, you can then try to download and unzip this -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip and try mfastboot from there.
Click to expand...
Click to collapse
I can't install drivers on a restricted pc. That's my main problem.
pintasmapila said:
Thanks for your help. Tried it but it doesn't work.
I can't install drivers on a restricted pc. That's my main problem.
Click to expand...
Click to collapse
Bummer.
No one has made a flashable zip for TWRP for Moto X yet....mostly because fastboot is so much easier. In the past (on other devices), you could often flash the recovery zip file from the bootloader - this would make fastboot unnecessary.
Since we don't have a flashable zip (only the .img), I can only suggest that you use a different computer that isn't restricted. Sorry, but it seems that will be your only option.
And lastly, when you DO find a computer that you're able to use, be sure to flash the recovery with 'mfastboot' and not the standard 'fastboot'.
samwathegreat said:
Bummer.
No one has made a flashable zip for TWRP for Moto X yet....mostly because fastboot is so much easier. In the past (on other devices), you could often flash the recovery zip file from the bootloader - this would make fastboot unnecessary.
Since we don't have a flashable zip (only the .img), I can only suggest that you use a different computer that isn't restricted. Sorry, but it seems that will be your only option.
And lastly, when you DO find a computer that you're able to use, be sure to flash the recovery with 'mfastboot' and not the standard 'fastboot'.
Click to expand...
Click to collapse
Yeah, i guess you're right.
Thanks man

Revert to stock after MOFO Root

To revert completely back to stock
The rootjunkysdl website. http://rootjunkysdl.com/?device=Droid Turbo&folder=Firmware
It's in the firmware section for the Droid Turbo
Download it, unzip it, run the .bat file while in fastboot mode, wait for the magic.
kevinmr82 said:
To revert completely back to stock
The rootjunkysdl website. http://rootjunkysdl.com/?device=Droid Turbo&folder=Firmware
It's in the firmware section for the Droid Turbo
Download it, unzip it, run the .bat file while in fastboot mode, wait for the magic.
Click to expand...
Click to collapse
Thanks, what firmware does this flash? It shows "21.128-15" in the file name so I am just wondering. The latest is 21.44.12.quark_verizon.en.us.
21.21.15 The original firmware from the October, 2014 release
kevinmr82 said:
21.21.15 The original firmware from the October, 2014 release
Click to expand...
Click to collapse
Oh yeah, thanks! I just downloaded it and opened it up. This will flash literally everything from radios to the bootloader to system. Thanks now I have it just in case.
Edit: bootloader stays modified...
where can i find 21.44.12?
Edit: do i flash through rsdlite or mofo?
I have been unable to find that version myself. You don't use RSD or MOFO. After you unzip the file look for the .bat file. Put your phone in recovery mode and open the .bat file. It will flash on its own.
kevinmr82 said:
I have been unable to find that version myself. You don't use RSD or MOFO. After you unzip the file look for the .bat file. Put your phone in recovery mode and open the .bat file. It will flash on its own.
Click to expand...
Click to collapse
Thanks for the reply... I actually messed up my recovery file so I couldnt go that route... luckily it was easy as fastboot flash recovery recovery.img after getting the correct file
Is there any way to get an unrooted system.img to flash with mofo? I'm trying to 'unroot' my phone and keep the modifications I have made, so I can continue using the apps that don't allow me to use them when I'm rooted (Barclays Mobile Banking and Pingit)
That I'm unsure of, have you tried any of the root cloaking apps in the Play Store?
kevinmr82 said:
That I'm unsure of, have you tried any of the root cloaking apps in the Play Store?
Click to expand...
Click to collapse
Yes, they don't work. I tried removing su and superuser.apk, but still no luck. It won't probably work, but I'd like to try, see the differences between a rooted and an unrooted system.img, also see if these apps work on a 'flashed' system.img that is unrooted...
I'll keep trying to convert the system.img_sparsechunk* from the stock rom into a mofo flashable system.img... If I can't do it then I'll open a thread asking for a dd from an unrooted system partition

HELPPP!

So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Edit: I have a feeling its due to a driver issue... during the downgrade the required driver probably changed... and thus disconnected in the middle of flash. If this is the case, then I feel like an idiot
diabl0w said:
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Click to expand...
Click to collapse
Try setting up another computer. You should be able to go into bootlader mode by pressing power and volume down buttons at the same time. Hopefully you have enought battery. If that doesnt work someone should be able to help you out.
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
r3pwn said:
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
Click to expand...
Click to collapse
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
diabl0w said:
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
Click to expand...
Click to collapse
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
r3pwn said:
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
Click to expand...
Click to collapse
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
diabl0w said:
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
Click to expand...
Click to collapse
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
r3pwn said:
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
Click to expand...
Click to collapse
I realized that after I downloaded the file and took a look at it further... thanks for your help and for bearing with me. It worked!

Nexus 6, Deleted System Partition- Cannot Recover

The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
evan7899 said:
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
Click to expand...
Click to collapse
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
simms22 said:
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
Click to expand...
Click to collapse
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
evan7899 said:
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
Click to expand...
Click to collapse
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
simms22 said:
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
evan7899 said:
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
Click to expand...
Click to collapse
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
simms22 said:
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
Click to expand...
Click to collapse
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
evan7899 said:
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
Click to expand...
Click to collapse
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
simms22 said:
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
Click to expand...
Click to collapse
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
evan7899 said:
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
Click to expand...
Click to collapse
honestly, I wouldn't know what you need on a Mac to get it working :angel:
simms22 said:
honestly, I wouldn't know what you need on a Mac to get it working :angel:
Click to expand...
Click to collapse
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
evan7899 said:
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
Click to expand...
Click to collapse
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
You need to run sudo fastboot insertcomand on Mac. good luck.
simms22 said:
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
Thanks but we have tired that. Due to distance this has all had to be over the phone which hasnt helped either. I will update this with how we got it working when we do.

Attempt to unbrick Axon M with provided Firehose and Firmware files.

As stated above, I am trying to unbrick my Axon M with the firehose provided by Unjustified Dev. and firmware from deadman96385. When I tried using QFIL, even placing everything in its own directory on the root of the PC with no spaces in file names, it would get stuck when flashing. And whenever I tried to use MiFlash, I would get the error:"couldn't find flash script" when I selected the firmware folder. Any help is much appreciated.
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
ehsan96696 said:
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
Click to expand...
Click to collapse
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
boot
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
ff7cloudsnobody said:
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
Click to expand...
Click to collapse
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Drakosha said:
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
Click to expand...
Click to collapse
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
ehsan96696 said:
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Click to expand...
Click to collapse
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
Click to expand...
Click to collapse
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
Click to expand...
Click to collapse
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
ehsan96696 said:
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
Click to expand...
Click to collapse
Weird but awesome that it worked
Drakosha said:
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
Click to expand...
Click to collapse
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Root
ff7cloudsnobody said:
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Click to expand...
Click to collapse
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Drakosha said:
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Click to expand...
Click to collapse
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
ff7cloudsnobody said:
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
Click to expand...
Click to collapse
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Drakosha said:
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Click to expand...
Click to collapse
Doing the unpatched boot with security removed works, so this must be something that is in a subsection of boot.img other than build.prop. I'll have to look at what magisk changes, see what other locks ZTE has inside the image, and go from there.
edit: at this point, this conversation is not related to the post. If I make a breakthrough then I will make a new thread.
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Hi all
I need Loader please for this AT&T Z999 model
the one I found in this publication did not work for me : https : // forum.xda-developers.com/axon-m/how-to/rom-zte-axon-m-stock-firmware-firehose-t3909847
I just wish this method would work to update the AT&T Axon M from B30 to B37.
tj65 said:
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Click to expand...
Click to collapse
Are you able to provide the firehose that you used?
I tried the B37 and the firehost from this link https://forum.xda-developers.com/t/rom-zte-axon-m-stock-firmware-firehose.3909847/
along with the miflash from this link https://forum.xda-developers.com/t/edl-a2017-a2017u-emergency-dl-mode-twrp-unlock-upgrade.3553514/
But it always fails.
It will simply give an error of "Cannot receive hello packet"
then it will eventually go to the error of
"Object reference not set to an instance of an object."
I am using an AT&T Z999 that is on B30, and I am trying to get it updated to B37 (currently not looking to root or anything else, just want to update without having to have active AT&T service.
Edit: I think I found the right one. https://forum.xda-developers.com/t/...-unofficial-twrp-recovery-for-axon-m.3959314/
So far, copying that firehose file into the B37 folder seems to be allowing it to flash.

Categories

Resources