Database Users

[Q] current rooting/2.3 instructions

As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.

There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.

Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.

Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal

Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.

Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck

Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?

Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.

Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?

Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.

Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device

No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.

acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?

Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...

acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?

looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111

Good luck Lars. Let us know that they did and if you had to pay.

PwnMyMoto Infinite Reboot Loop

Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony

minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.

jimmydafish said:
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
Click to expand...
Click to collapse
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!

minitele said:
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
Click to expand...
Click to collapse
you should join the G+ community for much better and more pointed help. The forums get cluttered.
1) download correct 4.2.2 (57-1) FXZ file
2) extract boot, system, recovery from the file
3) fastboot flash each of the partitions to your phone
(fastboot flash boot boot.img)
(fastboot flash recovery recovery.img)
(fastboot flash system system.img)
Doing this will put your phone in a state where it is ready to update.

minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.

jayboyyyy said:
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
Click to expand...
Click to collapse
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?

jimmydafish said:
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
Click to expand...
Click to collapse
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.

jayboyyyy said:
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
Click to expand...
Click to collapse
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!

minitele said:
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
Click to expand...
Click to collapse
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.

jayboyyyy said:
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
Click to expand...
Click to collapse
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!

minitele said:
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
Click to expand...
Click to collapse
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.

jayboyyyy said:
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
Click to expand...
Click to collapse
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!

minitele said:
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
Click to expand...
Click to collapse
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.

tracyde said:
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
Click to expand...
Click to collapse
To all,
The forums and people in our arena never fail, fastboot erase cache worked perfect. I have recovered all my data and now I will definitely continue to performing a full recovery with stock image.
Thank you again all for all of your help, I am glad to see at least this corner in the internet still is alive and kicking!

[Q] Wrong data partition size

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!

LG V20 H910 Root attempt fail, any plan of recourse?

Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.

First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic

MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?

Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again

MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.

reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.

MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.

Slightly better picture without anything cut off.

reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)

MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol

reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing

How do I fix a bootloop?

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!!)