yashsingh1/xdaforums huggingface dataset:
[Xperia Z Original Android Development] silencer51:
No problem, with your method, while riskier, I have a cleanly flashed .235 with root. :)

run in superuser:

/system/bin/stop ric

in a terminal app, this stops the reboots when messing around the system folder.

you need to run it at every boot though.
[Xperia Z Original Android Development] Incanity:
I'll make a note in the OP about this. Thank you very much!
[Xperia Z Original Android Development] mjs87:
heyy

I have the stock ROM installed 253 from sony updater,

I can now start directly from step 1 to rooten?,

* and if I want to make the TA backup than he indicates that the file sdcard / backup TA. ** does not exist
[Xperia Z Original Android Development] silencer51:
You need to downgrade to a rootable ROM first (like .434).

Flash .434, root it, then make a TA backup, then flash .235 and proceed.

If you 're already on .235 and haven't taken a TA backup there is no way to do it without downgrading first...
[Xperia Z Original Android Development] mjs87:
so I downgrade to 434 and then I go root

Bootlock unlock or not?

and then the stock kernel over flash

and restore the TA

as I understand it?

sorry for my english
[Xperia Z Original Android Development] [NUT]:
Flash this http://www.fun-industries.nl/xda/?dlid=c3VwZXJ1c2Vy in CWM or TWRP, it will fix the reboot issues.

NOTE: It will also install Superuser.apk to /system/app ... so if you have SuperSU installed, you will need to do the 'super user shuffle' to change it back.
[Xperia Z Original Android Development] silencer51:
1) Downgrade to .434 by flashing an appropriate FTF file through Flashtool

2) Root it via one of the rooting toolkits available here on xda

3) Backup TA (make sure you have a proper backup!)

4) Update to .235 via PC Companion or SUS

5) Unlock bootloader

6) Flash Advanced Stock Kernel by DoomLord

7) Root through CWM Recovery

8) flash stock .235 through Flashtool and appropriate .ftf

9) relock bootloader through a TA restore

these are the steps, pretty much
[Xperia Z Original Android Development] jjocer:
I updated my phone to 235 via PC Companion, but I didn't check if this version is rooted, so I flashed back 434, root and backup TA, but now PC Companion and SUS don't update my phone (no update available...). Can I flash 235 via flashtool or I have to wait?
[Xperia Z Original Android Development] [NUT]:
Click the 'Update to 10.1.1.A.1.253' link in my signature, it will update your device and root it.

With an unlocked bootloader the SUS and PC Companion update services will ignore your phone. You need to re-lock to make them update your phone again.
[Xperia Z Original Android Development] jjocer:
But my phone has locked bootloader.
[Xperia Z Original Android Development] [NUT]:
Hmm, then you flashed a .434 FTF which turned your phone into something you did not buy :p

Flash the update package in my signature, it will get you going, rooted and with dual recovery :D
[Xperia Z Original Android Development] jjocer:
I checked in service info: Bootloader unlock allowed: NO. Before flashing I had yes?! I flashed this http://xdaforums.com/showthread.php?t=2235046.

Bravia engine is working.
[Xperia Z Original Android Development] Incanity:
I believe that there are some threads on this. There is a way to go around the allowed=no on an unbranded phone. I had the same, I used PC companion to update my XZ to. 253 and the bootloader unlock allowed changed to yes.

From there I unlocked the bootloader, rooted, and restored the TA. Now it still says bootloader unlock allowed = yes

Sent from my glorious Xperia Z C6603
[Xperia Z Original Android Development] [NUT]:
Check the Z rooting thread by DooMLoRD, there is a flashable fix in there by someone.
[Xperia Z Original Android Development] jjocer:
Your guide works, and evyrything is ok now. Thanks.
[Xperia Z Original Android Development] californicated:
No relocking of the bootloader --> no reboot bug. Right?
[Xperia Z Original Android Development] flechaig:
Have you tried this http://xdaforums.com/showpost.php?p=41541856&postcount=1 ? No bootloader unlock, so no data wipe.

I will try tonight and let you know if it works.

EDIT : It worked perfectly without unlocking/relocking bootloader (no wipe).
[Xperia Z Original Android Development] press_enter:
From what i see in step 5 you do unlock and relock the bootloader, so you are loosing the warranty anyways, right? :|

S.
[Xperia Z Original Android Development] Incanity:
no, by restoring TA partition, you make the bootloader look like it's never unlocked before.
[Xperia Z Original Android Development] Rodrigo Vilhena:
On this step:

