Related
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
Your Nandroid backup was on that SDcard...I don't suppose you saved it before formatting it?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
nah. The happens sometimes. Could be your nandroid backup got corrupted or you are low on battery power. Two most common causes. I would make sure the nandroid backup is on the sd card. if so, simply try plugging it in to a power supply. Let us know if you get it working.
All right... I did not want to admit it but I believe what you said is probably true, and I either corrupted or simply deleted the nandroid backup during all the flashing and repartitioning. I am not seeing it at all when I mount the SD card. It crossed my mind a little too late that I should have pulled it off the card.
What are my options here? On the one hand, it is working fine for now. I had just got the Hero earlier that day (did an exchange due to dead pixels and network issues), so it was not like I lost anything important. Is there an easy way for me to go all the way back, such as flashing the original ROM to the phone, and essentially starting over, like I just opened the box and turned the phone on? That way I can do it right from the very beginning. I just worry that in all my partitioning things got scrambled, and I am not seeing the repercussions from it yet, other than Google Maps.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
if at first you try and fail.... try try agian
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
lorsoblu said:
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
Click to expand...
Click to collapse
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
johnsongrantr said:
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
Click to expand...
Click to collapse
All right, I am having issues already, from the very beginning.
The RUU ROM .exe will not recognize the HTC Hero. It throws an error 170 at the step where it is trying to pull information from the phone. I think this has something to do with ADB, and the fact the computer did not have the SDK on it. (I originally set up the root with my Mac.)
So, where do I go? I have a Boot Camp partition and another computer both running Windows 7, but my attempts to put the SDK on those computers and then have the phone drivers properly recognized failed on both, and the .exe still cannot complete. Is there something I am missing here, or can I somehow do this on the Mac side? I'll take anything!
Edit: Just cause I can see someone asking, yes, I tried to do this on both of my Windows 7 computers, not the Mac. I recognized that the .exe would not run on OSX pretty quickly.
can you put your phone into fastboot (power+vol down) and get to the point where windows basically sees your phone
what you are looking for is when you type adb devices it shows your hero
fastboot might not work because it's a seperate program but try custom recovery main menu.... enable usb.... or something to that extent
I appologize I don't have my main computer in front of me so I can't tell you EXACTLY where to go
once I do, I'll find which one to hit.... it does work though because I had to do the same thing with my godly preaching of backups :blush:
it's one of the recovery areas though i promise
fastboot will see the hero as the same device as adb will in fastboot
adb will see the hero as recovery device in custom recovery
attempt both of these I'm certain one of these work
if absolutely all else fails.... after you "install" sprint ruu search your computer for rom.zip it should be in your START>RUN>%TEMP% in here somewhere
rename rom.zip it to HERCIMG.ZIP and put it at root of your sd card and boot into hboot and it should automatically find it and press action to flash it
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
lorsoblu said:
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
Click to expand...
Click to collapse
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
johnsongrantr said:
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
Click to expand...
Click to collapse
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
lorsoblu said:
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
Click to expand...
Click to collapse
glad to be of assistance
johnsongrantr said:
glad to be of assistance
Click to expand...
Click to collapse
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
you'd think so.... but from my own experience if you do a backup on a partititon then convert it... it screws with the backup and you can't recover from it.... just in case... do 2 backups.... store the normal fat32 nandroid backup on your workstation (the entire nanddroid folder) and copy it back to sd after you convert it to fat32+ext2 .... you'll see what I'm talking about....
I don't quite understand why it does that... but for me I was only successful in recovering from a partition that I made a backup to not copied to (if that makes any sence)
also if you don't want to experiement yet... just leave it fat32... you can always change it later after you see it working (sorta confidence builder before tinkering)
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
Think about it this way, you do a nandroid backup...it places it on the sdcard.
Then you go and change the format of the sd card (potentially blowing away or corrupting any data on it, including the nandroid backup you just made).
Thus why it's better to do it afterwards (besides, nandroid doesn't back up your sd card, just your phone's OS and such)
solved for me
i had that problem its cuz the back up is brocken get anthoer copy of it if u hav 1 then restore it again it worked for me
Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
chaosthebomb said:
Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
Click to expand...
Click to collapse
From my understanding, as I saw it, I believe that the RUU's are safe, since they're HTC approved images, just that the gold card allows you to revert to a lower version of an HTC rom. Think of it as the RUU's as an official update, but an older official update, and the gold cards make your phone seen as a phone that can accept any update (new or old). So there will not be any harm when you run an official update like this unless your computer crashes midupdate or you pull the battery..or the cable gets unplugged.
Nandroid backups can be produced using the recovery image (i call it a menu since that's all you really see from it), which is covered later in a tutorial if you're reading one. This recovery image is applied after a downgrade (the downgrade gives you the ability to have root access, which is i believe necessary to get the recovery image installed), and thus be able to make these nandroid backups. The nandroid backups then get saved onto the SD card to which you can transfer to your computer for safe keeping. This ensures you can revert to an official rom with previous settings applied in case of an awry custom rom installation. The nandroid backups can also be used for nonofficial roms that you've deemed stable when you tested them, and this can be done as many times as you want.
I'm not sure if I'm entirely right, but I believe I have the gist of it. If anyone can correct me for any errors or can elaborate more, please feel free to share After all, we're all new at one point, hopefully veterans of this will chime in and allow us all to learn!
Also, welcome to the forums! Glad to have you!!
alright, so if I understand correctly, I first need to root my phone to gain root access to perform these nandroid backups?
I'm using this guide" Get started rooting Telus HERO130! (No need for QMAT!)", I'd post a URL but it seems that since I am a new member I'm not allowed to post URL's. I've gotten up to step 6. When I run that RUU file it says its going to erase everything on the phone, so I decided its probably best if I backed up my phone before I try this in the event that I mess everything up horribly.
Is this possible without having root access to use the recovery image with nandroid on it? or am I just having another noob moment?
thanks for the help!
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.
So I just dropped my Note 3 of 2 weeks on the floor (with a case on it) and although the glass isn't cracked, the LCD and digitizer is definitely junk since its all warped in color and mostly black. Thank the gods I have insurance.
I have it Rooted and Safestrap installed and luckily made a backup before I installed Xposed when all was still well. I'm familar with Clockworkmod and flashing that way but new to Safestrap. What is the best way to get my new phone back to how the dropped one was like? Not sure of what files to copy onto my PC and back onto the new phone once I get a new one. Would it make a difference if the backup is from another phone?
My main concern is getting all my username and passwords out of the OI Safe app so it's the main reason for wanting to flash my old backup to the new phone. Other than that I'm not to worried about the rest of the phone since it's fairly new and didn't have it long enough for lots of pics and getting it set up the way I really wanted it.
Thanks
That should work with the following big caveat: if you were on the MJ7 kernel (or earlier), and the new phone is on MJE, restoring the full nandroid backup probably won't work at all and is not adviseable. (Remember that Safestrap "ROM"s do not replace the stock kernel).
If the two phones are from the identical release, then what I would do is the following:
- Root and install SafeStrap as usual.
- Immediately make a Nandroid of the Stock Slot using Safestrap. Get it copied off the phone someplace safe (and named in a way that you can remember it) too.
- Make a second slot in Safestrap and restore the backup from the previous phone to this alternate/second slot.
( Note if you were using a ton of the userdata partition on the old phone you will need to right-size the 2nd slot when you create it. Of course, if you were a data-pig on the old phone and there is no room for a sufficiently-large 2nd slot, then this method of rescue is not available to you. In this case you could restore the original nandroid backup directly to the stock slot - only if you were 100% positive of the same kernel release being used on both phones - but if something goes wrong here you might be making a trip to Odin to re-flash stock and then going through the rooting process all over again ).
- You can use it this way for a little while if you like to see if things are working, or rescue critical data from individual apps, or perhaps make TiBu backups of individual apps (that can be later restored into a different ROM). If things seem to be going swimmingly, you can certainly repeat this process, restoring to the stock slot and then destroying the alternate/second slot.
Note that there are other means of rescue of individual apps which do not require a full restore; this is because the Nandroid backups are (concatenated) "tar" archives, and with sufficient command-line knowledge, you could manually splice into place the appropriate folders from /data/data/*, /data/app/*, and /data/lib/* for individual market apps you wanted to rescue from the old backups. Essentially you are doing the same thing that TiBu does, but manually using adb with the phone in Safestrap recovery mode and the command line.
I'm not going to document this, as it is too tedious to do so - either you already have the working knowledge to do this or you don't. The only tricky part to it is getting the user/group ownership of the files correct. (The easiest way to do this is to install the app from the market, then record the owner/group information it used for the new install of the app, restore the /data/data/* files into the correct place, and then as root "chown" them to the correct user ID... either that or run the "Fix Permissions" script of the recovery).
good luck
I am about 99% sure it was on MJE, I remeber checking it before rooting and following the newest root method available for the newest kernel among other things such as installing Safestrap and Xposed framework.
I unfortunately don't have any experience using Odin or adb, which is something I should know how to do seeing I'm always tinkering with all the phones I get. I'm pretty good with figuring things out when someone points me in the right direction such as you did by searching and following guides here on xda so I thank you for that! I'll try your idea of rescuing the individual app such as TiBu would do using adb. Or even restoring the ROM into a second slot, grabbing the data I need, then get rid of that rom.
And for anyone else reading this...it's never too early to use TiBu or any other backup app for all your important data. Never expected my brand new phone to break after only 2 weeks of owning it but lesson learned.
Thanks a lot for the help, I'll let you know how things go once my new phone arrives.
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!!)