Related
Frequently Asked Questions
Motorola Droid 4
This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Q1: How can I tell if I have a Motorola Droid 4?
1. In the software Menu>settings>about Phone>system version will include XT894.Verizon.en.US2. If you install RSD Lite on a PC, connect phone(In AP Fastboot Mode) to PC via usb, and open RSD Lite, The Droid 4 will be listed as Maserati in RSD Lite. see [Video]How to Use RSD Lite to flash a .XML Stock Rom (firmware)
Q2: What is the newest Stock Android Version and System Version?
Android: 4.1.2System Version: Blur_Version.98.72.188.XT894.Verizon.en.US
Q3: Where are the Custom Bootloaders, Recoveries, and Kernels?
Because of the Locked bootloader, the stock bootloader and Stock recovery can not be replaced, But using Safestrap the boot process can be hijacked allowing Custom Recovery, and KernelsFor more on Bootloaders see XDA Wiki: Bootloaders
Q4: Where do I find information on how to root the Droid 4?
[Root] Droid 4 (XT894) Jellybean with SafeRoot
Q5: Can I root the Droid 4 without a computer?
No
Q6: How do I restore the stock rom?
1. DROID 4 Utility XT894 Jellybean -- Windows + Mac + Linux (All In One!)2. [Video]How to Use RSD Lite to flash a .XML Stock Rom (firmware)3. Unbrick Moto device with moto-fastboot.exe
Q7: I have a question about a particular ROM but I can't post in the Development section. What can I do to get the help I need?
The Development forum is for sharing ideas on development. If you have a question about a particular ROM, ask it in the Q&A section.
Q8: How Do I use the Droid 4 on GMS?
[PATCH][GUIDE] Patch to fully enable GSM on Verizon CDMA Android phones
Q9: How Do I Install a Custom Rom?[/SIZE]
See [How To][Video]Installing Rom with SafeStrap
Q10: Where can I find a Custom Rom For the Droid 4?
see [INDEX] Motorola Droid 4 Development for List of Droid 4 Roms and more
Q11: What is a Factory Cable and why would I need one
A Factory Cable aka Motorola Factory Programming Cable or Fastboot Cable. Allows Many Motorola Devices to be flashed without a battery or Low battery for more see Motorola Fastboot/Factory Programming CablesQ12: What is a SBF?
Quote by cellzealot "SBF is a file type and stands for Single Binary File that is the older format of Motorola flash files for use with RSD lite or other flash tools.They include all of the code groups, header files, and checksums as well as a RAM Downloader for all of the device partition images in a single file and flashed from the legacy boot loader enumerated as a flash device.The new format for all dual core Motorola devices is zip archive of fastboot images and an XML file that can be used with RSD lite to flash in a single operation or flashed as individual images using the fastboot binary and DLLs in the Android SDK from the fastboot boot loader and enumerated as an ADB device.These are entirely different modes of access and operation and SBF is both wrong and a misnomer for the firmware files for current devices.The fast boot interface provides far more flexibility and safety for flashing than the old flash interface and avoids all kinds of problems that would arise from managing and updating the firmware on newer chipset devices.It is an extremely important distinction to make and understanding to have about how these phones work.Please stop using SBF when referring to XML.zip files.The current acronym for Motorola firmware files is FXZ and means Full XML ZIP file.".SBF, XML.zip and tar.gz" are Offical Motorola file extensions
Q13: Can I use the Droid 4, without activating with a carrier (WiFi only)?
Yes, see Bypassing the JB Activation Screen of any Motorola Device*Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
added [SIZE=+1]Q11: What is a Factory Cable and why would I need one[/SIZE]A Factory Cable aka Motorola Factory Programming Cable or Fastboot Cable. Allows Many Motorola Devices to be flashed without a battery or Low battery see
Motorola Fastboot/Factory Programing CablesAdded:[SIZE=+1]Q12: What is a SBF?[/SIZE]Quote by cellzealot "SBF is a file type and stands for Single Binary File that is the older format of Motorola flash files for use with RSD lite or other flash tools.
They include all of the code groups, header files and checksums as well as a RAM Downloader for all of the device partition images in a single file and flashed from the legacy boot loader enumerated as a flash device.
The new format for all dual core Motorola devices is zip archive of fastboot images and an XML file that can be used with RSD lite to flash in a single operation or flashed as individual images using the fastboot binary and DLLs in the Android SDK from the fastboot boot loader and enumerated as an ADB device.
These are entirely different modes of access and operation and SBF is both wrong and a misnomer for the firmware files for current devices.
The fast boot interface provides far more flexibility and safety for flashing than the old flash interface and avoids all kinds of problems that would arise from managing and updating he firmware on newer chipset devices.
It is an extremely important distinction to make and understanding to have about how these phones work.
Please stop using SBF when referring to XML.zip files.
The current acronym for Motorola firmware files is FXZ and means Full XML ZIP file.".SBF, XML.zip and tar.gz" are Offical Motorola file extentions
Added:
[SIZE=+1]Q13: Can I use the Droid 4, without activating with a carrier (WiFi only)?[/SIZE]Yes, see Bypassing the JB Activation Screen of any Motorola Device
Thank you!
Thanks
I have a problem at any moment after reboot it is me in the logo of CM11, install the stock from apfastboot with utility and I left after motorola logo, which could be the solution. thanks.
Enviado desde mi DROID4 mediante Tapatalk
Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!
useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!
@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.
Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.
fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.
useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.
Currently I am on Evolution X latest build and today my camera was opened but it won't close.
Now since my phone is under warranty I want to claim it.
How do I revert back to MIUI, unroot the device and remove TWRP. Please help me.
Regards
flash fastboot rom and u will revert back to stock miui unrooted.
^^ Do I need to download MIUI package or simply that command alone will work?
If yes please guide to resources I have Indian variant of K20 Pro.
shashpant said:
^^ Do I need to download MIUI package or simply that command alone will work?
If yes please guide to resources I have Indian variant of K20 Pro.
Click to expand...
Click to collapse
"Flash fastboot rom" was a sentence/direction/hint what you have to do, not a (fastboot) command
I think there is a detailed guide in the Guides section. Otherwise, you need to google about MiFlash, install to the PC, read how to use, find on xiaomifirmwareupdater an appropriate tgz/fastboot rom for your device.
I'm not on Pro, not on Indian, cannot guide you more than as above, where to start googling/reading/learning
^^ Thanks for the clarification.
I downloaded latest rom from https://xiaomifirmwareupdater.com/miui/raphaelin/ I tried both recovery and fastboot version.
I flashed the rom using twrp (is that right?) but nothing happens and devices reboots itsefl into recovery. What am I doing wrong?
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Edit - The guides mention flashing magisk. But I don't want to root as I have to claim warranty. What do I do now?
Edit 2 - I flashed magisk root but still not able to boot. It reverts back to recovery.
shashpant said:
^^ Thanks for the clarification.
I downloaded latest rom from https://xiaomifirmwareupdater.com/miui/raphaelin/ I tried both recovery and fastboot version.
I flashed the rom using twrp (is that right?) but nothing happens and devices reboots itsefl into recovery. What am I doing wrong?
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Edit - The guides mention flashing magisk. But I don't want to root as I have to claim warranty. What do I do now?
Click to expand...
Click to collapse
I wrote you to google about and to use Mi Flash, not TWRP.
Besides, I don't know if they have Linux version.
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How to Install MIUI Fastboot ROM - android file box
For some reasons you may want to completely re-install Android OS running on your Xiaomi phone either Mi series or Redmi series. While updating the ROM is simply a one-tap action through...
androidfilebox.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
etc - google for more
shashpant said:
I am also unable to locate the guide to revert back. Plus I am on Linux so that windows too might now work.
Click to expand...
Click to collapse
Actually, consult these guides for Linux:
How to flash MIUI Fastboot ROM from Linux
How to flash MIUI Fastboot ROM from Linux. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
[GUIDE][Linux] Flashing Xiaomi .tgz
Hello everyone, I recently had to flash a stock firmware file from Xiaomi (.tgz) and being primarily a Linux user I was quite disappointed by the fact that the company only provides a flashing tool for Windows. Either way, I booted into Windows...
forum.xda-developers.com
[OTA][FASTBOOT][ROM] Official Stock Fastboot image (V10.0.10.0.PDHMIXM, Android P)
Attention: To be able to flash, the bootloader needs to be unlocked (https://en.miui.com/unlock/). Please be warned though: Xiaomi changed something in the method of unlocking the device from May 2018 security update onwards. Now all data will be...
forum.xda-developers.com
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
If flashing/rooting errors out, and you end up in Qualcomm Crash Dump Mode, please perform the following:
Restart into Fastboot Mode by holding Volume Down + Power buttons until the device vibrates, then release only the power button
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Follow the steps on this site to Flash the stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
If you have trouble rebooting to FastbootD (Recovery)
Try swapping Active slots from the application (typically slot A worked for me)
Choose reboot to FastbootD
Sorry if this is a stupid question, but is this to be used when the OP 10 Pro is ALREADY on OS 13, or is this to be used when the unit is on OS 12 (not yet rooted) and you want to take it to OS 13?
Thanks for your help.
Either or would be fine.
It's an upgrade using a full OTA update.
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Not yet, but once I find one I'll upload it ASAP for the community.
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
thanks. It would be nice. good work.
Hi there, do you have for C.22?
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
There is...check this out
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
linhdanstore said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Literally look above.
Savio Dantes said:
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
Click to expand...
Click to collapse
Can you use ADB tools to restore stock rom if the device was soft bricked?
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them in the first place becomes both forgotten and obsolete, that's when I typically stop supporting them.
Savio Dantes said:
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them becomes forgotten, an obsolete, after which I typically stop supporting them.
Click to expand...
Click to collapse
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
SKNIZZY said:
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
Click to expand...
Click to collapse
Yes it does.
Fastboot enhance works fine, you need to remove the cow files first and have a valid payload.bin but that's it