Develop Bugs

New carrier unlocked GSM M8

This is the first carrier unlocked phone I've purchased. It's brand new and I bought it because I'm an M8 fanboy and my first M8 is dying. I'm on AT&T. I just got the phone and installed my SIM and setup my google accounts and all that stuff. I want to update Android but when I go to setting/about/software updates all it says is "checking". It's been checking for over an hour. Did I do something wrong? Is there a way to get the latest OTA Android for an AT&T M8?
My plan is to get to MM then unlock the bootloader and flash TWRP so I can start flashing custom ROM's. I never did anything to my original M8 but have done rooting etc on my old HTC Vivid and both my ASUS tablets.
Thanks in advance for your help.

Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.

ckpv5 said:
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
Click to expand...
Click to collapse
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.

theandies said:
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot getvar all

Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now help me continue with getting this phone updated to at least MM.
:good:

theandies said:
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
Now help me continue with getting this phone updated to at least MM.
:good:
Click to expand...
Click to collapse
Download this RUU.zip
Rename it by deleting everything in name of the .zip except for 0P6BIMG (and .zip of course)
Place the renamed .zip onto your extSD card and put it into your phone. (the card must be formatted to FAT32 for this, and if it is 32gb or less, it probably already is)
Boot to bootloader and follow the prompts (vol up to confirm the flash ~ power button to reboot after it's flashed)
And that's it, super easy.
Make sure to delete the renamed .zip after the flash, or every time you boot to bootloader it'll try to update again
Good luck!

Awesome. Trying it now.
Can you school me on the information that I posted? I'm used to messing with WiFi only tablets and this is my first time messing this deep into a phone. I don't want to brick my brand new M8 so I'm going real slow.
Here is some more info if needed. I see it says s-off, is that correct? Also, once I update can I then proceed to flash TWRP and custom ROM's?

Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.

theandies said:
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
Click to expand...
Click to collapse
Cool! glad I could help.
A little info: since you are S-Off you shouldn't need to unlock the bootloader before you flash TWRP and ROMs, S-Off is all you'll need.

So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.

theandies said:
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
Click to expand...
Click to collapse
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.

xunholyx said:
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
Click to expand...
Click to collapse
Understood. I have one more problem. My mobile data is not working. I checked all the APN settings and all of them are grayed out. Any ideas on what to do? I'll post a screenshot in a while. Just got to work.
I also tried *#*#4636#*#* but I really don't want to do anything with that yet as I really don't know what to do there and don't want to make things worse.
Texting and phone calls are working just fine.
Well snooping around the internet at work tonight I was able to figure out that I need to set my APN setting. More snooping and I found an APN setting that works......kind of. It will not go 4G LTE only HSPA. Here is a screen shot and the APN settings that get me HSPA.
I will try and duplicate the APN settings from my old phone in the mean time does anyone have a known good 4G (or 4G LTE) AT&T APN that will work with this phone? Hopefully I've posted enough information for the experts to help me get back up to speed.

Either of those APNs should work fine. Literally, the grayed out one (nextgenphone) is the one I'm on now, and it works flawlessly for me (3G, LTE, MMS, etc.). The one you entered (ATT Phone) I believe is actually the new/current one being used as default on most newer ATT phones, and should work fine as well. Your problem isn't APN, I think it's the RUU you used.
I would suggest using the AT&T RUU 6.20.502.5 from here (see RUU section): https://forum.xda-developers.com/showthread.php?t=2751432
Note the red text below the RUU. If you get Error 155 installing the RUU, you'll need to fastboot flash the firmware, before the RUU will install properly (peculiarity of US Marshmallow RUUs).
Reason you need the AT&T RUU, is that by flashing the Euro RUU, you installed the Euro radio, which is only intended to support LTE bands 3, 7, 8, 20. AT&T uses LTE bands 2, 4, 5, and 17. Therefore, you are missing support for every LTE band used by AT&T (the band or bands used by AT&T in you local area being the most important), and explains why everything works but LTE.

Great information redpoint73. I'll flash the other RUU this weekend.
Please bear with me, when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer? Forgive me but as I said this is my first phone I've messed with this deep. My experience has been on ASUS tablets and most of the custom stuff done on them is usually flashed via SD card (or internal storage) 99% of the time. I can do it with the help of XDA I just don't want to render my new M8 inoperable.

theandies said:
when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer?
Click to expand...
Click to collapse
If you read the red colored note regarding Error 155, under the RUUs in my Index thread (which I linked) you will see another link there, to a separate post/thread that will tell you exactly how to flash the firmware (if needed). Follow those instructions, and you will be good.
Flash via fastboot uses your computer and USB. But keep in mind that adb and fastboot are similar, but not exactly the same.

I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks

theandies said:
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
Click to expand...
Click to collapse
Just hook up your phone and double click on the download. The .exe will install a lot like software for your PC
If it fails to install booting to bootloader first before starting the RUU.exe sometimes helps.
On HTC's US website, there are both manual update instructions and a download for the RUU
I'm not sure if you'll need to flash the firmware first since you are already on Android 6, but it couldn't hurt to do so, and you might actually need to.

Awesome, this place is full of great people willing to help. I just wish I could reciprocate more.

theandies said:
Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Click to expand...
Click to collapse
It wouldn't hurt to flash firmware first. Only reason I would suggest folks to run the RUU first (and see if it works) is because not everyone is comfortable using fastboot commands to flash the firmware (and therefore may avoid having to learn how to do that). But if you are comfortable with the process to flash the firmware (it's not hard), then go ahead and do so before running the RUU.
Like xunholyx, I'm not sure if you need to flash the firmware first, or not. If you were coming from Lollipop, you definitely would need to. I have a feeling that you will indeed need to flash the US firmware before the RUU will install. Even though you are on Marshmallow firmware, it's the Euro one, so I think (but not sure) the RUU will still fail until you flash the US MM firmware.

