Thanks to blueether for His very useful thread
! ATTENTION !
There is a SIMPLE SOLUTION HERE
The C6833 modem works for my C6802 [TESTED]
Thanks to Triflot
Requirements:
*. DO IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANYTHING THIS WILL DO TO YOUR PHONE
1. Xperia Z Ultra (Absolutely! ) [Tested on XZU with Unlocked Bootloader]
2. FlashTool, Download link & tutorial here
3. Required FTF (NUT's *.532 & *.136)
4. Custom ROM
5. PC running Windows OS
How to get into Flash Mode:
1. Power Off your Z Ultra
2. Press & hold Vol-
3. Plug your phone to your PC (USB driver > read for intallation step here)
How to get into FastBoot Mode:
1. Power Off your Z Ultra
2. Press & hold Vol+
3. Plug your phone to your PC (USB driver > read for intallation step here)
[TRICK] Get Into FastBoot Mode/Flash Mode
If you're having trouble getting into FastBoot Mode/Flash Mode, you can try this trick
1. You have to be on Windows
2. Make sure you opened FlashTool & installed driver for Z Ultra
3. Open Device Manager
4. Show hidden device [Not really necessary, I did this to make sure my Z Ultra driver is installed]
5. Plug your phone while holding Vol+ (FastBoot) OR Vol- (Flash)
6. If it doesn't recognized by Windows, then Scan for hardware changes (this simulate USB Unplug & Replug for me), do this while holding the Volume Rocker
7. Repeat number 6 until you got it connected
For Windows 8/8.1 Only:
When you connected Z Ultra using Flash Mode to your PC, it'll disconnect after a while, to solve this problem, try to prepare your files you want to flash first, then when FlashTool asked to connect your phone, do step 1 to 7, your phone won't disconnect at the time it being flashed
Fresh Install [RECOMMENDED]
Steps:
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool [Default Settings, Flash Everything]
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available
Thanks to x1123 for his post here
Update Custom ROM [EXPERIMENTAL]*Please Correct Me If I Wrong
Steps:
*. This Will Not Keep Your Google Account, So, Contacts, Mails, Hangouts Messages, etc. That Related To Google Account Will Disappear
1. Flash NUT's Modified *.532 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
2. Flash extracted boot.img file from CUSTOM ROM You Want To Install via FastBoot Using FlashTool
3. Boot Into CWM/TW Recovery
4. Flash CUSTOM ROM + GAPPS via Recovery [GAPPS Must Be Installed, Otherwise Google Framework Will Crash]
5. Flash Custom Kernel Here If You Want To Use It, If Not, Then Go To Step 6
6. Reboot Into System You Just Installed [IDK If This Is Necessary]
7. Reboot To Flash Mode
8. Flash ANY *.136 STOCK ROM Using FlashTool
Settings:
[Wipe] AppsLog : Unchecked
[Wipe] Cache : Unchecked
[Wipe] Data : Unchecked
[Exclude] Kernel : Checked
[Exclude] System : Checked
9. Reboot, Hopefully IMEI and BASEBAND Will Be Available [Some Google Apps Will Disappear, You'll Need To Re-Install It]
Tested ROMs: copied from here
Carbon - Build 8: Working
SlimKat: Not tested yet
LiquidSmooth: Not tested yet
FXF CM11: Not tested yet
CM11: Working
AOSP: Not tested yet
AOKP: Not tested yet
AICP: Not tested yet
Lungo: Not tested yet
PAC-man: Not tested yet
PA: Working
Chameleon OS: Not tested yet
GPe ROM: Not tested yet
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
blueether said:
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
I lost my imei yesterday so i have to go through this process. And since i'm already in a custom rom, so i don't need to flash boot.img via fastboot right? Just flash everything via recovery?
And if i do lost imei again, i just need to restore the backup of my previos rom?
Coming from a nexus, this quite confusing :/
Azra4 said:
Hi! I've installed CM11 on my phone (C6806) and have lost the IMEI. How do I flash a FTF? I'm new to all this, can you please give me a bit more info? Thanks!
Click to expand...
Click to collapse
You flash it via Flashtool. The link for the thread is in the op.
satriamau said:
You flash it via Flashtool. The link for the thread is in the op.
Click to expand...
Click to collapse
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Azra4 said:
Thank you. So I need to install Flashtool. That should be easy enough. But what FTF should I use? I have a C6806 (GPE). I'm looking at this page - http://forum.xda-developers.com/showthread.php?t=2453921. Should I use "STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "Generic US""?
Click to expand...
Click to collapse
I don't think you should flash ftf to a gpe z ultra. I've read somewhere it'll brick your device.
Dang! OK, so how do I get my IMEI back then?
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
you flashed the normal togari CM11 not the togari_gpe version? is so just flash the _gpe version over top
satriamau said:
halo gan,
do we have to do all these step to flash a custom rom?
Thanks gan.
Click to expand...
Click to collapse
blueether said:
You should't have to. Just get recovery and flash. There does seem to be an issue with the odd c6802.
If you do lose you IMEI just flashing a FTF will restore it
Click to expand...
Click to collapse
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
Azra4 said:
Dang! OK, so how do I get my IMEI back then?
Click to expand...
Click to collapse
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Riza said:
It's like blueether said, this steps meant for ODD C6802, not every C6802 need this step
give blueether solution a try, because i don't really have many experience with GPe edition of XZU
Click to expand...
Click to collapse
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
So Carbon worked fine with no IMEI issues?
blueether said:
So Carbon worked fine with no IMEI issues?
Click to expand...
Click to collapse
No since i follow these steps while flashing carbon. I flash cm without these steps. Wanted to try cm since carbon giving me random reboots sometime. I love the features btw.
Oot : is there anyway i can turn heads up off on carbon?
Thanks.
juggz143 said:
Does this guide assume you've unlocked bootloader or is that not necessary?
Only asking because it says from stock to custom rom and I read that as completely stock untouched.
Sent from my C6806 using XDA Free mobile app
Click to expand...
Click to collapse
i tried this AFTER i unlocked my bootloader, so idk about XZU with locked bootloader, but i think it's safer to unlock your bootloader first, it's to avoid soft brick of the device, many thread says u must unlock your bootloader before you install any custom ROM
satriamau said:
so i flash CM m11 over carbon rom, and i got this imei and baseband lost again.
is that mean i have the odd one and i have to do these painful steps to flash a rom?
is there any way to flash a rom, gapps and full wipe just from the recovery without losing imei and baseband?
thanks
Click to expand...
Click to collapse
i'm afraid idk the other way, if you want to change your rom, then you must follow the fresh install guide, but if ure upgrading [from CM 11 to later CM 11] then follow upgrade guide
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Flash the attached c6833-modem.zip file for a workaround.
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
That makes perfect scene, good on you mate
Triflot said:
I looked at this a bit tonight. There's a c6x02.sh script which is run at the end of flashing ROMs on togari and honami (Z Ultra and Z1), which copies some particular modem firmware files needed for certain device models (C6802 for togari, C6902 for honami) if it detects that the device is one of these. This script is included in CM11, PA, PAC and SlimKat, but not in others, like Carbon and LiquidSmooth (because TARGET_DEVICE is improperly set in rhine-common/releasetools.py). As @wtfhax says here, the problem may be something around this.
Can someone with the lost IMEI problem on an AOSP ROM try flashing the two attached zips and tell us if either one solves the problem? One is with the c6x02 modem files which some ROMs copy over, while the other is with the "normal" files. Extracted from the latest CM11 nightly. Remember to say which device model you use.
Click to expand...
Click to collapse
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Riza said:
WOW, works like a charm...
Device: C6802
Modem Works: C6833 [idk why]
btw, i added your solution to the first post, is it okay for you?
just tell me if you don't want to, thanks
Click to expand...
Click to collapse
Thanks, that's great!
Did you try the c6x02 file, too? And it didn't work? I wonder why it's included, then - I guess we should ask CM on their issue tracker. In the meantime, you can just delete the c6x02.sh file from the root of any ROM zip you want to install, and it should use functional modem files. (Or use the above zip, but it may become obsolete in the future.)
Still, this doesn't tell the full story if for example Carbon users have had the IMEI problem, since it doesn't have the script. Have you had reports of that, @blueether? Maybe they were caused by not flashing on top of a compatible stock ROM?
There was one I think. I'm not sure what the cause was though
Related
I'm looking for a brave soul or two that has a GPe and would like to do some testing to see if we can have a tool that will convert any togari ROM into one that will boot and have working radio on a togari_gpe. PM me if you want to be a tester.
A huge thank you to @flipperg and @adfurgerson for testing this and helping to improve this tool and the instructions below.
Warning:
If this does't work it may leave your GPe in a non booting state, only test if you are comfortable re-flashing boot.img and ROMs again
ROM 2 GPe:
A tool for converting a ROM into GPe ROM
This tool will take an installed ROM and GPeize it so that it will boot with a working radio etc
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
Getting a working kernel & recovery: <=== Read This Section Carefully
If you are running DooMKernel or if you get "This device is a honami" and you are flashing a custom ROM do this:
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
Download:
Version 1 [10/05/2014]
Working conversions:
Working on CM11 and Carbon with some bugs
Should work with all AOSP/CM11 ROMs
Might even work with Stock based ROMs (read monx and partial* FTF flashes)
Now that I have thought about it I can't see this working on Stock based ROMs, and now we have DooMLoRD's Sony port there is little point in trying to get it to work on Sony firmware.
* Warning:
Never flash the whole FTF or you will hard BRICK your GPu Ultra, only ever flash the kernel and system and never use Sony OTA/PCC updates
Again:
Code:
[B][SIZE="4"][COLOR="red"]
***********************************************
** **
** Never Flash a full FTF to a GPe Z-Ultra **
** **
***********************************************
[/COLOR][/SIZE][/B]
XDA:DevDB Information
ROM 2 GPe, Tool/Utility for the Sony Xperia Z Ultra
Contributors
blueether, flipperg, adfurgerson for testing and prbassplayer for the idea in the first place
Version Information
Status: Testing
Created 2014-05-10
Last Updated 2014-05-25
Reserved
Any one testing? We cant have development if no one tries I dont have my phone yet or I would man
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gtshiftin6 said:
Any one testing? We cant have development if no one tries I dont have my phone yet or I would man
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
30 hours and no takers? I'll just upload the zip and someone can test at their leisure...
blueether said:
30 hours and no takers? I'll just upload the zip and someone can test at their leisure...
Click to expand...
Click to collapse
Firsrt let me say thank you for your work. I have had my GPE for less than a week and am still getting a grasp on what is needed for unlocking,root, and recovery. I am also waiting for parts to arrive for my old LG Optimistic G, if I can get it working as a backup phone I will be willing to test. Hopefully you won't lose interest before then.
Edit...parts came for what I hoped would be my backup phone, but it didn't fix it.
Edit...tried to flash Carbon with TWRP from DooMLoRD's kernel and it failed with message "This package is for C6802 C6806....E:Error executing updater binary in zip"
@blueether if you can upload a zip later I will try, or I could try to remove that line if it was explained to me.
I'd prefer to not be the first... Has anyone attempted?
CCJ22 said:
I'd prefer to not be the first... Has anyone attempted?
Click to expand...
Click to collapse
See my second edit in above post. Updater script wouldn't let me flash ROM.
Thanks for the willingness to test.
The error will go away if you open the zip and edit the updater script and remove the check... or I could upload another version...
EDIT
bugger, the error is on the Carbon_togari zip isn't it, this is because DooMKernel is ported from the Z1, if you are coming from CM11 or Carbon for the GPe etc then the extra step shouldn't be needed.
um So new instructions:
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
If you are running DooMKernel, do this:
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
I hope that will work
Alright, I'll bite.
I'm backing up now, but just to make sure I understand:
I will:
1) Wipe/Format
2) Install [ROM][LB&UB] C68XX ★ monxDIFIED ★ ZUltra™ (442.757) BEST AROMA [v06-02][24/04] from the Android Dev Thread
3) Install rom2togari_gpe from your thread
4) Reboot
Right?
FAILURE
:crying:
rom2togari_gpe fails complaining this is for togari and my phone is a honami. (My phone is a togari_gpe, promise)
flipperg said:
I'm backing up now, but just to make sure I understand:
I will:
1) Wipe/Format
2) Install [ROM][LB&UB] C68XX ★ monxDIFIED ★ ZUltra™ (442.757) BEST AROMA [v06-02][24/04] from the Android Dev Thread
3) Install rom2togari_gpe from your thread
4) Reboot
Right?
Click to expand...
Click to collapse
---------- Post added at 09:57 PM ---------- Previous post was at 08:59 PM ----------
So I figure the Honami - Togari issue is because I'm using ZU_GPe-AdvStkKernel-KOT49H.S2.2052-v01 to do the flashing... for some reason it has a boot.img signature for the Honami - go figure. But I'm not sure how to get around this.
If I flash the boot.img from any other ROM (I tried CM11), then how do I flash the Custom Rom and Tool without a Custom Recovery? Do I do all this via adb/fastboot from my Mac?
Just trying, thanks for all the help.
Flipper
flipperg said:
:crying:
rom2togari_gpe fails complaining this is for togari and my phone is a honami. (My phone is a togari_gpe, promise)
Click to expand...
Click to collapse
flipperg said:
:crying:
rom2togari_gpe fails complaining this is for togari and my phone is a honami. (My phone is a togari_gpe, promise)
---------- Post added at 09:57 PM ---------- Previous post was at 08:59 PM ----------
So I figure the Honami - Togari issue is because I'm using ZU_GPe-AdvStkKernel-KOT49H.S2.2052-v01 to do the flashing... for some reason it has a boot.img signature for the Honami - go figure. But I'm not sure how to get around this.
If I flash the boot.img from any other ROM (I tried CM11), then how do I flash the Custom Rom and Tool without a Custom Recovery? Do I do all this via adb/fastboot from my Mac?
Just trying, thanks for all the help.
Flipper
Click to expand...
Click to collapse
Thanks for testing, I cant up load a version with out the check as my dev machine is down, but it will be back up over the weekend.
I think an easy fix for you would be the instructions just above (not the ones in OP) or to reboot back into recovery after flashing monx. All the kernels / boot.img should have recovery so you can flash the boot.img from the ROM zip... so:
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
If you are running DooMKernel or if you get "This device is a honami" do this: <=== Read This Line
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
I hope that this works and we get a GPe running a modified Sony ROM. if it does work it will work on a pure Sony firmware
Again I have to say:
Code:
[B][SIZE="4"][COLOR="red"]
***********************************************
** **
** Never Flash a full FTF to a GPe Z-Ultra **
** **
***********************************************
[/COLOR][/SIZE][/B]
Thanks for the quick response
I'll try it tonight. But if I may - I do not believe that monx has a boot.img, I searched for it. As far as CM11, what you're telling me is that it's boot.img had it's own custom recovery and I should be able to flash the tool from there? As I understand it, the only way for me to boot into cwm or twrp was to hot boot into Doom's via flashtool. How else can I get the pick led so I can get in?
Am I just being dense or noob?
Thanks for your help,
Flipper
blueether said:
Thanks for testing, I cant up load a version with out the check as my dev machine is down, but it will be back up over the weekend.
I think an easy fix for you would be the instructions just above (not the ones in OP) or to reboot back into recovery after flashing monx. All the kernels / boot.img should have recovery so you can flash the boot.img from the ROM zip... so:
Install:
Download and save Custom togari ROM to ZU_GPe
Download and save rom2togari_gpe to ZU_GPe
If you are running DooMKernel or if you get "This device is a honami" do this: <=== Read This Line
extract boot.img from Custom togari ROM to desktop (or similar)
flash boot.img to the ZU_GPe using flashtool or fastboot.exe while phone is in fastboot mode
Boot into recovery
Wipe data and caches
Flash a custom togari ROM
Flash rom2togari_gpe
Reboot and pray
I hope that this works and we get a GPe running a modified Sony ROM. if it does work it will work on a pure Sony firmware
Again I have to say:
Code:
[B][SIZE="4"][COLOR="red"]
***********************************************
** **
** Never Flash a full FTF to a GPe Z-Ultra **
** **
***********************************************
[/COLOR][/SIZE][/B]
Click to expand...
Click to collapse
flipperg said:
I'll try it tonight. But if I may - I do not believe that monx has a boot.img, I searched for it. As far as CM11, what you're telling me is that it's boot.img had it's own custom recovery and I should be able to flash the tool from there? As I understand it, the only way for me to boot into cwm or twrp was to hot boot into Doom's via flashtool. How else can I get the pick led so I can get in?
Am I just being dense or noob?
Thanks for your help,
Flipper
Click to expand...
Click to collapse
I would try rebooting system after flashing img. when the Google splash screen shows and led lights up press volume up or down to get into recovery.
flipperg said:
I'll try it tonight. But if I may - I do not believe that monx has a boot.img, I searched for it. As far as CM11, what you're telling me is that it's boot.img had it's own custom recovery and I should be able to flash the tool from there? As I understand it, the only way for me to boot into cwm or twrp was to hot boot into Doom's via flashtool. How else can I get the pick led so I can get in?
Am I just being dense or noob?
Thanks for your help,
Flipper
Click to expand...
Click to collapse
OK, it sort of makes sense that monxROM doesn't include the kernel. You could use jackie099's kernel or the port of DooMKernel for the togari. Both of these kernels have recovery built in (as should all custom ROMs). A CM11 kernel or one from/for a custom ROM will not boot Stock Sony or monx's ROM, nor the other way around so we have to get the correct kernel for the type of ROM you are flashing.
Once you have a custom kernel installed you can boot into recovery by pressing the vol up or down key when the LED lights during boot (could be pink, purple some other colour depending on the kernel)
Changed the install instructions in the OP again, I hope that it is clearer
@blueether I'm in Carbon and mostly all good. Camera doesn't connect and Play Store crashes when trying to install apps then closes with the message "Unfortunately,Google Play Store has stopped." if I try to open it gain.
---------- Post added at 05:04 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @blueether I'm in Carbon and mostly all good. Camera doesn't connect and Play Store crashes when trying to install apps then closes with the message "Unfortunately,Google Play Store has stopped." if I try to open it again.
edit...camera crash has small toast message saying "Insert anSD card before using the camera" and tried downloading a new Play Store from web and get toast saying "No D card'.
Report
Ok - so CM11 - Success! I used the boot.img from CM11 to Flashtool HotBoot into Recovery, and everything went as planned.
Monx - No Good, I was able to install the ROM, but when I ran the tool I got:
Creating Symlinks...
symlink: some symlinks failed
E: Error in /data/media/0/Download/rom2togari_gpe.zip
(Status 7)
Installation Aborted
You do point out that we can't use a CM11 boot.img with Monx (I read that after I tried), is that it?
Could you please point me to a place I can get a good boot.img with custom recovery that will let me boot Monx correctly please? The only jackies099 one I found is for the non-GPe version - is this the one I should try?
Doom's is the one that reports the wrong phone type (Honami) right? So I'm not sure if I can use that one.
But I'm almost there... I'm going to keep trying some iterations.
One more question (noob): What's FTF? (I gather it's a ROM that includes Radio and/or other Partitions but I'd like to know an easier way to determine this so I don't screw up)
I've done many Android Custom ROMS installations/Mods but this is my first Sony, sorry.
Thank you,
Flipper
blueether said:
OK, it sort of makes sense that monxROM doesn't include the kernel. You could use jackie099's kernel or the port of DooMKernel for the togari. Both of these kernels have recovery built in (as should all custom ROMs). A CM11 kernel or one from/for a custom ROM will not boot Stock Sony or monx's ROM, nor the other way around so we have to get the correct kernel for the type of ROM you are flashing.
Once you have a custom kernel installed you can boot into recovery by pressing the vol up or down key when the LED lights during boot (could be pink, purple some other colour depending on the kernel)
Changed the install instructions in the OP again, I hope that it is clearer
Click to expand...
Click to collapse
flipperg said:
Ok - so CM11 - Success! I used the boot.img from CM11 to Flashtool HotBoot into Recovery, and everything went as planned.
Monx - No Good, I was able to install the ROM, but when I ran the tool I got:
Creating Symlinks...
symlink: some symlinks failed
E: Error in /data/media/0/Download/rom2togari_gpe.zip
(Status 7)
Installation Aborted
You do point out that we can't use a CM11 boot.img with Monx (I read that after I tried), is that it?
Could you please point me to a place I can get a good boot.img with custom recovery that will let me boot Monx correctly please? The only jackies099 one I found is for the non-GPe version - is this the one I should try?
Doom's is the one that reports the wrong phone type (Honami) right? So I'm not sure if I can use that one.
But I'm almost there... I'm going to keep trying some iterations.
One more question (noob): What's FTF? (I gather it's a ROM that includes Radio and/or other Partitions but I'd like to know an easier way to determine this so I don't screw up)
I've done many Android Custom ROMS installations/Mods but this is my first Sony, sorry.
Thank you,
Flipper
Click to expand...
Click to collapse
FTF=flashtool file which are stock firmwares.
flipperg said:
Ok - so CM11 - Success! I used the boot.img from CM11 to Flashtool HotBoot into Recovery, and everything went as planned.
Monx - No Good, I was able to install the ROM, but when I ran the tool I got:
Creating Symlinks...
symlink: some symlinks failed
E: Error in /data/media/0/Download/rom2togari_gpe.zip
(Status 7)
Installation Aborted
You do point out that we can't use a CM11 boot.img with Monx (I read that after I tried), is that it?
Could you please point me to a place I can get a good boot.img with custom recovery that will let me boot Monx correctly please? The only jackies099 one I found is for the non-GPe version - is this the one I should try?
Doom's is the one that reports the wrong phone type (Honami) right? So I'm not sure if I can use that one.
But I'm almost there... I'm going to keep trying some iterations.
One more question (noob): What's FTF? (I gather it's a ROM that includes Radio and/or other Partitions but I'd like to know an easier way to determine this so I don't screw up)
I've done many Android Custom ROMS installations/Mods but this is my first Sony, sorry.
Thank you,
Flipper
Click to expand...
Click to collapse
Getting there :victory: did cell, wifi and data work in togari cm11?
The status 7 error is my script not the kernel, so it looks like monx will be harder to crack than custom then, I'll have to create a separate version for stock based ROMs I think.
We need the kernel that will boot the system/ROM that we are installing, not a GPe when you flash monx's ROM ie jackie's one or the ported DooMKernel one (not the GPe version of DooMKernel). But with the status 7 error this may not work.
If you still have monx on the GPe you could just flash jackie's or the DooMKernel http://forum.xda-developers.com/showthread.php?t=2705130 and then see if it boots, the simlink errors might not be too important.
adfurgerson said:
@blueether I'm in Carbon and mostly all good. Camera doesn't connect and Play Store crashes when trying to install apps then closes with the message "Unfortunately,Google Play Store has stopped." if I try to open it gain.
---------- Post added at 05:04 PM ---------- Previous post was at 04:54 PM ----------
edit...camera crash has small toast message saying "Insert anSD card before using the camera" and tried downloading a new Play Store from web and get toast saying "No D card'.
Click to expand...
Click to collapse
Getting there, did cell, wifi and data work?
blueether said:
Getting there, did cell, wifi and data work?
Click to expand...
Click to collapse
Cell, WiFi, Bluetooth worked didn't think to try regular data. Made a backup of Carbon then restored stock GPe ROM just fine. Can restore Carbon and test or should be able to restore and flash anything else you need tested.
edit.....cell data works but it seems auto rotate doesn't, tried toggling it off then on and looking for more than one place to set it but didn't find any others.
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
This post shows you how to upgrade your system to lollipop 5.1.1 and optionally have root privileges. This is tested on C6833 model. For other models see the troubleshooting section near the end of the post.
Requirements:
Flashtool 0.9.18.6. or 0.9.19.6 or higher Important: Do not use Flashtool 0.9.19.0.
If you want to root the phone: Rooted XZU on Android version 5.0.2 or Kitkat with custom recovery installed.
This works on locked or unlocked bootloaders and any customization.
Download link for upgrade only:
C6833_14.6.A.0.368_1275-8026_R2D.ftf (unmodified Customized DE):
https://mega.nz/#!khF1nILD!C5D70e-BjCKVBCuOurjFOLcIMZDcldYVeIDnFiR-PGM
Download link for upgrade and root:
5.1.1-system.zip:
https://mega.nz/#!YoFgCSjA!Zh8t_4jeXcAEWhOYePA40uQLI7vw4-CnxohjBdMbpz0
C6833_14.6.A.0.368_No_System.ftf
https://mega.nz/#!l4dllSTT!R393EG4W3CwOZp1OLOzfUzpHF0IlvsmfW04BrGOggXc
Instructions for upgrading without root:
1- Back up your internal SDCARD and your apps.
2- Download C6833_14.6.A.0.368_1275-8026_R2D.ftf
3- Open Flashtool and click on the flash icon. Choose flash mode.
4- Navigate to where you saved C6833_14.6.A.0.368_1275-8026_R2D.ftf and flash this ftf with your phone in flash mode. I recommend wiping apps and cache and data (Note that wiping data will erase your internal SDcard too). To put your phone in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
5- Reboot.
Instructions for upgrading with root:
0- If your existing system is rooted using Kingroot read the troubleshooting section below before continuing.
1- Back up your internal SDCARD and your apps.
2- Download C6833_14.6.A.0.368_No_System.ftf and 5.1.1_system.zip.
3- Copy 5.1.1-system.zip to your phone's internal SDcard.
4- Reboot to recovery and install 5.1.1-system.zip.
5- If you are coming from Kitkat just Turn the phone off. If you are coming from 5.0.2, reboot the phone and let it work through the boot animation which will take a while. Then it will show force closing messages and possibly reboots itself. At this point turn it off by holding down the power and volume-up keys for a few seconds. The phone will vibrate 3 times and turns off.
6- Open Flashtool and click on the flash icon. Choose flash mode.
7- Navigate to where you saved C6833_14.6.A.0.368_No_System.ftf and flash this ftf with your phone in flash mode. I recommend wiping apps and cache and data (Note that wiping data will erase your internal SDcard too). To put your phone in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
8- Reboot.
Troubleshooting, etc.
This procedure works only if you follow every step carefully. When you are done you can easily test your root status in a terminal emulator or via adb. Please see the attached image.
If you have used Kingroot to root your existing system flashing this ROM may not work and it may leave your system with a partially updated file system that may be broken. The reason is that Kingroot (which in my opinion is malware) makes some of your system files immutable which means they cannot be removed during a software upgrade. To proceed, you should either find a way to replace this horrendous piece of code with SuperSU or downgrade to Kitkat and root with XZDualRecovery before trying this guide. Read the second part of http://forum.xda-developers.com/showpost.php?p=62936808&postcount=22.
If during the procedure for root the flashing of the ftf in step 7 fails, repeat step 7 with C6833_14.6.A.0.368_1275-8026_R2D.ftf or any other 14.6.A.0.368 ftf but exclude the system partition in the flashtool dialog window. If you don't exclude the system partition you will not get root.
If you have root after the procedure but something else doesn't work, try a factory reset.
Note that flashtool 0.9.19.0 was specifically released to support the new sin format on new devices and some of its features don't work with older devices. So to avoid taking any chances I used version 18.
I don't know if this works for C6802 or C6806. Some users reported success on 6806, like this one and this. For that model you follow this guide and use the zip file posted here. The only difference is that instead of flashing the ftf posted here in the next step, use the stock 14.6.A.0.368 ftf for your phone and exclude system.
Will this C6833 FTF work on a C6806 USA phone?, because I can't find a C6806 FTF anywhere...
Can this system zip be used with other customized versions of c6833 ftf.
usagi111 said:
Will this C6833 FTF work on a C6806 USA phone?, because I can't find a C6806 FTF anywhere...
Click to expand...
Click to collapse
I just uploaded a C6806 US version in Development thread yesterday.
Sent from my A0001 using Tapatalk
could you share flashtool 0.9.18.0 cos I can't find that version only higher.
will this work on c6802 just wondering?
I did as you said but. I see no super-su
jaime4272 said:
I did as you said but. I see no super-su
Click to expand...
Click to collapse
You probably didn't exclude the system partition in this step:
7- Navigate to where you saved C6833_Customized+DE_14.6.A.0.368.ftf.*Exclude system partition*and flash this ftf.
Out of curiosity, what is wrong with the latest flashtool?
---------- Post added at 10:11 PM ---------- Previous post was at 10:00 PM ----------
jaime4272 said:
could you share flashtool 0.9.18.0 cos I can't find that version only higher.
will this work on c6802 just wondering?
Click to expand...
Click to collapse
I've uploaded 0.9.18.6
https://drive.google.com/file/d/0B2L0y84PJ2rteVNGVnlJWjFlOGs/view?usp=sharing
Never mind, i already found out, also flashtool published a new version wich is compatible with our device
http://www.flashtool.net/downloads.php
thanks mate, everything worked fine
I was able to flash android 5.1.1 but could not get root and I did every step as posted and I did exclude system partition. and without root could not install dual recovery there for could not flash SuperSU
I am sorry for my noobie question...but what is customised DE?
ALso if i run this, I am still at locked bootloader...will i lose the partition that enable me to have all Sony's special goodies (i didn't mean the bloatware of course)?
Also i am running stock 5.1.1 already after OTA but interested to have root...shall i go with the 2nd steps with root?
im4u2nv said:
I am sorry for my noobie question...but what is customised DE?
ALso if i run this, I am still at locked bootloader...will i lose the partition that enable me to have all Sony's special goodies (i didn't mean the bloatware of course)?
Also i am running stock 5.1.1 already after OTA but interested to have root...shall i go with the 2nd steps with root?
Click to expand...
Click to collapse
Customized DE just means it is the German version of the ROM. I used that because I bought the phone in Germany. But the menus and keyboard and everything is in English so you would not even notice the difference.
This method will not touch your bootloader status so if you are locked you remain locked.
If you are already on 5.1.1 through OTA this will not work for you. You need to start from rooted 5.0.2 with recovery installed.
najoor said:
Customized DE just means it is the German version of the ROM. I used that because I bought the phone in Germany. But the menus and keyboard and everything is in English so you would not even notice the difference.
This method will not touch your bootloader status so if you are locked you remain locked.
If you are already on 5.1.1 through OTA this will not work for you. You need to start from rooted 5.0.2 with recovery installed.
Click to expand...
Click to collapse
Thank you Najoor...in that case, i will wait for some guide to root 5.1.1 then...
I am using stock kitkat custom rom will I have to update to Lollipop 5.0 first or can i directly flash 5.1
terminator1983 said:
I am using stock kitkat custom rom will I have to update to Lollipop 5.0 first or can i directly flash 5.1
Click to expand...
Click to collapse
I think you can still do it straight from kitkat but if you are following the instructions with root in step 5 instead of rebooting just turn the phone off.
Let me know if that works.
so my ZU used to be rooted with Lollipop 5.0.2, but i removed Kinguser/chinese root app and no longer have root access. I've also previously installed recovery but don't know if it will still work ? i forgot how to boot into recovery to see if it even works.. any helpers?
Power on the phone and when u see the led notification start pressing either the Volume UP or Volume Down key a couple of times to make your phone boot into recovery mode
corrado85 said:
so my ZU used to be rooted with Lollipop 5.0.2, but i removed Kinguser/chinese root app and no longer have root access. I've also previously installed recovery but don't know if it will still work ? i forgot how to boot into recovery to see if it even works.. any helpers?
Click to expand...
Click to collapse
najoor said:
I think you can still do it straight from kitkat but if you are following the instructions with root in step 5 instead of rebooting just turn the phone off.
Let me know if that works.
Click to expand...
Click to collapse
Thanks najoor it worked now i am using a rooted stock 5.1.1
jaime4272 said:
I was able to flash android 5.1.1 but could not get root and I did every step as posted and I did exclude system partition. and without root could not install dual recovery there for could not flash SuperSU
Click to expand...
Click to collapse
I am not able to instal 5.1.1-system.zip on rooted Sony Xperia Z Ultra c6833 with Android 5.0.2. The instalation is aborted
Had 5.1.1 lollipop installed, downgraded to 4.4.4 kitkat and rooted with kingroot successfully- installed xzu dual recovery and rebooted into recovery mode.
Flashed 5.1.1 zip and turned off. Flashed 5.1.1 Saudi Arabia ftf with flashtool (wipe everything - ticking to exclude system partition) with phone off and connected z ultra in flash mode and flashed successfully. Disconnected and booted.. took a while on wave animation and started fresh but no supersu and not rooted in 5.1.1?? any help thanks
This is the latest December update for the Z Ultra (C6833). It has some uninstallable Telenor (Norway) apps, so just remove them if you want to. This FTF is completely stock and untouched, so it's not rooted. If you want root, then download SuperSU and flash it in recovery (unlocked bootloader is required). This release only contains bugfixes.
- Download: FTF
- Download: SuperSU
- Download: NUT's Dual Recovery
NOTE: Remember to do a full wipe in Flashtool if you're coming from an AOSP ROM (CyanogenMod etc.), or else you'll risk getting bootloops.
Klaos3000 said:
This is the latest December update for the Z Ultra (C6833). It has some uninstallable Telenor (Norway) apps, so just remove them if you want to. This FTF is completely stock and untouched, so it's not rooted. If you want root, then download SuperSU and flash it in recovery (unlocked bootloader is required). This release only contains bugfixes.
- Download: FTF
- Download: SuperSU
- Download: NUT's Dual Recovery
Click to expand...
Click to collapse
Flash Tool Failed to flash the FTF file
jamaljmys said:
Flash Tool Failed to flash the FTF file
Click to expand...
Click to collapse
It's the one I'm currently running, so there shouldn't be any issues with it. Also, I'll have to get some more info. What does Flashtool tell you when it fails?
So if I soft brick my phone can I flash this to fix it? I normally resort back to kk ftf. So just flash, add recovery then flash root?
RealityFails said:
So if I soft brick my phone can I flash this to fix it? I normally resort back to kk ftf. So just flash, add recovery then flash root?
Click to expand...
Click to collapse
I usually just hotboot a random kernel with recovery when I soft brick. Flashing a complete ROM is taking it a few steps too far, but sure, it'll work just fine if you decide to do it. Remember to wipe though, or else you'll risk getting yet another bootloop, especially if you come from an AOSP ROM.
Klaos3000 said:
It's the one I'm currently running, so there shouldn't be any issues with it. Also, I'll have to get some more info. What does Flashtool tell you when it fails?
Click to expand...
Click to collapse
thank you bro. its been solved, drivers issue with Win10
Hey guys after my initial failure at trying to upgrade to 575 at the weekend, I didn't realize 575 was a MM upgrade so that was partly the problem the rest was the wrong SU and recovery in my PRF flash file.
Problem I have now is i've read that many forum posts im not 100% sure what files and steps I need to take , every 575 flash instructions Ive read seem to have slightly different ways of doing it.
Im coming from 23.4.A.1.264 (LL) What i need help is to clarify exactly what i need to make a successful prf upgrade.
Im assuming Recroot is one in the recovery section of PRF?
So called dummy file in SU section of PRF?
What about bootloop.zip and RIC.zip I hear about , are they required as well?
I know xposed needs to be uninstalled as well.
LOCKED bootloader
Thx for any help/links or clarification on steps you can provide.
edit:- Sorry mods this is in wrong section, wasnt paying attention , Sorry could someone move to QA section ? thx
SwiftSmoke said:
Hey guys
Click to expand...
Click to collapse
...went through this two days ago:
(from this post, that helped me):
prerequisities: 5.1.1 stock, rooted, with NUT Dual recovery
put all ZIPs to your MicroSD card and flash in this order.
0: do you currently have xposed? If yes, get the xposed uninstaller (google it, easy to find) and flash uninstaller first.
0. Factory reset from within current recovery (Dalvik, data, cache...)
1. flashablemm.zip
2. byeselinux.zip
3. ricdefeat.zip
4. bootloopfix.zip (FOR .575, important to get this version)
5. xposed installer.zip
6. reboot
7. INSTALL BUSYBOX (get app in PlayStore and use it to install it)
8. enable unknown sources and usb debugging
9. then connect your phone to the PC and run the install.bat from the Z2_MM_Recovery folder (Accept any prompt popping up on your phone)
5. Phone will reboot into recovery when successfull, then you're done
ZIP files from this thread: http://forum.xda-developers.com/xperia-z2/general/z2-pre-rooted-twrp-3-0-0-2-xposed-t3390498
RECOVERY INSTALL: from here https://mega.nz/#!UlxGBQaD!HObJIHr9vq4VDRNI97Ni1cIiAn6iVxwE4qlPa89CGbY - Remember: only install the recovery from this file, everything else from the thread above.
NOTE: I had big problems when flashing TWRP 3.0.x IMG file from this thread. Instead get the recovery downloaded in this ZIP and install it form your PC, as described in the steps above.
One more note: I've waited for about 15minutes after finishing the flashing proces (step6). I had the startup animation going on, normally it should take maybe 5-10minutes. I got fed up after nothing was happening and restarted the phone - press the red button beside SIM flap and than power on the phone. After that it started normally.
thx i'll look into this
Do you have a link for 575 bootloop fix file?
what version of z2 do you have? if you have D6503, you can use my prerooted MM (.575). Here's the link:
http://forum.xda-developers.com/xperia-z2/general/prerooted-23-5-0-575-customized-t3387571
no need for bootloop fix
if other version, you can use these files in your prf:
dummy flashable: https://drive.google.com/file/d/0B8n...pJdzZwRm8/view
Recrootv4: http://forum.xda-developers.com/z3/g...-0-mm-t3337357
loonlekim said:
what version of z2 do you have? if you have D6503, you can use my prerooted MM (.575). Here's the link:
http://forum.xda-developers.com/xperia-z2/general/prerooted-23-5-0-575-customized-t3387571
no need for bootloop fix
if other version, you can use these files in your prf:
dummy flashable: https://drive.google.com/file/d/0B8n...pJdzZwRm8/view
Recrootv4: http://forum.xda-developers.com/z3/g...-0-mm-t3337357
Click to expand...
Click to collapse
Yeah I have the d6503
Sent from my D6503 using XDA-Developers mobile app
SwiftSmoke said:
Yeah I have the d6503
Sent from my D6503 using XDA-Developers mobile app
Click to expand...
Click to collapse
You can try then either of those.
So, my end goal is to have Resurrection remix marshmallow running on my D6503 Z2. I guess I made the mistake of updating the phone to the stock Marshmallow ROM from sony so I can not find a way to root the phone. So is there a step by step guide on how I could possibly root and add a recovery tool?
DarkEvE said:
So, my end goal is to have Resurrection remix marshmallow running on my D6503 Z2. I guess I made the mistake of updating the phone to the stock Marshmallow ROM from sony so I can not find a way to root the phone. So is there a step by step guide on how I could possibly root and add a recovery tool?
Click to expand...
Click to collapse
Have you got an unlocked bootloader?
If so, flash a custom kernel with a recovery and install your chosen rom?
If you have a locked bootloader you can't run a custom rom, like resurrection remix.
Regards,
Mohamed
moman2000 said:
Have you got an unlocked bootloader?
If so, flash a custom kernel with a recovery and install your chosen rom?
If you have a locked bootloader you can't run a custom rom, like resurrection remix.
Regards,
Mohamed
Click to expand...
Click to collapse
I do not have a unlocked bootloader but the issue is all the tutorials assume you have the lolipop version of android on the Z2 running with root. If I can't find out how to root on 6.0.1 on the Z2 then its kinda pointless..
To root mm, downgrade to lollipop or kitkat and follow a guide. If you don't want to downgrade, unlock you bootloader.
They are your options. This had been asked. This has been answered. Use the search.
Sent from my D6503 using Tapatalk
DarkEvE said:
I do not have a unlocked bootloader but the issue is all the tutorials assume you have the lolipop version of android on the Z2 running with root. If I can't find out how to root on 6.0.1 on the Z2 then its kinda pointless..
Click to expand...
Click to collapse
All you have to do is downgrade to 23.1.A.1.28 using flash tool, there are many threads on how to use it, have a search!
And use this thread which can be found
Here that will allow you to root your phone!
After that install XZDualrecovery,backup your ROM and flash resurrection remix!
Regards,
Mohamed
moman2000 said:
All you have to do is downgrade to 23.1.A.1.28 using flash tool, there are many threads on how to use it, have a search!
And use this thread which can be found
Here that will allow you to root your phone!
After that install XZDualrecovery,backup your ROM and flash resurrection remix!
Regards,
Mohamed
Click to expand...
Click to collapse
Ill give that a go then. Thanks a lot.
DarkEvE said:
Ill give that a go then. Thanks a lot.
Click to expand...
Click to collapse
No problem! Good luck!
ok so i got it rooted and put the recovery mods on but after i flashed the phone with the Resurrection remix rom now the phone wont turn on? apparently its called sleep of death or something..
moman2000 said:
No problem! Good luck!
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934548703 <- Where i downloaded the rom
http://forum.xda-developers.com/xperia-z2/help/how-to-rrot-z2-marshmellow-t3384384< Followed this guide
Yet when i flash the following in that order - Rom, Gapps and the bootfix then do the wipe cache the phone does not boot up. When the power button is pressed the red light just appears then the phone stays off :/
moman2000 said:
No problem! Good luck!
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934548703 <- Where i downloaded the rom
http://forum.xda-developers.com/xperia-z2/help/how-to-rrot-z2-marshmellow-t3384384< Followed this guide
Yet when i flash the following in that order - Rom, Gapps and the bootfix then do the wipe cache the phone does not boot up. When the power button is pressed the red light just appears then the phone stays off :/
DarkEvE said:
https://www.androidfilehost.com/?fid=95916177934548703 <- Where i downloaded the rom
http://forum.xda-developers.com/xperia-z2/help/how-to-rrot-z2-marshmellow-t3384384< Followed this guide
Yet when i flash the following in that order - Rom, Gapps and the bootfix then do the wipe cache the phone does not boot up. When the power button is pressed the red light just appears then the phone stays off :/
Click to expand...
Click to collapse
When you say boot fix, what do you mean?
moman2000 said:
When you say boot fix, what do you mean?
Click to expand...
Click to collapse
well there is a file that i downloaded from that link i provided on the tutorial which says z2's suffer from a "bootloop" issue so you have to flash this file after installing the rom apparently
DarkEvE said:
well there is a file that i downloaded from that link i provided on the tutorial which says z2's suffer from a "bootloop" issue so you have to flash this file after installing the rom apparently
Click to expand...
Click to collapse
Step : 0
Backup Ur Personal Data,
Step : 1
Download Your resurrection rom and gapps
Copy it to your phone sd card
Step : 2
Download Stock Lollipop Rom From HERE Select Version 23.4.A.1.264
Then Flash It via Flashtool
Step : 3
Then Latest Version of KingRoot from here
Install king root on ur stock lollipop rom and make sure ur internet connection is stable and open kingroot and root it.(It'll take 1-2 min)
Step : 4
After that download this XZDualRecovery From here
Extract recovery.zip on ur windows and run install.bat type 4 let it install adb driver on windows after that type 1 and press enter. And Then It'll boot into Recovery.
Step : 5
Go to TWRP Recovery Settings and (tick Use rm -rf instead of formatting). It's optinal. If u don't tick this setting then wiping device will take more than a few minute.
Wipe Everything Except Device storage where u put prerooted mm rom and bootlop fix.
Step : 6
Flash resurrection rom then gapps and reboot device.
moman2000 said:
Step : 0
Backup Ur Personal Data,
Step : 1
Download Your resurrection rom and gapps
Copy it to your phone sd card
Step : 2
Download Stock Lollipop Rom From HERE Select Version 23.4.A.1.264
Then Flash It via Flashtool
Step : 3
Then Latest Version of KingRoot from Here
Install king root on ur stock lollipop rom and make sure ur internet connection is stable and open kingroot and root it.(It'll take 1-2 min)
Step : 4
After that download this XZDualRecovery From Here Original Thread
Extract recovery.zip on ur windows and run install.bat type 4 let it install adb driver on windows after that type 1 and press enter. And Then It'll boot into Recovery.
Step : 5
Go to TWRP Recovery Settings and (tick Use rm -rf instead of formatting). It's optinal. If u don't tick this setting then wiping device will take more than a few minute.
Wipe Everything Except Device storage where u put prerooted mm rom and bootlop fix.
Step : 6
Flash Prerooted mm rom then bootloop fix and reboot device.
Click to expand...
Click to collapse
still doesnt work :/ I still get that sleep of death issue thing
DarkEvE said:
still doesnt work :/
Click to expand...
Click to collapse
I forgot to add the links, I have also changed the steps so it works for you:
Step : 0
Backup Ur Personal Data,
Step : 1
Download Your resurrection rom and gapps
Copy it to your phone sd card
Step : 2
Download Stock Lollipop Rom From HERE Select Version 23.4.A.1.264
Then Flash It via Flashtool
Step : 3
Then Latest Version of KingRoot from here
Install king root on ur stock lollipop rom and make sure ur internet connection is stable and open kingroot and root it.(It'll take 1-2 min)
Step : 4
After that download this XZDualRecovery From here
Extract recovery.zip on ur windows and run install.bat type 4 let it install adb driver on windows after that type 1 and press enter. And Then It'll boot into Recovery.
Step : 5
Go to TWRP Recovery
Wipe Everything Except Device storage where u put the rom and gapps.
Step : 6
Flash resurrection rom then gapps and reboot device.
yea i tried but still no dice
moman2000 said:
I forgot to add the links, I have also changed the steps so it works for you:
Step : 0
Backup Ur Personal Data,
Step : 1
Download Your resurrection rom and gapps
Copy it to your phone sd card
Step : 2
Download Stock Lollipop Rom From HERE Select Version 23.4.A.1.264
Then Flash It via Flashtool
Step : 3
Then Latest Version of KingRoot from here
Install king root on ur stock lollipop rom and make sure ur internet connection is stable and open kingroot and root it.(It'll take 1-2 min)
Step : 4
After that download this XZDualRecovery From here
Extract recovery.zip on ur windows and run install.bat type 4 let it install adb driver on windows after that type 1 and press enter. And Then It'll boot into Recovery.
Step : 5
Go to TWRP Recovery
Wipe Everything Except Device storage where u put the rom and gapps.
Step : 6
Flash resurrection rom then gapps and reboot device.
Click to expand...
Click to collapse
yea i tried but still no dice
DarkEvE said:
yea i tried but still no dice
Click to expand...
Click to collapse
what does not work, the root process?
moman2000 said:
what does not work, the root process?
Click to expand...
Click to collapse
well i follow each step till the end but when i reboot the device after flashing everything the phone doesnt boot up so i need to flash the stock rom again so its like back to square one...
DarkEvE said:
well i follow each step till the end but when i reboot the device after flashing everything the phone doesnt boot up so i need to flash the stock rom again so its like back to square one...
Click to expand...
Click to collapse
IS your bootloader unlocked?