Database Users

[HOWTO]Install zKernel on Wolfbreak's TW 007.1 ROM [UPDATE-THIS THREAD IS NOW OLD]

UPDATE: WOLF HAS RELEASED TW 007.2 THAT INCLUDES THE zKernel.
Thanks to that, the process is much more simpler now. Just flash the files as it says in the Wolf thread.
Mods, please close this. Thanks to all who used this and hopefully this helped you in 007.1

hey thanks for posting this...
i will link up to this from the kernel thread...
btw u should also mention this:
>>
if u have previously used the wifi patch wifi_bt_fix-fxk_froyo_v01.1.zip please remove it using remove_fix_v01.1.zip and try using this test kernel
<<

will do..can i plz have a link to the remove_fix_01.1.zip? Thanks

kantk20111 said:
will do..can i plz have a link to the remove_fix_01.1.zip? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1077437

Thanks...guide is updated

3.Go to settings-About phone. If, under kernel version, it says anything other than "2.6.29-zKernel-23062011 [email protected]#1", then you will have to do this.
Navigate to system/kernel using root explorer or similar app. DELETE boot.froyo.img, and RENAME boot.img to boot.froyo.img. Restart.
If it shows that kernel version, then skip this step.
Click to expand...
Click to collapse
Thanks a lot for this awesome guide. Im sure it will be very helpful to many users.
I followed ur guide to install custom kernel on WB TW007 with baseband .67.
But Im stuck on step 3. After flashing boot.img in Xrec I couldnt see custom kernel version in About Phone so I navigated to system/kernel using root explorer. There was only just one file named boot.img. So I renamed it to boot.froyo.img, rebooted but still get the stock kernel version in About Phone
Any kind of help will be greatly appreciated

digital_ism said:
Thanks a lot for this awesome guide. Im sure it will be very helpful to many users.
I followed ur guide to install custom kernel on WB TW007 with baseband .67.
But Im stuck on step 3. After flashing boot.img in Xrec I couldnt see custom kernel version in About Phone so I navigated to system/kernel using root explorer. There was only just one file named boot.img. So I renamed it to boot.froyo.img, rebooted but still get the stock kernel version in About Phone
Any kind of help will be greatly appreciated
Click to expand...
Click to collapse
hmm...I'm assuming that you have Stock kernel, right?
First, try re-flashing the boot.img file, but first wipe cache partition and wipe dalvik cache, then do the whole replacement an renaming. If that doesn't work, then try this:
(Thanks Haldi4803)
3. Restart Phone and enter X Recovery: Install first: "chargemon_FXRec_default_CUSTOM.zip" and then "bootloader_bypass_files_v2.zip"
Then, install the kernel on top of that while still in xRecovery. So, you would have installed all 3 files together . Please report back if it works so I can add this step in the OP.

^ Yes! Im on stock kernel. Sorry for not being clear.
Aiight. Im trying what u said right now and will report back.
EDIT: Nope. Nothing worked. Flashing all 3 files didnt work. On the other hand phone started lagging like hell after flashing. Its not responsive at all and Im constantly getting FC on System Process etc
Any thing else??

Hi everyone, dude, I tried follow u tutorial, but this didn't work (ok ok, I'm noob, i tried start this with Stock kernel...). Then I installed TW007.1 with Custom Kernel and didn't appears Custom kernel.. ok, i tried to install Z's custom kernel, following u tutorial and nothing again
What should I do?????

digital_ism said:
^ Yes! Im on stock kernel. Sorry for not being clear.
Aiight. Im trying what u said right now and will report back.
EDIT: Nope. Nothing worked. Flashing all 3 files didnt work. On the other hand phone started lagging like hell after flashing. Its not responsive at all and Im constantly getting FC on System Process etc
Any thing else??
Click to expand...
Click to collapse
u were most probably using xRecovery... flash FreeXperia recovery using FLASHTOOL and then try those files...
BTW if u use "chargemon_FXRec_default_CUSTOM.zip" then u dont need to do any renaming cause that files uses standard boot.img file name
cat /system/kernel/boot.img > /proc/splboot/boot_img

