Hi.
I got a pretty good deal on a S9+ (Korean version) and when I got it I saw it has TWRP as recovery and perhaps some custom rom installed in it (I don't really know).
I would like to leave it stock, as it comes from fabric, to get OTA updates and passing safetynet (very important to me).
What things do I need to do?
Thank you :good:
SkyLey said:
Hi.
I got a pretty good deal on a S9+ (Korean version) and when I got it I saw it has TWRP as recovery and perhaps some custom rom installed in it (I don't really know).
I would like to leave it stock, as it comes from fabric, to get OTA updates and passing safetynet (very important to me).
What things do I need to do?
Thank you :good:
Click to expand...
Click to collapse
if it has TWRP on it, 99% sure its rooted and therefore wont pass safety net. You can get it up and running and get magisk installed to hide root from the vast majority of apks that would be affected by root.
youdoofus said:
if it has TWRP on it, 99% sure its rooted and therefore wont pass safety net. You can get it up and running and get magisk installed to hide root from the vast majority of apks that would be affected by root.
Click to expand...
Click to collapse
Just ran RootChecker and it said it is not rooted.
Actually I'm not even interested in rooting. Just want it clean as from fabric.
I guess I have to flash its stock rom and recovery and closing the bootloader, but I have no idea how to. Any help?
Reboot to download mode and check the warranty state
i know you dont want to root due to the secure folder comment(errrr, safety net rahter)
im just saying that i bet it already has been rooted if it has TWRP on it, and youre likely out of luck
youdoofus said:
Reboot to download mode and check the warranty state
i know you dont want to root due to the secure folder comment(errrr, safety net rahter)
im just saying that i bet it already has been rooted if it has TWRP on it, and youre likely out of luck
Click to expand...
Click to collapse
Ok, this is its download mode:
https://i.imgur.com/YkzfQlv.jpg
I have no idea what all that means, lol
What things do I need to flash?
SkyLey said:
Ok, this is its download mode:
https://i.imgur.com/YkzfQlv.jpg
I have no idea what all that means, lol
What things do I need to flash?
Click to expand...
Click to collapse
flash this
https://www.sammobile.com/samsung/g...e/SM-G965N/KOO/download/G965NKSU1CSG2/282440/
bot download it with one of these
Samfirm
or this (newer prettier GUI, but its the exact same result with either tool)
Frija
youdoofus said:
flash this
https://www.sammobile.com/samsung/g...e/SM-G965N/KOO/download/G965NKSU1CSG2/282440/
bot download it with one of these
Samfirm
or this (newer prettier GUI, but its the exact same result with either tool)
Frija
Click to expand...
Click to collapse
it won't work
https://imgur.com/LZdLH9m
I also tried Samfrim but it displays an error too-
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Could not fetch info for SM-G965N/SKC. Please verify the input or use manual info
SkyLey said:
it won't work
https://imgur.com/LZdLH9m
I also tried Samfrim but it displays an error too-
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Could not fetch info for SM-G965N/SKC. Please verify the input or use manual info
Click to expand...
Click to collapse
install ADB drivers and reboot
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
View attachment 4846361
SkyLey said:
it won't work
https://imgur.com/LZdLH9m
I also tried Samfrim but it displays an error too-
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Could not fetch info for SM-G965N/SKC. Please verify the input or use manual info
Click to expand...
Click to collapse
please use the image upload on the forum itself vs imgur. I cant access imgur at work (where i currently am) and the forum now allows for pics to be attached almost regardless of size
youdoofus said:
install ADB drivers and reboot
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
OK, at the end I downloaded the ROM from the sammobile link you provided me (https://www.sammobile.com/samsung/g...e/SM-G965N/KOO/download/G965NKSU1CSG2/282440/)
I know you told me to not download from it but anyways... I flashed that ROM using Odin and well everything seems normal and working, but Safetynet still won't pass.
I checked on developer settings and the bootloader was still unlocked so I relocked it but... still nothing. Safetynet just won't pass.
What could be happening?
Related
Ladies and gentlemen, I would like to present to you all a formal guide to venture into one of the best smartphones in the market, the underdog to the other mass marketers, the Sony Xperia Z3v for Verizon!
*Please note I am not responsible for any bricking, destruction of your device, alien invasions, or any other problems. It is up to the user's choice to seek out what is done on your device on your own terms.*
This is the method I would recommend that's much quicker and efficient is Kingroot. I know there were some previous controversy about what could be behind Kingroot, but from what I will show here is using Kingroot as leverage to gain access quickly into my prerooted Lollipop firmware that can stand alone after removing Kingroot afterwards.
1. Have the Z3v in your possession.
2. Google "Kingroot" and download for Android and run the rooting process there.
3. Download "Superuser" from the Play Store to have the binary to run root fully. (Optional just in case the next step doesn't work)
4. Install XZDualRecovery (grab the flashinstaller for the Xperia Z3) to install TWRP from here: http://nut.xperia-files.com/path/XZ...40vagg0tpcrnm1vlnt63je5&randomizer=_ehkq575vz
(The link is subject to change, so if that happens, navigate through here: http://nut.xperia-files.com/)
5. Download my new 5.1.1 prerooted Lollipop zip from my thread here: http://forum.xda-developers.com/z3/...08-prerooted-lollipop-5-1-1-23-4-b-0-t3338967
6. Access TWRP by opening an app called NDR Utils in your App Drawer
7. Flash my zip through the install button and now you'll be on the latest prerooted stock build of Lollipop with a few mods.
Optional Step 8. Uninstall any traces of Kingroot from your phone and you're good to go. This step may already be done for you after you flash the prerooted because reportedly there were already no traces left behind. Enjoy!
Thanks to the following people:
@zxz0O0, for achieving root for our Z3v
@jal3223, for helping me as much as you can to guide me through myself
@[NUT], for the custom recovery to install onto our Xperia devices
Please hit thanks for the all in one guide to freedom!
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Mountainfisher said:
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Click to expand...
Click to collapse
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
GigaSPX said:
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
Click to expand...
Click to collapse
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Oh No, I vowed to stop messing with my phones....
jal3223 said:
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Click to expand...
Click to collapse
Personally, I'm fine without doing custom ROMs. I like how Sony's UI works as it is and I prefer it that way than going full AOSP like any other Nexus phone. I just like to buy what came with the package as is intended.
Bobby Buggs said:
Oh No, I vowed to stop messing with my phones....
Click to expand...
Click to collapse
This is well worth to do. I installed Xposed, and unlocked some awesome stuff. Such as using Superior Auto mode with 15 mp right off the start or 20.7 MP. Greater the details, amazing functions made.
Oh and also, I will now proceed to upload the flashable zip of the latest FW being prerooted. Just so there's some better things to deal with.
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Mountainfisher said:
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Click to expand...
Click to collapse
This guy said it took him 10 times so I am going to keep trying till it works!
sthrnsprtsmn said:
I was getting the same errors. I had to factory reset the phone multiple times and redo the steps. On about the 10th time, it took. I skipped the phone set up steps, and kept a root checker apk on my sd card to speed it up. Also, I unchecked the verify apps over USB. I didn't see that mentioned anywhere.
Time to send my donation. Thank you very much @zxz0O0
Click to expand...
Click to collapse
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
JediDru said:
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
Click to expand...
Click to collapse
Your C:/flashtool/firmware folder should be empty. Place the firmware you want to use in /USERNAME/.flashtool/firmware
make sure you uninstall all java and re install fresh!! that was what was holding me up
Someone should do a youtube of this process live
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Bobby Buggs said:
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Click to expand...
Click to collapse
You completely skipped steps 1 and 2 because you're on the latest build. Step 6 is following the instructions that are listed within the exploit.bat.
You won't be reflashing the latest until you've followed through to the new list of steps that occurs after 9.
Giga, sent you a Pm
---------- Post added at 09:31 AM ---------- Previous post was at 09:20 AM ----------
Call me a idiot but I dont see any instructions, I ran the exploit file and my screen shows daemon started successfully but nothing else
ROOT Z3V
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Great write up!
Thanks for the time and effort you put on rooting our abandoned Z3v.
Really look forward to flashing the Pre-rooted firmware that you're about to made
xratablancax said:
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
Click to expand...
Click to collapse
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
What line of code
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
If you look at the link I provided, that gives your a different set of root files, one that the Exploit runs and right after root runs automatically.
VERY IMPORTANT... YOU NEED TO FLASH YOUR DEVICE TO STOCK ROM, YOUR DEVICE NEEDS TO BE IN ROM, 23.0.E.0.376, BACKUP DEVICE, FLASH THEN ROOT THEN OTA UPDATE
Hey everyone I have just received a phone from assurance wireless and it’s a Wicko Phone. I called them and they are saying it’s the Wicko Life 2. In topic I show what a root checker shows as a model number and the sku number which came on the box.
Does anyone know if there is anyway to root this device. I would like to try a faster custom rom or overclock and just overall have root privileges. I have yet to find any information on this particular phone and would greatly appreciate it if anyone can pass along some info or a tutorial. I am friends with Max Lee on Facebook but I have not heard back from him so I figured I’d try here.
-cheers
@y0rper69
With regards to this phone's specs look inside here
Anyone have a crack at this one the boot loader only shows recovery option or normal boot.
@y0rper69
The phone is based on MediaTek chipset MT6739CH. Hence look inside here to get info about how phone's Android can get rooted.
I checked the website and downloaded the tools under windows 10. I plugged the device in and when I run either tools with usb debugging and developer mode enabled I’m not getting the device to show. I ran adb usb and says no device connected?
It does say that some devices may not be supported. I can check to see debugging is on and windows. detects the device for tethering etc but will not show with adb
Update : found the latest media tech drivers unsigned. Phone is now detected.
When I click root it says Su inaccessible - through CWM it is possible to get root on this phone look urls
It says to click on block map but when I click block map nothing is listed in any colums per the guide on the xda link that was given. /viewtTopic.php?P=502084#p502084. Not sure how to populate colums when reading block..
With two view topics so I’m following them now.. will update 2: mtk droid tools does not support new mtk chipsets. I’ve tried iRoot and latest kingroot and neither are supported but had an option to let them known the device is not supported.
Any other pros able to take a hack at this? This is one of those free Obama phones from assurance wireless it’s the Wicko Life 2
Has the how to root Wiko Life 2
Mystery been solved yet?
i was able to unlock the bootloader just now going to work on root next.
hello bigrooster88. You sir have gotten my attention. i am extremely interested in the steps you took unlocking the bootloader of the u307as. i am currently stuck in the orange state loop. May i please request instructions for your awesome new strategy?? please and thank you!!!
jwoegerbauer said:
@y0rper69
The phone is based on MediaTek chipset MT6739CH. Hence look inside here to get info about how phone's Android can get rooted.
Click to expand...
Click to collapse
This link is broken or unavailable
bigrooster88 said:
i was able to unlock the bootloader just now going to work on root next.
Click to expand...
Click to collapse
Yes I would like to know how u did this please.
bigrooster88 said:
i was able to unlock the bootloader just now going to work on root next.
Click to expand...
Click to collapse
Yes I would like to know how u did this please
I'm pretty sure you can buy replacement ones for $10. I would just cough up the money and replace it. That or throw in $10 more and get an upgrade
Basically you have to unlock the bootloader and then follow the instructions on the mtk-client page. Make sure to make a backup first and to install the magisk version listed. Afterwards you have to update magisk a couple of times. I have not gotten viper4android or James dsp to work yet. Also just to mention magisk no longer has an online repo to download from. I will put links below. This software should work for a lot of other devices that have mtk processors as long as the bootloader can be unlocked. For a long time I gave up on rooting this phone because I couldn't find a stock rom / boot.img for it. Another thing to mention is that you may have to change the extension of the boot image file around from .bin to .img and vice versa. Also the latest usbdev driver crashed my windows 10 but installing the version before the latest didn't crash my windows 11 install. I just did all this about 2 days ago so I am still finding issues that need to be worked on. I am not a software developer by any means. So far I have not gotten any audio mods to work but I have had issues with them on many devices. I can confirm that the backup and restore of apps and their data work on the 2 U307AS that I have. Getting the latest magisk alpha image to stick seems to not be working with the direct install method. It doesn't look like we can use magisk unless it is the alpha version. I have not tried patching the latest magisk into the boot.img and then flashing it with mtk-client yet. Another note (lots of them, lol) is I didn't know where the mtk-client program was looking for the patched boot.bin when it came to the part about flashing with an empty vmeta whatever file. I ran the command anyways which gave the error about the missing boot.bin file but it did do the empty vbmeta flash so I just flashed the patched boot.bin with the mtk-client gui afterwards. Hopefully no one hosed their windows os because I failed to mention the issue with the usbdev driver.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
jmurrtos said:
Has the how to root Wiko Life 2
Mystery been solved yet?
Click to expand...
Click to collapse
Yes
DaRkSkYxP said:
Yes
Click to expand...
Click to collapse
Yup I redid one today 4-5-23 and root and no dm verity issue and network unlocked.
So to use this, you will need to be bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled this is a must!!(its always good to make a nandroid before making any changes on your phone). What this will do is more or less provision your Lg G8x to your Desired Carrier, it will also let you change your apns, so you have volte working and also the data indicator will change to match the carrier. WIfi calling is working on tmobile, will need someone to test other carriers.
There seems to be confusion , this is only for the Stock rom. this will do nothing for GSI roms.
Instructions:
1.Extract to Content of zip to Sdcard
2.Make a copy/backup of your own files: Go to twrp and backup your product partition and your op configs in case you need to restore them
3.Copy and paste the files from my zip to:
/product/op/config
and this single file cust.prop to /product/op
make sure permissions are 644.
4.Reboot your device it should now be provisioned to your Desired Carrier.
Click to expand...
Click to collapse
Download
Sprint Untested
SPR-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
T-Mobile
Tmo-VOLTE-VOWIFI-FIx-G8x
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
VZW Untested
VZW-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Credits:
vl48 this guy is awesome, and also very patient an expert in lg devices.
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
e20140 said:
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
Click to expand...
Click to collapse
There is one already made, you just need the correct twrp from telegram
siulmagic said:
There is one already made, you just need the correct twrp from telegram
Click to expand...
Click to collapse
Why not post on xda? Is everyone switching to telegram? I've read everything on xda and don't see a specific method to unlock bootloader+twrp+DM but a few failed attempts on ATT version of the G8X. I only see working solution for India, Europe, and Sprint Models. You are the only one that has successfully unlock it. I am sure more people will need help as 3G is going away and we need Volte working on this phone.
well the basic gist of it is:
This will WIpe Your Phone, make sure to backup first.
Cant post the recovery zip, but pm il send it to you. i will move this to a proper thread later today. and better formatted
1.install qpst/qualcom driver or use windows update ones
2. download firehose uncompress it somewere on your pc
3.download g8x twrp and magisk 20.4 zip also the dm verity zip
also make sure to grab the eng abl for the g8x(eng bootloader that will allow us to unlock).
4. enable oem unlock in developer settings
5. boot phone into edl mode
6.start qpst set storage type to ufs, slect built type, make sure it is flat build
7.Look for select programer then click browse, here you will chose the firehose file
8. click select port on qfil then double click 9008 com port were the phone is detected in edl mode
9.now in qfil select tools then partition manager
10. when the list of partitions show up look for abl_a,abl_b,modem a/b, and modemst1 and 2, you will right click each of them and click manage partition data then read data, this will back them up to your computer(be very careful you can wipe your whole phone if you click in the wrong place)
11.after you back up everything select load img and flash abl_a to Abl_a and abl_b. after this unplug phone and boot into bootloader mode.
To boot into bootloader mode turn off your phone and hold volm down and plug in your usb cable, this should boot it into bootloader mode .
12. if you see text that says you active boot slot, you now have successfully flashed the eng bootloader witch will allow you to unlock the bootloader.
13. now while the phone is pluged into your computer you will open a adb window and type fastboot oem unlock , the phone will ask you to agree to unlock the bootloader, select yes.
14.after this reboot your phone into edl mode, reflash your backup abl_a to abl_a and abl_b, this will restore stock bootloader you wont have fastboot anymore but no worries, also you can flash your stock rooted boot.img to boot_a and boot_b.
15. After you reboot into android, install magisk manager, flash the g8x twrp zip and without reboot, also flash magisk 20.04 zip, if you do not do it this way you will break your boot.img and have issues, like freezing system.
16 now reboot to recovery wipe data then reboot and flash the dm verity disabler to disable encryption. after this create a nandroid backup, then just reboot back to system and enjoy.
17. profit
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
e20140 said:
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
Click to expand...
Click to collapse
why 0o with gpst and firehose you can root bl unlock any att g8x, unless there something im not aware of?
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
e20140 said:
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
Click to expand...
Click to collapse
thats a driver error, you need to let windows install the driver from windows update or like i did use qpst on windows 7. i never got that erro fixed, so i just used windows 7 on a old laptop i have, and it works mint.
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
e20140 said:
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
Click to expand...
Click to collapse
well thats the error i got, with my g8 and g8x on windows 10.
wangsu10 suggested the error could be installation selection option for the QCOMM driver. Need to be install as 2nd option " ETHERNET-DHCP". I already returned mine
Maybe you can try it on your Win10 and report back. If it works, we need to have it added to the OP for all others to see.
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
nate0 said:
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
Click to expand...
Click to collapse
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
siulmagic said:
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
Click to expand...
Click to collapse
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
@siulmagic where is the twrp image for the g8x? Did they pull it down?
nate0 said:
@siulmagic where is the twrp image for the g8x? Did they pull it down?
Click to expand...
Click to collapse
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
nate0 said:
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
Click to expand...
Click to collapse
there is another app that needs updated i forgot witch one it was.
siulmagic said:
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
Click to expand...
Click to collapse
Newbie to Telegram, how does one find the group please?
mangojain said:
Newbie to Telegram, how does one find the group please?
Click to expand...
Click to collapse
LG Mobiles India 🇮🇳
Political Discussion, Obscene material/words, Selling, Fraudulent link posting will lead to Ban SHARING COPYRIGHT CONTENT & PIRACY NOT ALLOWED, it leads to REPORT & BLOCK Photography Group: @lgg8xphotography OT Group: @LG_G8X_OffTopic
t.me
Hey guys, how's it going? I have run into a problem that I have never faced on a previous Pixel device in the past. Usually, you can download the factory images from Google's site, run the flash-all.bat/flash-all.sh, and start fresh with the latest images. However with the Pixel 6, it just results in a bootloop for me regardless if I force a factory reset or not. I have tried on both Windows and Linux Mint with the same result. I have tried:
Formatting before running flash-all.sh = bootloop
Formatting after flash-all.sh by directly booting into recovery = bootloop
Running flash-all.sh, rebooting directly to fastboot, then disabling verity and verification = bootloop.
The only way I have gotten it to work is by using Google's online Android Flash Tool and selecting: wipe, disable verity, and disable verification (which I have done manually with an unsuccessful result).
Has anyone manually flashed firmware (not the OTA) without getting a bootloop?? I'm starting to think they have uploaded courupted files or something. I've downloaded them multiple times to be sure it wasn't bad on my end. It's got me seriously scratching my head. Again, I have been doing the same with each previous Pixel for years now, so I don't know what the deal is.
jal3223 said:
Hey guys, how's it going? I have run into a problem that I have never faced on a previous Pixel device in the past. Usually, you can download the factory images from Google's site, run the flash-all.bat/flash-all.sh, and start fresh with the latest images. However with the Pixel 6, it just results in a bootloop for me regardless if I force a factory reset or not. I have tried on both Windows and Linux Mint with the same result. I have tried:
Formatting before running flash-all.sh = bootloop
Formatting after flash-all.sh by directly booting into recovery = bootloop
Running flash-all.sh, rebooting directly to fastboot, then disabling verity and verification = bootloop.
The only way I have gotten it to work is by using Google's online Android Flash Tool and selecting: wipe, disable verity, and disable verification (which I have done manually with an unsuccessful result).
Has anyone manually flashed firmware (not the OTA) without getting a bootloop?? I'm starting to think they have uploaded courupted files or something. I've downloaded them multiple times to be sure it wasn't bad on my end. It's got me seriously scratching my head. Again, I have been doing the same with each previous Pixel for years now, so I don't know what the deal is.
Click to expand...
Click to collapse
Might be a problem with your setup. I don't have a Pixel 6 / Pro so I can't confirm this, but I've had zero issues with the factory images on my Pixel 5. Others in this forum have used the factory images with no problems.
Disabling verity/verification is no longer necessary if you're rooting with Magisk.
V0latyle said:
Might be a problem with your setup. I don't have a Pixel 6 / Pro so I can't confirm this, but I've had zero issues with the factory images on my Pixel 5. Others in this forum have used the factory images with no problems.
Disabling verity/verification is no longer necessary if you're rooting with Magisk.
Click to expand...
Click to collapse
I've never had any issues with any other Pixel devices (granted, the latest device I have other than the Pixel 6 is the Pixel 4XL).
Do you have any advice on making sure my setup is correct? I mean, I tried in both Linux and Windows. It should be an all in one package in either environment though I would think.
I may try again in Linux to see what happens after a fresh download.
jal3223 said:
I've never had any issues with any other Pixel devices (granted, the latest device I have other than the Pixel 6 is the Pixel 4XL).
Do you have any advice on making sure my setup is correct? I mean, I tried in both Linux and Windows. It should be an all in one package in either environment though I would think.
I may try again in Linux to see what happens after a fresh download.
Click to expand...
Click to collapse
Have you tried a different USB cable? Are your platform tools and drivers up to date? I assume the bootloader is unlocked, otherwise you wouldn't be able to flash a factory image.
interesting.... i haven't manually flashed the whole image because the web installer is soo easy! I have just recently flashed the radio (had signal issues on december update so i tried the november radio) And it went fine.
Edit: I would maybe see if you have the newest version of ADB
thewraith420 said:
interesting.... i haven't manually flashed the whole image because the web installer is soo easy! I have just recently flashed the radio (had signal issues on december update so i tried the november radio) And it went fine.
Edit: I would maybe see if you have the newest version of ADB
Click to expand...
Click to collapse
Doesnt the firmware come with its own platform tools within the firmware zip? I was thinking it was a self contained package. At least on Windows.
jal3223 said:
Doesnt the firmware come with its own platform tools within the firmware zip? I was thinking it was a self contained package. At least on Windows.
Click to expand...
Click to collapse
No, Not at all. whats in the zip is several image files and a flash-all.bat for windows and flash-all.sh for linux. the .sh and .bat files are just scripts that send commands to adb and fastboot to flash the phone. If you open the bat or .sh file in a text editor you can actually see the commands it issues. It is all reliant on ADB and Fastboot being correctly installed.
thewraith420 said:
No, Not at all. whats in the zip is several image files and a flash-all.bat for windows and flash-all.sh for linux. the .sh and .bat files are just scripts that send commands to adb and fastboot to flash the phone. If you open the bat or .sh file you can actually see the commands it issues. It is all reliant on ADB and Fastboot being correctly installed.
Click to expand...
Click to collapse
Ah, for some reason I was thinking it had platform tools in it. I'll double-check and try to update everything on Windows. On Linux I definitely have everything updated though. Thank you for the advice.
jal3223 said:
Ah, for some reason I was thinking it had platform tools in it. I'll double-check and try to update everything on Windows. On Linux I definitely have everything updated though. Thank you for the advice.
Click to expand...
Click to collapse
if you continue to have trouble with the flash-all you can open it with a text editor and use it as a guide to flash the firmware manually. It'll at least give you an idea why the flash-all fails. I just took another looks at the script and looks like i forgot that the factory image only uses fastboot not adb. Looks like i have fastboot version 28.0.2.... looks like that means i'm a bit behind lol its up to 31.0.3
thewraith420 said:
if you continue to have trouble with the flash-all you can open it with a text editor and use it as a guide to flash the firmware manually. It'll at least give you an idea why the flash-all fails. I just took another looks at the script and looks like i forgot that the factory image only uses fastboot not adb. Looks like i have fastboot version 28.0.2.... looks like that means i'm a bit behind lol its up to 31.0.3
Click to expand...
Click to collapse
I feel stupid now. I updated to the latest fastboot from google platform tools and it is working now. I really appreciate the advice. It seems it's always the simple stuff that gets overlooked. lol
V0latyle said:
Have you tried a different USB cable? Are your platform tools and drivers up to date? I assume the bootloader is unlocked, otherwise you wouldn't be able to flash a factory image.
Click to expand...
Click to collapse
Thank you as well. I should have made sure things were up to date when you mentioned it earlier.
I unlocked the bootloader and installed TWRP, but have not rooted. I have the OTA install of Android 11. I keep getting this message on my phone. At least once a day!
"Package verification failed - the update package being downloaded is not compatible with the current software version on the device"
Please, someone help me to disable this message. It is driving me nuts. Also I don't know if it is wasting bandwidth downloading an update that it isn't able to install.
Did you change firmware regions?
No, I don't even know how to do that, and I doubt such a thing could be done accidentally by unlocking the bootloader and installing TWRP.
Ok, I see now there is an option in Settings called "System Updates", within which one can disable automatic downloading of new updates. I disabled it so we'll see if I stop seeing the annoying message. Though I'm almost certain that this will work. Yes I know I'm a moron for not having found this obvious setting sooner. Oh well, I hope this post will help other folks out there.
Is there any solution to this. I get the notification daily despite disabling the Settings/System Updates?
boltjuice said:
Is there any solution to this. I get the notification daily despite disabling the Settings/System Updates?
Click to expand...
Click to collapse
I ultimately had to root the device and then install the De-Bloater app. Nothing but rooting ever worked.
danahata said:
I unlocked the bootloader and installed TWRP, but have not rooted. I have the OTA install of Android 11. I keep getting this message on my phone. At least once a day!
"Package verification failed - the update package being downloaded is not compatible with the current software version on the device"
Please, someone help me to disable this message. It is driving me nuts. Also I don't know if it is wasting bandwidth downloading an update that it isn't able to install.
Click to expand...
Click to collapse
Its suppose to fail, if its a signature verification, just make sure you have the exact files needed, see if your device is 64arm or 64 etc I had the same problem before fully educating myself with the whole process, let me know if this helps. Do a factory reset fully, redo every step and apply the ota package then apply any other packages like gapps etc but if you're doing a gapps install do it immediately after the lineage ota. With all this being said I hope you've already booted into the lineage recovery' failure to do so will result as an unsuccessful attempt