Second, Go back to the service menu.

- Service Tests

- Verify Certificates

- Check if your certs are all there and intac

How should be the Certificates, I haven't seem before to do all the stuffs :silly:

Can you please help, I just want to know if every thing is right.

Thanks a lot.
[Xperia Z Original Android Development] Incanity:
Here's a screen from my certificate screen, if yours look similar, you're all good

Sent from my glorious Xperia Z C6603
[Xperia Z Original Android Development] SXUsr:
Sounds like your BL was already unlockable to begin with, and assume that all those claiming their status has now changed were also able to unlock their BL in the first place, so by People now making a such a big deal about it it's causing a lot of confusion. Operator locked Phones have never been able to be unlocked just by flashing FW, so I don't see what's changed now?

bootloader unlock allowed = yes after flashing 253

[development] bypassing/rewriting bootloader
[Xperia Z Original Android Development] Incanity:
Probably, yes.

I assume it was caused by the rooting process of. 434.

Sent from my glorious Xperia Z C6603
[Xperia Z Original Android Development] Osyx:
That's the wrong screen, the one you should look at is service tests/security and it should look like this:

Skickat från min C6603 via Tapatalk 2
[Xperia Z Original Android Development] Rodrigo Vilhena:
Mine is not like that.

This is mine.

https://www.dropbox.com/s/ua919scosoyunyo/Screenshot_2013-05-26-19-16-05.png

I'll try again tomorrow.

Thanks.
[Xperia Z Original Android Development] Osyx:
The one you show me is under Service tests/certificates you should look under Service tests/security.

Skickat från min C6603 via Tapatalk 2
[Xperia Z Original Android Development] Rodrigo Vilhena:
Why is mine like that, I've back to stock 434, all stock and my certificates look the same.

FW 434 Stock BL Locked:https://www.dropbox.com/s/skhl7cspxgrtl8m/434 stock certificates.png

FW 434 BL Unlocked: https://www.dropbox.com/s/dt5h51wa0fn6rtn/FW 434 BL Unlocked.png

So my certificates is not working? What that means?

How do I fix that?

Thanks.

Edited: Sorry, I get now. I was looking the wrong Service!!! My fault.

Ok mine is just like yours. Service tests / security

Thanks a lot.
[Xperia Z Original Android Development] Rodrigo Vilhena:
I've restored 434 stock, with Pc Companion, and this is how looks my screen: (BL Lock and all Stock)

https://www.dropbox.com/s/0hm9oz4fwj1oqb0/FW 434 stock BL Locked Sevice tests - security.png

I think there is some think wrong.

No metter what I do, I can't change MARLIN and WMLA [Unknow Error]

What that means? I lost my DRM? Even flashing stock back it still get that way.

Thanks for the attention guys.
[Xperia Z Original Android Development] Incanity:
And what if you try unlocking BL again and restoring your TA again?

Sent from my glorious Xperia Z C6603
[Xperia Z Original Android Development] Rodrigo Vilhena:
I did but did not worked.

I tried to dowgrade, 434, tried pc companion repair, tried others FW and nothing. (Marlin and WMLA show unknown error)

Could you please upload yours TA backup, so I try to use yours and see if it works for me? If you could do that for me I really apriciate that!

Wich model is yours? And wich FW are you using US, MEA?

Thank you very much.
[Xperia Z Original Android Development] Incanity:
oh no no no,

using someone else's TA backup will hard brick your device.

please don't try that.

I'm afraid that if restoring your backup doesn't work, you've lost your DRM keys... I'm sorry..

*EDIT*: http://xdaforums.com/showthread.php?t=2292598

there have been some reports on bugs in the TA backup program. Maybe there is a fix for your problem in that thread somewhere.
[Xperia Z Original Android Development] Osyx:
Wait, you haven't restored a TA backup? Then you're forced to live without DRM keys forever, sorry mate but you've to have made an TA backup or all your efforts will be for nothing.

Skickat från min C6603 via Tapatalk 2
[Xperia Z Original Android Development] Rodrigo Vilhena:
I know, I was stupid, did not read enought about it.

Jus did the unlock BL, I came from an S3, and there wasn't that kind of stuff.

But it's ok.

Just one more question, what do I loose? BE2 on pics, and what more?

Thanks.
[Xperia Z Original Android Development] Osyx:
BE2, Music Info thingy (but still work on some), OTA updates (can cause problems) and your warranty.