^ For some reason my Xrec is broken and I cant get into Xrec so I tried to install Rec thru Flashtool. It isnt working either
Insall Recovery option is disabled. I click on Ask Permissions, it says allow Superuseraccess on the phone but nothing happens on the phone. I cant do anything on the phone as it keeps FC Process System. It sometimes even doesnt detect USB conncetion
Is the SEUS repair the only option???

digital_ism said:
^ For some reason my Xrec is broken and I cant get into Xrec so I tried to install Rec thru Flashtool. It isnt working either
Insall Recovery option is disabled. I click on Ask Permissions, it says allow Superuseraccess on the phone but nothing happens on the phone. I cant do anything on the phone as it keeps FC Process System. It sometimes even doesnt detect USB conncetion
Is the SEUS repair the only option???
Click to expand...
Click to collapse
sadly, yes. I'm sorry about your phone, I wasn't sure if it would work with the stock kernel. another option could be to install the 3. 52 kernel first before following my instructions, or wait for wolf to officially release a kernel.
again, sorry about causing you to do a full repair

Na u dont need to be sorry. U were trying to help. I might've done something wrong or it was a bad day for me after all. Im repairing thru SEUS right now. Might give it another try in a day or two if WB doesnt officially release a Zkernel supported version of his rom.
But thanks once again for everything and keep up the good work

To those on the stock kernel,
Try to install the 3.51 kernel first, found here, then follow my instructions.
You won't get signal after installing the 3.51 kernel but that's ok, since it's meant for BB52 anyway. Your BB might become unknown as well.

That's what I do on a fresh install
Get baseband .67 first then
1) Fresh install TW007 stock kernel
2) Reboot and check for signal
2) Flash 007.1 update
3) Reboot
4) Flash transparent add-on (Optional)
5) Reboot
6) Flash zKernel_22062011.zip
9) Reboot and you will have the custom kernel but system keep on crashing and no signal
10) So I just reboot and flash this two files by DoomLord
Download link: (boot.img only)
http://www.mediafire.com/?vj9p2xy4p4w24ay
[VIMP NOTE FOR FROYO USERS who do not see any change in custom kernel after flashing the boot.img]
Download link: (wifi.ko module only)
http://www.mediafire.com/?lmh46quh490mzme
VERIFIED WIFI WORKS!
11) Signal is back and system doesn't crash
12) Reboot
13) Flash Contacts_ProSE _FIXED.zip & fb.zip
Thanks to them.
Everything is working. Use cpu master to overclock, it sometime give WLOD though

@gohwh1
u have linked to slightly older files...
i have posted updated kernel 23062011 based on FreeX10 ramdisk... which should work without any issue...

DooMLoRD said:
@gohwh1
u have linked to slightly older files...
i have posted updated kernel 23062011 based on FreeX10 ramdisk... which should work without any issue...
Click to expand...
Click to collapse
If that's working for me, I don't have to change right? Only problem is when overclocking to 1113mhz and playing games, it will WLOD when it's get too hot. Playing games for 3hrs non-stop and only one WLOD is normal right?
The updated kernel will not fix that right?

gohwh1 said:
If that's working for me, I don't have to change right? Only problem is when overclocking to 1113mhz and playing games, it will WLOD when it's get too hot. Playing games for 3hrs non-stop and only one WLOD is normal right?
The updated kernel will not fix that right?
Click to expand...
Click to collapse
thats wht it might!
please do try!

DooMLoRD said:
thats wht it might!
please do try!
Click to expand...
Click to collapse
Is it zKernel_freeX10_aZuZu_23062011.zip?
So I just have to flash it over current? Will flash it tommorrow, it's almost 3am here.

gohwh1 said:
Is it zKernel_freeX10_aZuZu_23062011.zip?
So I just have to flash it over current? Will flash it tommorrow, it's almost 3am here.
Click to expand...
Click to collapse
no this one:
zKernel_23062011 with FreeX10-beta4 ramdisk
http://forum.xda-developers.com/showthread.php?p=15170924#post15170924

STEP BY STEP How to install CM7.1.0 - FreeXperia Project

