Related
Having come close to hard bricking my device once already, I want to check some things before I attempt custom ROM installation.
I'm on 7.4.9, (rooted and with a factory cable to hand). The instructions for installing TWRP say to install "kfhd7-u-boot-prod-7.2.3" which I understand is the bootloader for OS 7.2.3 which is used because the later OS bootloaders were locked.
Now, if I flash that bootloader, and install TWRP, I can go on to flash a custom ROM. But if I just install TWRP for now, will the device still work with an 7.2.3 bootloader and the other images from 7.4.9 ? (or if I wish to continue with the stock ROM do I have to downgrade all images to 7.2.3?)
Also, are the checksums for the various stock images and files required to install TWRP around anywhere? Understandably, I'd like to verify them before starting.
thanks guys
cecr said:
Having come close to hard bricking my device once already, I want to check some things before I attempt custom ROM installation.
I'm on 7.4.9, (rooted and with a factory cable to hand). The instructions for installing TWRP say to install "kfhd7-u-boot-prod-7.2.3" which I understand is the bootloader for OS 7.2.3 which is used because the later OS bootloaders were locked.
Now, if I flash that bootloader, and install TWRP, I can go on to flash a custom ROM. But if I just install TWRP for now, will the device still work with an 7.2.3 bootloader and the other images from 7.4.9 ? (or if I wish to continue with the stock ROM do I have to downgrade all images to 7.2.3?)
Also, are the checksums for the various stock images and files required to install TWRP around anywhere? Understandably, I'd like to verify them before starting.
thanks guys
Click to expand...
Click to collapse
I would recommend you to keep a ROM and GApps zips on the sdcard,because we don't really know what evil Amazon has put into their latest update. So installing a second bootloader and TWRP might give you a bootloop. So keep a ROM so that you can flash it if you have a bootloop.
thanks for your reply but I'm still in the dark.
what I really need to know is if I flash a bootloader from a different OS version, without TWRP etc, ie a straight swap of bootloaders, will the device still work normally? I don't want to try anything until I know I will be able to get out of trouble and have a functioning device.
I appreciate your advice to put a ROM and GApps on the sdcard, but what ROM? Stock? Do you mean the bin file or 3 images?
Or do you mean CM11 or similar?
Installing CM11 is my goal, but having run into trouble the first time after installing TWRP I want to reduce risks as much as possible. My intention is to install TWRP first, then make a backup of the stock ROM so I can go back to that if needbe, then to install CM11 and give that a go. The only thing stopping me is that the first time I tried, after installing TWRP I couldn't boot up the stock ROM, and I don't know why it happened.
Would I be better off downgrading to 7.4.6/7.4.8 before doing anything else? I assume I'll lose all my apps and settings if I do that?
In any case, I'd like to verify the checksums of any file I download to be on the safe side, but haven't seen a comprehensive list of files/images and checksums. Where can I get that info?
cecr said:
thanks for your reply but I'm still in the dark.
what I really need to know is if I flash a bootloader from a different OS version, without TWRP etc, ie a straight swap of bootloaders, will the device still work normally? I don't want to try anything until I know I will be able to get out of trouble and have a functioning device.
I appreciate your advice to put a ROM and GApps on the sdcard, but what ROM? Stock? Do you mean the bin file or 3 images?
Or do you mean CM11 or similar?
Installing CM11 is my goal, but having run into trouble the first time after installing TWRP I want to reduce risks as much as possible. My intention is to install TWRP first, then make a backup of the stock ROM so I can go back to that if needbe, then to install CM11 and give that a go. The only thing stopping me is that the first time I tried, after installing TWRP I couldn't boot up the stock ROM, and I don't know why it happened.
Would I be better off downgrading to 7.4.6/7.4.8 before doing anything else? I assume I'll lose all my apps and settings if I do that?
In any case, I'd like to verify the checksums of any file I download to be on the safe side, but haven't seen a comprehensive list of files/images and checksums. Where can I get that info?
Click to expand...
Click to collapse
I meant the zip files,not the images or binaries. And a custom ROM is recommended.
As for your concern,I suggest you to make image backups of the system,boot and recovery partitions,not a nandroid backup via TWRP.
If you install a 2nd bootloader+TWRP on 7.4.9,there's a high chance that it'll bootloop. So there's no point in making a nandroid of a system that bootloops. But by flashing the backup images that I told you to make,you'll go completely stock,no risk.
And if you want to automate the process,use FireFlash by stanga72 or my Flasher. There's a good chance of them working since they both worked on 7.4.6 and 7.4.8
With the information to the title and with M coming soon, can I:
1) Update over the air?
2) Update over the air if I install a custom kernel?
Root, Xposed, TWRP, and a custom kernel will each make it so you can't install an OTA.
With that said, I'll have to keep doing fresh installs if I'm doing an ADB-like install with root, right? Or, can those be dirty flashed like you could with a custom recovery (no dirty flash from L to M, obviously)?
Don_Perrignon said:
With that said, I'll have to keep doing fresh installs if I'm doing an ADB-like install with root, right? Or, can those be dirty flashed like you could with a custom recovery (no dirty flash from L to M, obviously)?
Click to expand...
Click to collapse
You basically have two options. Flash the necessary bits through fastboot. Google provides the factory images usually pretty quickly, sometimes before the OTAs even start going out. There are guides on the site on how to use fastboot, as well as guides on how to flash updates without wiping. Basically you just flash the necessary parts (kernel, radio, system, and perhaps bootloader), making sure not to use the -w flag and to not flash the userdata image.
Or wait until someone makes a TWRP flashable one, and use that.
You may not have to wipe if you are stock with root. If you are on a non-Google build, then you probably will need to wipe. There are things that can get screwy after an update though, so never say 100% for certain you won't need to wipe. Generally speaking though, you should be fine if you are on an official Google built ROM. You will likely have to re-root after you flash the update as well, but that should be as easy as flashing a zip in TWRP.
Another thing to consider, if you have removed encryption from your device, flashing the stock kernel will force encryption again if you allow it to boot into Android. So if you want to avoid that you will need to flash a compatible kernel that doesn't force encryption. If you are still encrypted, then it doesn't really matter.
cupfulloflol said:
You basically have two options. Flash the necessary bits through fastboot. Google provides the factory images usually pretty quickly, sometimes before the OTAs even start going out. There are guides on the site on how to use fastboot, as well as guides on how to flash updates without wiping. Basically you just flash the necessary parts (kernel, radio, system, and perhaps bootloader), making sure not to use the -w flag and to not flash the userdata image.
Or wait until someone makes a TWRP flashable one, and use that.
You may not have to wipe if you are stock with root. If you are on a non-Google build, then you probably will need to wipe. There are things that can get screwy after an update though, so never say 100% for certain you won't need to wipe. Generally speaking though, you should be fine if you are on an official Google built ROM. You will likely have to re-root after you flash the update as well, but that should be as easy as flashing a zip in TWRP.
Another thing to consider, if you have removed encryption from your device, flashing the stock kernel will force encryption again if you allow it to boot into Android. So if you want to avoid that you will need to flash a compatible kernel that doesn't force encryption. If you are still encrypted, then it doesn't really matter.
Click to expand...
Click to collapse
Thank you!
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Charlie207 said:
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Click to expand...
Click to collapse
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Charlie207 said:
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Click to expand...
Click to collapse
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Charlie207 said:
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Click to expand...
Click to collapse
Yes.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Yes.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK.
Successfully upgraded TWRP, and the install of LOS seemed to go smoothly. Now it's back to the waiting game with the install/boot animation. I'll check back in a bit if nothing good has happened.
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Charlie207 said:
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Click to expand...
Click to collapse
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Charlie207 said:
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Click to expand...
Click to collapse
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
Click to expand...
Click to collapse
I haven't tried flashing a pure stock MM ROM yet, but will surely give that a try. Do you have a link to a recommended MM ROM?
And, I assume I'd be attempting the install just like I did previously.... e.g. wipe everything, DO NOT reboot, drag .zip from laptop to phone via USB cable, install, (then profit?).
Not that it should matter from a hardware point of view, but I'm using a 2011 MacBook Pro 15" running the latest beta version of OS 10.13.whatever. It sends files to the phone via the Android File Transfer app. I think that's the only way to physically send files from a Mac to Android.
Looking back at some past post of mine, I had a similar issue with cRDroid, which installed it's own recovery software, and wouldn't work with TWRP. I did end up (through serious trial and error headbanging) succeeding in using ADB commands via Terminal to get the phone wiped clean and installed TWRP. After that I was able to load custom ROMs via TWRP and had no problems swapping between different ROMs until just the other day.
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Charlie207 said:
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Well **** me running....
That worked. I followed the identical wipe+install procedure for the "stock" MM 6.0.1 ROM as I had for three other 7.x ROMs, and it installed with no issues this time. I'm staring at the Welcome screen, and pretty frustrated that this was the only way to get the phone working again. I'll do a basic setup, and then see if I can flash a 7.x ROM
Thanks for your help in solving this riddle up to now. I'll see what happens....
EDIT: Now that I think of it, the only thing I did different was that, after downloading the ROM to my laptop, I edited the file name from that long name to MM6.0.1.zip so I could simply recognize it faster when clicking between windows and stuff. Other than that I followed the same installation process as noted before.
I'm going to edit/shorten the filename of the LOS ROM and see if removing unneeded characters does anything.
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
The Brazilian MM ROM was junk for my purposes, but the other MM ROM worked.. Phone is setting up now. WiFi and LTE work on it, so I guess I'll be stuck with 6.x for a while until I feel like messing around with a 7.x ROM.
Charlie207 said:
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
Click to expand...
Click to collapse
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Yeah... I realized my mistake, and flashed the other MM ROM. That one works normally.
I'm stumped why all of a sudden 7.x ROMs refuse to install on my phone. I had prevously installed crDroid, AOKP, and RR 7.x ROMs just fine via TWRP.
ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?...
Click to expand...
Click to collapse
I'm not sure if all TWRP versions for different devices are the same, but with my Pixel C (TWRP 3.2.1) there is an "adb sideload" option in recovery to install zip files via adb from a computer.
I think the command is: adb sideload filenamegoeshere.zip
Sorry for reviving this thread, but I have exact same issue. Stock Lollipop and MM roms work, but any custom rom just hangs on boot animation forever did you manage to sort it out? @Charlie207
Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.
<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.
Can't we just flash Magisk on TWRP?
yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.
greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.
e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help