Related
So after spending a whole afternoon flashing 4.3 onto the N7 via fastboot and finally getting root to work, I connect my N7 to the PC and get the shock of my life to see my internal storage has shrunk to 6GB...it currently says I only have 5GB free out of 6GB...is there any way to fix this ? My N7 is the 3G, 32GB model running 4.3 with stock kernel, twrp and rooted.
Solution : http://forum.xda-developers.com/showthread.php?t=2033692
Just edit the steps to adapt to our Nexus 7 PM me if you need help with that
Anyone ?
We've had that with the first custom roms. The only way to fix that, that I know know of, is to flash back to older stock rom, verify the storage is right, and try again.
I would download the 4.3 rom from another source and/or verify the MD5 package.
Just for laughs, perhaps you could try to reflash the kernel (which is what I think gives the reading).
That or you are the only person with a 6gb N7.
Well, I talked to two other people and they said this is bound to happen with flash happy morons like me who go straight for the IMGs...will try re-doing from step 1, or else I'll go back to 4.2.2...oh and 1 more piece of info...as I was done with flashing 4.3, my sd was formatted as well...
This has also happened to me on more then one occasion when flashing back to stock would show only 6/27.5GB available. Rebooting into recovery and reformatting fixes it.
Username invalid said:
This has also happened to me on more then one occasion when flashing back to stock would show only 6/27.5GB available. Rebooting into recovery and reformatting fixes it.
Click to expand...
Click to collapse
i got that once...formatted all in Philz recovery...DONE..no problem..
Hey guys!
I'm coming to you at the end of a loooong way after trying to upgrade to KitKat.
I started the upgrade to 4.4, on the go, and quite confident. What a mistake ...
The upgrade failed, and my device got bricked. Fortunately, I had the recovery partition. Unfortunately, I destroyed the recovery partition by mistake...
I finally succeed to fix the things, but I have no idea how exactly I did it (I just tried the things as they were coming, messing around with partitions and switching from tutorial to tutorial),
Anyway, I made it.
This was 2 months ago ... then time passed, and today I got a message "no space left on device". Hm, weird. I check and oh damn, my SD card only had 5GB on it ...!!
It looks like I've loaded the *GB version partition scheme at some point ... or just wrongly formatted the partitions ... or I don't know.
I've tried to check using fdisk, but it doesn't help me much.
I also tried some tools like "Partition table" but I still can't find the missing 10GB. it seems like they're just unpartitioned, but not even recognised as it ...
Did anyone ever had this issue? Any process to fix it? Or at least any way to rollback to the original partition scheme.
Many thanks!
Best,
Stop messing with all this crap.
Get the factory images.
Put the phone into fastboot mode and connect to the computer
Your computer needs to have a working fastboot set up. If not fix it.
Run the flash all script include in the factory images. It's the. Bat on Windows and. Sh on osx / Linux.
It fully wipes the phone. Everything gets wiped and flashes the stock images.
If you have anything on the internal storage you want to keep you can remove the - w line from that script and it won't wipe it.
When done you a stock phone with a unlocked bootloader. From there do what you want.. Either run stock. Flash a custom recovery and root or rom etc.
Or just use stock recovery and factory reset. It fix the storage size problem for me. You'll lose everything on your internal though, so make a backup of your pic/music/anything you think important in your phone.
**** it seems like the post subscription didn't work, I've just seen your replies.
Thanks guys, it seems like the right way to do it.
I'll try to do it tonight and let you know the progress.
Cheers!
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
TheOkMan said:
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
Click to expand...
Click to collapse
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
clsA said:
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
TheOkMan said:
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
Click to expand...
Click to collapse
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
clsA said:
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
Click to expand...
Click to collapse
Thanks again, clsA. Looks like this could be it. Will try it soon. For now I have flashed [ROM][X72X][7.1.X][OFFICIAL] LineageOS 14.1 (which is now 8.1 somehow...) and it works without any issues so far.
Any insights on why I'm getting *Encryption unsuccessful* error after restoring my original system image via TWRP (first recovery was fluent, error appeared following my later attempts for recovery)?
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!!)