streamnlnl said:
Sorry for the late reply , I just see those post.
I haven't a x10 anymore. I have a arc S now.
So i don't read all the post on the x10 tread. I can't help anymore with the most question . But I have a idea. Just copy past my first post (or edit to your liking) and open a new tread. That person must be someone that actually can help.
If that is done, let me know so I can contact a mod and close this tread.
It hoe if I have helped somebody.
Greets Streamnlnl
Click to expand...
Click to collapse
After seeing the same question over and over again, I'm going to try to make a step by step guide for install this ROM.
So that the main tread will be as clean as possible.
In the second post, I will post tips and the most commen Q & A.
If you want to discuss about this ROM, please do that here
Now let's get started...............
First you need to unlock your boatloader.
You can read and ask ALL of your questions about unlocking here
(If you don't have a unlocked boatloader, there is a solution for that. But I suggest to unlock your boatloader. FXP team make this for unlocked bootloader. So you be warned. If you still want to install this with a locked bootloader, I suggest to go to cobrato tread, thank him for this.)
When you have a unlocked bootloader you are good to go to install this beautiful ROM .
THE ROMS ARE NUMBERED BY WEEK NUMBER.
I call the ROM FXP(week number), because I don't always have time to keep this up_to_date. Sorry for that!
Download the 2 files in this post (FXP(week number) & GAPPS ADDON)
FXP(week number) will be called something like this: update-cm-7.2.0-RC0-es209ra-KANG-signed
There are 3 files in update-cm-7.2.0-RC0-es209ra-KANG-signed
#Flashtool
#FXP(week number)
#unlock
Unzip those files on your PC
Put the map FXP(week number) (The one you just unzipped) and GAPPS ADDON (the one you have download at the start) somewhere on your SDcard.
Open flashtool and run the X10FlashTool.exe
No press Flash.
You will see just one file.
#x10i
Now flash that one, with this you will get the CWM.
After this reboot your phone en press repeatedly on the back button till you enter CWM.
Here you do:
1) wipe data/factory reset
2)wipe cauche partition
3)advanced ====> wipe Dalvik Cache
Now you can install the ROM:
1)Install zip from SDcard =====> choose zip from sdcard ===> and then go to the place where you have left FXP(week number) on your sdcard.
2)install now GAPPS ADDON, the same way you have install FPX(week number).
When it's done reboot your phone and enjoy
If I have write something what isn't correct.
PM me and I will edit it correctly.
To keep this up-to-date, also PM me for the bugs or tips.
So that I don't need to read every single post.
Thanks in advance
.

Tips:
# For faster bootup, just add this line in build.prop:
Code:
debug.sf.nobootanimation=1
Also, if you experiences battery drainage, simply change your governor from performance to ondemand (thanks to Hzu)
# For settings and explanation about CyanogenMod Settings look here
and for the standard home screen (adw-launcher) look here
Q&A:
Q: What are the changelog for latest version?
A: at the time of writing it's version FXP030 and you can look for the changelog here
Q: Is there any ETA for the next version?
A No, but if you want you can contribute here
Q: I really want to thank the dev, how can I do that?
A: You can hit the thank you button on his post,
or you can donate here
Q: Are there more pics about this ROM available?
A of course, You can look here , here or here
Q: Can I use Rom Manager with this Rom?
A: Yes you can
Q: Are all of the cm settings available
In this rom?
A:Yes
Q:
A:
.

Great job!!!!

For faster bootup, just add this line in build.prop:
Code:
debug.sf.nobootanimation=1
Also, if you experiences battery drainage, simply change your governor from performance to ondemand.
I found this from the past few releases and some people complained about battery drainage so I tried to find the source and this is what I found.
J said they set it to performance so that the phone will be faster and easier to test out features.
Sent from my X10 using XDA App

Maybe someone here can help me. I've followed those instructions but when I go to CWM based recovery and pick install from sd card it keeps saying cannot mount /sdcard
xrecovery on the other hand reads it just fine.
Maybe this is related to other roms not detecting my sd card.
Any suggestions?

Has anyone tried to flash dooms fxp for unlocked bootloaders with CM7??

