For context, I want to clear up a few things before trying to root so I don't end up bricking the phone.
So after reading a few threads it seems even recovering via twrp is messed up in this phone. Can someone shed some light on this matter?
Can I restore system, data, and boot partitions via twrp in case something goes wrong (while staying on official miui roms everytime, I don't intend to install custom roms) and I have to revert the phone back to the state it was in at the time of a backup?
It feels like at the very least we would be required to re-flash the entire firmware via mi flash tool and then restore whatever is needed via twrp later. Will this work?
Also I hear using twrp to install the official firmware is not a good idea, what's that about?
I know long post and a lot of questions, so please bear with me.
Thanks.
Custom ROMs and Stock ROMs differ in one aspect, which partitions are left untouched. Since stock ROM is a lot more invasive and formats all partitions, official flash method is recommended.
When you mess things up, mi flash tool is safest option. Its safe to experiment, backup, restore on boot+system+data in TWRP across ROM installs but don't mess up recovery partition. Remember to format data between ROM installs unless dirty flashing on same android version
miravision said:
Custom ROMs and Stock ROMs differ...
Click to expand...
Click to collapse
I see. Thank you for the reply!
Related
Okay I have flashed Calkulin's Rom
http://forum.xda-developers.com/showthread.php?t=712695
The one without the OTA update that killed Root (I haven't updated to that yet )
I rooted using Toast's method - I did part 1 of his root. For part 2, I did this one
For part 2, I did this http://forum.xda-developers.com/showthread.php?t=705113
I'm trying to flash a new ROM now. Maybe damage protection or even FROYO (Yeah froyo sounds better)
I also want to do the NOVATEK FPS bandaide as well.
I just don't know where to start. I read somewhere someone said you just re-flash a rom again with the recovery...but I don't want to screw up.
Can someone post a very brief what I should do or lead me please?
FYI, the Rom you flashed from the first link provided is stock rooted with the latest update.
Anywho, you heard right, you flash new roms the same way you flashed that Rom. Download the Rom to your sdcard, boot into recovery, wipe data cache and dalvik, flash from sdcard, choose the Rom you put on there and confirm. That's all there is to it!
The important thing to remember is to always wipe before you flash, this will ensure no errors occur.
Hey thanks for backing up data I heard nandroid and titanium which one is better
Sent from my PC36100 using Tapatalk
Two different things. You should have at least one nandroid that you know works, this is used encased you beef anything up from flashing or something and you want to return your phone to the exact state it was at when you did the backup. That's the purpose of nandroid, to backup a complete image of the state your phone is in, Rom and all (excluding radio and wimax)
Titanium is a utility you use to backup all of the apps you have installed, along with their data and market links. This is usefull when flashing a new Rom so you can easily restore all of your apps without having to download and install them again and again.
Check this, it answers quite a bit of your questions and then some.
http://forum.xda-developers.com/showthread.php?t=710513
Sorry for the noob question, what are the recovery roms for? Wouldn't you just need a stock to revert to if you messed up the phone royally? Also, where can you find them? I haven't seen the aman-ra anywhere, though people regularly refer to it.
Also, do all of the ROMs listed on the wiki work with 1.47? It doesn't mention the version.
Rilasis said:
Sorry for the noob question, what are the recovery roms for? Wouldn't you just need a stock to revert to if you messed up the phone royally? Also, where can you find them? I haven't seen the aman-ra anywhere, though people regularly refer to it.
Also, do all of the ROMs listed on the wiki work with 1.47? It doesn't mention the version.
Click to expand...
Click to collapse
A recovery ROM is what you use to manage full ROMs, you can backup, restore, wipe, mount as USB, all outside of the ROM loaded. These functionalities aren't available from within the system itself.
It's kind of like an advanced BIOS. You can't make a full backup of Windows XP while your IN Windows XP. (ASFAIK)
Edit : Amons recovery is included in all the full root method tutorials. It's called recovery.img
So, the recovery is more of a utility than just a backup. Usually you flash what is called the recovery partition with a recovery image. Once you do that, you don't need a computer to get into recovery. Anyway, the recovery does alia you to do a backup and restore, but it is actually the utility that you flash roms with. It also let's you wipe cache and stuff which is critical to flashing your own Rom.
You would use recovery to restore, instead of flashing stock, because it would return your phone to the exact state it was in when you did the backup. You don't lose any settings or apps or anything.
When you root via toast pt 2 you wind up flashing amon recovery. There is also a thread in the dev section with a different version I think, just search amon.
And most roms on the wiki have the newest ota integrated in the Rom, but you should always consult the first post in the roms thread to see more about that.
My wife got an Epic, while I have an EVO. I'm quite familiar with rooting, ROMs, etc. I think I've got all the Epic-specific details down, but I wanted to ask this question to make sure I've got this down.
I plan to use this root method. After that, her phone will be left with a basically stock, 2.2 ROM that uses the EXT4 file system, and Clockwork recovery image. I read that I won't be able to flash new versions of Clockwork from within ROM Manager. From then on, I will need to stick with ROMs designed for the EXT4 file system or both EXT4 and RFS. I assume I flash ROMs and Kernels just like with my EVO: choose my ROM, it will come with a kernel, but I can flash whatever kernel I choose on top of that (as long as my ROM matches my Android type, DK or EB). There are currently no Gingerbread ROMs for the Epic, but when they are released, I should be able to use CM 3.x to flash them.
OK, I would greatly appreciate if someone could just read over that and let me know if I understand anything incorrectly. Also, if someone could tell me if there's a good reason to choose Odin's recovery vs. Clockwork, I would very much appreciate that as well.
Odin Vs. Clockwork
Everything you posted above sounds accurate.
I use Clockwork to flash my ROMs just because it is easier to me (no cables involved). The only time I use Odin is when my phone is bricked. This has happened after installing Samsung updates, but it is very easy to use Odin to restore back to Stock, then flash a new ROM over.
One advantage to Clockwork is that some ROMs support a full backup. I use Bonsai4All and during installation from Clockwork it will backup your information, then restore it. As far as I know, Odin is not capable of any such thing.
Hope this helps...
OK wait, some ROMs support full backup? Why couldn't I do a full nandroid backup with any ROM I'm running from within Clockwork Mod Recovery?
WrlsFanatic said:
OK wait, some ROMs support full backup? Why couldn't I do a full nandroid backup with any ROM I'm running from within Clockwork Mod Recovery?
Click to expand...
Click to collapse
You can use these two zips from within clockwork if you are flashing a rom that doesn't backup/restore for you.
Flash the "backup" before you wipe anything and then after you flash the rom - before you reboot - flash the "restore".
These .zips take care of data/settings/apps. Not actual system items, so they don't seem to cause some of the issues that programs like Titanium Backup cause.
EDIT: It's always good to do a complete backup within Clockwork before flashing ANYTHING new. Roms, zips, etc.!
Awesome! Thanks! I can't believe that Clockwork isn't working any better than that where it has problems backing things up. I know the EVO gets a lot of dev love, but seriously... SO much easier.
Hi. I backed up my phone using the backup method found here: http://android.stackexchange.com/questions/28296/full-backup-of-non-rooted-devices
This method uses CMD and creates an android backup file (.ab) I want to unlock my bootloader and add the custom clockwork recovery. Of course unlocking the bootloader wipes everything. So if i were to restore everything with the .ab file, then do the custom recovey with the superuser thing, would that give me root, and would all of my apps and data be restored as they are right now?
Probably a stupid question, but i want to be completely 100% sure i won't mess up my phone. I know its going to void warranty, which would be a problem if i dropped it of course
Thanks
It should work yes, you can also backup apps with an app called carbon. Free in the playstore.
Then unlock the bootloader,flash a custom recovery and make a backup of the stock rom in there right away too (needed when you want to go back to full stock for future updates) its called a nandroid backup.
Then root it and restore, or install a brand new custom already rooted rom
Thanks a lot
If it was a custom rom i chose to install, will it still restore? or would it need to be the original stock for the restore to work properly?
Danw20 said:
Thanks a lot
If it was a custom rom i chose to install, will it still restore? or would it need to be the original stock for the restore to work properly?
Click to expand...
Click to collapse
Afaik know you can restore apps on any rom with carbon. Watch out with restoring system data, it can crash the rom.
Because some custom roms have more changes and if you restore system parts it will break the rom. But apps should not be a problem. The most important thing is that you do a nandroid backup of the stock rom. The rest is easy to setup new in the worst case.
Brilliant. Thanks for the help, much apreciated.
Was half expecting an answer like that, i think i will give root stock a go, then probably when HTC stop updating i will be very tempted to give a custom a go.
Cheers
I have unlocked the bootloader, i think i have flashed the recovery, downloaded nandroid and still says i need root, so i downloaded the superuser thing and when i try to install the binary thing it says there is an error. Anything i can do?
Update: I have learnt Its all good now.
Good mate ! Have fun with your rooted phone
CASE CLOSED !
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Balteck said:
Hello everybody, it is time to update to Nougat and I'm ready to do it.
According to this thread https://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
I need a system_image and stock recovery backup for being able to do an OTA.
I did it and I must restore the system_image and the stock recovery as written in point 8.
But according to this other thread https://forum.xda-developers.com/showpost.php?p=64299835&postcount=4
in Hidden Content point 13, I must backup the system_image, the stock recovery and the boot image.
I have only backupped system_image and recovery and I can download boot.emmc.win from the second thead, but I wish to ask:
Is it really necessary to restore boot.emmc.win? Now I'm on ViperOneM9 4.3.0
Why @Captain_Throwback didn't mention it in his official TWRP thread?
I thank you in advance anyone may help me to get the OTA in the right way
Click to expand...
Click to collapse
If I didn't mention it, then you don't have to do it .
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Sent from my HTC One M9 using XDA Labs
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
shivadow said:
I thought it's impossible to backup the stock recovery seeing as twrp is needed to be flashed to make the backup..
Beamed in by telepathy.
Click to expand...
Click to collapse
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock recovery.
Flippy498 said:
@Captain_Throwback can you maybe explain that a little further? I made the experience that people are facing problems if they return from a custom rom to a stock rom and don't wipe their phone. That's why I added the wiping step to my instructions. After that several users reported that their phones didn't boot after they restored the first version of my backups (which lacked the boot.img). Therefore, I thought the boot.img is needed as well and all backups got replaced over a year ago with the current version which includes the boot.img.
However, all this is based on the reports of users who had problems with returning back to stock. I've never faced these issues myself. So if there is anything wrong with my instructions I'll correct them, of course.
Click to expand...
Click to collapse
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Captain_Throwback said:
Not sure what to explain - OTA does no verification on boot.img. So it doesn't have to be stock for an OTA to install. It's that simple.
Click to expand...
Click to collapse
OK. I guess there was a little misunderstanding.
The current version of my instructions is meant to be used if you want to return to a clean stock system. (In other words the ability to install OTAs, again, is only a side effect.) I never was talking about the boot.img being necessary for being able to install the OTA. I thought you were saying that the boot.img wouldn't be needed inside a backup if you do a full wipe before the restoration and that the phone would still boot.
Sent from my HTC One M9 using XDA Labs
I'm little confused now.
For installing an OTA update I MUST have an untouched system partition and stock recovery.
But the steps I need to do are:
1) backup apps and settings
2) restore untouched system partiton and stock recovery partition from TWRP, doing a factory reset (wipe data, dalvik and cache)
3) boot the original stock OS, configure wifi and go to Software Update
4) download OTA(s)
5) apply update and reboot phone
6) with ADB start TWRP recovery and backup the new stock recovery and the new stock system_image
7) flash TWRP and new custom ROM
8) restore apps and settings from point 1)
So, is it possible that at step 3 my HTC cannot boot because I didn't restore the boot partition (I'm coming from ViperOneM9 4.3.0)?
Or is there a simpler method, without backuping, wiping, restoring?
Flippy498 said:
Since firmware 3.x you can boot TWRP via fastboot from the bootloader without overwriting the currently installed stock firmware.
Click to expand...
Click to collapse
Looks liks i used an out of date tutorial then.. What a bugger..
Beamed in by telepathy.
Anyone can confirm me that my previous steps are right?
So I may uodate to Android n without doubt
Thank you very much