EDIT - Forget it I found it........duh.
Thanks redpoint73. I'm going to flash the firmware first because of what you said (Euro phone vs. US).
I can't seem to find your post on how to do that again in the sea of posts. I thought I bookmarked it but it's not there. Can you be so kind as to link it up.
:good:

[Guide] Getting H933/Any? Modem to work on a converted US998/H930.

A SOLUTION WAS DISCOVERED
CLICK HERE TO ENJOY
Hi Guys!
So... I've no clue if my LTE connectivity is worse then before and since I'm scared of bricking my device by reverting back to the canadian firmware...
I've got a canadian G6 so I compared both of them and.. even tho the Band 4 had weaker signal, the G6 still picked the Band 4 over the Band 2 that my phone picked.
(I know that my network band 4 is way faster then the band2, so maybe that's why it's still using it even if the signal is weaker)
Based on that, I've been playing around, trying to get the H933 modem file to work with a converted phone and behave like my G6.
First of, I don't have my original modem files (the 3 bin files). I tried to flash the modem partition using PARTITION DL with LGUP. It doesn't flash it and prompt an alert about a risk of writing of 4 differents partitions.. From there, I assume the partition scheme for the H933 is not the same as the US998. (And I know a lot of people reported it just bootloop the device which makes sens at this point.)
I gave up on flashing the modem files for now and played around with the build.prop file.
US99820a04 vs H93320e00
First, I looked at the difference in the Global Canadian firmware and the us998 firmware
https://www.diffchecker.com/uQi9MMYA
I handpicked some of the differences and tried them directly on my phone (using a rooted file explorer)
https://www.diffchecker.com/vVrIpjts
this change was just a test to see if I get the option to record in the phone call app
Code:
persist.vendor.audio.fluence.voicerec=true
But, sadly, it doesn't change anything so It's not valuable and i'll probably revert it back to false.
From there, strangely, I got different elements appearing in the stock OS and the icon from indicating LTE changed back to what it was before the conversion.
So I can assume one more thing, the US998 system should have everything that is needed to behave like a canadian device
The last step would be to flash the modem partition using dd
(https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193)
Code:
dd if=/sdcard/modem.bin of=/dev/block/bootdevice/by-name/modem
dd if=/sdcard/modemst1.bin of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/modemst2.bin of=/dev/block/bootdevice/by-name/modemst2
But I don't have access to the modem setting file.. But I know erasing them should be fine.
(https://forum.xda-developers.com/showpost.php?p=75507379&postcount=38)
BUT! this command doesn't work on my device, so i'll have to do this :
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
I'm not sure about the bs=16384 argument
And the next concern is.. the modem file from the H933 is smaller then the US998 modem file.
H933 : 98,422,784
US998 : 98,947,072
But, since it's smaller, I assume it's fine to flash it over the US998 modem partition
From there, I assume, everything should work as before.. right?
Just posting this here because I'm not sure of some stuff.
Thank you!

Also, I've been looking at the content both modem file.. and i'm pretty sure they both have all the band...
https://www.diffchecker.com/eV4MAeul
these are the references to the lte band i found while comparing the 2 files
lets try to check the content of modemst1 and modemst2, pretty sure the restriction can be found there and maybe we can just edit the content to enable/disable whatever we want.
Edit:
It's probably a generic modem provided by qualcomm.. So maybe lg didnt remove all the band reference and just blocked them..
Edit2:
By extracting both modem file, I can now say that their configurations are completely different. (sadly)

cloud1250000 said:
Not sure you can just flash a modem.bin.
While cheaply opening the modem.bin of the US998 and the H933, I found that the configuration of the modem is way different. Where the us998 has more visible configuration then the H933.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, carrier wise, they are completely different too. The US998 modem configuration file are pretty straight forward while the canadian one heavily really on nv/item_files/
ATT vs Bell
So i'm pretty sure you cannot flash just the modem.bin. Where is stored the nv/item_file? I think we need to flash one more thing in order to make it work.
Ps. the us998 modem file has a specific configuration for spint too.. I really wonder what's the different between the us998 modem and the LS998 (maybe the content of the NV?)
Click to expand...
Click to collapse
More info~

Okay, just flashed the modem file doesn't work (using dd)
The phone can still boot fine but no sim card is detected.
I've tried to edit more stuff in the build.prop in hope it would allow the modem to pick the right config.. but... nothing.. So I flashed back to the us998 modem. (While keeping my build.prop change)
The lte seems fine for now... still it doesnt have the network optimisation of the canadian modem
So there's clearly something that is checked by the modem before the system load.

cloud1250000 said:
Okay, just flashed the modem file doesn't work (using dd)
The phone can still boot fine but no sim card is detected.
I've tried to edit more stuff in the build.prop in hope it would allow the modem to pick the right config.. but... nothing.. So I flashed back to the us998 modem. (While keeping my build.prop change)
The lte seems fine for now... still it doesnt have the network optimisation of the canadian modem
So there's clearly something that is checked by the modem before the system load.
Click to expand...
Click to collapse
Honestly, I don't think it's worth going back to the Canadian modem. My personal experience:
Bluetooth is more stable
Signal strength more accurately presented on the signal icon
Lost some performance on LTE, but marginal
I have a first gen LG V30 which is plagued with signal issues... It's most likely hardware more than software. Now that I Bootloader unlocked it, it's pretty much over if I want a replacement though.

Honestly.. I don't have signal issue..
But. I know for a fact that the Bell LTE band 4 is better and it is not picked by default here...
It prefers the band 2 for some reason.. If we could just change the band preference.. It would be amazing. (Because both are available here and it doesnt pick the band 4 often.. Probably because of signal strength.. But the band 4 is better even with less signals..)
I might try some stuff soon.. But since I was alone.. I didnt really bother with that anymore..

There is also the lack of VoLTE on the 998. I would like to have that working again as it did on 933.

bnevets27 said:
There is also the lack of VoLTE on the 998. I would like to have that working again as it did on 933.
Click to expand...
Click to collapse
True.. There's another thread where the op explained on how to get volte back in their country.. which is not canada. It doesn't work with our device..
I'll look more into this...

Removed; was hyped and didn't search. Thanks; carry on.

bnevets27 said:
There is also the lack of VoLTE on the 998. I would like to have that working again as it did on 933.
Click to expand...
Click to collapse
cloud1250000 said:
True.. There's another thread where the op explained on how to get volte back in their country.. which is not canada. It doesn't work with our device..
I'll look more into this...
Click to expand...
Click to collapse
Any progress for anyone on this? ( I mentioned elsewhere but I will drop it here too as ot is relevant) Freedom Mobile announced that they will be releasing a software update tomorrow to activate VoLTE on their V30's.

cloud1250000 said:
Honestly.. I don't have signal issue..
But. I know for a fact that the Bell LTE band 4 is better and it is not picked by default here...
It prefers the band 2 for some reason.. If we could just change the band preference.. It would be amazing. (Because both are available here and it doesnt pick the band 4 often.. Probably because of signal strength.. But the band 4 is better even with less signals..)
I might try some stuff soon.. But since I was alone.. I didnt really bother with that anymore..
Click to expand...
Click to collapse
Hey there,
Just like you I have been for over a month now trying to find ways of flashing the H933 modem file back to our canadian phones once the 998 conversion is done. As i have recently written to @Mad Medik i have tried several different approaches and have arrived to the same conclusion that flashing the modem.bin/img file on dd or twrp is only part of the process. Not only does it kill the SIM access but also wifi as well once you do this this H933 Modem flash and also shows blank IMEI. Some other .bin/img file is necessary and not merely buildprop tweek. I went back to the drawing board yesterday and tried every possible build.prop manipulations but to no avail. I I am now thinking that maybe this requires us to also flash the persist.img/bing from H933, what do you think about this?
I also wanted to add that it is not only with the US998 but allso with the VS996. I flashed westwood24's twrp flash-able zip for stock996 and tried the Canadian modem flash but with same results. On a side note, i feel that, notwithstanding some of the Verizon bloat which is easily removed/frozen, the 996 operates smoother and better battery performance than the US998 but i am not able to full quantify that quite yet.
Either-way, as I have posted elsewhere -- I am able to get LTE here in Atlantic Canada no problems with EITHER the 998 or 996 modems. That said if you find that that these modems are favoring one band over another which you feel would be better you can disable that one particular band. I found the same thing happening here, my v30 was regularly defaulting to either band 2 or 5 instead of the better 4 or 7. So i disabled them and now it works excellent.
gs

hm.. Probably the next thing I would try would be to flash the canadian system img and boot img... (like they did to get sprint working) (using dd)
I tried forcing the setting to load the configurations files modem manually... The idea came from here https://forum.xda-developers.com/lg-v30/how-to/guide-volte-vowifi-functional-available-t3834267
I've dropped some of my concern there. btw while following this thread.. I lost the volte option that I had in my mobile setting menu...
The problem is.. it doesn't load the files (the modem config files).. so.. we can also try to check the logcat to, maybe, get some insight about why it doesn't initialize the modem at all (lte/wifi/imei)
Edit: Someone also mentioned something about not flashing the root checker thingy.. maybe this would help?

cloud1250000 said:
hm.. Probably the next thing I would try would be to flash the canadian system img and boot img... (like they did to get sprint working) (using dd)
I tried forcing the setting to load the configurations files modem manually... The idea came from here https://forum.xda-developers.com/lg-v30/how-to/guide-volte-vowifi-functional-available-t3834267
I've dropped some of my concern there. btw while following this thread.. I lost the volte option that I had in my mobile setting menu...
The problem is.. it doesn't load the files (the modem config files).. so.. we can also try to check the logcat to, maybe, get some insight about why it doesn't initialize the modem at all (lte/wifi/imei)
Edit: Someone also mentioned something about not flashing the root checker thingy.. maybe this would help?
Click to expand...
Click to collapse
Hi,
Yeah I tried that already -- flashing both boot and system from the Canadian KDZ file -- didnt work, just bootloops even after several wipes. I also had zero luckwith the logcats after the modem flash, no relevant info. Hopefully you have better luck than me...
Cheers,
GS

Did you erase the modem setting partition when you tried?
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
edit:
https://forum.xda-developers.com/ga...ofessional-t1308546/post77558988#post77558988
the person who made this thread and tools might have an idea.
Edit 2 :
Looking here, I assume the nv partition/folderis within the modem setting partition
https://androidforums.com/threads/v...leon-some-efs-imei-info-brick-backups.782318/

OKay from one of the link I shared, we might need to overwrite the backup and fsg partition (and then delete the modemst*) parititon
backup - NV data backup partition
FSG - Modem Storage "Golden Copy"

okay good news guys.
I made it.
I'm currently on the latest global ca version, twrp for recovery and fully rooted
(i've just done it... I lost all my data sadly... :'( )
I'll keep you updated tomorrow since i have to sleep now (2:45am and i work at 8...)
It's totally doable by anyone with enough patience but sadly.. I'm 100% sure it's not possible to provide a nandroid backup as an easy solution.
I'll probably drop my solution tomorrow.. once I confirm volte works on the global version (one of the main reason lol)
Good night.

This is awesome news! Good job. You were perfect for the job, right amount of ambition and smarts to figure it.
I'll patiencently wait for you information or in my case a guide/instructions. I'm in no hurry, just really happy you got it figured out.

cloud1250000 said:
okay good news guys.
I made it.
I'm currently on the latest global ca version, twrp for recovery and fully rooted
(i've just done it... I lost all my data sadly... :'( )
I'll keep you updated tomorrow since i have to sleep now (2:45am and i work at 8...)
It's totally doable by anyone with enough patience but sadly.. I'm 100% sure it's not possible to provide a nandroid backup as an easy solution.
I'll probably drop my solution tomorrow.. once I confirm volte works on the global version (one of the main reason lol)
Good night.
Click to expand...
Click to collapse
cloud1250000 said:
Did you erase the modem setting partition when you tried?
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
edit:
https://forum.xda-developers.com/ga...ofessional-t1308546/post77558988#post77558988
the person who made this thread and tools might have an idea.
Edit 2 :
Looking here, I assume the nv partition/folderis within the modem setting partition
https://androidforums.com/threads/v...leon-some-efs-imei-info-brick-backups.782318/
Click to expand...
Click to collapse
Hey @cloud1250000,
First of all my apologies for not getting back to your previous message sooner re; erasing the modemst1/2 partitions. I was gonna respond when you posted it but depending on my and my wife's work schedule there are times when I have zero opportunity to get back on xda. We have a 9month old crawling around so that makes it even more complicated.
Second, I am elated that you found out some more information about how to get our H933 working with twrp/root. I had some new theories about partition locations for the modem and efs backups but simply did not have the chance play with it. I also never considered the FSG partition but it makes sense. Glad you got it working and looking forward to hearing your procedure. When i had done the modemst1 / 2 erase just as is without any efs backup/NV config file not only did it fail to load the canadian modem i was not able to flash other modems re; 998 or VS996 , which i was able to do before , only way back was to do a full rom install. This implied that the modemst partition could not -- as you also indicated -- simply be erased and that other things were linked to it. Again, glad you figured it out. Now you had mentioned overwriting the fsg partition but i thought when we flash the KDZ with LGUP it does infact do that no?
One thought that just occured to me is that even though a simply nandroid approach wont do it could we not, using twrp do the required manipulation of different FSG/EFS partiitions using twrp backup and restore? For example, as we had discussed earlier when we install the full KDZ of the H933 oreo in LGUP flashing all partitions except the Recovery one, we got bootloops but still are able to access twrp. I assumed that meant that while the system was not booting the full canadian rom was infact installed and that you we could do a twrp backup of the required partitions, re; efs, system etc and manipulate them. Not sure if this was your approach? Looking forward to hearing your wizardry,
cheers,
gs

Working VOLTE
+ working magisk/root~~
I'll explain how I did it later today and why I think a nandroid backup wont do

cloud1250000 said:
Working VOLTE
+ working magisk/root~~
I'll explain how I did it later today and why I think a nandroid backup wont do
Click to expand...
Click to collapse
Dynamite man. DYNAMITE!! looking forward to seeing the magic . Can you see if you get the HD voice calling enabled during calls, regardless of VoLTE?

How To Guide Root Galaxy A22 SM-A225F Android 11

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Root:
1. Unlock Bootloader
Boot to Downloadmode
On first screen press and hold volume up button until unlock screen appears
2.Flash my Magisk-prepatched boot.img with Odin
In Odin first untick the autoreboot
press on AP, select my customboot.tar and press Start
Dont Reboot !!!! You need to Factory Format or it will bootloop so turn device off and reboot to recovery and make factory reset
3.Reboot
Attention !!! I made my own Kernel for this customboot.tar The device Starts with Selinux Permissive so only use it if you know what you do here
Viper4Android is working with my Kernel
to make your own patched boot.img download stockboot.tar extract it with 7zip and patch the extracted .img on your Phone ....than pack the patched img as .tar and flash it with odin

hi, can you or someone explain more carefully?
how to unlock bootloader? how to flash that magisk prepated boot.img? what is odin and where do I get it?
do I need my own kernel for this customboot.tar? Also, what is customboot.tar and where do I download it?
Please, we need something much more clear.

virividiann1434 said:
hi, can you or someone explain more carefully?
how to unlock bootloader? how to flash that magisk prepated boot.img? what is odin and where do I get it?
do I need my own kernel for this customboot.tar? Also, what is customboot.tar and where do I download it?
Please, we need something much more clear.
Click to expand...
Click to collapse
take a look under Attachments there you can download stock and custom.tar

Hi there! I have couple ( 4 pcs) of Samsung Galaxy A22(SM-A225F) 4G 64gb devices. I successfully flashed and root two of them, but the other two no. Both phones where i succeeded with flash and root have spec: AP: A225FXXU1AUG1, CP:A225FXXU1AUF5, CSC:A225F0LE1AUG1. The other two I bricked are with AP:A225FXXU2AUH1, CP:A225FXXU2AUH1, CSC: A225F0XM2AUH4. The problem is that the two bricked phones worked but missing IMEI and baseband connection also when i check wit *#1234# the CP is missing. How can I restore my phones to work?

dimitrov94 said:
Hi there! I have couple ( 4 pcs) of Samsung Galaxy A22(SM-A225F) 4G 64gb devices. I successfully flashed and root two of them, but the other two no. Both phones where i succeeded with flash and root have spec: AP: A225FXXU1AUG1, CP:A225FXXU1AUF5, CSC:A225F0LE1AUG1. The other two I bricked are with AP:A225FXXU2AUH1, CP:A225FXXU2AUH1, CSC: A225F0XM2AUH4. The problem is that the two bricked phones worked but missing IMEI and baseband connection also when i check wit *#1234# the CP is missing. How can I restore my phones to work?
Click to expand...
Click to collapse
Try to flash stock from this website. If the IMEI is still gone, re-partition and maybe even select NAND Erase. That's how I restored IMEI on my device.

Successful Root!!!!

Hi i have a few questions:
- Why do you uploaded stockboot.tar? Is that the original boot.img in case we want to go back to the original unrooted?
- Can this root method be model dependent? Mine is SM-A225MZKEARO , not the global version, and it has NFC; can it loose functionality by applying your image?
- Does this root method bypasses SafetyNet?
Thanks in advance, great work.

BlueTower said:
Try to flash stock from this website. If the IMEI is still gone, re-partition and maybe even select NAND Erase. That's how I restored IMEI on my device.
Click to expand...
Click to collapse
I have this same problem but on an A32.
I would try re-partitioning and maybe NAND erase as you say, but:
- do I need the PIT file later?
- doesn't that finish erasing the nvram, efs or whatever contains the IMEI information and finish killing the phone capabilities?
Tanks!

Fixed it on the a32, working so far
[fixed] rooted a325m suddenly no imei, no sim
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now...
forum.xda-developers.com

Hello all, I bought a phone on installment payment but i wasn't able to continue the payment. But unfortunately, there is an APP on the PHONE that automatically LOCK the phone one the PAYMENT has DUE. My question is: Is there a way I can remove the APP from my phone ENTIRELY without it (the phone) been lock again?
The device name is SAMSUNG A22 4G
The company is M-KOPA

Adekunlex said:
Hello all, I bought a phone on installment payment but i wasn't able to continue the payment. But unfortunately, there is an APP on the PHONE that automatically LOCK the phone one the PAYMENT has DUE. My question is: Is there a way I can remove the APP from my phone ENTIRELY without it (the phone) been lock again?
The device name is SAMSUNG A22 4G
The company is M-KOPA
Click to expand...
Click to collapse
Phone is locked. Since u do not have root access to the phone, it is a paper weight. But, after paying it off they would have unlocked it or at least told u the steps to unlock it. Always buy phones out right and unlocked, otherwise u buy a paper weight in the end.

I think you should not buy used phones because the price of the phones is not too expensive and now telcos have a policy of buying new phones without losing money but with the condition that they sign a long-term contract with them. This ensures the security of your information.
getting over it​

Question Can't register fingerprints

After updating the requisite firmware, I performed a clean flash of the latest CRDroid build (previously I was using the March 28) build. During the initial setup, as well as after through the regular settings page, I was unable to register any of my fingerprints to the biometric unlock. In the setup screen, the UDFPS lights up when pressed (see screenshot), but no matter how long I keep my finger pressed on it the print will not register. I have rebooted, clean flashed, and dirty flashed the ROM, and the problem appears every time. I have tried installing both with and without GApps. I even tried flashing LineageOS instead of CRDroid, and I had the same issue. What steps should I be taking to troubleshoot this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Do you have the backup of persist partion?

PattasuBalu said:
Do you have the backup of persist partion?
Click to expand...
Click to collapse
No, the only backup I have of my previous install is the Swift Backup of apps and settings.

Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.

PattasuBalu said:
Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.
Click to expand...
Click to collapse
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?

Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms

sumfahg said:
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?
Click to expand...
Click to collapse
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.

EugenStanis said:
Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms
Click to expand...
Click to collapse
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.

sumfahg said:
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.
Click to expand...
Click to collapse
Just dont forget to lock your bootloader and say that the new update broke your phone. BTW dont forget to take a backup of persist.img when you flash a new rom.

Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.

PattasuBalu said:
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.
Click to expand...
Click to collapse
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.

mattie_49 said:
Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.
Click to expand...
Click to collapse
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
I think he took the backup via Partitions Backupper app which was the same app I used take a backup of my persist.img. But the app requires super user access to take backup.

TheKnux said:
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.
Click to expand...
Click to collapse
Can you please mention the steps and what are the backsides of doing this?

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Many ways to accomplish without root. And you back up the persist partition. Not root directory. Msm Read back with F8. Then find persist and send it to the root directory of C drive with Read back feature. . Password oneplus

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can backup persist and co with msm tool (read back modus)

PattasuBalu said:
Can you please mention the steps and what are the backsides of doing this?
Click to expand...
Click to collapse
Just search xda. Pretty sure it's on the OnePlus 8 or 8T forums.

Question how to relock bootloader rog 6 ?

if using qualcomm tools it need mbn file . i cant find that mbn file in the firmware folder . urgent hlp

fastboot oem asus-csc_lk

Andrologic said:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
Command not working

AmeNahar said:
Command not working
Click to expand...
Click to collapse
How is it not working? What do you get?

Andrologic said:
How is it not working? What do you get?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AmeNahar said:
View attachment 5831065
Click to expand...
Click to collapse
Wrong fastboot. Do it from the bootloader page: 'fastboot reboot bootloader' or just turn on the device in bootoader mode without navigating to fastboot/fastbootd. Then use the same command. Should help.

Andrologic said:
Wrong fastboot. Do it from the bootloader page: 'fastboot reboot bootloader' or just turn on the device in bootoader mode without navigating to fastboot/fastbootd. Then use the same command. Should help.
Click to expand...
Click to collapse
i got <waiting for device> (side charger port) .can u give the actuall usb device driver ? if using fastbootd can detect . but from fastboot reboot bootloader just waiting for device

AmeNahar said:
i got <waiting for device> (side charger port) .can u give the actuall usb device driver ? if using fastbootd can detect . but from fastboot reboot bootloader just waiting for device
Click to expand...
Click to collapse
Same problem did you find any solution?!

I just found the solution
You should use side usb port for update just connect to the pc reboot to fast boot and run the command

havard20009 said:
I just found the solution
You should use side usb port for update just connect to the pc reboot to fast boot and run the command
Click to expand...
Click to collapse
cool. sorry for late reply.. my solution is change the usb cable ..i always use side port btw ..i flashed raw and flash A13 now . bcs i want to play new state(not working on rooted devices and bootloader unlocked) . thats the reason why im relocking my bootloader

*deleted.

Does relock the bootloader on official rom will give error and need to flash official rom again?
I want to root my Batman edition but scared it will give bootloop after relock bootloader in future. As the Batman official rom is never be found on the net, I would lose the Batman theme if flashed to normal version.

deddo86 said:
Does relock the bootloader on official rom will give error and need to flash official rom again?
I want to root my Batman edition but scared it will give bootloop after relock bootloader in future. As the Batman official rom is never be found on the net, I would lose the Batman theme if flashed to normal version.
Click to expand...
Click to collapse
It may give you a device corrupt error after re-lock that requires a factory reset or RAW flash meaning you may risk losing your Batman stuff - whatever that is. Best to root and leave it unlocked (you can still unroot it), or leave it alone...

Andrologic said:
It may give you a device corrupt error after re-lock that requires a factory reset or RAW flash meaning you may risk losing your Batman stuff - whatever that is. Best to root and leave it unlocked (you can still unroot it), or leave it alone...
Click to expand...
Click to collapse
The only reason I want to root it to take out the Batman theme. It's in Zip file inside the Asus Theme folder, I can extract it but all files are unreadable. Where's photos and videos are in .enc format and APKs cannot be open, even changed to .zip format.
It seems all Asus themes are like this not only for Batman theme. So my plan is to root it and take out the theme that may be inside System folder that only can be reach via root. Then relock the bootloader before selling it later.

deddo86 said:
The only reason I want to root it to take out the Batman theme. It's in Zip file inside the Asus Theme folder, I can extract it but all files are unreadable. Where's photos and videos are in .enc format and APKs cannot be open, even changed to .zip format.
It seems all Asus themes are like this not only for Batman theme. So my plan is to root it and take out the theme that may be inside System folder that only can be reach via root. Then relock the bootloader before selling it later.
Click to expand...
Click to collapse
Or unlock it and take a full system image backup with TWRP or something else and keep it stored. That way you can roll back and re-lock in case you want to sell the device one day.
You could also switch your active slot and leave one with the Batman theme on the inactive, but need to be very careful not to overwrite the Batman slot. Requires strickt manual management of where system updates are installed. Not recommended but possible.

AmeNahar said:
cool. sorry for late reply.. my solution is change the usb cable ..i always use side port btw ..i flashed raw and flash A13 now . bcs i want to play new state(not working on rooted devices and bootloader unlocked) . thats the reason why im relocking my bootloader
Click to expand...
Click to collapse
Excuse me can you share the raw file link and version information?

sorankira said:
Excuse me can you share the raw file link and version information?
Click to expand...
Click to collapse
sorry for late reply...the links and info availble on rog 6's forum

sorankira said:
Excuse me can you share the raw file link and version information?
Click to expand...
Click to collapse
[TOOL] RAW Firmware for ROG Phone 6 - can be used for CN -> WW converting
Too many people are trying to use firmware to make money, so I decided to release them for free! I got them from a site that distributes them for $10. DOWNLOAD Password is: https://androplus.org How to flash: Plug the USB Type-C cable into the...
forum.xda-developers.com

Can i relock and unlock after?

Effizio01 said:
Can i relock and unlock after?
Click to expand...
Click to collapse
Yes. I already 3 times unlock .root and relock bootloader