which version of cwm do i use?? im using doomlords kernel where it has two versions of cwm and xrecovery

fcb1 said:
which version of cwm do i use?? im using doomlords kernel where it has two versions of cwm and xrecovery
Click to expand...
Click to collapse
Read the op mate, it tells you how to install the rom, the part that says flash the fxp firmware with flashtool will give you the correct recovery, you can not use Dooms cwm's as you also need the kernel in FXP.
From the op....
Now flash FXP, with this you will get the CWM.
Click to expand...
Click to collapse

Any ideas guys? I even flashed back to 2.1 and started over but in CWM I keep getting can't mount /sdcard

Can you please give us some more info?
What exactly have you did?
Like, do you have a unlocked bootloader? Did the flashtool say that it was successful?
What kind of baseband do you have. Etc etc.

streamnlnl said:
Can you please give us some more info?
What exactly have you did?
Like, do you have a unlocked bootloader? Did the flashtool say that it was successful?
What kind of baseband do you have. Etc etc.
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader. The Free Xperia screen comes up and I press the back button to get into recovery.
I'm running the .71 baseband and have had no problems flashing from flashtool.
Before I was running a custom 2.3.3 rom and I unlocked the bootloader, flashed in the FXP custom kernel and got the same problem of mounting sd card in recovery.
I just went back to stock 2.1 (This rom reads my sd card just fine), flashed .71 baseband, flashed FXP kernel and still got the same error when I entered recovery to install custom zip.

Why mounting sdcard?
If you put the right files before flashing on your card. You don't need to mount your card.
Can you access your card trough the menu?
Install zip from sdcard?
Edit.. i was reading your latest post on xda and are you sure that you have successful unlocked your bootloader/
in HOW-TO]UNLOCK bootloader for X10 you find a tool in the second post (s1tool.7z).
If I rember it correctly, when you run it you can see 2 different things in the fist line
RUNNING S1_EROM VER "R8A013" ======> locked bootloader
or
RUNNING S1_EROM VER "r8A013" ======> unlocked bootloader
(can anyone confirm this?)
@takerfan you got a PM

streamnlnl said:
Why mounting sdcard?
If you put the right files before flashing on your card. You don't need to mount your card.
Can you access your card trough the menu?
Install zip from sdcard?
Click to expand...
Click to collapse
That's the thing, when I go to install custom zip from the menu it gives me an error that says "Can't mount /sdcard"
edit: Yes, I ran the tool and the r was lowercase. I even did recover to relock the bootloader and the R became uppercase and I again unlocked it.
edit2: I think I should mention this..whenever I flash a 2.3 rom whether it's stock or custom, the rom does not detect my sd card. Once I go back to 2.1 it does. Do you know why this is the case?

Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.

jusiek said:
Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.
Click to expand...
Click to collapse
That is nothing, ignore the message.
takerfan said:
That's the thing, when I go to install custom zip from the menu it gives me an error that says "Can't mount /sdcard"
edit: Yes, I ran the tool and the r was lowercase. I even did recover to relock the bootloader and the R became uppercase and I again unlocked it.
edit2: I think I should mention this..whenever I flash a 2.3 rom whether it's stock or custom, the rom does not detect my sd card. Once I go back to 2.1 it does. Do you know why this is the case?
Click to expand...
Click to collapse
Try unmounting the sd card from mounts & storage menu in recovery and choose install zip from sdcard again. See if this helps.
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
xXHITMANXx508 said:
Has anyone tried to flash dooms fxp for unlocked bootloaders with CM7??
Click to expand...
Click to collapse
Yep, works fine here.

jusiek said:
Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.
Click to expand...
Click to collapse
It's because you haven't unlocked your bootloader, the phone would not allow you to flash unsigned .sin files, which means you can't flash the FXP kernel.

jusiek said:
Hi,
Let me know what I do wrong.... despite of turning ON debbuging in settings options during FXP flashing via Flash Tool I,ve got permanently error " turn on debbiging...." but It is already done.
What should I do to make a progress.... baseband .71, bootloader loocked.
Click to expand...
Click to collapse
Are you saying that after flashing the kernel it still says turn on debugging bla bla? That's normal. See if it shows freexperia upon turning on your phone.
If not, then you have not unlocked your bootloader.
Sent from my X10 using XDA App

