Database Develop

[Q] Root deviced, BL locked, no custom recovery, nandroid backup?

Hi guys,
Thanks to jcase, we can now root out Razr i without unlocking the bootloader.
However, a locked BL prevents from installing CWM or another custom recovery.
I've googled and found Onandroid and Orange Backup, which are solutions for backing up a rom without a custom recovery.
Is it reliable?
What's the method to restore the created backup?
Can I set the path to the backup? (because our external sdcard is not mount at the standard mount point)
Thanks!

ciberbeb said:
Hi guys,
Thanks to jcase, we can now root out Razr i without unlocking the bootloader.
However, a locked BL prevents from installing CWM or another custom recovery.
I've googled and found Onandroid and Orange Backup, which are solutions for backing up a rom without a custom recovery.
Is it reliable?
What's the method to restore the created backup?
Can I set the path to the backup? (because our external sdcard is not mount at the standard mount point)
Thanks!
Click to expand...
Click to collapse
What I usually do is just backup my add data with Titanium Backup cause that the most important stuff.
Everything else can get flashed back.

dagoban said:
What I usually do is just backup my add data with Titanium Backup cause that the most important stuff.
Everything else can get flashed back.
Click to expand...
Click to collapse
I actually don't minf losing my app data.
I'm talking about the system, the rom itself.
How can I make a backup of the entire system and restore it with no custom recovery?
I know the stock recovery has an option to flash a zip, but in which format?
I also checked the Onandroid topic, and a custom recovery seems to be needed...

ciberbeb said:
I actually don't minf losing my app data.
I'm talking about the system, the rom itself.
How can I make a backup of the entire system and restore it with no custom recovery?
I know the stock recovery has an option to flash a zip, but in which format?
I also checked the Onandroid topic, and a custom recovery seems to be needed...
Click to expand...
Click to collapse
Maybe this one could help you http://forum.xda-developers.com/showthread.php?t=614016

Need a bit of help, not sure what to do

So I was running Ultimate PureXSP v2.1 and it was starting to get really bogged down and slow so I figured id try and reinstall the ROM over the existing install, so I went into TWRP and installed it, the install said failed but because of the touch debug messages, I couldnt see the error message.
Anyway, TWRP has always had erratic screen movements and general weirdness, it would keep going back to the homescreen when trying to flash. So I rebooted and it got stuck in a bootloop!
I used flashtool to put a stock 201 firmware on and now its runnning okay again. But I have lost root and recovery and I dont think 201 can be rooted unless I downgrade first but I will probably run into data problems, I cant use titanium backup or a nandroid to back up my data.
What should I do? I dont have any backup software that works without root and I cannot root without downgrading and losing data.
Can I unlock the bootloader from 201 and then add recovery and root? I already have a TA backup and my unlock key.
Any help would be great!
Sent from my C5303 using XDA Premium 4 mobile app

Yup, that's what I did.
Unlocked the bootloader. Then can flash any custom kernel. I flashed DoomLord's Adv Stock kernel, which has an inbuilt recovery. Then flash chainfire's SuperSU update through recovery to get root. Then can install any other recovery and flash stock .201 kernel back. One problem though.. [highlight]YOU WILL LOSE ALL YOUR DATA (INCLUDING WIPING OF INTERNAL SDCARD) WHEN UNLOCKING THE BOOTLOADER.[/highlight] So, do you have any cwm data backup done before?
Edit: Backup&Restore app that comes with stock Rom is supposed to backup and restore data without root. But it never worked for me when restoring things. Other option is to use 'ADB backup' commands from a pc. It also didn't do restore properly for me. Can try those as last resorts.

[Q] Questions before flashing custom ROM

I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers

Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.

TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?

Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.

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.

Question Need help installing Xiaomi EU Weekly

Hey, so i opened my Bootloader and now I cant find how the hell to flash the latest Weekly version of Xiaomi EU, can someone help me? I searched on youtube but they flash via Fastboot and I don't see a weekly version with Fastboot

