Related
i just flashed a rom and forgot to backup nandroid.
but i backed it up straight away after flashing it , will it be ok?
also how does all this nandroid backup thing work what does it really do,
last time i flashed a rom i still got that backed up if it will be any use.
thanks
A Nandroid backup backs up the entire state of your phone apart from its SD card. You should do one when you have a fully working (and rootable) phone, so that if you screw up flashing it in future you can get back to a working phone with it set up how it was before.
It's not enough just to do the backup, you need to ensure that you can restore from it too. I had to do a restore recently and realised I couldn't use fastboot because I didn't have the right SPL (part of the bootloader) installed. Luckily the recovery image I had let me manipulate it via adb etc. I learned a lot of things the hard way and I suspect I came very close to having a bricked phone.
I don't understand..hopefully I don't mess up my phone, when do I have to restore.nandroid
When flashing a ROM goes wrong (usually unlikely), you can end up with a phone that won't boot. If you do a nandroid backup before you Flash, you have a backup of your entire phone's state before you flashed. There are ways to restore Nandroid backups (or flash other images) even if your phone won't boot normally. You really have to research this and make sure you have everything right before you flash any ROM.
If you don't understand these concepts, you probably shouldn't be flashing ROMs. Just use the official updater provided by HTC in your country.
how can i restore nandroid then if my phone gets messed up thats the main question
hawwy said:
how can i restore nandroid then if my phone gets messed up thats the main question
Click to expand...
Click to collapse
Google is your friend. Seriously, there are thousands of resources on this around the web - frankly if you are not willing to do the research into this, just don't flash any ROMs. Doing so is only for technically minded people who know how it all works or are willing to go off and learn about it thoroughly. It doesn't sound like that is you.
This stuff isn't easy, for the same reason flying a 747 isn't easy: it shouldn't be attempted by novices.
I can't just explain it in a couple of sentences.
Hi!
This is my first post and I apologize if it would be a bit long but I wanted to be honest and express what I wanted to say.
First of all, I just want to say.. You guys are great!
I have been browsing your forums years ago while I was still using my HTC Desire HD. I wanted to join then I was afraid to brick my phone and didn’t have the liberty of time to research and study how. I just observed as you guys enjoy modding your phones. But this time, I really wanted to start modding and participate in this community that is why I registered. I just bought my new phone and after two weeks of research and contemplating, I decided to get the Nexus 4. With this, I know this is a very good phone to start my modding ventures..
One thing that’s really hard to do is keeping up with all the information that you guys have already discussed or contributed. Honestly, its so hard to back-read pages and pages of different topics or even the same topics! I consider myself a noob coz’ I do not have yet any experience in rooting. I did some modding way back before when I had my MotoRazr flip phone and did some crazy modding to it, but now android is a new world to me in terms of modding.
XDA is such a large forum already and sometimes you’ll really get dizzy back-reading similar topics, trying to find the right guide for me. Im more of interested to know how things work and not just use toolkits. This way I would not just benefit but rather be educated as well.
I really wanted to start modding and in the future, also be able to contribute to this very great community. I am not a guy who has knowledge in scripts and programming but I am an easy learner and have common sense as well. But I’m not that kind of guy who can easily spend to buy a new phone. I really worked hard to be able to buy my new Nexus 4. Since I am just a newbie it is very likely I might make mistakes. I hope you could help me and guide me as I learn from our forum and from you guys. I do not want to end up bricking my phone.
Thank you for all those who would acknowledge my message and help. To all you guys, great job!
I myself coming from Desire HD..I still remember how painful its rooting process was.Nexus 4 isn't like that..From Unlocking to Flashing a Custom Rom..Whole Process is easy to understand & less chance of getting into trouble..
For learning..you can have a look at this thread..
[Guide] Ultimate Nexus 4 Root Guide
I myself coming from Desire HD..I still remember how painful its rooting process was.Nexus 4 isn't like that..From Unlocking to Flashing a Custom Rom..Whole Process is easy to understand & less chance of getting into trouble..
For learning..you can have a look at this thread..
[Guide] Ultimate Nexus 4 Root Guide
Click to expand...
Click to collapse
thanks for the reply!
I read here in xda that you just need to turn your bootloader off so that anytime you want to root it or do some mods, you do not have to make factory reset and lose all your data. So I was thinking should I just turn it off first while I am still trying to learn more about rooting, Roms, flashing, etc. before actually doing it? That way I do not have to erase my data during factory reset if I decide to root a little more later in time where I have already made several settings and setups, contacts and messages. Is this right?
But if I were to turn my loader off then eventually I have to do a factory reset. Since this is my first time to mod, root, flash or use custom roms, so I think the first I should learn before anything else is about backup so I could still put it back to original stock in case I needed to. Could you guys guide me how to make a backup or a full backup from stock and unrooted phone? I also read that there are custom recovery/backup. Could I do this or my phone should be rooted first before I could do this which means I would need to factory reset first to turn my loader off and eventually erase my data even before I could make a backup. Are there apps I could use and what particular files should be backed up? Some things I am concerned of losing is the words I have added in the dictionary coz I have to do it all over again. For apps, sms and contacts should I just use apps available at the Play store to back it up or is there a better way to actually backup everything including settings? Pls guide me how should I do this.
vinz_bangiz said:
thanks for the reply!
I read here in xda that you just need to turn your bootloader off so that anytime you want to root it or do some mods, you do not have to make factory reset and lose all your data. So I was thinking should I just turn it off first while I am still trying to learn more about rooting, Roms, flashing, etc. before actually doing it? That way I do not have to erase my data during factory reset if I decide to root a little more later in time where I have already made several settings and setups, contacts and messages. Is this right?
But if I were to turn my loader off then eventually I have to do a factory reset. Since this is my first time to mod, root, flash or use custom roms, so I think the first I should learn before anything else is about backup so I could still put it back to original stock in case I needed to. Could you guys guide me how to make a backup or a full backup from stock and unrooted phone? I also read that there are custom recovery/backup. Could I do this or my phone should be rooted first before I could do this which means I would need to factory reset first to turn my loader off and eventually erase my data even before I could make a backup. Are there apps I could use and what particular files should be backed up? Some things I am concerned of losing is the words I have added in the dictionary coz I have to do it all over again. For apps, sms and contacts should I just use apps available at the Play store to back it up or is there a better way to actually backup everything including settings? Pls guide me how should I do this.
Click to expand...
Click to collapse
First setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/, and stay away from Toolkits
Flash a custom recovery like CWM or TWRP in fastboot for backing up and restoring the whole rom (system and user apps, so the whole configuration).
Install Titanium Backup or Helium to backup and restore users apps and data.
vinz_bangiz said:
thanks for the reply!
I read here in xda that you just need to turn your bootloader off so that anytime you want to root it or do some mods, you do not have to make factory reset and lose all your data. So I was thinking should I just turn it off first while I am still trying to learn more about rooting, Roms, flashing, etc. before actually doing it? That way I do not have to erase my data during factory reset if I decide to root a little more later in time where I have already made several settings and setups, contacts and messages. Is this right?
But if I were to turn my loader off then eventually I have to do a factory reset. Since this is my first time to mod, root, flash or use custom roms, so I think the first I should learn before anything else is about backup so I could still put it back to original stock in case I needed to. Could you guys guide me how to make a backup or a full backup from stock and unrooted phone? I also read that there are custom recovery/backup. Could I do this or my phone should be rooted first before I could do this which means I would need to factory reset first to turn my loader off and eventually erase my data even before I could make a backup. Are there apps I could use and what particular files should be backed up? Some things I am concerned of losing is the words I have added in the dictionary coz I have to do it all over again. For apps, sms and contacts should I just use apps available at the Play store to back it up or is there a better way to actually backup everything including settings? Pls guide me how should I do this.
Click to expand...
Click to collapse
Backup all of your data before unlocking the bootloader..It'll wipe everything
gee2012 said:
First setup adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/, and stay away from Toolkits
Flash a custom recovery like CWM or TWRP in fastboot for backing up and restoring the whole rom (system and user apps, so the whole configuration).
Install Titanium Backup or Helium to backup and restore users apps and data.
Click to expand...
Click to collapse
thanks for the advice! already flashed twrp because I would use PA later on and many said its better to use this recovery. I actually encountered some problems on Bootloop which is my first real challenge in the world of modding. But i managed to solved it with help form xda members as well.
Tonight I will be proceeding with flashing customs rom (PA). im just reading some more threads to learn more and be prepared to solve problems in case something goes wrong.
Hey guys, I've run into an issue while attempting to flash a custom rom to my i337. First off, I was successfully able to obtain root and have verified that I have su privileges. My issue is happening when I try to install any type of boot loader. I've tried the following methods to install a bootloader:
http://forum.xda-developers.com/showthread.php?t=2314494 (step 3- both methods)
http://forum.xda-developers.com/showthread.php?t=2297033
using odin to flash .img recoveries using this conversion method http://forum.xda-developers.com/showthread.php?t=2281287
Whenever I install any recovery and I try to boot into it, I boot into odin/download mode. After this happens I am unable to boot into the stock rom (or any rom for that matter) until I use this (http://forum.xda-developers.com/showthread.php?t=2360859) method to restore my current rom.
Additionally, I have been unable to perform a factory or soft restore since I've had this issue. I can't boot into recovery so I can't do a hard reset, but every time I attempt to restore within the android OS, I boot into odin mode....
It's become quite frustrating and I'm unsure of where to go next.
Additionally, additionally, I do believe that I have the MF3 update installed. I could be wrong, but I'm pretty confident I do.
I just got this phone a few weeks ago and I'm still learning the ropes here... so forgive me for my lack of knowledge on the subject
Thanks in advance for any input
If you have mf3 you can not flash roms or put on a custom recovery. In fact you'll lucky you haven't bricked your phone. Don't try any more until an exploit is found.
Edit, in the mean time, do some more reading and research. You need to know a lot more before you are ready to flash anything if the devs find away to put a custom recovery on.
I just don't understand why people that don't even have a basic concept of how their phone works would do something to it that could (and probably will) turn it into an expensive brick? Is it really to difficult to do a little reading first? It's forum rules, it's common sense, and it can save you a lot of time and trouble. I'm not trying to bust the OP's balls, but if you don't take a little time to be responsible for your own actions (searching and reading and reading some more), you get what you deserve. Being "new" is never an excuse, it's just more reason to do some reading. Everyone, don't touch your phone until you learn about what it is you are doing to it first!
Good luck to the OP, I hope you decide to read (at least) the pinned threads in the General section (and hopefully a lot more) before you do anything else to your phone.
Sad but true
Sent from my SAMSUNG-SGH-I337 using xda premium
I'm curious as to whether anyone has successfully restored one of the recently posted backups to the point where you can take a OTA update. For that matter, has anyone successfully restored to the point where you can boot into the system and use it. We have various people who fear that they've bricked.
Has anyone who can't get their phone working returned it? And if so, has Alcatel accepted it and given you your money? It may be too soon to know on this, I realize.
I don't need to change anything at the moment, but I have some trepidation about doing a restore out of fear that I'll brick my phone or something close to it. I don't want to be on 5.02 for as long as I have the phone.
It would be nice if Alcatel would release system images. I'm not holding my breath, though. Has anyone contacted them to make that request? Any response from them about this?
My purpose here is to get, for all of us, a sense of what works and what doesn't, whether or not people should feel confident about rooting their phone, etc.
As it was mentioned, their support is lacking any usefull info on any question (my experience writing to them from different email accs) or they aren't willing to share.. Too bad I would say..
source code will be given, but i think after next big update. Releasing source code of lauch firmware does not make any sense.
I have spoken with Alcatel support here in Czech republic and they said, they will sure release the source code and that the updates will come every 4-6 weeks.
And for the restore thing. You can always root your device, make backup, and when update is online, just backup your apps (titanium backup), restore the system., unroot, update. Then root, and restore your apps using titanium backup. Sounds complicated, but its matter of one hour maximum.
DallasCZ said:
source code will be given, but i think after next big update. Releasing source code of lauch firmware does not make any sense.
I have spoken with Alcatel support here in Czech republic and they said, they will sure release the source code and that the updates will come every 4-6 weeks.
And for the restore thing. You can always root your device, make backup, and when update is online, just backup your apps (titanium backup), restore the system., unroot, update. Then root, and restore your apps using titanium backup. Sounds complicated, but its matter of one hour maximum.
Click to expand...
Click to collapse
I had a disaster of sorts yesterday that ended up answering a lot of the questions I had in the OP. I had some concerns, based on experiences a few had posted here, that restoring the backups posted in another topic weren't a sure thing. I got into a situation where I had to start over again from scratch. I wiped my data from TWRP, then restored the UER0 backup. It appeared that I was back to factory status. TWRP even prompted me about whether or not I wanted to maintain a state where I'd be able to take an OTA or compromise it to root. And the updater on the phone worked, too, though I was running the latest and there was no need for it to download anything. But it gave all the right messages. So getting into a state to receive an OTA or return the device seems very doable.
Foolishly, I hadn't done a nandroid or Titanium backup, yet, so I had to do a lot of this the hard way, other than that I copied the contents of my sdcards to my computer. But, yes, now I've done a nandroid and a Titanium backup of the reconfiguration and am well positioned to make a quick recovery should I have to do this again or when the next OTA arrives. I agree that once set up right with backups, that the whole process is less daunting than it would seem on the surface.
i don't get the point.. you just want to say, that you have mafe a restore of a system successfully? great.
DallasCZ said:
i don't get the point.. you just want to say, that you have mafe a restore of a system successfully? great.
Click to expand...
Click to collapse
I started this topic to get feedback from people on whether they'd successfully restored the system with the backups that have been provided here on the forum. Some had expressed that their attempts had failed and they feared that they were bricked. If there are problems inherent in these devices for whatever reason with respect to this, users here should know about them and we should be able to find out whether or not those problems can be remedied by one protocol or another. I was concerned that people with rooted phones, myself included, were potentially facing problems that would prevent us from getting OTA updates, among other things. Nobody came forward here to respond to my questions. That's OK. No one is obligated. But the topic has had 344 views, so some people must be curious. So I wanted to let people know that the UER0 backup does work, at least for me.
Others have had trouble, possibly even when trying to restore from TWRP in what they think are appropriate ways. I'm not clear exactly why, but it would be great to be able to help them, if possible. Nobody wants their new phone to be bricked. Everyone wants to know what works and what doesn't when they're faced with starting over again or getting set to take an OTA. These are new, low priced phones. There are no system images available from the manufacturer. People have generously done all they could here to work around that. We don't have the resources available to us that a Nexus phone does, or some of the others that have larger sales and communities here. Without data to show whether the efforts on XDA are succeeding or not, it's harder to act with confidence. So I'm providing some.
That's the point.
i think if you flash the corresponding system image there should be no problem. Twrp backup is device specific since it allows to backup also persiat partitions with device specific imei. I just unrooted the phone and the chceck for updates worked as it should.
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.
SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)