Hzu said:
That is nothing, ignore the message.
Try unmounting the sd card from mounts & storage menu in recovery and choose install zip from sdcard again. See if this helps.
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
Yep, works fine here.
Click to expand...
Click to collapse
In mounts and storage it only gives me the option to mount sd and when I select that it gives me the same error. Xrecovery works fine but I can't flash cm7 with that.

I've made the leap and installed this ROM. First of all I want to say how brilliant it is and it'll obviously only get better. I've also installed FXP28 on my wife's x8 with similar results. Great work FXP team!
So on to my problem... when I go to bed my phone has switched itself off and my alarm hasn't gone off. When I switch it back on there was still 20 odd % battery remaining. This has happened twice. I've been running the govener on 'on demand'. One thing that is odd is that the phone has a flashing green light which presumably means it is in fact not off. The only way to wake it up though is to hold the power button.
Does anyone have any suggestions? Thanks.

Ok. Another problem. Cannot get wifi tether to work at all... also USB tethering doesn't work and could only get barnacle to work with no security.
Is anyone having success with tethering.
PS. I never had a problem with my previous rom - Wolf's!
Sent from my X10i using XDA App

Root D6603 on .77 by downgrade, no data wipe

I managed to use giefroot root my D6603 (US version) on firmware 23.0.1.A.5.77 by downgrading to 23.0.A.2.93 without wiping the whole /data.
This is what I did: (Try at your own risk!)
1 Backup the contacts first. The contacts data will be cleared.
2 Use Flashtool to flash D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Uncheck wipe DATA.
3 Restart the device. There will be lots of annoying force close popups. For me, only two packages were reported closing: android.process.acore and android.process.media. USB debugging doesn’t work either.
4. Just close the popups and go to Settings – Apps – All. Find “Media Storage” and press “clear data” to get rid of FCs of android.process.media. USB debugging should work now.
5. Find “Contacts Storage” and press “clear data”. No more FCs of android.process.acore.
After this, no more FC popups for me. It looked normal on fw 2.93 and I tried many times to use giefroot v2 but failed. It seems like that the system exploit app CVE-2014-7911 will crash android.
6. I tried clearing data of more apps. After clearing ApplicationSettings and ConfigUpdater, giefroot v2 worked! I don’t know which one is the key. Can anyone confirm?
Hope it's helpful for you.
Thanks again! @zxz0O0

I followed your steps and after a few tries i got root. The only thing i did diferrent was that i enabled "Allow mock locations" and it worked.
Thanks @zxz0O0

carasd said:
I followed your steps and after a few tries i got root. The only thing i did diferrent was that i enabled "Allow mock locations" and it worked.
Thanks @zxz0O0
Click to expand...
Click to collapse
Yes, you are right. After my steps, one still needs to follow the instructions of giefroot by zxz0O0:
How to use
Download the tool (latest version) and extract it
Start your device and plug it to your computer
Put your device in air plane mode
Run install.bat and follow the instructions on screen
Congratulations! You should now be rooted. If you get an error "Device not rooted", try running the tool a second time.
Click to expand...
Click to collapse

It worked
This works like a charm. I followed every step to the T and im rooted. Awesome Job.

It worked
thanks for this useful tip. Step 6 was not needed with D6603_23.0.A.2.98_Customized_20DE.ftf and giefroot v2.

I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?

lalala2003 said:
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
Click to expand...
Click to collapse
There's already a pre-rooted version which you can flash in recovery

Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
---------- Post added at 09:45 PM ---------- Previous post was at 09:25 PM ----------
omnikai said:
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
Click to expand...
Click to collapse
I seem to have gotten around this for now by using adb push to copy the file to the /tmp folder of my device. I still can't access internal storage, which is a pain, but at least I can finish the steps to get back to .77 (and hopefully Lollipop soon!).

