Finally I'm (again) rooted on stock, but that GPE rom becomes more and more attractive every single day...
My questions are:
I still have my TA Backup from the VRoot days (more or less day 1), is it still actual or do I have to redo a more recent backup? The TA partition changes with firmware updates?
And then, I'm unlocking, therefore deleting any user data on my internal memory, and subsequently I'm installing the GPE rom from scratch.
Let's say I'll stay like that for a week and then I'll miss the Sony rom, can I simply restore my previous (locked) nandroid backup? Would I get any troubles from that?
Thanks for the help in advance!
Sent from my C6833 using Tapatalk
fastest83 said:
Finally I'm (again) rooted on stock, but that GPE rom becomes more and more attractive every single day...
My questions are:
I still have my TA Backup from the VRoot days (more or less day 1), is it still actual or do I have to redo a more recent backup? The TA partition changes with firmware updates?
And then, I'm unlocking, therefore deleting any user data on my internal memory, and subsequently I'm installing the GPE rom from scratch.
Let's say I'll stay like that for a week and then I'll miss the Sony rom, can I simply restore my previous (locked) nandroid backup? Would I get any troubles from that?
Thanks for the help in advance!
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Numbered you Q's
1, Yes it will still be valid, even though the TA changes with each firmware update.
I take it you relocked the BL at some stage?
2, Yes re-unlocking will do a data wipe again. If you had taken a TA backup with a unlocked BL as well you could use that to unlock again without the data wipe - just make sure to make sure to name them well and dont lose the 'locked' one
3, The nandroid should work fine, but wont relock the BL (from what I understand)
blueether said:
Numbered you Q's
1, Yes it will still be valid, even though the TA changes with each firmware update.
I take it you relocked the BL at some stage?
2, Yes re-unlocking will do a data wipe again. If you had taken a TA backup with a unlocked BL as well you could use that to unlock again without the data wipe - just make sure to make sure to name them well and dont lose the 'locked' one
3, The nandroid should work fine, but wont relock the BL (from what I understand)
Click to expand...
Click to collapse
I'll reply with numbers as well
1)Seeing I'm rooted again, I may as well redo the TA backup and keep both, you'll never know...
2)I never unlocked the bootloader, so I don't have a TA Backup with the bootloader unlocked...
3) What I really was asking was if I could (if fed up with the GPE or another rom) restore my old (locked) nandroid even if I was unlocked. I think once unlocked I'll stay that way unless there's a problem, so relocking it's not a concern right now (and will not be anyway because if I have to send it in for warranty wiping would be the first thing to do... ).
Basically, I want to:
- do the TA backup now while rooted and never locked,
- make a nandroid backup
- unlock
- restore my nandroid backup -----> this is what I'm interested in, because I don't want to start from scratch if I don't feel like keeping another ROM.
By the way, redoing the TA backup while unlocked would be great if it'd mean never wiping data again... But correct me if I'm wrong, once you relock (with the TA backup) you'll end up wiping everything anyway, so...
Sent from my C6833 using Tapatalk
fastest83 said:
I'll reply with numbers as well
1)Seeing I'm rooted again, I may as well redo the TA backup and keep both, you'll never know...
2)I never unlocked the bootloader, so I don't have a TA Backup with the bootloader unlocked...
3) What I really was asking was if I could (if fed up with the GPE or another rom) restore my old (locked) nandroid even if I was unlocked. I think once unlocked I'll stay that way unless there's a problem, so relocking it's not a concern right now (and will not be anyway because if I have to send it in for warranty wiping would be the first thing to do... ).
Basically, I want to:
- do the TA backup now while rooted and never locked,
- make a nandroid backup
- unlock
- restore my nandroid backup -----> this is what I'm interested in, because I don't want to start from scratch if I don't feel like keeping another ROM.
By the way, redoing the TA backup while unlocked would be great if it'd mean never wiping data again... But correct me if I'm wrong, once you relock (with the TA backup) you'll end up wiping everything anyway, so...
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Yeah those steps are about it, the nandroid should work just fine even with the new unlocked BL
I dont think that restoring the TA wipes data
blueether said:
Yeah those steps are about it, the nandroid should work just fine even with the new unlocked BL
I dont think that restoring the TA wipes data
Click to expand...
Click to collapse
Thanks for the quick replies, but as this is uncharted territory for me, I would like some certainties, while all I find over the net are should and would...
I'm baffled over the fact that nobody ever tried (or ever reported) to do as I'm trying to do...
Sent from my C6833 using Tapatalk
You should be fine. I've never done a NANDROID on a locked bootloader before, but I have switched between the GPe and Stock ROM like every couple of weeks for several months now, and it restores it just fine. Will a backup made while on a locked bootloader make any difference? I highly doubt that.
Either way, backup your stuff to your computer and the cloud, and expect things to go straight south. Nothing bad will happen of course, but you should always be prepared.
Let's say that you can't restore you NAND. What's the big deal? You can either flash an FTF in Flashtool, or if you want the local build, re-lock the bootloader, un-root and download it from PC Companion.
I understand that you have a lot of stuff on your phone and you want to keep it that way, and that's why you want to be sure that the NAND will work, but you shouldn't keep important things in one place, and definitely not on your phone. Again, back it up and save it on your computer/Dropbox/Drive/etc.
Sent from my C6833_GPe using Tapatalk
LordManhattan said:
You should be fine. I've never done a NANDROID on a locked bootloader before, but I have switched between the GPe and Stock ROM like every couple of weeks for several months now, and it restores it just fine. Will a backup made while on a locked bootloader make any difference? I highly doubt that.
Either way, backup your stuff to your computer and the cloud, and expect things to go straight south. Nothing bad will happen of course, but you should always be prepared.
Let's say that you can't restore you NAND. What's the big deal? You can either flash an FTF in Flashtool, or if you want the local build, re-lock the bootloader, un-root and download it from PC Companion.
I understand that you have a lot of stuff on your phone and you want to keep it that way, and that's why you want to be sure that the NAND will work, but you shouldn't keep important things in one place, and definitely not on your phone. Again, back it up and save it on your computer/Dropbox/Drive/etc.
Sent from my C6833_GPe using Tapatalk
Click to expand...
Click to collapse
First of all, thanks for the reply.
Secondly, you're right, nobody should keep their stuff in one place, and that's what I do with Drive, Box and Dropbox.
There's nothing that important on my phone, and even if I can't restore the nandroid backup and I remember there's one particular I should have backupped (there's ALWAYS something you forget), if I remember correctly Titanium Backup PRO lets you browse nandroid backups for apps and files and stuff...
That said, how do I proceed? My steps would be:
1)unlock bootloader
2)install dual recovery
3)wipe data from recovery
4)flash GPe rom
Is that right?
Wish me luck!
Sent from my Nexus 10 using Tapatalk
fastest83 said:
That said, how do I proceed? My steps would be:
1)unlock bootloader
2)install dual recovery
3)wipe data from recovery
4)flash GPe rom
Is that right?
Wish me luck!
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Yup. That's pretty much it.
LordManhattan said:
Yup. That's pretty much it.
Click to expand...
Click to collapse
I have NUT's dual recovery installed, and that's what I was planning to install, but I read that's only for stock kernels...
Do I have to go with Doomlord one, once wiped after unlocking the bootloader? Or there's something better?
What I don't understand is if I have to install NUT's dual recovery (cause I'll be on stock before GPe), and then install the zip file with Scrubber's GPe rom (which from what I understand, has the dual recovery included that overwrites the stock dual one?)...
I think I'll flash through Flashtool to be sure...
Sent from my C6833 using Tapatalk
The kernel isn't that important when you're about to flash a different ROM. The ROM you'll flash will flash another recovery, so you'll only use the "first" recovery to be able to flash the ROM.
Use Flashtool or QuickIMG to flash the kernel/boot.img if you want a GUI, and do not want to use ADB.
Sent from my C6833_GPe using Tapatalk
LordManhattan said:
The kernel isn't that important when you're about to flash a different ROM. The ROM you'll flash will flash another recovery, so you'll only use the "first" recovery to be able to flash the ROM.
Use Flashtool or QuickIMG to flash the kernel/boot.img if you want a GUI, and do not want to use ADB.
Sent from my C6833_GPe using Tapatalk
Click to expand...
Click to collapse
I thought that might be the case, but wanted to be sure anyway.
Ok, I have my unlock code now, let's try and not f*ck this up then...
Thanks mate!
Sent from my C6833 using Tapatalk
How did it go? Are you weeping in a corner now, or what? Haha
LordManhattan said:
How did it go? Are you weeping in a corner now, or what? Haha
Click to expand...
Click to collapse
Ahahahah I didn't do it yet, I made all the backups and everything but I didn't have the time to go through with the steps.
That's partly because family takes all of my time now (we're preparing for a vacation next week), but I confess, part of me doesn't like changes at all...
Yeah, I'm a lazy mot*erfu**er...
Sent from my C6833 using Tapatalk
fastest83 said:
Ahahahah I didn't do it yet, I made all the backups and everything but I didn't have the time to go through with the steps.
That's partly because family takes all of my time now (we're preparing for a vacation next week), but I confess, part of me doesn't like changes at all...
Yeah, I'm a lazy mot*erfu**er...
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
Hmm, alright so you should probably wait until you're back from vacation before messing with it. I don't wanna get yelled at when you're having car issues and can't make a call or something unexpected, OR you feel adventurous and want to mess with it BECAUSE you have a lot of free time on your hands?
So... any progress?
LordManhattan said:
So... any progress?
Click to expand...
Click to collapse
Are you crazy? Do you have the slightest idea of what is like to have 2 kids and a wife screaming at you for this or that and you're freaking out because ADB is not working at the moment, or the single file you planned to flash was corrupted so you end up wiping everything for nothing? Well, I do.
And no, it's not pretty. XD
Anyway, now 4.4.4 is in sight, so I'm even more confused...
After all, I use mini apps a lot, device is super responsive, now I can use gestures and xposed, viper for the sound, I don't really know how much could this be improved with vanilla android...
(Yeah, monkey on my shoulder, I see your point, but eat your banana and shut the fu*k up for now... )
P. S. Just for a laugh, my friend's S4 literally EXPLODED last night, battery fused with back cover and cell destroyed... I told him to get a Sony...
(they gave him an S5 in exchange, and that seems a bit admitting they know it's something that can actually happen...)
Sent from my C6833 using Tapatalk
Dude, is your friend a Reddit user? And did he post about his S4? Because some guy posted about a burning S4 yesterday or something, LOL.
Aaaaand no. I don't have the slightest idea, and thank God for that, hahah So... You're not sure if you're going to stick with the new 4.4.4 stock ROM or the ridiculously smooth GPe ROM? If you're really happy with your current setup then just keep it. Don't mess up "perfection". If you're bored on the other hand, then flash GPe.
Or you know.. I can do it for you if you pay for my flight down. I'm only a couple of hours away, LOL!
LordManhattan said:
Dude, is your friend a Reddit user? And did he post about his S4? Because some guy posted about a burning S4 yesterday or something, LOL.
Aaaaand no. I don't have the slightest idea, and thank God for that, hahah So... You're not sure if you're going to stick with the new 4.4.4 stock ROM or the ridiculously smooth GPe ROM? If you're really happy with your current setup then just keep it. Don't mess up "perfection". If you're bored on the other hand, then flash GPe.
Or you know.. I can do it for you if you pay for my flight down. I'm only a couple of hours away, LOL!
Click to expand...
Click to collapse
No actually he's not, but I did find the user you pointed out, and that is NOTHING compared to what happened to his S4...
I mean...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway, the smoothness really attracts me, but I really never encountered nothing but, in this particular phone.
With Sammy I was forced to flash something else (CM) because the system was laggy to say the least, but with this?
I guess I'll really flash when updates are far far away...
P.s. I'll pay the flight next time, I swear! Ehm...
fastest83 said:
No actually he's not, but I did find the user you pointed out, and that is NOTHING compared to what happened to his S4...
I mean...
Anyway, the smoothness really attracts me, but I really never encountered nothing but, in this particular phone.
With Sammy I was forced to flash something else (CM) because the system was laggy to say the least, but with this?
I guess I'll really flash when updates are far far away...
P.s. I'll pay the flight next time, I swear! Ehm...
Click to expand...
Click to collapse
Woow.. WTF man! He should contact Samsung ASAP, and he'll probably get a new phone of his choice so he doesn't sue them. This is normal. If not, make him publish it so Samsung gets a bad rep. I'm completely serious, but I'm guessing that Samsung doesn't want bad PR, so they'll give him a new device ASAP as long as he signs some papers.
LordManhattan said:
Woow.. WTF man! He should contact Samsung ASAP, and he'll probably get a new phone of his choice so he doesn't sue them. This is normal. If not, make him publish it so Samsung gets a bad rep. I'm completely serious, but I'm guessing that Samsung doesn't want bad PR, so they'll give him a new device ASAP as long as he signs some papers.
Click to expand...
Click to collapse
I think I would require years of therapy to get over that traumatic experience.
Related
So I've had my Atrix for a few months now, and it's mostly awesome. I'm coming from having owned an iPhone before, and it's just fantastic. I've stayed away from modding it too much however, since I knew the bootloader was locked and not a lot could really be done. But, according to several posts I see here, the bootloader seems to have been unlocked recently. Yay?
So, I ask that you forgive my ignorance. What does this mean? Does a given ROM need to be modified to work with every model of phone? If so, which ones presently work with the Atrix? Any? (It looks like the unlock was found very recently.) How does that process work exactly? Is there any way to ensure a recovery path if something were to go wrong, so that I don't brick my phone?
I'm just curious here. Presently, my phone is on the stock firmware without any upgrades at all, and I've simply rooted it and installed the webtop mod so I could play games on my TV. Other than that, it's been lots of Android Market for me. I'd like to branch out, and I don't even know where to begin.
There aren't any custom rom's for this yet, there's work being done, so it's just a matter of time. However, there is a developer build from Asia that can be flashed. There are a few issues with it, so if you are averse to troubleshooting or dealing with issues then just wait a few days.
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
schlupp88 said:
Can I flash the UK Firmware on a unlocked ATT Atrix now?
Click to expand...
Click to collapse
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
_Dennis_ is right. You should sbf_flash -x to extract the UK firmware and use fastboot to flash just boot.img (CG56 in Froyo) and system.img (CG57 in Froyo). If you want to flash the radio, use a custom .sbf (for AT&T) with only the radio. We don't yet know whether you can replace your bootloader with a UK bootloader. We still flashed a signed bootloader to our phone. In the worst case, if you flash a UK signed bootloader and your boot ROM is looking to find an AT&T signature in your bootloader: BAD! It is fairly unclear that the unlock ALSO tells boot ROM not to care about signatures, it may very well still care. And the order of RSD: erase,write,verify is a little dangerous...
I as well, don't know much about this... but as far as I know, this will mean that developers will be able to create real operating systems for the phone and not have to wait for att/moto to do that...
in the past it was an OS from att/moto, and all the "roms" in xda were actually the same OS but with some skins and mods added to them...
Yes, if you look at the development forums for just about any other android phone, you will see full customized ROMs that can be installed. That's where we are headed.
_Dennis_ said:
Pretty sure you can at least fastboot flash the CG from the SBF (need system and boot) not sure about flashing the whole SBF. You can try though.
Click to expand...
Click to collapse
I did a test with this.
I flashed 1.8.3 SBF over my unlocked bootloader to see if I could use moto-fastboot to flash over a 'stock' bootloader. It works to flash system (since it is still technically unlocked) but fails to flash boot.
So DO NOT TRY TO SBF FLASH A INTERNATIONAL VERSION unless you want to be stuck on the version with no way to get your phone back off.
I also would not flash the boot.img of a international version for the same reason.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
climo said:
I just finished unlocking and installed the new CWM recovery, just waiting for some roms! About the full system backup with CWM, does is deposit a folder to the SD card I can remove for safe keeping like TIBu? I never used CWM to backup or restore.
Click to expand...
Click to collapse
I think that the backup will be found in a Clockwork folder on your sd card. I also think that when you do the backup you will get to choose the destination. Either sd or external sd.
I haven't used the bl unlock or the new ClockworkMod (Just waiting on a nice rom). But that is how it went for me on the previous CWM that didn't require the unlocked bootloader.
Maybe someone who has this newer stuff can shed a little more light on it.
beatphreek said:
One of the good things you can do right now though is to Unlock it, and then install the Clockwork Mod recovery port in the developer's section. You can use that to make full system backup that you can flash.
Click to expand...
Click to collapse
Does this essentially create an image of your device? Or does it just back up the firmware?
When CWM backs up ur files it creates a image file of
Boot.img
Cache.img
Data.img
recovery.img
system.img
so yes it does use a image.
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Viamonte said:
Y'all talking about custom ROM's and such, no one seems to care about overcloking.. no one seems to realize what a beast a 1.4ghz Atrix would be.
Click to expand...
Click to collapse
+1.
ROMs will sometimes require you to have the custom kernel associated with them. CM7 for the Captivate comes to mind. With custom kernels, the Captivate was a beast. We had the VooDoo lagfix, which actually made the device usable on bootup. We were able to convert all partitions to ext4, and kind-of make the GPS work.
Overclocking is a possibility too. There's so much that is able to be done. It's a bit difficult coming from an iPhone where customization was limited, even with jailbreaking. But you'll soon get the hang of it.
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Viamonte said:
GPS. Nice point too, but Moto itself promisses improvements on the 2.3.4 OTA. This is the most sorely needed fix for me, since my gps SUCKS. It can take anywhere up to 30 minutos to find my locations. Yes, you read that right.
Click to expand...
Click to collapse
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
JayRolla said:
Mine works great. You may have a hardware issue?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+2
It shouldn't take that long to lock on. Mine locks on instantly.
WARNING!!!!!Use of the following has been know to cause bricks and/or loss of functions in most of the devices it was attempted on. Because of this, the Thread was permanently closed. However the files will remain to assist in further development. Additionally, there is no promise if any of the links still work. So if you choose to mess with these files, you do so knowing it will probably brick your device.
Moscow Desire, XDA Moderator*******************************************************************************
[Pudding]
WARNINGS: READ ALL OF THIS BEFORE CONTINUING
1. All phones You most likely will lose 4g data connectivity from using this, hopefully a workaround is on the horizon.
2. All phones This has received limited testing, use at your own risk and accept that there may be a risk of hard bricks now or in the future (Unless you get your SBK.)
3. All phones Charge your phone, all the way please.
4. Use at your own risk. Have a backup phone, insurance plan or other means of recovering from a possible brick or loss of functionality. You are using experimental software at your own risk.
Works/Does not work list
Sprint en/us 45.2.5: Warning: Loss of 4g connectivity very likely
Electrify 2.3.5: Danger: Untested, I do not own one and cannot test
Click to expand...
Click to collapse
Updates
8/30/2011 Added stock recovery image for those wishing to use pudding remover.
8/25/2011 Pudding remover added. This restores your stock bootloader. 4G will be restored but your phone will be locked again. This is only the bootloader, so system changes will not be removed (root, recovery, program data, etc). Having the custom recovery still installed with the locked bootloader may cause problems (soft-brick, you will need to use full sbf or re-unlock and flash back the stock recovery). will cause you to soft brick. You will need to reflash the unlocker to recover and either leave it unlocked or restore the stock recovery and use the pudding remover afterwards. Thank you tuxy for being the only one basically willing to test this.
8/16/2011 Just a quick update on the 4g issue, most likely this will go unresolved until your kernel source is released and someone with the appropriate skills in kernel hacking fixes your ATAGS passed by the bootloader. For now you can either be unlocked and use 3g, or locked and use Wimax/4g. Pick your poison, at least neither is a permanent thing.
Click to expand...
Click to collapse
Who does/doesn't need this.
You need this if:
1) You need to flash custom single partitions such as system, osh, boot.img, recovery, or data.
2) Mainly for testing custom kernels, see number one.
3) You have a real ROM with a custom kernel, like CM7 or MIUI, and want to flash it.
You don't need this if:
1) Number one in the last section doesn't make any sense to you or sounds like gibberish.
2) You wanna show your friends how much cooler or better than them you are.
3) You just want to install P-ROMs and Themes.
Click to expand...
Click to collapse
You want pudding for Photon? There is pudding in space too!
Pudding:
http://diamantephoto.com/photon_pudding.rar 1mb bootloader only
Fastboot:
Use this to unlock after flashing pudding sbf (not available), also to flash custom partitions.
Windows: Moto-fastboot for windows thanks to romracer. Direct Download Link
Linux/Mac: Moto-fastboot for linux in several flavors thanks to eval-.
RSD/Drivers/SBF_FLASH:
You may need to reinstall drivers after the unlock.
RSDLite 5.5 Download
http://mophoforum.com/Roms/rsdanddrivers.zip
64bit windows drivers
SBF_FLASH(*nix/Mac)
Pudding remover:
Directions:
1) Make sure you are on the stock Recovery. If not, flash the image I provided below using this command:
Code:
fastboot flash recovery stock_recovery.smg
2) Flash the nopudding4u sbf using RSDLite or sbf_flash.
3) Done
http://www.multiupload.com/A4KCLBTL3K - 3.6mb stock recovery image from CM5
http://diamantephoto.com/photon_nopudding4u.rar - 1mb bootloader only, stock locked bootloader. For those of you who want a quick way to return to 4G.
Howto:
Is your phone fully charged? This should be first thing you check whenever you flash anything.
0) Back up all your apps and anything else you want to keep that is stored in /data, YOU WILL LOSE ALL FILES IN /DATA
1) Flash the pudding sbf file via sbf_flash(*nix/Mac) or RSDLITE(Windows).
2) Get moto-fastboot in your $PATH or at least in the same directory as the command line you open.
3) Open a command line or well, linux users know what to do, in the folder with pudding.
4) Type moto-fastboot oem unlock
5) Look for the UNIQUE ID number and copy it, use copy or your fat fingers might mistype it.
6) Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED
7) Enjoy!
Here is a picture of the steps on a windows command line (yes, I renamed moto-fastboot to just fastboot on my PC.) The blurry bits are where YOUR unique ID shows/is entered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root:
A moto-fastboot flashable /system image with su already in /system/bin (pre-reooted) This is based of the system in Yay4jugg's thread (NB: you need to be unlocked to flash this .)
Instructions:
0) Make sure your phone is charged.
1) Boot your phone in to fastboot mode, connected to PC.
2) At the prompt/cmdline type moto-fastboot flash system system.img
3) Make sure you have superuser app installed from market.
4) Enjoy!
CWM:
Romracer's official CWM thread for Photon
Calkculin's CWM thread
A video guide on how to root and install CWM for unlocked Bootloaders by qbking77
Kernels:
Hewett Kernel
Shabby's OC kernel
Problems?:
1) Don't panic.
2) Stop panicing.
3). If you get the following error messages, try restarting the flash process from the start:
- The "secure_motorola_flash" interface could not be found the super-file is secure and for re-flash, the phone needs a super-file that is not secure and for reflash. (0x7066)
4) Just try and go through with the unlock process anyhow
5) Try a different USB port, this is most likely because windows will reinstall all the drivers.
6) Try a different version of RSD Lite.
7) Make sure you put your phone in to USB NONE before plugging it back in. If you do not do this your system will not install all the devices correctly. Alternately, try Motorola Phone Portal mode.
8) Last resort PM me with very specific information about your problem and if applicable screen shots from your computer or phone.
Big thanks to Yay4juggs and Edgan.
The attached file below is only for Electrify owners and is untested
MOD EDIT: Attachment Removed
Yea BL unlock and root without dock? I gotta sleep, hope christmas comes in the morning!! I get some cash soon, gonna buy you guys a round! Man you guys are persisting and pushing tonight...
-DJ
Grats to everyone involved. You did amazing work.
Sent from my MB855 using XDA App
My stomach is ready. Thanks for the efforts and the work into this, we are grateful.
Chocolate pudding.
Has anyone tried this?
Sent from my MB855 using XDA App
evonate said:
Has anyone tried this?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I beleive its still being tested isnt it?
Hey you,
My name is Rick, and I am never gonna give you up. All of you have let me down, made me cry, and spent all day telling lies and hurting people. Your heart's been aching but you're too shy to say it. Honestly, have any of you ever gotten this from any other guy? I mean, I guess it's fun knowing the game and playing it, but you all take to a whole new level. Inside we both know what's been going on.
Don't be a stranger to love. You know the rules and so do I. I'm pretty much perfect. I have been nominated for a Grammy, and had a #1 hit. What games do you play, other than "running around deserting people"? And if you ask me how I’m feeling, I also have a banging hot girlfriend (We’ve known each other for SO long). I just wanted to tell you how I was feeling. I gotta make you understand.
Sent from my MB855 using XDA Premium App
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
theres a handful of people that actually knew anything about the photon and motorolas in general. i knew it wouldnt take long....im selling my nexus s as we speak, im that confident we will see awesomeness very soon.
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
I'll leave that up to you I don't own a Photon or Evo.
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
ooxcfhxoo said:
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
Click to expand...
Click to collapse
it is very exciting. i saw this right here and sold my nexus s this is my Photon in the picture btw...
Huge thanks to the2dcour for making this happen!!!!
what are the chances of getting the sbf tonight from someone?
ooxcfhxoo said:
what are the chances of getting the sbf tonight from someone?
Click to expand...
Click to collapse
0% check back tomorrow around noon EST.
I was thinking along the lines of a small (coffee sized) donation?....on say..........Newbury Street
ooxcfhxoo said:
I was thinking along the lines of a small (coffee sized) donation?
Click to expand...
Click to collapse
I _never_ ask for donations so don't feel obligated to, the work I do is a lot less intensive and technical than people imagine. As I've said before 99% credit belongs to moto for making this, 0.5% to the leaks/people who provide the leaks, and I'm happy to take the last 0.5% credit for being the script kiddie that assembles the pudding.
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
ericdabbs said:
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
Click to expand...
Click to collapse
That's precisely the reason that it hasn't been posted yet. There still may be side effects in the future as we are seeing with the atrix. Be warned, the unlock is irreversible and you should be careful. Most people will not need an unlocked bootloader. When you get custom kernels and CM that is another matter. People who dev this stuff can certainly use the unlock wisely. Till there is a reason for you to unlock I wouldn't bother unless you are adventurous and have a spare phone 99% of the reason people need / want unlock is for a custom kernel the other 1% is for using fastboot or non-bootstrap cwm. Hopefully you will have a non-bootstrap CWM soon. I'm rambling so I'll stop talking.
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
I would be using ......fastboot or a non-bootstrap cwm (when one is available).
i understand CWM is possible now and the reason for me unlocking my boot-loader is to get it done before someone puts the brakes on it.
I like to have access to the things i own based on principal. Its the same reason why i refuse to pay twice for the same data stream i already pay for in order to tether.
ooxcfhxoo said:
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
Click to expand...
Click to collapse
Coming tomorrow, I promise.
so this is my problem. Im having some issues with my phone and I want it to be changed. The issues really dont matter. In order for my provider to send me another phone they want me to do a master reset. This of course will delete all my apps and settings. As far as I know there is not a backup app that once you restore the phone and apps the restored phone will have all it's app data in place, the icons will be where you want them, etc, just like you would from when you clone or make an image from a Hard Drive from pc... Or is there and application that will do this? My only other option (i believe) is to root the phone to then use an app to do a real backup, then unroot the phone, root the new phone and do the restore. I also have to remove the root from the old phone but can that be done without increasing the counter? This is all a big hassle. I cant believe you can do a real backup/restore on a phone nowadays....
If there is any other way to do it I will appreciate the help. I will have to do this in the next days since my warranty expires in a bit over a month...
Thanks!
You are correct ....
Rooting of the device is needed, then the unroot.
It's the only method I'm aware of in getting a full nandroid backup ..g
Sarge has it right if you want to use backup apps.
If you don't want to root, you will need to flash TWRP or CWR to get the custom recovery and backup. Then make a backup to your external SD card. Use recovery to factory reset. Send the phone away after removing SD card and sim card. The backup is called a nandroid and it is basically an image of the phone.
On new phone flash same recovery then restore the backup. When you start the phone it will be as the broken one was.
You can remove the recovery from the broken phone, but I never heard of anyone getting problems from the warranty people for that.
Thanks both of you guys for the information. I am getting ready to do the root not only for the backup but there are quite a few apps that I want to use that require root that I am going to have to do it.
Now, I started reading tonight and the more I read the more I get confused. Is there an official guide to root the note (specifically AT&T running ICS 4.0.4 if there is a difference) in a way that I can unroot it in the future avoiding tripping any counters?
I have read so many different threads about rooting, they tend to be different so I am looking for the "current" accepted "method" to do this with decent steps if possible. Thanks much!
Whoa whoa, are we forgetting about ADB Backup?
What do you mean CPA?
BTW, I want to root the stock att ics, I am not interested into flashing another rom.
Fernandq said:
What do you mean CPA?
BTW, I want to root the stock att ics, I am not interested into flashing another rom.
Click to expand...
Click to collapse
Yeah I understand, you're wanting to do a full backup of your phone before you turn it in right? Or, at the very least, your apps and settings?
Welp, here you go: no root required.
A quick google search for "ADB backup" should get you the info you need as well.
Also looks like there's an XDA dev who came up with a much easier interface (as opposed to doing everything via command-line, which still isn't that difficult). Might be worth checking:
http://forum.xda-developers.com/showthread.php?p=36499906
Edit: Read your second post, and it looks like you're interested in rooting...I guess I was confused as to your intentions after reading you first post, which just sounded like you didn't want to lose your info after doing a factory reset. Regardless, it is HIGHLY advised before doing any sort of root-related activity to do an ADB backup. That way, if anything goes wrong in the rooting process itself, or if you later decide you want to go back to stock and/or all of your original apps and settings from before the root, you can literally be back with a clean slate within a matter of minutes.
Thanks very much for the link. I have swapped phones already but it will be helpful before I root. THANKS!
after looking at adb I see it would not work for my initial needs as it only can be restored to the same device. I wanted something I could do a backup in the old one and restore that backup in the new one. Anyway, since I am past that anyway I am going to give it a try in theold device.... thanks!
Fernandq said:
after looking at adb I see it would not work for my initial needs as it only can be restored to the same device. I wanted something I could do a backup in the old one and restore that backup in the new one. Anyway, since I am past that anyway I am going to give it a try in theold device.... thanks!
Click to expand...
Click to collapse
The full backup, yes (regarding being able to only restore to the same device) but you could literally extract whatever data you want from the ADB backup using WinRar, then manually push it to your new device.
Apparently ADB backup is broke, it does not respect the -noshared flag and the resulting file is corrupted requiring more processing on the file for it to work... dang it! Seems it has been fixed in JB...
http://code.google.com/p/android/issues/detail?id=28303
http://www.acertabletforum.com/foru...stem-backup-ics-only-root-not-required-2.html
and there is more if you search the net.... Now, why will they not fix it is beyond me. Ok, so the command does not respect -noshared, that is easy to fix, I can just pull my sd card out but making an otherwise broken and unusable file giving the user the false sense of security and not fixing the bug is plain wrong... The only option will be to upgrade to JB but the official upgrade is not out and knowing at&t I wont be for a bit... I am not much into flashing leaked rom although that might change in the near future...
Thanks.
Fernandq said:
Apparently ADB backup is broke, it does not respect the -noshared flag and the resulting file is corrupted requiring more processing on the file for it to work... dang it! Seems it has been fixed in JB...
http://code.google.com/p/android/issues/detail?id=28303
http://www.acertabletforum.com/foru...stem-backup-ics-only-root-not-required-2.html
and there is more if you search the net.... Now, why will they not fix it is beyond me. Ok, so the command does not respect -noshared, that is easy to fix, I can just pull my sd card out but making an otherwise broken and unusable file giving the user the false sense of security and not fixing the bug is plain wrong... The only option will be to upgrade to JB but the official upgrade is not out and knowing at&t I wont be for a bit... I am not much into flashing leaked rom although that might change in the near future...
Thanks.
Click to expand...
Click to collapse
Well crap man, that sucks - sorry! I'm not gonna lie, I didn't read the link you posted as I'm pulling all nighters about 3 times a week during for the busy season of my profession (see my user name lol)...but you're saying that something actually went WRONG with the SDK on ICS firmware - and Google isn't fixing it?? That can't be right...right?
I can personally couch for this method, as I used it to make a full unrooted backup - of stock 4.0.4 ICS - back in October when I rooted my Note for the first time. And the first thing I did (per the rooting tutorial I was following) was verify the backup by doing a restore via ADB before I rooted - and everything worked fine. Like I said, sorry it's not working for you! Have you considered rooting, installing a custom recovery, doing a nandroid backup (and saving it someplace safe of course), then doing a full unroot back to stock + reset your flash counter? There are some great tutorials to walk you through all of that on the Galaxy Note Everything Thread in the General forum, in case that's an option.
CPA Poke said:
Well crap man, that sucks - sorry! I'm not gonna lie, I didn't read the link you posted as I'm pulling all nighters about 3 times a week during for the busy season of my profession (see my user name lol)...but you're saying that something actually went WRONG with the SDK on ICS firmware - and Google isn't fixing it?? That can't be right...right?
I can personally couch for this method, as I used it to make a full unrooted backup - of stock 4.0.4 ICS - back in October when I rooted my Note for the first time. And the first thing I did (per the rooting tutorial I was following) was verify the backup by doing a restore via ADB before I rooted - and everything worked fine. Like I said, sorry it's not working for you! Have you considered rooting, installing a custom recovery, doing a nandroid backup (and saving it someplace safe of course), then doing a full unroot back to stock + reset your flash counter? There are some great tutorials to walk you through all of that on the Galaxy Note Everything Thread in the General forum, in case that's an option.
Click to expand...
Click to collapse
As mentioned in my post....
Root, full backup, and unroot is the fastest method......g
gregsarg said:
As mentioned in my post....
Root, full backup, and unroot is the fastest method......g
Click to expand...
Click to collapse
But what's the point in putting things simply like that when I can write an entire paragraph saying the same thing, but more confusing??
Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)
Got my XZU last Saturday and decided today to keep it. Being long out of the Sony-world (last was an XS, now coming from a Find 5), I've got some questions. I'm also going to search for the infos, but I feel a single thread for "my stuff" makes it easier for me, so please be kind.
So, for the current state, here's the device's information.
- Sony Xperia Z Ultra (C6833), black
- running on Vodafone DE
- Android version 4.2.2
- Baseband version 8974-AAAAANAZQ-10220006-09
- Kernel 3.4.0-perf-gde8296d-02194-ga2561a5
- Build 14.1.B.1.510
- The device shows me an update to 14.2.A.1.136
Questions:
1) Do Sony's official updates only update Android + Sony Apps or are there also firmware updates included?
2) I want to root and install a custom ROM, should I start from the current build or should I upgrade to $something first?
3) I've read that KitKat is restricting SDcard usage for non-system apps. Do custom 4.4 ROMs work around this(,yet) or should I update to 4.3 max?
4) I probably won't use the camera much, if at all, still, most custom ROMs can't get the camera quality on a level the stock ROM has, so how bad is it on this device?
5) is the PowerCover CP12 available somewhere in the EU? It's "out of stock" in all big shops I looked at in .de,.at,.ch and the Twitter-Team wasn't really helpful. Ordering from outside the EU would be possible, but pretty much guaranteed to get stuck at the customs where the next office is ~50km away and doesn't have work-friendly times at all.
6) About screen protectors: a) can I apply them over the shatter shield and if so b) will input by pens or something still work on a decent level?
7) is there a prefered solution of recoveries on this device or does it not matter at all, if I'd choose CWM or TWRP(or is there something else entirely)?
8) are there known problems in general with custom ROMs regarding external hardware? I'd like to use my "SmartWireless Headset Pro", my "SmartWatch (1)" and TV-Out
That's it for now, thanks for any help
1) The 136 update is a firmware update (to Android 4.3), but they also push out updates for their Sony apps.
2) You have to update to at least 290 (Android 4.3) if you don't want to lose your IMEI when you flash a custom ROM. Also note that you'll lose your IMEI if you downgrade from 136/290 to anything older. There are no real reasons to downgrade though, but just keep that in mind. It's easily fixable, so it's not the end of the world if you do it.
3) Yes, there's a workaround to get SD card working on KitKat (you just have to replace one file)
4) The camera is still bad on custom ROMs. It might get better with official Sony KitKat.
5) I have no idea.
6) a) Yes. b) Yes.
7) We've got double recovery, meaning you'll get both CWR and TWRP when you flash recovery, so use the one you prefer. (Vol Up for CWR and Vol Down for TWRP)
8) I think the only known issue on 136 is that Bluetooth might be a little wonky, but i'm not sure, so be sure to read around here since there's a thread about it.
Thank you for that.
In regard to 1), I meant firmware updates of hardware, f.e. the Find5 received some updates regarding the touchscreen.
As for 2), so there's currently no reason not to install the latest official Sony update, meaning it's also rootable without too much hassle? What would be the consequences of a lost IMEI?
S.D.Richards said:
Thank you for that.
In regard to 1), I meant firmware updates of hardware, f.e. the Find5 received some updates regarding the touchscreen.
As for 2), so there's currently no reason not to install the latest official Sony update, meaning it's also rootable without too much hassle? What would be the consequences of a lost IMEI?
Click to expand...
Click to collapse
Bugfixes are included in firmware updates, so they don't release an update to fix one minor thing. The Find5 receives updates every two weeks, if i'm not mistaken?
There's really no reason to update to 136 (the newest) if you're going to flash a custom ROM. Rooting is fairly easy if your bootloader is unlocked, and it only takes a couple of minutes, but it's a little more complicated if your bootloader is locked. Luckily, you're on 510, meaning it's even easier to root, and once you've rooted 510, make a backup of your TA partition. It holds all of your unique DRM files that makes X-Reality work etc. You'll lose the TA partition when you unlock the bootloader, so that's why you have to make a backup of it before you unlock it. Once you've done that, update to 290, unlock the bootloader, root it and do whatever you'd like to do.
Thanks again.
Now rooting worked(+OTA keeper from the Playstore), so did creating the TA backup.
Having a glance over the custom ROMs available as of now, I think I'd like to stay on rooted stock until Omni (official) comes around.
So what would be the (better) procedure to get latest Sony ROM running? Use Sony's updater and hope OTA keeper works or unlock, install recovery and flash a pre-rooted FTF?
S.D.Richards said:
Thanks again.
Now rooting worked(+OTA keeper from the Playstore), so did creating the TA backup.
Having a glance over the custom ROMs available as of now, I think I'd like to stay on rooted stock until Omni (official) comes around.
So what would be the (better) procedure to get latest Sony ROM running? Use Sony's updater and hope OTA keeper works or unlock, install recovery and flash a pre-rooted FTF?
Click to expand...
Click to collapse
OTA Root Keeper doesn't work on 4.3, so you'll lose root no matter what you do. Are you still on 510, or have you updated to something else?
You have your TA partition backed up now (recommend you to upload it to your Drive or Dropbox), so you can unlock the bootloader without permanently losing the TA partition. It'll delete it when you unlock the bootloader, but you can easily restore it again in case you have to send it in for repairs. Rooting 290 and everything else becomes so much easier and faster the second your BL is unlocked, so head over to the General section and look for Jackie's root guide and see if that's something you might want to do...
...or you can simply stay with the firmware you're on now, granted it's not the most stable firmware version, but it'll save you a lot of time. Official KitKat is also scheduled for release this month, so you can:
A ) Stay on current firmware and wait for official Sony KitKat
B ) Go all out and flash a custom ROM
I'm currently running the GPe ROM, and I can highly recommend it. It's solid as a rock with no bugs.
Any questions?
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
OTA Root Keeper doesn't work on 4.3, so you'll lose root no matter what you do. Are you still on 510, or have you updated to something else?
Click to expand...
Click to collapse
Still on 510, bedtime was up and I don't wanted to do something stupid with a sleepy head.
You have your TA partition backed up now (recommend you to upload it to your Drive or Dropbox), so you can unlock the bootloader without permanently losing the TA partition.
Click to expand...
Click to collapse
Yes, did that and mirrored it over a few systems. BTW, if I'd ever go back to stock, would the TA-p get changed so I'd need to back it up again or does it stay the way it is over the phone's lifetime?
It'll delete it when you unlock the bootloader, but you can easily restore it again in case you have to send it in for repairs. Rooting 290 and everything else becomes so much easier and faster the second your BL is unlocked, so head over to the General section and look for Jackie's root guide and see if that's something you might want to do...
Click to expand...
Click to collapse
No problem, I had my Xperia S unlocked, so I now the procedure. Only question related to that: I read that for the Z1(?) there's a minimal version one should update to before unlocking the BL, if you don't camera stops working or something - so, is this also a problem on the ZU or has this already been fixed?
I'm currently running the GPe ROM, and I can highly recommend it. It's solid as a rock with no bugs.
Click to expand...
Click to collapse
I'll have a look at it, thanks.
S.D.Richards said:
.
Yes, did that and mirrored it over a few systems. BTW, if I'd ever go back to stock, would the TA-p get changed so I'd need to back it up again or does it stay the way it is over the phone's lifetime?
Click to expand...
Click to collapse
The TA partition is unique to your device, so you do it only once, so be sure to not lose it.
No problem, I had my Xperia S unlocked, so I now the procedure. Only question related to that: I read that for the Z1(?) there's a minimal version one should update to before unlocking the BL, if you don't camera stops working or something - so, is this also a problem on the ZU or has this already been fixed?
Click to expand...
Click to collapse
The ZU has never had any of the camera issues when we unlock the bootloader, so there's nothing to add here
Sent from my C6806_GPe using Tapatalk
So to be clear, when you're talking about the GPe ROM, you're meaning this one: http://forum.xda-developers.com/showthread.php?t=2608708 ?
So if I'd like to try this, I'd need to:
1. unlock bootloader
2. install recovery
3. take NAND backup
4. Flash .290 fw
5. flash this ROM
Correct?
S.D.Richards said:
So to be clear, when you're talking about the GPe ROM, you're meaning this one: http://forum.xda-developers.com/showthread.php?t=2608708 ?
So if I'd like to try this, I'd need to:
1. unlock bootloader
2. install recovery
3. take NAND backup
4. Flash .290 fw
5. flash this ROM
Correct?
Click to expand...
Click to collapse
The bootloader unlocking doesn't need to be the first step since you can flash Recovery on a locked bootloader. You can do everything except the ROM flashing on a locked bootloader. But yeah, that looks fine to me. Be sure to download the tweaked GPe version that includes Recovery and SD fix.
If you can't bother making a NAND:
- Unlock the bootloader
- Update to 290
- Flash boot.img (includes recovery)
- Boot into recovery and flash (VOL UP when LED lights up)
- Done.
Thanks again, could/would you link me to a .290 ftf for germany/europe/generic? The ones I found are either for other regions or the links seem to be down.
Here's 290 EU for the C6833.
https://mega.co.nz/#!VR4HyJia!PGxJXHOi8V-eJpWDnsJKShRPlhoYHR5DpFRkko6m0Nk
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
Here's 290 EU for the C6833.
https://mega.co.nz/#!VR4HyJia!PGxJXHOi8V-eJpWDnsJKShRPlhoYHR5DpFRkko6m0Nk
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Thanks, already found that link, but it gives me a "the file you are trying to download is no longer available"-error.
Already searched on Google, but couldn't find one, yet, or only for the other models.
Here's the Chilean 290 for C6833. It doesn't matter which one you use, and you're planning to flash the GPe, so just flash this one and get it done
Sent from my C6806_GPe using Tapatalk
Thank you very much for all your help, GPe is up and running smoothly now.
Apart from anything looking pretty huge, guessing different DPI settings compared to Sony's values, it's fine so far. One question though: under display settings it says X-Reality is on. Is that just cosmetics, since at no point I restored the TA-backup. If it's "fake", is it possible to restore TA and have it working or would that "trash" the system and restore should only be done in case of a stock re-install?
S.D.Richards said:
Thank you very much for all your help, GPe is up and running smoothly now.
Apart from anything looking pretty huge, guessing different DPI settings compared to Sony's values, it's fine so far. One question though: under display settings it says X-Reality is on. Is that just cosmetics, since at no point I restored the TA-backup. If it's "fake", is it possible to restore TA and have it working or would that "trash" the system and restore should only be done in case of a stock re-install?
Click to expand...
Click to collapse
just cosmetic and does nothing. If you restored the TA the GPe rom would fail to boot.
blueether said:
just cosmetic and does nothing. If you restored the TA the GPe rom would fail to boot.
Click to expand...
Click to collapse
Thanks for that quick answer, satisfied for now, so I can finally go to sleep
One last thing. Just change ro.sf.lcd_density=400 to 320 in build.prop to get the same sized UI like the Sony ROM. Unless you like 400.
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
One last thing. Just change ro.sf.lcd_density=400 to 320 in build.prop to get the same sized UI like the Sony ROM. Unless you like 400.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Perfect, just what I've been looking for, thanks.
Now to hope that the ZU also gets double tap to wake, than I'd be pretty happy.
S.D.Richards said:
Perfect, just what I've been looking for, thanks.
Now to hope that the ZU also gets double tap to wake, than I'd be pretty happy.
Click to expand...
Click to collapse
Yeah, the leaked footage from the Z2 KitKat build shows the option to use double tap to wake, so it looks like we'll get it. It's a kernel feature, so it'll work on mostly anything out there.