Skickat från min C6603 via Tapatalk 2
[Xperia Z Original Android Development] :
I skipped to flash the stock kernel before restoring ta and my phone wont start but i can get into fastboot, should i unlock it again and flash the stock kernel? will that boot up my phone or should i send it to the service center?
[Xperia Z Original Android Development] kamalmawa:
DRM certificates requires the stock kernel signature.. So it won't boot.. Just flash the stock kernel only using flash tool it should work. Read the step 6 in OP
[Xperia Z Original Android Development] :
Flashtool wont work since my bootloader's locked now (restored the ta already, remember?)

so that's what i am asking, i have two options:

1. unlock the bootloader again, flash the stock kernel, boot up the phone and restore ta again

2. send the phone to service center and lose my data all over again [remember if i unlock my bootloader this time and am not able to boot it up i will have to send it to service center anyway and have to pay for it]

SO MY QUESTION IS IF I UNLOCK IT AGAIN AND FLASH STOCK KERNEL, WILL IT BOOT UP?

---------- Post added at 01:01 AM ---------- Previous post was at 12:47 AM ----------

And btw is there anyway to flash the TA.img through fastboot and what command should i give

(in case i cant boot up my phone)

EDIT:

Unlocked the device again and it booted up like nothing happened ;)
[Xperia Z Original Android Development] kamalmawa:
Why is that flashtool won't work? Just put your phone into flashmode and flash tft file with kernel only... I have done it so many times

PS: if you read the OP properly and followed them you wouldn't have run into any problems at all
[Xperia Z Original Android Development] Osyx:
Flashtool will ALWAYS work, no matter if you've locked, unlocked, relocked or have an nonunlockable device as long as you flash stock firmwares.

Skickat från min C6603 via Tapatalk 2
[Xperia Z Original Android Development] :
Never read this thread untill i ran into the problem

BTW since my bootloader was locked the flashtool said something like locked bootloader detected, go to unlockbootloader.sony.com or something like that, are you sure you used flashtool on a locked bootloader?
[Xperia Z Original Android Development] Osyx:
Yes... That's if you're trying to flash an other boot.img than stock on an locked one or if you're about to unlock it. If you just flash stock .ftf's you'll have absolutely no problems with flashtool.

Skickat från min C6603 via Tapatalk 2
[Xperia Z Original Android Development] silencer51:
Someone should try this with the latest .307 update, unless Sony has made changes to the TA partition (highly unlikely), then it should work.
[Xperia Z Original Android Development] dcx3:
Well it works :)
[MDA II, XDA II, 2060 General] Swiftcorp:
Hello,

In the past I am sure that my display screen went off after a certain time during a phone call (saving on battery life). I have noticed recently that the screen stays on the whole time, regardless of call length. I have looked through all the settings I can think off, and can't seem to find one relevant to auto screen shut off during a call.

I have installed Pocket Bluetooth Tools and PocketZenPhone (previously I was using My:Phone:Profiles).

Is there a setting I am missing, or some software that I can use to have an auto screen shut off during a call.

Many thanks for any help.
[MDA II, XDA II, 2060 General] Effan:
The screen will not turn off if Bluetooth headset is being used.

Normally, the screen will not turn off if there is any serial port activity (like while connected through activesync)
[MDA II, XDA II, 2060 General] GoldenSands:
Are you sure that in Settings/Backlight/Bttey Power: the "Turn Off Backlight" option is selected?, it should be selected to turn the device screen off after 30 seconds or so.

I use a car kit running on bluetooth, and the screen goes off after 30 seconds!
[MDA II, XDA II, 2060 General] Swiftcorp:
I've set both the power and the back light to go off after 1 minute. There is not normally a problem and the screen powers off ok, unless I'm on a call (with or without a bluetooth headset).
[MDA II, XDA II, 2060 General] mindracing:
There is an option in JGUI Phone Profiles that does this.

If you no longer have it installed then you won't get that effect.

When I uninstalled Phone Profiles I missed the screen off option so much I reistalled it just for that.
[MDA II, XDA II, 2060 General] boybi:
mine does.
[MDA II, XDA II, 2060 General] mindracing:
So does mine.
[MDA II, XDA II, 2060 General] powerppc:
After installing Pocket Bluetooth Tools (PBT), my screen won't turn off while on call. If I do turn it off during a conversation, my bluetooth headset cuts out while the other person is still on the phone and won't be able to recover it until I hang up.

If I have the timer working for the PBT, then my autoshut off will work, but that's after I change the timer from 60 seconds to 10 seconds in the registry. If I disable the timer, the autoshut off will work. So if you don't want to play around with the registry, then I suggest leaving PBT timer on.