Follow the instructions found on the first post here https://forum.xda-developers.com/t/...mi-eu-rom-for-xiaomi-mi-11-pro-ultra.4260617/
Look at the bottom, there's an edit that tells you how to install TWRP, that's the primary way to install the new versions of that rom

Bananablob said:
Follow the instructions found on the first post here https://forum.xda-developers.com/t/...mi-eu-rom-for-xiaomi-mi-11-pro-ultra.4260617/
Look at the bottom, there's an edit that tells you how to install TWRP, that's the primary way to install the new versions of that rom
Click to expand...
Click to collapse
HELP - i flashed the EU rom and wiped Dalvik cache, and reeboted, now It reboots to the TWRP over and over again, what do I need to do?

You also need to wipe data and such before flashing, so maybe you didn't notice or forgot, but as long as you have TWRP, you can recover.
Maybe your ROM download got corrupted. If possible, check the checksum, they should provide it.
It's also possible your USB port + cable combo doesn't work properly, it's happened to many people, so if you are sure it's not the rest, it might be just that

Bananablob said:
You also need to wipe data and such before flashing, so maybe you didn't notice or forgot, but as long as you have TWRP, you can recover.
Maybe your ROM download got corrupted. If possible, check the checksum, they should provide it.
It's also possible your USB port + cable combo doesn't work properly, it's happened to many people, so if you are sure it's not the rest, it might be just that
Click to expand...
Click to collapse
I flashed it but now every app I open crushes, Im on weekly version and I restored apps from the Xaiomi backup, do you know why?

I can't say I do, but I'd assume it's because Xiaomi backup is configured to work only on stock roms.
It's possible that uninstalling and reinstalling each app using whatever the proper app shop is for the given app will fix it without losing the restored data and cache for it.

Bananablob said:
I can't say I do, but I'd assume it's because Xiaomi backup is configured to work only on stock roms.
It's possible that uninstalling and reinstalling each app using whatever the proper app shop is for the given app will fix it without losing the restored data and cache for it.
Click to expand...
Click to collapse
omg I only did it because i thought I would be able to restore everything within 1 click and now everything crushes. I have like 100 apps + tons of accounts to login

I would always assume auto backup things to fail when you need them.
Try to reflash your original rom from here and restore using the same backup tool: https://forum.xda-developers.com/t/miui-updates-tracker-mi-11-pro-ultra-star-mars.4263135/
Then you can reevaluate how you wanna backup and restore to transition.
It's possible it failed because you have an official rom backup, but it would work if the tool had backed up from Eu to Eu

Bananablob said:
I would always assume auto backup things to fail when you need them.
Try to reflash your original rom from here and restore using the same backup tool: https://forum.xda-developers.com/t/miui-updates-tracker-mi-11-pro-ultra-star-mars.4263135/
Then you can reevaluate how you wanna backup and restore to transition.
It's possible it failed because you have an official rom backup, but it would work if the tool had backed up from Eu to Eu
Click to expand...
Click to collapse
I dont wanna mess with reinstalling CN version, etc
I will just Factory reset and reinstall manually..
To factory reset in brings me to TWRP, why is it?

Because you installed TWRP instead of the normal recovery utility, you now have TRWP in that partition on your phone. If you use TWRP to flash the proper stock ROM, it will have the same effect as using factory reset using the stock recovery utility. BTW, the stock recovery utility is not built to support having flashed another rom, so you're in good hands having TWRP instead.

You probably had issues because you only wiped dalvik rather than format data after installing the EU ROM. You must format data after flash because the different branches have different partition layouts, hence your problems.
As you must format, you might as well start from scratch again or go in to twrp wipe menu and select format, type yes to confirm and then reboot system. If you want to go down the full install, then flash the ROM again, format data, with the yes confirmation, then reboot system. After each update, just a dalvik wipe is