Database Develop

[Q] Unlocking Bootloader

Got a question about unlocking bootloader and the current state of my phone:
First up, this is the current state of my phone:
Bootloader locked
Rooted
Dual Recovery installed (??)
RomAur 4 installed
So basically the state of my phone is that I followed to guide in the RomAur post to install their ROM.
When I reboot my phone I get the extra buzz so I can hold Vol up/down to enter recovery.
I have root, but the sys partition is not mountable as R/W in RomAur 4 but I can flash zips in recovery.
I want to install iHackers v2 ROM and maybe also unlock bootloader as it seems all camera issues have been sorted (correct me if I'm wrong) (are there are reasons I should/shouldn't unlock the bootloader?).
What do I have to do to go from RomAur 4 to iHackers 2.0 with the current state of my phone? Should I bother unlocking bootloader to use a 3rd party kernel?
Are [nandroid] backups done in CWM any use at all as it seems that when flashing a ROM you then have to use flashtool to flash a kernel and radio so I'm guessing that the backups wont be able to restore these either?
Thanks for all the help and bloody hard work you guys put into developing for our phones.

cyberguru said:
Got a question about unlocking bootloader and the current state of my phone:
First up, this is the current state of my phone:
Bootloader locked
Rooted
Dual Recovery installed (??)
RomAur 4 installed
So basically the state of my phone is that I followed to guide in the RomAur post to install their ROM.
When I reboot my phone I get the extra buzz so I can hold Vol up/down to enter recovery.
I have root, but the sys partition is not mountable as R/W in RomAur 4 but I can flash zips in recovery.
I want to install iHackers v2 ROM and maybe also unlock bootloader as it seems all camera issues have been sorted (correct me if I'm wrong) (are there are reasons I should/shouldn't unlock the bootloader?).
What do I have to do to go from RomAur 4 to iHackers 2.0 with the current state of my phone? Should I bother unlocking bootloader to use a 3rd party kernel?
Are [nandroid] backups done in CWM any use at all as it seems that when flashing a ROM you then have to use flashtool to flash a kernel and radio so I'm guessing that the backups wont be able to restore these either?
Thanks for all the help and bloody hard work you guys put into developing for our phones.
Click to expand...
Click to collapse
As long as you save backs up on an external SD card you should be fine. I don't know what data you can restore back though. Photos, texts, apps, etc, should be okay. I'd back up with Titanium or something then just restore after. (I recommend nandroid also for your own peace of mind and hassle free experience)
Best thing to do is just do it from fresh to save you any hassle if you're going to wipe the phone anyway. It's best to wipe the phone before so nothing goes wrong.
http://forum.xda-developers.com/showthread.php?t=2539008
As it says:
Copy the ROM to External SDCard.
Install iHackers Advanced Stock Kernel.
Reboot into Recovery.
Make Sure to do a Wipe Data/Factory Reset before Installing the ROM.
Start the Installation. (Install Zip >> Choose Zip for External SDCard).
Switch Off Your Phone (Do Not Reboot). Select No to Disable Flash Recovery Confirmation.
Install Kernel.ftf for C6903 (.290) or Kernel.ftf for C6902 (.290) with Flashtool to get compatible Kernel and Baseband.
Reinstall Your Desired Kernel.
Reboot and Enjoy.
Click to expand...
Click to collapse
All camera issues sorted in iHackers v1.2.
Personally I'm running iHackers's PureStock.

If you want to unlock the bootloader, DON'T FORGET TO BACKUP TA partition.
You can unlock bootloader (after you have backed up TA), then install iHackers kernel, and go to Philz recovery (I believe it is volume up, but might be down), then click on wipe, then wipe for installing new ROM (or something like that), then install the iHackers ROM.zip
Regards,
~J2C

Just2Cause said:
If you want to unlock the bootloader, DON'T FORGET TO BACK TA partition.
Click to expand...
Click to collapse
Why I should do that? With 4.3 still no problem unlock bootloader and I am already on 4.3 and I didn't backup anything. The only reason is Warranty.

To be honest I don't really have any 'data' on my phone that I would miss if I lost it... some photo's, MP3's.. I only do nandroid backups so that I can test a new ROM, if I don't like it or it doesn't work I can just go back to Recovery and restore the nandroid and continue as I was but that was on Samsung devices and I'm a little worried as to the usefulness of the nandroids on this phone. Why do we have to flash kernel and radio using flashtool and why can't they be installed with the .zip/ROM?
I have a backup of my TA partition; I did it as a step in rooting/flashing some other ROM but didn't really know why I was doing it but it's stored away for whatever reason I need it!
I think for the time being I'll keep a locked BL, but I want to get rid of this ROM off my phone. I really need /sys to be mounted as R/W and I'm having some WiFi issues with RomAur 4.