But either way, if the timer is on or off, during a call, it won't turn off automatically with PBT installed. I like PBT because I was able to quickly connect to my headset faster than the built-in MS Bluetooth Stack.
[MDA II, XDA II, 2060 General] Swiftcorp:
I guess its a case of balancing the use of Pocket Bluetooth tools with the power saving function of having an auto screen cut off during a call. I'm not sure what is more important to me just now.

I am reluctant to return to My Phone Profiles. I am really enjoying the latest version of PocketZenPhone. I think I will make a request to have autoscreen included in a future version. Who knows, I might get lucky!
[MDA II, XDA II, 2060 General] powerppc:
IF you have Pocket Bluetooth installed, then while on call, it will not automatically turned off. But if you turned it off manually, while on call, it will cut out from the bluetooth headset and I find no way to get it back yet.
[Motorola Droid X2] Dasoccerguy:
Hello everyone. I'm a noob.

I have a Droid X2 and Verizon service. It was running Gingerbread 2.3.5 and version 1.3.418, and up until yesterday I hadn't even rooted it. I followed these instructions for CM10 carefully but apparently made a slight mistake.

I made sure to root properly: Superuser worked perfectly, I had Busybox, NANDroid, and Bootstrap Recovery all working, and the phone worked just like before.

In the tutorial I linked to above, I think I know where I went wrong. I downloaded GAPPS 4.2.2 (funky wording since he said 'latest' and then '4.1.x' , so not the latest) and then CM10 A3. I then went into BSR and installed from the external SD card. GAPPS succeeded, but CM10 did not (Status 7, some kernel disapproval or something). When I booted the phone after that, MultiTouch keyboard couldn't start and so I just froze it with Titanium Backup and used Swype because it was annoying. The next thing I tried came from another xda thread (that I seem to have misplaced) saying that removing the top 2 lines of META-INF/com/google/android/updater-script would make it work. I'm pretty sure this failed similarly to before. I then tried wiping all data (since I had backed it up 3 different ways) and installing CM10. It still didn't work, and when I booted I got to my current state of purgatory.

Now when I boot, it tries to run the initial setup but that crashes (and multitouch keyboard crashes too). I've probably lost root access and currently don't have Titanium Backup or any other method to restore from backup since the programs were wiped. I've been trying to do an SBK factory reset using RSD Lite, but the phone won't go into RSD mode.

At this point I just want a working phone again and I'm not sure what to do.

TL;DR: Used the wrong GAPPS version when installing CM10 A3, decided to wipe all my data and try the install, now I'm stuck in neutral.
[Motorola Droid X2] Dasoccerguy:
I guess the internet lied and gave me the wrong SBK the first time. Setup did work, and it wasn't RSD like I had thought.

I still would like to know what went wrong the first time through, and why it seemed like I wasn't able to overwrite the incorrect GAPPS version I had first installed. Once I saw my mistake I did use the correct version and nothing changed.
[Motorola Droid X2] Simpsons11:
Did you get it working then? Were you running A2 before hand?
[Motorola Droid X2] Lorenzo VonMatterhorn:
you state in the beginning that you are on 2.3.5. it is crazy that you were even able to flash cm10. it is made for 2.3.4 . and DZKs OP on cm10 is a bit sketchy in the wording and severly outdated.

there are a few things you need to do in order to get BSR working inside of A3 , as well as needing the GAPPS for 4.1.X and not 4.2.2 this is only cm10 , not 10.1 .

you need to SBF back to 2.3.4 (google EZsbf for droid x2) it is way easier than trying to use rsdlite for a "noob" , and then root. then follow the steps you completed to get where you are now, except use the right gapps.

THEN: (this is not in the OP for cm10 ) , perform THIS : http://xdaforums.com/showpost.php?p=37698274&postcount=1573 in order to get the patched cm7 bootstrap working. DO NOT try to use the regular BSR .

i can try to help as i get back to my computer here and there, but hopefully others pitch in , as i dont have that much time. hope this helped.
[Motorola Droid X2] Dasoccerguy:
I got back to 2.3.5 and restored all my apps and data, so I called it a night. Well... the sun had come up, but same idea. Like I said, up until yesterday I had yet to even root the phone, so I was just running the stock version of Android given to me by Verizon.

I wasn't able to flash CM10. I was able to flash GAPPS 4.2.2, but then unable to flash GAPPS 4.1.x over that installation.

