Related
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
Hi guys,
I have a sunmi v2 android PDA, and i want to remove blocked OS.
I can't find bootloader, or i dont know how to enter on it, also i want to install a recovery mode to flash a new ROM.
Someone can help me please with this problem?
Thank You.
Hi, I have the same problem. Did you find a way to do it?
Can you tell me please?
Thank you
I have V.1.. Firstly, are you guys able to allow installation of apps from "Unknown Sources"?
Just wondering if you ever managed to load android onto the V2 and remove the Sunmi OS? I have managed to enable dev mode and allow untrusted sources but on installing google play services and store all I get is crash reports and have to factory reset.
Thanks
J
Can you tell me what you did to install apps from untrusted sources? and what progress have you managed to make?
wesleybr90 said:
Can you tell me what you did to install apps from untrusted sources? and what progress have you managed to make?
Click to expand...
Click to collapse
To enable untrusted sources I had dev mode on but under security > device admin > unknown sources. I don't know if you need to enable dev mode to turn that on but if so go to about > build number > tap until it enables. I'm not really a software guy and was hoping someone on the internet would have a solution to rooting the device and maybe ADB it, I did ask a software engineer friend of mine and he did some research on them, these things talk to Sunmi's servers on boot with the current FW so they are heavily locked down, so progress wise for me is it's been in a drawer since January and I'm hoping someone will have a way to root the thing :S
So I have no idea about Android things but I bought secondhand Sunmi V2 that is locked on Glovo aplication.
For the last week I managed to do some research about that:
1. The thing runs custom OS with some kind of recovery-from-boot.p thing that prevents most of modifications, cause after reboot it reverts some system things.
2. I tried to use SP flash tool to do full backup, made mine scatter file and thing I have no idea about
3. Managed to download TWRP recovery to device recovery partition with use of SP flash tool, this did not do anything and the thing booted to Phoenix recovery as normal....
4. With the help of WWR 2.51 I managed to install applications on it...
5. Installed Kingroot, didnt do anything, installed, APKPure, works nice, Magisk, dont know how to root...
6. Tried installing google play, it says it is installed, cant uninstall it nor open it...
7. Can't and don't know how to enter fastboot...
8. I am afraid to flash complete ROM from some other same chipset device...
9. After powering up, Sunmi connects to its own server and does some kind of evil magic to preinstall software and settings.
10. I contacted Sunmi, they kinda don't want to help, cause I will resell device after unblocking it.
11. Fount "that guy" from youtube that does unlocking it, on the minus side he wants money for unlock... and from his videos he flashes complete EMMC_USER bin to device to unlock google play.
Do anyone know which steps can I take further to try to unlock it by myself?
I have some spare time at work to do this kind of playing around.
Update:
I managed to extract system.img from device and I am able to browse files on it, the plan is to see can i change some files and setting in it and reflash it back to device. This is all overwhelming to me as I have no experience in android development.
Noob Sailbot said:
So I have no idea about Android things but I bought secondhand Sunmi V2 that is locked on Glovo aplication.
For the last week I managed to do some research about that:
1. The thing runs custom OS with some kind of recovery-from-boot.p thing that prevents most of modifications, cause after reboot it reverts some system things.
2. I tried to use SP flash tool to do full backup, made mine scatter file and thing I have no idea about
3. Managed to download TWRP recovery to device recovery partition with use of SP flash tool, this did not do anything and the thing booted to Phoenix recovery as normal....
4. With the help of WWR 2.51 I managed to install applications on it...
5. Installed Kingroot, didnt do anything, installed, APKPure, works nice, Magisk, dont know how to root...
6. Tried installing google play, it says it is installed, cant uninstall it nor open it...
7. Can't and don't know how to enter fastboot...
8. I am afraid to flash complete ROM from some other same chipset device...
9. After powering up, Sunmi connects to its own server and does some kind of evil magic to preinstall software and settings.
10. I contacted Sunmi, they kinda don't want to help, cause I will resell device after unblocking it.
11. Fount "that guy" from youtube that does unlocking it, on the minus side he wants money for unlock... and from his videos he flashes complete EMMC_USER bin to device to unlock google play.
Do anyone know which steps can I take further to try to unlock it by myself?
I have some spare time at work to do this kind of playing around.
Update:
I managed to extract system.img from device and I am able to browse files on it, the plan is to see can i change some files and setting in it and reflash it back to device. This is all overwhelming to me as I have no experience in android development.
Click to expand...
Click to collapse
Thank you for the update, Im following this thread to see how this goes. Im trying to unlock my Sunmi V1 too
I managed to brick it, stuck at boot looping... Somehow I redownload boot and system from my backup with SP flash tool and got it working back again...
So I tried using ASSAYED Kitchen and remove some Bloatware, rebuild it, and upload it back to device, used two files: System.img and boot.img... This bricked my device.
What am I doing wrong? This must surely be my error. Do I need to do something to recovery partition?
UPDATE:
Managed to install custom recovery TWRP, made it myself using Carliv Image Kitchen
UPDATE 2:
Even thou TWRP seems working, It does not mount any partitions: /data, /system... Invalid argument...
Does anyone know how to fix it easy way? because I cant find too similar custom TWRP to Sunmi...
Any custom system.img that I flash with SP tool does not want to boot, never, and even if I only open ASSAYED Kitchen, do nothing and repack it. Is the only way to install it with TWRP?
BIG UPDATE:
I have done 99% of the job!
I could write full from zero to hero tutorial for this, but basically I used TWRP to recover /data/system/users/0/package-restrictions.xml and edit it as I pleased and unlock google play.
Noob Sailbot said:
BIG UPDATE:
I have done 99% of the job!
I could write full from zero to hero tutorial for this, but basically I used TWRP to recover /data/system/users/0/package-restrictions.xml and edit it as I pleased and unlock google play.
Click to expand...
Click to collapse
I am also looking forward to the results you have done
So amazing!!
I am slowly loosing interest in this. Whatever I do it is just endless loop...
When I modify package-restrictions.xml and settings_secure.xml files I got GooglePlay and Maps and stuff, but first time you connect the device to internet, SunmiBaseService overwrites them with options used for this DeviceID.
I renamed this SunmiBaseService to something else, got this working, but then since the whole thing runs on this sunmi backbone you can't install any apk's. I can normally install apks using USB and enabled BaseService.
It would be best if I could have just normal Android on this thing since it is unusable if you block BaseService, and if you would do any system upgrade on some point in time it would overwrite and install this service by itself. Like I said, it is endless loop. Even after contacting sunmi my region cant't have this for private use.
I can provide all files used in this process, my scatter files, my TWRP recovery and else...
The question is is it possible to port clean Android to this device, like we install new windows on a PC?
Hello guys, any news for Sunmi? I got one, but i wan't to remove the OS, or enable Play on it.
Velcis Ribeiro said:
Hello guys, any news for Sunmi? I got one, but i wan't to remove the OS, or enable Play on it.
Click to expand...
Click to collapse
No, I tried everything I know. Only thing that I did not do is replacing sunmibase service with some kind of android base service or paying some youtube guy 20$ for unlocking, but I doubt it would work correctly. Couse after you, in some point in time, update software or something I highly doubt it would work after that.
{Mod edit: Quoted post has been deleted}
I am going to upload files that I have, but I need few days to do so.
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Noob Sailbot said:
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Click to expand...
Click to collapse
Can you share the files again please, the links don't work anymore. Thank you
My buddy has toast loaded on an old device and was looking to replace the os so his kid can use the tablet. Sunmi t2
Noob Sailbot said:
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Click to expand...
Click to collapse
I am after these files also if you still have them
Would it be possible for you to re-upload the files?
This might be completely unnecessary (mods feel free to remove if it is), but I see a LOT of misinformation regarding GSI ROMs and the G8. So. Here's a guide/FAQ for those wondering if/what is possible:
***I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, LOSE YOUR DATA, OR OTHERWISE DAMAGE YOUR DEVICE. IF YOU CHOOSE TO FOLLOW THIS GUIDE, THE FATE OF YOUR DEVICE IS IN YOUR HANDS, NOT MINE, NOT YOUR MOTHER'S, NOT ANYONE OTHER THAN YOUR OWN***
Prerequisites (yes, these are all NECESSARY. If you don't know how to unlock your bootloader or use fastboot, there are other guides here. Go find one.)
Unlocked bootloader (and the V50 engineering abl files as well as stock, plenty of guides here with download links)
QFIL/QPST
Basic Fastboot, ADB knowledge
BACKUP. I mean ALL YOUR DATA kinda backup. This WILL wipe your phone, do NOT come crying to me if you lose the last picture of your favorite sock. Not my fault.
GSI for Treble device (ab)
GApps (optional, but recommended)
Instructions to Flash via Fastboot
WIPE YOUR PHONE
Yeah, completely factory reset that sucker. Doesn't matter if it's through recovery, settings, or adb, just bite the bullet and restore factory settings. You can technicially flash without doing this first, but you'll still have to wipe it before any flashed ROM will run. Sorry.
Boot to EDL (NOT download, your screen should be black, dev manager should show QD Loader 9008 COMx)
Use QFIL to flash engineering abl file to both a and b slots - yes, all this work just for fastboot.
Reboot to fastboot!
I just unplug my phone, use power + vol- to shut phone off and then reconnect while holding vol-, but you do you.
In case you don't remember, your touch screen WILL NOT WORK during this time, even if you fully boot to system! Completely fine and normal, means you're on the right track!
Fastboot Devices should yield "LG850UM", also good!
Open cmd prompt from platform_tools, copy path to desired GSI while you're in there
Run these commands line-by-line:
fastboot format system
fastboot flash system *Path_To_GSI.img*
This is where I usually repeat the 2 commands and attempt reboot while I still have fastboot, whether or not it changes anything I have no idea, but it's never given me problems so why fix it if it ain't broke?
fastboot flash abl_a abl_STOCK.bin
fastboot flash abl_b abl_STOCK.bin
fastboot reboot
Ta-Da! Your shiny new ROM should be up and running. Use TWRP or any kernel manager (I like SmartPak) to flash TWRP, GApps, blah blah blah.
FAQ/Troubleshooting
Touchscreen still not working? Go back to EDL and load the stock abl bin files through QFIL, then reboot as normal.
You will likely be asked to input a password upon successful reboot, just enter your PIN/password, whatever you used to unlock your phone pre-flash
The cool things like QuadDAC and LG-specific tweaks will probably not work. Weigh your options before flashing.
Magisk comes pre-installed with most GSI's, just follow the prompts and you'll be just fine.
Don't want GApps? Just sideload desired apk's via ADB, or use the browser to search for them.
Can't I just use TWRP and make this whole process a lot simpler? Yep. But some of us don't have working TWRP or prefer using fastboot commands. This is for those people, don't hate.
Which ROMs work?? Not sure, haven't tried them all. Currently running HavocOS found in Treble GSI forum on here.
Help! I broke my phone! No, you probably didn't. It's advisable that you know how to emergency restore via LGUP prior to starting this process though. Please be specific as to what part of this "broke" your phone and why exactly your phone is "broken" if you're going to ask for help- "bricked device" has never helped anyone.
Rebooting is your best friend in this process, especially during the first boot. If anything starts to hang up or act funny, just give the phone a minute to catch its breath and, worst case, turn it off and back on again
As previously stated, this is probably pointless, but given all I see on the G8 forum is "no custom ROM" or "why bother trying to *insert idea here*", I figured it might help some folks out. I'm sure I left a few things out, feel free to correct or provide input as necessary.
Works on LM-G820QM5?, I have bootloader unlocked
Elihu_GmG said:
Works on LM-G820QM5?, I have bootloader unlocked
Click to expand...
Click to collapse
Yep, it's basically the unlocking/root process only you're formatting/flashing the "system" partition instead of "boot_a/b"
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
AsItLies said:
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
Click to expand...
Click to collapse
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
SirOlive said:
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
Click to expand...
Click to collapse
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
AsItLies said:
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
Click to expand...
Click to collapse
Sorry for being short, but a simple Google search would back up everything I've written. I wouldn't have written this up if it didn't work, or if it was just a theory... I wouldn't have said that my Verizon G8 is running Havoc if it didn't work. I was able to flash with zero problems. With the Treble Project, Google has mandated that Android devices boxed with 11+ (possibly 10?) be capable of not only recognizing, but running GSIs as to assist developers in testing apps and builds in varying versions of Android as quickly, easily, and simply as possible. This means that not only can one download and flash Android releases downloaded directly from Google, but devs can use the source code to create versions of their ROMs that will apply to a wide array of models that would never have seen development otherwise. Because these are "generic" images and are based upon system architecture type alone- not a particular make/model- there are sometimes things overlooked. For instance, in our case, the audio processing and LG's camera software are not present. These are decently made up for by the presence of flashable mods, though, and the phone remains fully functional, Google Play Certified (if desired), and as reliable as the ROM you choose to flash.
Basically, Google>LG. LG wants to use the Android platform, they must abide by Google's rules. They need not go into great detail, nor allow their devices to be changed to something fundamentally non-LG, nor divulge any potentially propitiatory subject matter (once again, "generic"), but they must allow the device to be open to a certain level of customization as designated by Google.
Is it ideal? Not if you're lucky enough to have ROMs tailored for your specific phone. But for those left behind- like the G8- it's a fantastic workaround that does, in fact, work. As I'm sure you're still skeptical, I will add screenshots tomorrow to prove the validity of this seemingly ludicrous claim. In the meantime, please do some research on the topic- or better yet, give it a shot- there's gotta be a guide around here somewhere.
It works
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
hooutoo said:
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
Click to expand...
Click to collapse
Where did you get V50 engineering abl files as well as stock?, I just want to make sure to get the correct files
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
hooutoo said:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
Click to expand...
Click to collapse
Ok,ok
Hello, I followed your instructions as written but when I reboot my phone I am stuck at a boot logo cycle, but my comment doesnt have to do with that, I want to ask if maybe you know what could've gone wrong.
I also own a g8 from verizon, I do have bootloader unlock, and tried to install Havoc OS, I wanted to mention this in case it is useful
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
hooutoo said:
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
Click to expand...
Click to collapse
Yeah, I know, like I said in my previous comment my phone got stuck in a boot loop, I fix it just by loading system_a partition in qfil, so I am gonna give it another shot and see if it works, already backed up every partition just in case anything goes wrong
If you're goona play around, this is secondary bs. My real phone is a FLIP3 and I'm not allowed to play unlesss to make/awnswer call.
Does somebody tried tp flash GSI with LineAge (A11) or Arrow(A12) vendor to g8?
I`m interesting about dt2w .. I flashed GSI`s to my G820UM on the past (A10 stock vendor) and it have no dt2w.. ((
i ended zeroing my imei from sprint G8 but thats okay i dont care for it much but what i do care is getting some LOS 17.1 on the sprint G8
where do we have any links to these so called GSI images?
blaze2051 said:
where do we have any links to these so called GSI images?
Click to expand...
Click to collapse
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
From what I remember when I tested multiple Android 11 GSIs such as Pixel Experience, I couldn't get vibration to work on my G8.
Disclaimer: By attempting this I accept no responsibility for any consequences or repercussions or perceived consequences or repercussions of using this guide or any of the files in it. I'm simply a n00b trying to make things easier for the next guy because this was quite a process and my phone was "bricked" for several days before i found the solution so this is more a "how i did it, maybe it will work for you" guide then most of these guides by guys with a lot more experience than me. If you run into something crazy I didn't run into, ill likely not be able to help you.
With that being said after 3-4 days of struggling, this is what was working TODAY, 6-3-2022
Now that the disclaimer is out of the way, here's a further warning... THIS WILL ONLY WORK FOR THE NORD N100 Metropcs Variant (BE2015) BE82CF. You WILL have issues if you try this on another N100! Furthermore, this will leave you stuck on OOS 10.5.8 (android 10) rooted with no way (that I could find) to update further. If that's not ok with you, well then this guide isn't for you.
PLEASE READ THE WHOLE GUIDE BEFORE BEGINNING TO AVOID MAKING MISTAKES OR MISSING STEPS/NOTES!
So normally we would unlock the bootloader and then install magisk and take our boot.img from the firmware we are on and patch it and flash the patched boot img and then we would be done.... HOWEVER there's not a lot of newer firmware floating around for this phones variant.... so first, a step backwards before we continue.
0) Before you start make sure you have everything you want to keep backed up one way or another because this will wipe your phone several times over and you will lose everything that you don't backup!
1) Flashing OOS 10.5.8 using MSMDownloadtool.exe so that our boot.img will match our current version
So the newest firmware I could find that I could VERIFY belonged to this exact variant was 10.5.8 (android 10). However i was on the newest firmware which was android 11. The boot.img wouldn't match so this could likely brick my device
So first i used the firmware i found to go back to an older firmware that i got from here [OPN100][OOS METRO BE82CF] Unbrick tool to restore your device to OxygenOS
and in case a newer version is posted in the future here's the direct link from this post OOS 10.5.8
I used the included MSMDownloadTool but had trouble connecting until i used my motherboard USB port AND uninstalled the qualcomm driver that was already installed and installed the one i got from this post: Qualcomm HS-USB QDLoader 9008 Drivers: Download & Install
After i finally connected it took me just about 4 minutes to flash the new firmware. Once again you have a fresh clean install. Setup everything really quickly in OFFLINE mode. This is for 2 reasons, one is speed but the other is to stop the auto update of the system firmware! Before enabling internet. enable developer mode and uncheck Automatic System Updates
NOTE: For some people it will make more sense to do this next part first so they aren't stuck on an old firmware for a week while waiting for an unlock token, but regardless if you do these steps first or not they still need to be done here as well since flashing firmware with MSMDownloadTool relocks the bootloader if it was unlocked already.
This is already going to be long so for sake of shortening it im putting these steps here instead
2) Switch the OEM UNLOCK toggle in dev options
We have to flip the OEM Unlocking option in developer options. But it's greyed out! I myself did this the time consuming way but theres two methods, ONLY CHOOSE ONE
2.1a) Its greyed out because you're carried locked. You can get this ungreyed by waiting 6 months and using the stock carrier unlock app named "unlock." You can do this quite easily using this app and following the prompts.
2.1b) There's a way to skip the carrier unlock, after all we dont want to switch carriers just unlock the bootloader. This was found the best way: by accident. Someone made a one plus debloat script and the people that were running it found out that the"unlock bootloader" came unlocked afterwards. It's a neat little script, i ended up running it myself. I found somewhere in my searches the exact command in the script that did it but i can't remember exactly and can't find the post that identified the one command.
I BELIEVE it's one of these three:
com.qualcomm.qti.remoteSimlockAuth
com.qualcomm.qti.uim
com.qualcomm.qti.uimGbaApp
The most obvious one seems to be the remoteSimlockAuth. TBH i only added that because it seemed so obvious. I believe it's actually one of the other two, but i'm just not sure. You could try removing those three only and see if it works. Worse come to worst, run the whole script from this post: One Plus Pure Debloat
NOTE: If you are going to run the whole debloat script make sure to install a keyboard FIRST or you will be stuck without one! Or remove com.google.android.inputmethod.latin from the list.
2.2) No matter which way you completed it (using step 2.1a or 2.1b), the OEM Unlocking toggle in developer option will be usable now. Enable it. While you're in developer options, make sure usb debugging is on because you will need it for the next part. Make sure to plug your phone in and when the rsa key fingerprint pops up, choose "always allow from this computer"
3) Unlocking the bootloader
This part is pretty standard with no serious deviations. I followed this guide from step number 3 on: How to unlock bootloader for OnePlus smart Phone
When you get to step 5 they don't mention it but it takes about a week to get the unlock token.
The only real thing i changed for all of this pretty straightforward guide was when they say the command is fastboot flash cust-unlock <unlock_token.bin> ... Well the bin is called unlock_code.bin so i ended up using fastboot flash cust-unlock unlock_code.bin instead.
Once you finish and your phone restarts, set up the phone quickly in offline mode just to get through it again. Before enabling internet. enable developer mode and uncheck Automatic System Updates. While you're in developer options, make sure usb debugging is on because you will need it further on. Make sure to plug your phone in and when the rsa key fingerprint pops up, choose "always allow from this computer"
4) Decrypt the .OPS firmware file from step 1 to get the boot.img
The next part seemed very complicated but really wasn't. We need to decrypt the .OPS firmware file to get the boot img out of it. I used Oppo Decrypt
There were some changes I needed to make in this section which ended up working, i don't know if the issue was a newer python version or what but if following the readme from the github doesn't work as-is for you, try this instead.
4.1) install python for windows from the official website Python Official Site
4.2) Navigate to the python install directory. C:\Users\%username%\AppData\Local\Programs\Python\PythonXXX\ is the default directory, with %username% being your account username, and XXX being the current python version without the .'s For me this was C:\Users\Kaladin\AppData\Local\Programs\Python\Python310\
Now launch a command prompt from this location.
4.3) Run the command pip3 install -r requirements.txt and if it complains about anything not being updated run that command next to update everything.
4.4) Move a copy of bengal_14_O.04_201221.ops from step 1 into the python310 folder and then run the command opscrypto.py decrypt bengal_14_O.04_201221.ops and wait for it to finish. You can now close the CMD window. You will find the boot.img we need in the "extract" folder in the same directory. Put your phone in file transfer/MTP and move just the boot.img over to your phone or however you want to get this done, do it.
5) Install magisk and root by patching the boot.img and then flashing the patched boot.img
Now we just follow these steps starting at step 2.3 from this guide How to Root OnePlus Nord N100 using Magisk [No TWRP Required]
The only thing that seemed wrong here is in step 3.4 they say to run the command fastboot devices and not only is this not needed but wont work here. If you want to make sure you're connected, use adb devices here instead or reboot to fastboot first before running fastboot devices (so after step 3.5 before step 3.6 instead of step 3.4).
Then, in step 3.6 we have an A/B partition systems, so we need to use the first command only, fastboot flash boot boot.img ... ignore the second part about non A/B Partition systems. Flashing the wrong command here could probably brick your device.
Follow the rest of the guide.
One additional thing i needed to do to obtain root after rebooting was to again open Magisk Manager and click install and choose "Direct Install (recommended)" this time (instead of select file and patch it). When the process is done, reboot your phone and then once it restarts you will be able to download a root checker app off the play store and verify root.
Yay! It was a long journey, but we are done!
NOTE: Magisk has a way to install OTA updates while keeping root by half uninstalling Magisk and reverting to the stock boot.img before allowing the OTA update, then you would reinstall Magisks patched boot.img to the other partition before restarting but i wasn't able to get this to work myself. I will give you the tutorial here though just in case but for me it auto restarted as soon as the OTA update finished installing and updated me to the newest firmware which removed my root and made it so that i had to start this whole process all over again from step 1 (minus the wait time for the carrier unlock and the unlock token of course). So up to you if you want to try this out.
For now i'm just happy to be rooted on a stock rom even if it is a little old. Hope this helps someone out =)
SPECIAL THANKS FOR ALL THE PEOPLE WHO WROTE THE GUIDES, TUTORIALS, AND PROGRAMS USED THAT I LINKED TO! I WOULD HAVE BEEN LOST WITHOUT THESE AND ALSO WITHOUT GOOGLE TO FIND THEM!
any chance you could upload the patched and unpatched boot.img?
dabman710 said:
any chance you could upload the patched and unpatched boot.img?
Click to expand...
Click to collapse
Sure, but i don't know enough to know if you should use the patched one or not. I think you should use magisk and patch yourself.... But ill include it anyways Boot.img from bengalm_14_O.04_201221 it may be totally safe im just not sure. but the boot.img is unaltered.
AesopRock127 said:
Sure, but i don't know enough to know if you should use the patched one or not. I think you should use magisk and patch yourself.... But ill include it anyways Boot.img from bengalm_14_O.04_201221 it may be totally safe im just not sure. but the boot.img is unaltered.
Click to expand...
Click to collapse
i didnt try using your patched boot.img, but the unpatched one worked perfect for me after patching myself. saves everyone a few steps too by having that available. thank you
So even though i debloated all one plus things i could find and kept autoupdate automatically in dev settings turned off , my phone still pushed an update and i lost root.... Unless someone knows how to fix this, CFW may be our only hope of keeping root, at least for this variant
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Loustsoul said:
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Click to expand...
Click to collapse
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
jeffsga88 said:
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
Click to expand...
Click to collapse
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Grin59 said:
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Click to expand...
Click to collapse
For root? Just use the global patched boot.img and boot into OS, go to Magisk and perform a direct install. No issues at all with root on T-Mobile firmware. I've been rooted ever since they allowed us to unlock the bootloader and get our tokens.
Removed
EtherealRemnant said:
Really all you should need to do to convert to global is unlock the bootloader, take the NA downgrade package, and flash it with Fastboot Enhance. Make sure you go to the partitions screen and search for cow and delete every one of them so there is room for the image and if you get any other errors, don't continue. Once the flash is successful (the bar will seem to stop, just let it sit for a bit and it will continue), choose English on the phone screen and go through the menus to find where to wipe the phone and then reboot.
There is a risk of a brick if something goes wrong so without the MSM Tool, this is at your own risk, but Fastboot Enhance doesn't tend to brick phones like fastboot scripts do as long as you stop if it gives you an error.
Here is the NA downgrade package.
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
Click to expand...
Click to collapse
Yeah, technically should work. Unfortunately the risk is too high without having the MSM in case something goes wrong. Especially if it's your daily phone, like it is mine. But if anyone wants to give it a go, let us know how it goes, just know it could brick your phone and there's no current way to restore it without sending it to OnePlus or paying a scam artist to restore it.
Removed
Can I get my boot.img off of my phone or do I need to download it? Also the 10 pro is not listed in the software on the oneplus website. Where can I get the official stuff I need? Im happy with just root for now, I just want to use Magisk and do the updates......
EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
Im willing to try but I am too unsure of what to use as far as the correct boot and rom.... You seem to have way more knowledge than I and I would greatly appreciate your help.
Removed
EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
The only downside I could see then it's that we don't even have the full T-Mobile firmware to flash back to in case it starts to flash global but then failed. I'm tempted to take the plunge and try (would be nice to be on Android 13 now instead of waiting months for T-Mobile to get the update) but just don't want to end up bricking with no way to recover. Also, in the past I know people were using the MSM to convert to global or EU, does using the global downgrade script alone work for converting? I might take a look at your guide for the 9 series and try with the 10 pro. I guess I can always send it in if it does brick, still have my 9 pro I can use in case something goes wrong.
Removed
EtherealRemnant said:
It is a legitimate concern that you can't get back to T-Mobile firmware if something goes wrong and that is definitely something to think about.
I can tell you that the downgrade package is as close as you can get to the MSM Tool in terms of a restore without an MSM. I have used the downgrade packages to convert between regions on my 9 and never had any issues except for when I used the India MSM Tool for the 9 Pro on my 9 and kept losing touchscreen in OOS12. That was only fixed with an MSM Tool modded to get me back on regular global 9 firmware.
Click to expand...
Click to collapse
Well I'm taking the plunge so I'll update after if it's successful or not. Was able to delete all the COW partitions and start the flash no issue, so just have to wait for it to finish.
Removed
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
tman23 said:
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
Click to expand...
Click to collapse
Yeah, don't think it's going to work. Can't fully get out of the setup screen (or if you do it just stays at black screen only able to pull down quick settings and not enter options or anything). Wiped after flashing and won't work. I guess I could try using Fastboot Enhance to flash some of the global update zips and see if that does anything.
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. EDIT: I was wrong. There is no true full T-Mobile NE2217 ZiP available.. really sad.
But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success. That being said, as said above, root is very easily achievable by just BOOTing a patched global boot.img if you just want to root and maintain your original software.
Prant said:
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success.
Click to expand...
Click to collapse
I haven't really heard of anyone converting the 10 due to lack of MSM. Also, haven't seen any full zips for the 2217 (T-Mobile version), so if you have a link to it that would be very useful. Also on 2217, you can't flash from in system as it's disabled in firmware (unless the separate apk works).
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
EDIT: As mentioned later in the thread even these are not full images for NE2217.
Prant said:
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
Click to expand...
Click to collapse
Thank you, not sure how I missed those. If my attempt to restore the device doesn't work I'll try restoring it by flashing T-Mobile firmware again.