eclyptos said:
Why I should do that? With 4.3 still no problem unlock bootloader and I am already on 4.3 and I didn't backup anything. The only reason is Warranty.
Click to expand...
Click to collapse
Well, you said it. Warranty.
cyberguru said:
I think for the time being I'll keep a locked BL, but I want to get rid of this ROM off my phone. I really need /sys to be mounted as R/W and I'm having some WiFi issues with RomAur 4.
Click to expand...
Click to collapse
So far, you can't get /sys mounted as R/W with a locked bootloader, even on custom ROMs.
If you want full root, the only way is to unlock bootloader.
Regards,
~J2C

Just2Cause said:
Well, you said it. Warranty.
So far, you can't get /sys mounted as R/W with a locked bootloader, even on custom ROMs.
If you want full root, the only way is to unlock bootloader.
Regards,
~J2C
Click to expand...
Click to collapse
Dont think thats 100% accurate - you can get Root with /sys mounted as R/W on roms <4.3. I had iHackers (1.2 I think) working with r/w system partition I just got a little flash-happy when a 4.3 ROM came out and went and flashed it.
Doesn't matter now anyway.. I unlocked the BL! Flashed iHackers 2... what a pile of crap (my opinion)... installed a load of stuff I purposefully unticked in Aroma and has lost me root.. yay.
If I restore a nandroid of iHackers 1.2 from CWM will I brick my phone in any way seeing as I'm currently on Android 4.3 with all the kernels and radios that brings..? That is of course saying I can get into recovery...
[edit]
Can't get into CWM... brilliant. I guess I'm going to have to use flashtool to downgrade and root my phone or something like that now.. Wouldn't mind but I'm at work and have to download ROMs on my phone because of work proxies!

cyberguru said:
Dont think thats 100% accurate - you can get Root with /sys mounted as R/W on roms <4.3. I had iHackers (1.2 I think) working with r/w system partition I just got a little flash-happy when a 4.3 ROM came out and went and flashed it.
Doesn't matter now anyway.. I unlocked the BL! Flashed iHackers 2... what a pile of crap (my opinion)... installed a load of stuff I purposefully unticked in Aroma and has lost me root.. yay.
If I restore a nandroid of iHackers 1.2 from CWM will I brick my phone in any way seeing as I'm currently on Android 4.3 with all the kernels and radios that brings..? That is of course saying I can get into recovery...
Click to expand...
Click to collapse
Yea, I meant it can't be done on 4.3
Well, Why don't you just flash stock ROM (4.3) then 257 then 534 and then install iHackers 1.2 without any problems.
Regards,
~J2C

Right, deleted last post but in summary; got root back but no Play Store and no recovery installed so did some good old fassioned searching:
Over in Original Android dev there is a discussion for Root on 4.3. The first post has links to kernels with recoveries and SuperSU by chainfire... downloaded Philz and SuperSU and now just need to figure out how to flash the two of them..
I take it something like
Code:
fastboot flash boot filename.img
will take care of flashing kernel to my UL phone so then I power on and press Vol Up, Vol down to enter recovery and flash SuperSU?
Wish me luck