And is it really that outdated and sketchy? The version of CM10 I was trying to flash was made on January 11, 2013. Correct me if I'm wrong, but Gingerbread 2.3.5 is almost 2 years old now, right? It's surprising that I'd have to go back to the previous version.

I may try out your suggestions later, but 8 hours of fiddling with my phone yesterday wore me out a little (a lot). Thanks!
[Motorola Droid X2] Lorenzo VonMatterhorn:
the OP for cm10 hasnt really been updated since alpha 1 . so yeah it is outdated. alpha 2 had a non working wifi module that was never even mentioned in the OP and had to be figured out by the droid x2 community. alpha 3 had the working wifi back in, but did not have the proper Hijack.zip in place in the system files, whereas the old versions did. this was also never mentioned in the OP.

watch this video. it may help.

http://www.youtube.com/watch?v=HJdvyufvYp0

the dude who made this video also has DOZENS of how-to videos for the droid x2 on his channel. just search for it on youtube. (ex: how to sbf droid x2)

sbfing your phone to 2.3.4 , using EZSBF , shouldnt take more than 15 minutes.

2.3.5 re-introduced a lot of issues that we had with 2.3.4, so most devs base their roms around 2.3.4. in fact, there are really only two roms for 2.3.5 worth trying out, Eclipse, and gingerbread phone , 7 and they are both gingerbread. :crying:

if you read up on what needs to be done, the whole process of SBF, ROOT, and flash cm10 THEN gapps, should all take less than an hour, even for someone who is fairly inexperienced.

i wasnt trying to dog DZK's post for cm10. i was only stating that if you follow HIS instructions, it is confusing as hell.
[Motorola Droid X2] Dasoccerguy:
Thanks for the link. I remember watching one of his videos yesterday for something, but apparently this was the one I needed! He does have another video on how to SBF back to 2.3.4, so I think I will just go for it right now.

Also yesterday it only took so long because I had to figure out what mess I had gotten myself into before I could figure out how to figure out what to do. This definitely looks like it shouldn't take more than an hour. :good:

I do have one quick question about backups. NANDroid is a full system backup, including the OS, right? And Titanium Backup is for apps and data? Therefore I should be able to restore all of my apps and data into Android 4.2.1 with Titanium, right? I at least know how to get back to 2.3.5 and restore my data if I can't restore it in 4.2.1, but I'd rather not have to go through this process again if I find out that Titanium can't restore everything.

(haha... I couldn't quote you because of the outside link and my 'xda noob' status :eek:)
[Motorola Droid X2] Lorenzo VonMatterhorn:
a nandroid backs up the OS as well as all apps and data, but that only helps you if you are modding/messing with that specific rom. so yes, TB is the way to go for restoring apps across roms. :cowboy: glad to point you in the right direction! report back once youve made the jump. :fingers-crossed:
[Motorola Droid X2] Dasoccerguy:
Success!

I used Tomsgt123's tutorials and they were fantastic. First I had to install the 2.3.4 SBK and then CM10 and Gapps. I'm currently running Titanium Backup and it's working flawlessly.

I did have one hiccup earlier though. I noticed that my contacts weren't backed up, and apparently I had disabled the online contact backup also. I was hoping that I could do a NANDroid restore, backup my contacts, and then go through with the CyanogenMod installation. But, the restore kept hanging and refused to finish. I tried 3 or 4 times, and on the last try I restored by section and it was the data section that caused the hang.

So, I'll have to rebuild my contacts list a little bit, but since SMS was backed up I'll at least get the people I care about :p. Cyanogen is pretty sleek and so far it's been noticeably faster than Gingerbread. I was constantly getting a low framerate just navigating my mainscreen before, and that's one of the reasons I was inspired to try out Jellybean or just anything newer. I can't make any claims about battery life yet since I haven't unplugged it, but other reviews said the battery can last more than twice as long which is fantastic.

I can't thank you enough, Lorenzo, for pointing me in the right direction. :highfive:
[Motorola Droid X2] Lorenzo VonMatterhorn:
thats awesome. i loved the feeling when i first flashed a new rom on this phone. glad you got it figured out. make sure to thank Tomsgt for his videos as well . hes a cool dude and put a lot of time into it.

as for battery life, its kinda a bit rough on cm10. i wouldnt say twice as good. that would be too good to be true...lol . but if you limit your apps, it shouldnt be that much worse.

one thing, to improve performance, under settings, go to developer options, and near the bottom there is background processes. its set at standard limit by default. change it to three at most. this will make a noticeable improvement in performance, but will also need to be re-set at 3 at most if you ever reboot/power off.

glad i could help! :highfive: