When I unlocked my bootloader I made a backup of the TA partition beforehand.
Everything went fine, I installed a CM12 ROM, no problem. Lollipop goodness! Yay.
Restoring the TA partition I left until this morning. The restore appeared to go successfully, but when I selected reboot device, it turned off, but not back on again.
When I hold on the power button. It vibrates, but does not turn on.. Nothing has appeared on the screen since I rebooted after the TA restore.
red reset button doesn't appear to do anything. I am fully charged. .... At least I think so. When the charger is connected, I get a red flashing light..
PC Companion will not connect to the phone.
I managed to unbrick it...
http://forum.xda-developers.com/showthread.php?t=2428319
OMFG... lol
RedMist said:
When I unlocked my bootloader I made a backup of the TA partition beforehand.
Everything went fine, I installed a CM12 ROM, no problem. Lollipop goodness! Yay.
Restoring the TA partition I left until this morning. The restore appeared to go successfully, but when I selected reboot device, it turned off, but not back on again.
When I hold on the power button. It vibrates, but does not turn on.. Nothing has appeared on the screen since I rebooted after the TA restore.
red reset button doesn't appear to do anything. I am fully charged. .... At least I think so. When the charger is connected, I get a red flashing light..
Click to expand...
Click to collapse
If you restore your TA, you lock the bootloader automatically, then you can't Boot a custom ROM
Sent From my Xperia Z Ultra C6833 using MultiROM
CM 12.1 (5.1 Lollipop)
LiquidSmooth 4.0 (5.0.2 Lollipop)
Stock Rom (4.4.4 KitKat)
Interesting thanks.
So am I right in saying you only need to restore the TA when you want to return to stock?
And therfore you lose drm and screen quality when using a custom rom.
RedMist said:
Interesting thanks.
So am I right in saying you only need to restore the TA when you want to return to stock?
Click to expand...
Click to collapse
Yes that is Right
Sent From my Xperia Z Ultra using MultiROM
CM 12.1 (5.1 Lollipop)
LiquidSmooth (5.0.2 Lollipop)
Stock ROM (4.4.4 KitKat)
the-cortana-project said:
Yes that is Right
Click to expand...
Click to collapse
Thanks for explaining. I didn't realise the bootloader and ta partition were linked
RedMist said:
Interesting thanks.
So am I right in saying you only need to restore the TA when you want to return to stock?
And therfore you lose drm and screen quality when using a custom rom.
Click to expand...
Click to collapse
Yes, but I Think, Use a Custom ROM because that is Vetter, and the Bravia and X-Reality Engine are only enabled in the Album APP, and i Think it is very useless
the-cortana-project said:
Yes, but I Think, Use a Custom ROM because that is Vetter, and the Bravia and X-Reality Engine are only enabled in the Album APP, and i Think it is very useless
Click to expand...
Click to collapse
YesI agree, I will try again after my long weekend away. Frustrating I had I working 100% and then messed it up.
Cheers!!
Related
Hey All,
I tried looking up answers here and via google, but all of them refer to bootloops/hangs after flashing a rom.
I've been using the prerooted JB rom via the guide given by Pandemic . Following the guide to the letter, the rom is working fine, and the recovery is accessible after installing via atis112's method. However, the problem I've run into is that whenever I restore a backup through CWM after flashing a mod (tested with Cybershot mod and ACiD audio mod), my phone hangs upon cold booting.
Immediately after restoring the backup, the phone boots into the restored OS without any problems, and hot boots (Power button + Volume Up button) also work fine - when I power off the phone and then start it up, it hangs on the sony logo (no bootloop, and can't access CWM recovery), after which I have to use flashtool and follow Pandemic's guide again to get JB. I've tried the following methods to see if anything changes, but the result is the same:
Method 1:
1- Backup through CWM recovery
2- Flash mod and wipe cache+dalvik cache
3- Reboot and test mod
4- Reboot and access recovery
5- Restore created backup
Result: Hangs at cold boot
Method 2:
1-4: same as method 1
5- Advance Restore > restore only /data from created backup
Result: Hangs at cold boot
Method 3:
1-4: same as method 1
5- Normal restore
6- Wipe data/factory reset (preserves any changes on /system, wanted to see if /data was the culprit)
Result: Hangs at cold boot
The above 3 methods were also tried by wiping cache+dalvik cache after restoring the backup, but that had no effect either. Has anyone else been having the same or a similar problem? Can someone kindly refer me to a solution to this?
Edit 1: The phone was finally able to boot into android after about hanging at the sony logo for about 20-25 mins. Tested restoring various other restore points and each time the phone hung for about 20 minutes or so. After that initial boot, the phone boots up within a minute as always. Still haven't been able to narrow down the problem causing the delay on the first boot.
@H4R81N63R bro,I think that's because you installed cybershot mod and AC!D . Try with a clean install of the rom and try installing only cybershot without intsalling AC!D and check if boots without issues. Not sure if this causes the issue but test it if you want.
Thanks for the suggestion. Flashing works fine and the phone boots up without issues. Its just that whenever I restore any backup I had made before flashing the mod, the phone takes a long time at the sony logo only during cold boots (kind of annoying really).
H4R81N63R said:
Thanks for the suggestion. Flashing works fine and the phone boots up without issues. Its just that whenever I restore any backup I had made before flashing the mod, the phone takes a long time at the sony logo only during cold boots (kind of annoying really).
Click to expand...
Click to collapse
Try backup a fresh flashed Rom with only cybershot mod installed and check if restore works.
DaRk-L0rD said:
Try backup a fresh flashed Rom with only cybershot mod installed and check if restore works.
Click to expand...
Click to collapse
Tried that as well, still the same. The hang ups seem to vary in time though, sometimes its just 10 mins, other times its about 30 mins. Is it possible to somehow see the processing that android is doing during bootup to see where its hanging up (similar to desktop OS'es)?
H4R81N63R said:
Tried that as well, still the same. The hang ups seem to vary in time though, sometimes its just 10 mins, other times its about 30 mins. Is it possible to somehow see the processing that android is doing during bootup to see where its hanging up (similar to desktop OS'es)?
Click to expand...
Click to collapse
Don't know how do that mate. Did you try using a custom kernel with cwm5?
DaRk-L0rD said:
Don't know how do that mate. Did you try using a custom kernel with cwm5?
Click to expand...
Click to collapse
Can't - have a locked bootloader (might unlock it if someone figures out how to bring back the drm keys, or to circumvent them). It's possible that the devs might know something about this issue, but I'm not sure who to call on.
H4R81N63R said:
Can't - have a locked bootloader (might unlock it if someone figures out how to bring back the drm keys, or to circumvent them). It's possible that the devs might know something about this issue, but I'm not sure who to call on.
Click to expand...
Click to collapse
here is how to relock bootloader http://forum.xda-developers.com/showthread.php?t=1920195&highlight=relock+bootloader
So you can unlock it if you want. Works on jb also
DaRk-L0rD said:
here is how to relock bootloader http://forum.xda-developers.com/showthread.php?t=1920195&highlight=relock+bootloader
So you can unlock it if you want. Works on jb also
Click to expand...
Click to collapse
Hmm, looked into your link and another, but it seems DRM keys are lost in the process - I'm partial to Bravia
Hopefully a dev might have some more info regarding the boot hang up.
Hello people, since today i have the exact same problem as the topic maker
I am on stock Jelly Bean 6.2.A.1.100 with thesliding XP kernel (tried v8.3 and v9 beta with same results)
I am really frustrated right now because i don't have cybershot mode nor acid, it started to happen today after i tried a custom rom and didn't liked it so i did a restore with the backup i made .... :/
arnes_king said:
Hello people, since today i have the exact same problem as the topic maker
I am on stock Jelly Bean 6.2.A.1.100 with thesliding XP kernel (tried v8.3 and v9 beta with same results)
I am really frustrated right now because i don't have cybershot mode nor acid, it started to happen today after i tried a custom rom and didn't liked it so i did a restore with the backup i made .... :/
Click to expand...
Click to collapse
I haven't been able to find a solution yet. For now, the only thing that works is to boot it up so that it gets stuck on the sony/kernel logo and wait till it boots into the OS (may take 10 mins, or may take 40, can't seem to find a pattern). I do tend to attach the power cable just to be sure that it doesn't run out the battery.
A little off topic and near to your problem, cybershot is only supporting ICS roms at the moment, but I have found that their 4.7.2 and 5.1.1 work with the JB based MoonBreakers v3.5 rom that I have. As for AC!D, haven't been able to make their mod work on JB yet (even the universal one supporting JB 4.1 and above doesn't work).
Hello all, i just wanted to share with you that i have successfully fixed the problem and here is what i did :
I just used Flashtool and flashed the latest stock JB FW which was on the phone earlier, but i unticked the "Wipe data" option, after that i flashed again a custom kernel and now the phone boots normal and i didn't loose any data
Actually that doesn't fix the problem - we are talking about restore because we have multiple mods installed as well - we can't just keep reinstalling all of them every time we test something new.
Sent from my LT22i using xda app-developers app
H4R81N63R said:
Actually that doesn't fix the problem - we are talking about restore because we have multiple mods installed as well - we can't just keep reinstalling all of them every time we test something new.
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Yeah you are right the problem will surely be there again if i do a restore, but anyhow now i don't have the problem and i am happy for now
I have same problem.
After restored backup, device booted successfully only first reboot.
but device hung up on the sony logo thereafter.
My device is installed cybershot7.9.1 MOD without acid.
Same error here, is there any solution?
Gesendet von meinem LT22i mit Tapatalk
xaver54645 said:
Same error here, is there any solution?
Click to expand...
Click to collapse
Sorry mate, I haven't found any solution but to leave it alone (plugged in with the charger of course) for up to 40 mins while it waits at the logo before booting up
xaver54645 said:
Same error here, is there any solution?
Gesendet von meinem LT22i mit Tapatalk
Click to expand...
Click to collapse
Hmmm I had this too.
What if you install the CWM for LB reboot and restore again?
I had this too couple of days ago
H4R81N63R said:
Sorry mate, I haven't found any solution but to leave it alone (plugged in with the charger of course) for up to 40 mins while it waits at the logo before booting up
Click to expand...
Click to collapse
Is the next cold boot faster then? If yes, I could live with that.
@ChikeD
Nope, still the same. Even with my second phone with unlocked bootloader I'm stuck at Sony logo after restore
I somewhere read that immediately after restoring the backup reflashing the kernel should help, but that's only an option for UB I guess.
Didn't try that yet.
xaver54645 said:
Is the next cold boot faster then? If yes, I could live with that.
@ChikeD
Nope, still the same. Even with my second phone with unlocked bootloader I'm stuck at Sony logo after restore
I somewhere read that immediately after restoring the backup reflashing the kernel should help, but that's only an option for UB I guess.
Didn't try that yet.
Click to expand...
Click to collapse
And resoring after flashing stock?
I would have tried that but I didn't realized the problem is related to the kernel.
Hello,
I just got my Z ultra yesterday. Set up everything, installed dual recovery and rooted, backed up TA partition, backed up via Titanium and Helium, and then through recovery, and then attempted to flash PA 4+. Now my phone will not turn on. When I press the power button it vibrates once but nothing happens. I can get the blue led to turn on for flash mode but screen is still off. I read through the PA 4+ and did not find anything, how can I fix it, will it be done with Flashtool? This is the first time I have had problems as I could usually always find a fix on the forum for my note 2.
Edit: Sony C6833 running kitkat .108 with a locked bootloader. Backups are all on the EXT SD Card.
tylermus said:
Hello,
I just got my Z ultra yesterday. Set up everything, installed dual recovery and rooted, backed up TA partition, backed up via Titanium and Helium, and then through recovery, and then attempted to flash PA 4+. Now my phone will not turn on. When I press the power button it vibrates once but nothing happens. I can get the blue led to turn on for flash mode but screen is still off. I read through the PA 4+ and did not find anything, how can I fix it, will it be done with Flashtool? This is the first time I have had problems as I could usually always find a fix on the forum for my note 2.
Edit: Sony C6833 running kitkat .108 with a locked bootloader. Backups are all on the EXT SD Card.
Click to expand...
Click to collapse
Bootloader needed to be unlocked, see this thread.
http://forum.xda-developers.com/xperia-z-ultra/general/bricked-help-t2828853
adfurgerson said:
Bootloader needed to be unlocked, see this thread.
http://forum.xda-developers.com/xperia-z-ultra/general/bricked-help-t2828853
Click to expand...
Click to collapse
Thank you, I'm glad to see that I'm not the only one who made this mistake. I will post as soon as I get home and am able to flash. Right now I have been thumbing through all the threads and had just come across using Flashtool and the stock FTF to get it bootable again. Thank you for the quick response.
tylermus said:
Thank you, I'm glad to see that I'm not the only one who made this mistake. I will post as soon as I get home and am able to flash. Right now I have been thumbing through all the threads and had just come across using Flashtool and the stock FTF to get it bootable again. Thank you for the quick response.
Click to expand...
Click to collapse
Posting update, was able to flash and boot. Phone is back up and running.:victory:
You didn't research before trying to flash a custom ROM did you?
I did the same damn thing day one but I got lucky. Hopefully this will show as a lesson to others that just jump in. But then again I guess that's how all learn.
Well I read one post that stated that as long as you kept the stock kernel you could flash. Just didn't realize only some roms worked. Also everything I'd different from my old Verizon note 2.
Sent from my C6833 using XDA Free mobile app
Black screen after twrp beanstalk 4.4.4
Full wipe re-format data
firmware still 4.4.2
Secure boot -yes
Locked state -Locked
I Fast boot doul recovery
Zu_Gpe-advstkkernel-KOT49H.s2.2052-v01
Using windows 8.1 64bit
Still can't boot?
jojoshizzle said:
Black screen after twrp beanstalk 4.4.4
Full wipe re-format data
firmware still 4.4.2
Secure boot -yes
Locked state -Locked
I Fast boot doul recovery
Zu_Gpe-advstkkernel-KOT49H.s2.2052-v01
Using windows 8.1 64bit
Still can't boot?
Click to expand...
Click to collapse
^ Fix that.
Have you backed up the TA partition?
Did you flash the GPe version of beanstalk?
How did you install the ROM zip?
I'm at work for the next 9 or 10 hours and probably won't hell cell service, but I'll think on the best way to recover the phone with out loss of a working camera and DRM keys - unlocking the BL on 4.4.2 normally leaves the camera somewhat broken
reply
jojoshizzle said:
Black screen after twrp beanstalk 4.4.4
Full wipe re-format data
firmware still 4.4.2
Secure boot -yes
Locked state -Locked
I Fast boot doul recovery
Zu_Gpe-advstkkernel-KOT49H.s2.2052-v01
Using windows 8.1 64bit
Still can't boot?
Click to expand...
Click to collapse
blueether said:
^ Fix that.
Have you backed up the TA partition?
Did you flash the GPe version of beanstalk?
How did you install the ROM zip?
tool flashed successfully the original (rom C6806_14.3.A.0.681 US_Unbranded.ftf )
I'm at work for the next 9 or 10 hours and probably won't hell cell service, but I'll think on the best way to recover the phone with out loss of a working camera and DRM keys - unlocking the BL on 4.4.2 normally leaves the camera somewhat broken
Click to expand...
Click to collapse
Yes I backed up the TA left a copy on my computer. and I had it rooted and flashed beanstalk with twrp
Now
a different problem
tool flashed successfully the original rom (C6806_14.3.A.0.681 US_Unbranded.ftf )
but once i discontected from pc it dosnt turn on
has a red light when i connect it to pc the pc reconises something is connected i get the connection chime sound
when i connect it to the power cord i get a red light for one second then dark.
called google support they weren't any help
jojoshizzle said:
Yes I backed up the TA left a copy on my computer. and I had it rooted and flashed beanstalk with twrp
Now
a different problem
tool flashed successfully the original rom (C6806_14.3.A.0.681 US_Unbranded.ftf )
but once i discontected from pc it dosnt turn on
has a red light when i connect it to pc the pc reconises something is connected i get the connection chime sound
when i connect it to the power cord i get a red light for one second then dark.
called google support they weren't any help
Click to expand...
Click to collapse
Bad news, you have hard bricked it by flashing an ftf to GPe phone.
jojoshizzle said:
Yes I backed up the TA left a copy on my computer. and I had it rooted and flashed beanstalk with twrp
Now
a different problem
tool flashed successfully the original rom (C6806_14.3.A.0.681 US_Unbranded.ftf )
but once i discontected from pc it dosnt turn on
has a red light when i connect it to pc the pc reconises something is connected i get the connection chime sound
when i connect it to the power cord i get a red light for one second then dark.
called google support they weren't any help
Click to expand...
Click to collapse
adfurgerson said:
Bad news, you have hard bricked it by flashing an ftf to GPe phone.
Click to expand...
Click to collapse
Unfortunately adfurgerson is correct.
You might want to talk to @the_laser and see if they can help, but you have over written all of the partitions of the ZU GPe. Have a read of (and maybe post to) the Hard Brick thread in the general section, but DON'T flash anything from that thread.
blueether said:
Unfortunately adfurgerson is correct.
You might want to talk to @the_laser and see if they can help, but you have over written all of the partitions of the ZU GPe. Have a read of (and maybe post to) the Hard Brick thread in the general section, but DON'T flash anything from that thread.
Click to expand...
Click to collapse
Thanks guys
The retailer I bought it from is taking it back today for exchange they ask me if I want different model number
Should I stay with the gpe c6806 or get the gpe c6833
I live in Sacramento on T-Mobile LTE
Hi All,
I've just unlocked my Z2's bootloader and flashed AuRom V4
Since doing so, my Video Unlimited seems to be broken, I keep getting 'Network Unavailable' when trying to sign in...
Does anyone have a definitive solution for this or is this a definite side effect of unlocking the bootloader?
I couldn't seem to find a definitive answer but I would very much like to get it working again as I have lots of content on Video Unlimited I'd like to enjoy on the phone.
I did backup my TA Partition, but the problem remains!
Any help would be appreciated!
Side effect, it relies on the drm keys in the ta partition
Sent from my Xperia Z2 using Tapatalk
Mr.R™ said:
Side effect, it relies on the drm keys in the ta partition
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Hmm, well I think I've just made my first n00b mistake...
I backed up the TA partition before I left Stock.
Because I wanted to get video unlimited back I figured I may as well restore the partition and the keys, so I plugged in the usb cable and pushed restore TA partition.
The integrity checks said restore success, restart phone? Now the phone won't boot, not even to the xperia logo I just get a vibration and nothing else...
Please don't tell me I've bricked the thing If I have I guess I should have read more carefully :/
MurphmanL said:
Hmm, well I think I've just made my first n00b mistake...
I backed up the TA partition before I left Stock.
Because I wanted to get video unlimited back I figured I may as well restore the partition and the keys, so I plugged in the usb cable and pushed restore TA partition.
The integrity checks said restore success, restart phone? Now the phone won't boot, not even to the xperia logo I just get a vibration and nothing else...
Please don't tell me I've bricked the thing If I have I guess I should have read more carefully :/
Click to expand...
Click to collapse
try reunlocking your bootloader
use flashtool to flash stock firmware
repush ta partition
Envious_Data said:
try reunlocking your bootloader
use flashtool to flash stock firmware
repush ta partition
Click to expand...
Click to collapse
Thankfully I've recovered back to stock. I will stay on stock for some time now with my movies unlimited working until I feel particularly gutsy again and fancy dipping my toes into Custom Roms again !
Was worried for a minute there I'd toasted the thing!
MurphmanL said:
Thankfully I've recovered back to stock. I will stay on stock for some time now with my movies unlimited working until I feel particularly gutsy again and fancy dipping my toes into Custom Roms again !
Hi i have the same problem, I locked my bootloader again and am back on stock Rom but my video unlimited still doesn't work... How did you do it?
Click to expand...
Click to collapse
drgigaherz said:
MurphmanL said:
Thankfully I've recovered back to stock. I will stay on stock for some time now with my movies unlimited working until I feel particularly gutsy again and fancy dipping my toes into Custom Roms again !
Hi i have the same problem, I locked my bootloader again and am back on stock Rom but my video unlimited still doesn't work... How did you do it?
Click to expand...
Click to collapse
Hi,
The experience of holding a dead Z2 in my hand was not a pleasent one so it has put me off custom romming for a while on this device until I do a bit more reading as coming from a Samsung Note 2 where I never had a bricking episode...
Basically as I had nothing to lose, I downloaded Stock Generic DE firmware .314 and flashed it using flashtool and it has not only revived the phone but my movies unlimited and everything else is working.
I am guessing because I restored the TA partition (bricking my phone) my TA partition was then intact and then upon installing the stock firmware everything is back to normal
Pity really, my battery life was better with the Custom Rom, but it's a tough toss up as I am an avid user of movies unlimited!
Click to expand...
Click to collapse
I'm on .28 existenz Y but no matter which rom/stock i use, photo quality is terribly weak. For example, the front camera, It has a lot of noise, whatever or is sunny or is dark. The rear camera makes good pictures until you look at the details. What is wrong? You know how to correct it?
Someone also has the impression that xperia Z2 doing ugly pictures?
botanicfts said:
I'm on .28 existenz Y but no matter which rom/stock i use, photo quality is terribly weak. For example, the front camera, It has a lot of noise, whatever or is sunny or is dark. The rear camera makes good pictures until you look at the details. What is wrong? You know how to correct it?
Someone also has the impression that xperia Z2 doing ugly pictures?
Click to expand...
Click to collapse
Do you have unlocked bootloader? If yes what is with your DMR keys?
Sent from my D6503 using XDA Free mobile app
drlemi said:
Do you have unlocked bootloader? If yes what is with your DMR keys?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
i have unlocked bootloader, i tried to restore this DMR keys, but doesnt work
botanicfts said:
i have unlocked bootloader, i tried to restore this DMR keys, but doesnt work
Click to expand...
Click to collapse
Here is a simple DRM restore solution:
1.flash .69 ftf
2.relock and unlock the bootloader after that
3.turn on the phone and force it off(volup+power)
4.flash .28 ftf without TA
5.flash Androplus kernel(to get recovery) and in TWRP flash the DRM restore zip
6.it should work
BlAckXpeRia said:
Here is a simple DRM restore solution:
1.flash only TA partition from .69 ftf
2.flash .28 ftf without TA
3.flash the DRM restore zip
4.it should work
Click to expand...
Click to collapse
should, but doesnt
botanicfts said:
should, but doesnt
Click to expand...
Click to collapse
Tried it ?
botanicfts said:
should, but doesnt
Click to expand...
Click to collapse
Those instructions worked for me and for everyone else. It has to work with your device, there is no reason it shouldn't. It also worked on my Z1.
I forgot to mention that you need to relock and unlock the bootloader after you flash .69. I updated my previous post with proper instructions.
BTW I have the device from 5 days and did it, so is can't be a problem for you.
Pandemic said:
Tried it ?
Click to expand...
Click to collapse
yup, 2 times, doesnt work
BlAckXpeRia said:
Those instructions worked for me and for everyone else. It has to work with your device, there is no reason it shouldn't. It also worked on my Z1.
I forgot to mention that you need to relock and unlock the bootloader after you flash .69. I updated my previous post with proper instructions.
BTW I have the device from 5 days and did it, so is can't be a problem for you.
Click to expand...
Click to collapse
i did this 2 times, with my phone and from my friend, still doesnt work for both, idk why. i have original TA.img from my phone, before i have uncloked this bootloader, can that help me?
botanicfts said:
yup, 2 times, doesnt work
i did this 2 times, with my phone and from my friend, still doesnt work for both, idk why. i have original TA.img from my phone, before i have uncloked this bootloader, can that help me?
Click to expand...
Click to collapse
I think not.
You must be forgetting something. Are you using .69 or other kk ftf? It must be .69 to work. Also, the relocking has to happen while on .69(in my case it didn't even boot like the original instruction said, but it worked). The .69 firmware ABSOLUTELY needs to have TA in it! Maybe that is the mistake? I can't think of other reasons.
BlAckXpeRia said:
I think not.
You must be forgetting something. Are you using .69 or other kk ftf? It must be .69 to work. Also, the relocking has to happen while on .69(in my case it didn't even boot like the original instruction said, but it worked). The .69 firmware ABSOLUTELY needs to have TA in it! Maybe that is the mistake? I can't think of other reasons.
Click to expand...
Click to collapse
ok, I'll do it as soon as let you know. what i want to do? i want back this DRM keys, but i want to flash existenz too, should it work?
I'm interested in this too, currently I'm on existenz with androplus kernel, but I want to get DRM back because the camera quality is really bad.
can I flash .69, then lock and unlock the bootloader, then flash the existenz rom, after the androplus kernel and after the DRM fix?
the problem that I'm facing, or at least I think it is, the existenz rom is a zip, and I need to flash a ftf, right?
jok3r4u said:
I'm interested in this too, currently I'm on existenz with androplus kernel, but I want to get DRM back because the camera quality is really bad.
can I flash .69, then lock and unlock the bootloader, then flash the existenz rom, after the androplus kernel and after the DRM fix?
the problem that I'm facing, or at least I think it is, the existenz rom is a zip, and I need to flash a ftf, right?
Click to expand...
Click to collapse
that's what I'm doing now.
1. flash .69
2. lock bootloader
3. flash .69 again
4. unlock bootloader
5. flash .28 without TA partition (check under exclude)
6. flash androplus kernel
7. drm fix
8. existenz
when still doesnt work, whatever im gonna kill myself
whoa, take it easy, the phone doesn't worth it
if it works, can you post a link to the right files to flash and how to do so, I just got my phone the other day and I don't wanna mix something up with it already.
*haven't flashed any ftf files yet, still have to figure it out how to do it.
jok3r4u said:
whoa, take it easy, the phone doesn't worth it
if it works, can you post a link to the right files to flash and how to do so, I just got my phone the other day and I don't wanna mix something up with it already.
*haven't flashed any ftf files yet, still have to figure it out how to do it.
Click to expand...
Click to collapse
@@edit
when i check drm keys with this service menus, that says [unknown error] and [active] what does it mean?
You can restore your DRM partition using your TA.img. Just download Backup-TA from here http://forum.xda-developers.com/showthread.php?t=2292598
connect your phone with USB debugging on then open .bat file of script then select "Convert TA.IMG". At this point there must be some folder to tell your where you put your img in. After there's a backup restore by press 2.
so a simple restore is enough and no need to go through the .69 flash/DRM fix zip ? are you sure ?
My TA backup was done on 4.4.x rom, would it work normally on LP roms ?
http://www.mrcrab.net/viewstockrom/12900-d6503.html
Try this FTF
Perform these steps
1. lock bootloader using Flashtools
2. flash 17.1.A.2.69 TW with full wipe
3. reboot, check camera and x-reality - OK
4. unlock bootloader
5. reboot, check camera and x-reality - still OK
6. root, install recovery
7.Install your rom
8.Install DRM restoration zip for LOLLIPOP
9.Reboot and restore your data. (Including your SD Card)
BlAckXpeRia said:
Here is a simple DRM restore solution:
1.flash .69 ftf
2.relock and unlock the bootloader after that
3.turn on the phone and force it off(volup+power)
4.flash .28 ftf without TA
5.flash Androplus kernel(to get recovery) and in TWRP flash the DRM restore zip
6.it should work
Click to expand...
Click to collapse
Does this work if you unlocked the bootloader but didnt backup the DRM keys?
Eanan said:
Does this work if you unlocked the bootloader but didnt backup the DRM keys?
Click to expand...
Click to collapse
Yes. It is made exactly for that.
BlAckXpeRia said:
Yes. It is made exactly for that.
Click to expand...
Click to collapse
Ok, where do I get the .69 ftf and the .28 ftf? ive never heard of these ftf things.
Thanks