Database Develop

[Guide] Safestrap on xt883

I believe should goes to development section, but i don't have enough premisson.
Sorry but I worte down this in hurry, i'll provide more details and needed files later
Inspired by doveOrz 's post: http://forum.xda-developers.com/showthread.php?t=1474775, I try to workaround safestrap on xt883.
One major difference between xt883 and xt862 (I believe they have the same hardware) is the partition table, xt862 have about 2Gb /data and 500 Mb /preinstall while xt883 have 2.5Gb /data and a unused 512kb /preinstall. Safestrap use the /preinstall as the secondary system, this is why it doesn't work on xt883.
At first i try to repartition using parted or fdisk, but it just mess things up... Until I realized that MOTO just flash in the partition table, but not accutaly partitioning the disk.
Howto:
1. Download the xt883 (2.3.4 57.1.60) & xt862 SBF file (easily found in development section) and uncompress them.
2. copy the xt862's cdt.bin, mbr, and ebr and replace the xt883's, modify the corrsponding "MD5" value in xt883's xml file.
3. copy the xt862's allow-mbmloader-flashing-mbm.bin, mbmloader.bin, and mbm.bin to xt883, add the following on the top of <steps> section in xml file:
HTML:
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="1c5fe78a10bb79533934015b8eaddf8b" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="b09feb246298ca721e2ae6b3becdd1b4" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="6e062a68fe054ec128d4b253f1f3bd19" />
<step operation="reboot-bootloader" />
4. Optional. copy xt862's preinstall.img to xt883, and add following to the bottom of <steps> section in xml file:
HTML:
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="c91a9cc7746732888e75483f9449cd8a" />
I believe it will make the /preinstall partition ready to use, or else you'll have to make filesystem manually, but didn't tested.
5. use RSD Lite the flash in the modified "SBF"
6. Boot the phone, dial *#*#2468#*#* and reboot， now you unlock the gsm/wcdma
7. reboot to recovery, flash the gapps for xt883
8. in recovery, install the 2.3.6 (60.3.250) update. reboot
It should be ok the directly modify and flash the 2.3.6 sbf, but rumors says that it cannot unlock the gsm/wcdma and have difficulity installing gapps in 2.3.6, so i flash 2.3.4 and do the update.
9.root it with the D4 root exploit, and install safestrap (i recommand the 1.08d console version).
10. Optional, if you skipped step 4. Reboot to the recovery, open adb shell (contained in the d4 root exploit) or the console from 1.08d, input these command:
Code:
mkfs.ext2 /dev/block/mmcblk1p23
tune2fs -j /dev/block/mmcblk1p23
Maybe xt860/me863 users can use the same techique.
It's Done.
=============================
about cm9, and maybe other xt862-based roms:
after flash the roms in safesystem, replace the /system/lib/libmoto_ril.so with xt883's, edit /system/build.prop, changes:
ro.mot.eri=1 >>> ro.mot.eri=0
ro.cdma.nbpcd=1 >>> ro.cdma.nbpcd=0
ro.telephony.gsm-routes-us-smsc = 1 >>> # ro.telephony.gsm-routes-us-smsc = 1
ro.cdma.home.operator.isnan=1 >>> # ro.cdma.home.operator.isnan=1
find ro.kernel.android.ril=yes, and append these 2 lines：
persist.ril.rssi.enable.param6 = 1
persist.ril.baudrate=230400
many thanks to dmc_universe

can this be simplified to just fix the partition table without flashing xt883.

Does anyone try this need help ?

does anybody have the gapps file? i've got safestrap to work on droid 3. put the chinese rom but no gapps.

chagla said:
does anybody have the gapps file? i've got safestrap to work on droid 3. put the chinese rom but no gapps.
Click to expand...
Click to collapse
refer to this post -http://forum.xda-developers.com/showthread.php?p=35126235#post35126235
yea above method works , m using the modified version of 862 and 883 rom.

Yes please
NIGHTMARE- said:
Does anyone try this need help ?
Click to expand...
Click to collapse
the flashing process fails on step 6/18. any ideas ?
thanks : )

I need help
Hamza.abdulwali said:
the flashing process fails on step 6/18. any ideas ?
thanks : )
Click to expand...
Click to collapse
Hello everyone,
How do I know I need to do this safetrap procedure?
I bought an unlocked XT862 and was following this thread,
http://forum.xda-developers.com/showthread.php?t=1249720&page=24
and someone pointed to your thread.

[Q] Variable not supported! message when trying to flash recovery

Hi there i've successfully unlocked bootloader
but i'm unable to flash CWM onto device
When I try (i'm on windows) i get the following message
D:\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\pla
tform-tools>fastboot flash recovery recovery-razri-try9touch.img
(bootloader) Variable not supported!
target reported max download size of 104857600 bytes
sending 'recovery' (6926 KB)...
OKAY [ 1.034s]
writing 'recovery'...
OKAY [ 1.232s]
finished. total time: 2.268s
D:\adt-bundle-windows-x86_64-20130717\adt-bundle-windows-x86_64-20130717\sdk\pla
tform-tools>
Note: i do not have SD card installed - is it a requirement to have SD card in order to flash recovery ?
Can anyone help
Regards

Is anything about getVar or similar?
If yes, maybe line 11 from .xml file. Then go there and delete that line and try again.
If not, please give us more information.

jeanmoretto said:
Is anything about getVar or similar?
If yes, maybe line 11 from .xml file. Then go there and delete that line and try again.
If not, please give us more information.
Click to expand...
Click to collapse
Sorry i'm confused by what you mean on .xml?
I have no xml file??
Just the recovery and the apk files.
recovery in the directory with adb

Tiger33 said:
Sorry i'm confused by what you mean on .xml?
I have no xml file??
Just the recovery and the apk files.
recovery in the directory with adb
Click to expand...
Click to collapse
When you mention "(bootloader) Variable not supported!" I was think that you are using a .xml file to do "something".
I had a problem when try to unlock my device with a similar message, then go to .xml file and remove the getVar line that always stop the process.
I was think that you has some problem.
Sorry if not.

[Q] TWRP flash via Fastboot failing

I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so.
Code:
fastboot flash recovery twrps.img
sending 'recovery' (4822 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5.
Need help to flash the TWRP and begin using JB roms.

YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.

giveen said:
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
Click to expand...
Click to collapse
Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.

Help with moto x

I tried to manually flash back to stock 4.4.2 (so I can upgrade to 4.4.3) on my moto x but whenever I type the command "mfastboot flash system system.img" I get "invalid sparse image chunk count. The rest of the commands worked. Now my phone is stuck in the unlocked bootloader screen and I don't know what else to do. Help please?

Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app

serophia said:
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Where would I get the latest version?

http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip

KidJoe said:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
Click to expand...
Click to collapse
Thanks for the link. I used it and I still got the same error.

Make sure you are using the system.img from the correct firmware. Below is a link to the Moto model firmwares. Download the right one, unzip the files until you get to the .img files and use that system.img.
Motorola Firmwares

I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated

n0obpr0 said:
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
Click to expand...
Click to collapse
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.

samwathegreat said:
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
Click to expand...
Click to collapse
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s

n0obpr0 said:
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
Click to expand...
Click to collapse
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0

samwathegreat said:
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)

n0obpr0 said:
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
Click to expand...
Click to collapse
That's what were here for to help others xD
Sent from my XT1053 using XDA Free mobile app

(((SOLVED)))bricked phone failed <remote: sparse flash write failure>

Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it

IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?

Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)

xtcislove said:
Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)
Click to expand...
Click to collapse
I don't think this would work since all of this happened because I tried to overwrite both recovery and recovery2 with twrp which ended up soft bricking my phone. So basically the only thing that would flash is the recovery, recovery2 and boot images.

felroric said:
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?
Click to expand...
Click to collapse
Yes, I did.
You have to flash the same version of Android you wiped before.
It happened with me when I wiped N system then I tried to install MM, the solution was just flash N system.

IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
You get error every time cause your frp is lock

Rafa Mistry said:
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
You get error every time cause your frp is lock
Click to expand...
Click to collapse
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package

IDontKnowAnythingAtAll said:
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package
Click to expand...
Click to collapse
Your twrp is installED?

Rafa Mistry said:
Your twrp is installED?
Click to expand...
Click to collapse
Well, My phone is working now. But yeah I had twrp

IDontKnowAnythingAtAll said:
Well, My phone is working now. But yeah I had twrp
Click to expand...
Click to collapse
I have the same problem. How did you fix it?