omnikai said:
Thanks for this guide!
The only problem I'm having is, once rooted and with the dual-recovery installed, I can't decrypt my device in TWRP. It asks for my password, but tells me it's wrong and just asks for the password again. If I choose 'cancel' it continues but won't load anything off my sd card/internal. So I can't flash the update to .77
Anyone know why this might be?
---------- Post added at 09:45 PM ---------- Previous post was at 09:25 PM ----------
I seem to have gotten around this for now by using adb push to copy the file to the /tmp folder of my device. I still can't access internal storage, which is a pain, but at least I can finish the steps to get back to .77 (and hopefully Lollipop soon!).
Click to expand...
Click to collapse
Sorry that I know nothing about the decryption. After a quick search, it seems to me probably a bug of TWRP (github.com/TeamWin/Team-Win-Recovery-Project/issues/247).

lalala2003 said:
I've heard that you can create a pre rooted version of the latest update, is this possible or will I have to stick with the downgrade?
Click to expand...
Click to collapse
Yes. Once you root your phone and have the dual recovery installed, you can use the pre rooted image to upgrade to the latest version and keep root.

hi
hello sir. i deleted everything on your step. now i cant access my wifi. how can i return it again? thanks. noob here.

nivek4th said:
hello sir. i deleted everything on your step. now i cant access my wifi. how can i return it again? thanks. noob here.
Click to expand...
Click to collapse
Flash a FTF file but exclude the system

hi
gregbradley said:
Flash a FTF file but exclude the system
Click to expand...
Click to collapse
i already flashed a latest firmware i can't root my phone even in the old firmware. i followed all the steps.

nivek4th said:
i already flashed a latest firmware i can't root my phone even in the old firmware. i followed all the steps.
Click to expand...
Click to collapse
Then you must be doing something wrong
You can try to force a software repair using PCCompanion,

gregbradley said:
Then you must be doing something wrong
You can try to force a software repair using PCCompanion,
Click to expand...
Click to collapse
i flashed version 23.0.1.A.5.77 everything went back to normal. when i will flash again the older FW the acore stopped and media stopped gonna show again and when i deleted everything in the step it disappears but i cant root. i tick the debug and allow mock even put it into airplane mode. but CVE is showing up. not rooted.

it works, thanks a lot!

Worked perfekt. Thanks!

nivek4th said:
i flashed version 23.0.1.A.5.77 everything went back to normal. when i will flash again the older FW the acore stopped and media stopped gonna show again and when i deleted everything in the step it disappears but i cant root. i tick the debug and allow mock even put it into airplane mode. but CVE is showing up. not rooted.
Click to expand...
Click to collapse
On the older FW, did you clear the data of ApplicationSettings and ConfigUpdater as well (as in Step 6)?

Friends have achieved to root my phone, it also improves the latest system version and everything is great I put the dual recovery 2.8.2 and of there add Xposed. But after a day in the early morning the phone started to constantly reboot, try to get into recovery mode and freezes with the logo of Sony. turn off and turn on in normal mode, install the recovery again and I wipe cache and dalvik, every normal by day and in the early morning again restarts. PLEASE any solution

Has anyone managed to successfully downgrade from a LP firmware (ex. 690 or .726) back to .93, a KK firmware, without having to wipe using this method?

[Q] RSD Lite Flash XT905 - Phone return FAIL - now bricked - what now?

Hi guys, I have just bricked my Australian XT905 with a RSD Lite firmware flash and hope somebody can help me to unbrick it. This is why I have done it in the first place:
I experienced the increasing 'insufficient storage' problem where despite free memory, it would return this error during updating/installing apps. I made more room on my phone, but the error kept on re-occurring. I brought it into the Telstra shop and was told it's a ' Google issue' and they would have to send it in, but unfortunately it was just outside of warranty. So I thought if I re-flash stock firmware it might fix it (Telstra dude in the shop also said that this might work). So I downloaded the firmware from here: http://motofirmware.center/files/category/29-scorpionmini-xt905/ and first tried flashing the Retail firmware which produced an unknown 'getvar' command error. So as suggest in many other threads, I removed the two getvar lines out of the xml file and tried again. It now worked until it flashed the system_signed file where it produced a 'phone return FAIL' error. I can still get into AP Fastboot mode, but nothing else works now. I tried flashing the Telstra fw and it returned the same error, I tried removing the <step operation="oem" var="fb_mode_set" /> and <step operation="oem" var="fb_mode_clear" /> lines which produced the same fail....
....I am at my wits end. I wonder whether this fail has something to do with the storage problem I had. Anyway, time for a new phone or has somebody a bright idea as to how I could unbrick it? Any help would be much appreciated!