Need help bricked phone :(

i recently flashed the eXistenZ Ultra 2, and im sure i did everything fine, after flashing the rom in recovery and flashing suprsu and wifi fix, i powered off the phone, and powered on but sony logo has apeared until now , and welcoming`s sounding 999..times. i cant turn it off, or i should say i cant do anything.
please help,

After flashing ROM and the fixes you should flash the 12.1.A.0.266 Firmware with FlashTool!
If problem still persists:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Take a look at this site A recovery would be quite useful, but I think the kernel of eXistenZ ROM has one. If not, you'll find one in the development section. Otherwise, use the ADB as solution.
Good luck

Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?

eefathi said:
Thanx for the post!
I used force shut down and then flash the 254 rom, and did all those things, and the problem occured again.
does the recovery software have to be the touch recovery? I use CWM v6 that enables with volume +.
and i use SuperSU fix.zip rather than superUser.zip and generally i flash rom, supersu fix.zip and wifi fix.zip. i flashed those three, before first booting, do i have to boot first before flashing wifi fix.zip?
Click to expand...
Click to collapse
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!

Schokonuss said:
I think you need to flash 12.1.A.0.266 instead of 12.0.A.2.254 after flashing ROM. You could also wipe data, cache and dalvik cache, reflash eXistenZ ROM and SuperSU fix (or SuperUser but SuperSU should be ok), shut down the phone with the option in recovery and then flash the 12.1.A.0.266 with FlashTool.
It doesn't matter which recovery you take. Use the one you like best. I'm not quite sure, but to go sure, please flash the wifi fiz.zip after first boot up!
Click to expand...
Click to collapse
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.

eefathi said:
thanx again,
i flashed the 266 kernel before the first boot, and the rom runs correctly,
but ive got some new problems:
1. performance, when i click on performance, it closes unexpectedly and says it has stopped.
2. i used go backup for backing up from data in 4.1, but in this rom i restored my apps,the apps installed correctly but goBackup says the data restoring successfully finished , but the data didnt restored, by the way at the time i backed up from my apps&data, i swapped memories with that linux code that this forum did.
Click to expand...
Click to collapse
You're welcome
1. Do you have SuperSU installed? On AOKP ROM I'm running it asked for superuser permission for ROM Control (the control center implemented in the settings of the ROM). Maybe it'll ask you if SuperSU is installed. Otherwise, because it is after the first boot it needs to rebuild cache and so on.. If problem persists after reboot, just use an other clock speed controler (No-frills CPU, SetCPU..)
2. If you did that at the same time, maybe Go Backup didn't really backup your data. Try again, if it doesn't work and if you have a nandroid backup (backup from recovery) you can go into recovery, then to advanced restore and restore data. Otherwise your data is unfortunately gone I think :/
PS: I prefer Titanium Backup

[HELP]Xperia SP stuck in cyanogenmod logo after update

Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!

try to use flashtool. google it on how to use flashtool or check other threads.

So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.

Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.

Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?

Don't use OTA, just download and flash updates manually using recovery.

In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.

How can I backup my rom.

I finally got my phone rooted on lollipop. I want to install the xposed framework but all the instructions say backup your rom. I rooted using Deodexed_ROM but when I do home button, volume, power. I don't see an option to backup my rom. I'm also confused does titanium backup only backup apps or can in do a full system rom backup that I can restore from in case of a looping boot when flashing.
thanks

Because the bootloader is locked on AT&T S5's you can't install a custom recovery therefore you can't do a complete ROM backup. If you use Titanium, you will backup all your settings and apps for future updates. If you bootloop you have to reinstall the ROM that works for your model. Then use Titanium to reinstall everything back to the way you had it. Paid version is best for this.

Sgt.CM said:
Because the bootloader is locked on AT&T S5's you can't install a custom recovery therefore you can't do a complete ROM backup. If you use Titanium, you will backup all your settings and apps for future updates. If you bootloop you have to reinstall the ROM that works for your model. Then use Titanium to reinstall everything back to the way you had it. Paid version is best for this.
Click to expand...
Click to collapse
Technically, you can install safestrap for a custom recovery, but you'd also need to flash the NCE kernel to boot into safestrap. But, you'll likely softbrick trying to get back into the operating system, or you'll get constant app crashes. That's why I don't do system backups on lollipop. It was a headache getting the phone back to the way was.

[Solved] Trouble rooting, trying to install Dualrecovery for a nandroid backup.

Edit: The flashable zip seemed to be a good workaround and got everything done in one go. Fingers crossed from here on in.
Hi guys, this is my first post here, so please go easy on me.
So recently my phone screen cracked and I had to send it off for recovery.
The company wiped and upgraded my firmware, but I did my data backup as a nandroid backup, so I have to get a recovery installed to restore it.
I have managed to unlock the bootloader and flash this version of the firmware : - D5803_23.4.A.1.264
I am simply trying to root the phone so I can get SuperSU onto it and the method I used last time uses CWM. However, when I try to install CWM I can access CWM, but otherwise, it goes into a boot loop and I have to reflash that firmware to restore it, which deletes the CWM. The CWM version I can flash does not seem to be able to restore nandroid, so it's fairly useless.
i have tried downgrading but then the phone crashes on startup. I noticed when I restored to the current firmware above, the phone had kept all my settings, so I don't know if there's extra I need to wipe, or if I'm not flashing correctly.
Now I have used PRF tool to create a flashable zip, that I thought might be able to do the job for me if I can get something to install it. It has the working firmware, SuperSU and dualrecovery in it.
I have done this all before without issues, but the new firmware version is making things more difficult.
So questions are;
1. Am I flashing incorrectly when downgrading? Or is there some other factor at play preventing me from doing so?
2. Is there a way I keep the CWM and flash the working firmware? Like it would go into boot-loop but then I could get the normal systems operating again and have the phone rooted, continuing the work. I figured there might be an option in flashtool, but I didn't want to press anything without confirmation from someone.
3. Is there an easier way to froot this? Last time I was able to use giefroot, but now it says my kernel isn't supported.
Any help would be greatly appreciated. I'm not new to modding my phones, but I'm not advanced either. Let me know if there are other details I can give that might help.
Thanks.