mormopterus said:
Hi guys, I have just bricked my Australian XT905 with a RSD Lite firmware flash and hope somebody can help me to unbrick it. This is why I have done it in the first place:
I experienced the increasing 'insufficient storage' problem where despite free memory, it would return this error during updating/installing apps. I made more room on my phone, but the error kept on re-occurring. I brought it into the Telstra shop and was told it's a ' Google issue' and they would have to send it in, but unfortunately it was just outside of warranty. So I thought if I re-flash stock firmware it might fix it (Telstra dude in the shop also said that this might work). So I downloaded the firmware from here: http://motofirmware.center/files/category/29-scorpionmini-xt905/ and first tried flashing the Retail firmware which produced an unknown 'getvar' command error. So as suggest in many other threads, I removed the two getvar lines out of the xml file and tried again. It now worked until it flashed the system_signed file where it produced a 'phone return FAIL' error. I can still get into AP Fastboot mode, but nothing else works now. I tried flashing the Telstra fw and it returned the same error, I tried removing the <step operation="oem" var="fb_mode_set" /> and <step operation="oem" var="fb_mode_clear" /> lines which produced the same fail....
....I am at my wits end. I wonder whether this fail has something to do with the storage problem I had. Anyway, time for a new phone or has somebody a bright idea as to how I could unbrick it? Any help would be much appreciated!
Click to expand...
Click to collapse
RSD Lite failure when flashing system indicates that your using a too old RSD Lite version (one that can't handle flashing of images above certain size).
Please use at least RSD Lite 6.1.5 (or newer).

THANK YOU!
kabaldan said:
RSD Lite failure when flashing system indicates that your using a too old RSD Lite version (one that can't handle flashing of images above certain size).
Please use at least RSD Lite 6.1.5 (or newer).
Click to expand...
Click to collapse
Geez, what a n00b mistake. Thanks heaps - it worked! Didn't even have to modify the xml file. I was using 5.7 and now installed 6.1.6 which worked perfectly. Couldn't find any solution via Google (well, a couple reporting a similar failure, but no solution), so I feared the worst! Thanks kabaldan!!!

Most people over use the term bricked. If your phone was bricked, then there would be not point in posting about it. It just got stuck OP.
Glad to hear you got it working tho

Need that file!
Could you upload the radio image (NON-HLOS) for the xt905 please? Broke mine but can't find a useable link to the radio image anywhere

[GUIDE] Motorola Moto X Pure(Style) XT1575 - Relock Bootloader, flash, Unbrick etc

1 - Download This File and extract
https://drive.google.com/file/d/0ByH4eje3nMs-dl91VGk2SjRvdDg/view?usp=sharing
2 - Inside folder and double-click the bat file and a command window will be shown up.
------------------------------------------------------------------------------------------------------------
Flash orginal Firmware = Relock_and_format.bat
Relock Bootloader = Relock_and_format.bat
Unbrick = Relock_and_format.bat
Unroot = Relock_and_format.bat
Logo fix = OnlyLogo.bat
Repair Modem = OnlyModem.bat
Firmware version : Android 6.0 - XT1575_CLARK_RETUS_6.0_MPHS24.49-18-3 (Latest version) (24.201.3.clark_retus_en_US)

How is this different from the other recovery scripts/threads?
What specific version of firmware is included?

gpz1100 said:
How is this different from the other recovery scripts/threads?
What specific version of firmware is included?
Click to expand...
Click to collapse
this best. because, i test all other method but my phone did not relock.
When I tried this method, phone is relocked and everything work without error.

Thank you, thank you, thank you!
You are a life saver! This is the only method that worked for me after struggling for a couple of days trying to overcome errors wen I tried to flash stock and re-lock the bootloader. :good::good::good: Will this allow the OTA update and receive Motorola updates?

relock bl returns te warranty?

no. there is no reason to ever relock this phone.

So,if you want to receive Motorola OTA Updates, you only need to unroot and return to stock recovery?

Rotondo said:
relock bl returns te warranty?
Click to expand...
Click to collapse
No
You have to use motorola's website to get the unlock code. They know you unlocked, warranty still void.

I can't thank you enough for this thread!!! I've run through several of these and yours has been the only one to include the most recent security patch!!! You are a STAR!

Thank you for making this easy!

Awesome!
This worked beautifully, I can't thank you enough.
Update** Since using this to un soft brick my device, My bootloader seems to be in a weird place, It says "Device unlocked Status code 3". I followed directions from Motorollas site to relock boot loader nothing in ADB or Fastboot flashes. I tried re unlocking it fails. im not sure what happened. any suggestions would be great though! thanks.

THANK U!!!!
so I tried like 3 other methods to restore my xt1575 after I soft bricked it like an idiot... This was the easiest, quickest method by a long shot.... I wish I could shake ur hand sir! Thank u soooo much....
Edit : Now...it seems...my Bluetooth wont turn on....I've tried resetting network settings, clearing data under BT sharing in App Manager settings, and doing a full factory reset. Ive rebooted numerous times as well. I cannot, for the life of me , get BT to turn on! I'm about to flash TWRP, wipe, and install AICP... IDK..... has this ever happened to anyone? anyone got any idea's?

svensudels said:
so I tried like 3 other methods to restore my xt1575 after I soft bricked it like an idiot... This was the easiest, quickest method by a long shot.... I wish I could shake ur hand sir! Thank u soooo much....
Edit : Now...it seems...my Bluetooth wont turn on....I've tried resetting network settings, clearing data under BT sharing in App Manager settings, and doing a full factory reset. Ive rebooted numerous times as well. I cannot, for the life of me , get BT to turn on! I'm about to flash TWRP, wipe, and install AICP... IDK..... has this ever happened to anyone? anyone got any idea's?
Click to expand...
Click to collapse
The firmware and procedure in the OP are outdated, doing any flashing via a batch file is highly frowned upon as you cannot see if any piece fails and judging from the date of the OP the firmware is out of date.
Aside from that, if just the BT isn't working, you likely need to reflash the BT firmware... it should be included in the firmware you downloaded, go to that directory and execute "fastboot flash bluetooth BTFM.bin" to reflash the BT firmware partition. I am not sure what fastboot is included in this firmware archive, so it that fails try it as "mfastboot fastboot bluetooth BTFM.bin".
If BTFM.bin does not exist in this firmware archive, try over from scratch, look in my signature for a more up to date method of restoring stock and (optionally) relocking the bootloader.

acejavelin said:
The firmware and procedure in the OP are outdated, doing any flashing via a batch file is highly frowned upon as you cannot see if any piece fails and judging from the date of the OP the firmware is out of date.
Aside from that, if just the BT isn't working, you likely need to reflash the BT firmware... it should be included in the firmware you downloaded, go to that directory and execute "fastboot flash bluetooth BTFM.bin" to reflash the BT firmware partition. I am not sure what fastboot is included in this firmware archive, so it that fails try it as "mfastboot fastboot bluetooth BTFM.bin".
If BTFM.bin does not exist in this firmware archive, try over from scratch, look in my signature for a more up to date method of restoring stock and (optionally) relocking the bootloader.
Click to expand...
Click to collapse
THANK U! this worked 1st try! u sir, are a gentleman & a scholar!

svensudels said:
THANK U! this worked 1st try! u sir, are a gentleman & a scholar!
Click to expand...
Click to collapse
Glad you got it resolved.

Hello there! The link seems to be corrupted not available anymore . Where can I find the link?
Thank you for your excellent work

osk4rin said:
Hello there! The link seems to be corrupted not available anymore . Where can I find the link?
Thank you for your excellent work
Click to expand...
Click to collapse
This guide and it's files are outdated, and seems to be abandoned... look at one of the more current tutorials like the one in my signature maybe.