Database Users

Unlocking and rooting Vzw G2

I am trying to help a friend unlock and root his Vzw G2. I am very familiar with unlocking, rooting and adb commands and have messed with many devices.
As mentioned, he is running the Vzw G2 and here is a screen shot of his settings info.
{
"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"
}
From my research so far, I have found that the G2 boot loader has yet to be officially unlocked. So as of now, we need to use the work around using loki tool which is here:
http:www.androidpolice.com/2013/09/18/da...d-bootloader-on-att-and-verizon-lg-g2-models/
After using the work around, I will then root and flash custom recovery using:
http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
1. Are these the proper tools to be used for this version and model?
2. Is the boot loader workaround Loki necessary in order to root and flash custom recovery.
3. If /when the boot loader becomes unloackable, will the loki patch be able to be reverted into fully unlocking?Thanks for all the tips and advice ahead of time!!
Sent from my Nexus 5 using Tapatalk

bradm23 said:
I am trying to help a friend unlock and root his Vzw G2. I am very familiar with unlocking, rooting and adb commands and have messed with many devices.
As mentioned, he is running the Vzw G2 and here is a screen shot of his settings info.
View attachment 2536367
From my research so far, I have found that the G2 boot loader has yet to be officially unlocked. So as of now, we need to use the work around using loki tool which is here:
http:www.androidpolice.com/2013/09/18/da...d-bootloader-on-att-and-verizon-lg-g2-models/
After using the work around, I will then root and flash custom recovery using:
http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
1. Are these the proper tools to be used for this version and model?
2. Is the boot loader workaround Loki necessary in order to root and flash custom recovery.
3. If /when the boot loader becomes unloackable, will the loki patch be able to be reverted into fully unlocking?Thanks for all the tips and advice ahead of time!!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Use ioroot to root and use custom recovery from this thread
http://forum.xda-developers.com/showthread.php?p=48879826
Sent from chdhsheh fhhdud

Get latest update to my rooted i337ucuamdl with 4.2.2

Hello!
I have AT&T (i337ucuamdl) Samsung Galaxy S4 with 4.2.2 installed. I have rooted the phone years ago and have not touched since. How do I update the phone to the latest 5.XX version? Is it possible to preserve the root? I saw the warning about MDL version that it is not supported. Anyone?
Thank you!

Look here.

Will I be able to use OTA updates with this ROM?
Thank you!

viva_unix said:
Will I be able to use OTA updates with this ROM?
Thank you!
Click to expand...
Click to collapse
If you really still have the mdl bootloader, then you don't want to do an ota update, which will replace the exploitable mdl bootloader with a locked one.
If you have already done ota updates on the phone in the past, then you are already on a locked bootloader, and the above link would be irrelevant.
How did you get 4.2.2 onto the phone without replacing the UCUAMDL bootloader?

{
"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"
}
This is what I have now. Interesting that some applications are saying the phone is not rooted. I have done it 2 years ago. I cannot recall how I did it.
Thank you!

The application tells me I am not rooted.
I guess it is better to repeat the root procedure now.

viva_unix said:
The application tells me I am not rooted.
I guess it is better to repeat the root procedure now.
Click to expand...
Click to collapse
This will root and install TWRP on MDL.
http://forum.xda-developers.com/showthread.php?t=2297900
This will give you stock OC3 lollipop and keep your MDL bootloader.
http://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197

I have rooted the phone successfully yesterday. I got a problem during my backup with FlashFire. Apparently something happened during backup and my microSD card got locked. What ever I do now I cannot format it or write anything on it. Anyone experienced it?
Thank you!

Yeah. I had 2 go bad on me out of the blue. Thankfully, they were SanDisk, which has a lifetime guarantee.
Snapping along on stock rooted 0C4 I337, wishing for some good up to date lollipop ROM's to throw into flashfire

Installed OC3. Do you know if the OC4 is available? It fixes the security bug that I would like to use.
Thank you!

[FAQ] General FAQ about Samsung Galaxy Note 4 Verizon

I'm starting this thread to continue collecting all necessary information about Samsung Galaxy Note 4 Verizon version mobile phone. This thread is aimed as continuation of currently closed sibling thread: http://forum.xda-developers.com/note-4-verizon/general/guide-to-note-4-wip-t2939288.
Ask any questions below and I'll add most common questions to this post.
Information relevance: 02/27/2016
Let's start from main information:
Verizon version of Samsung Galaxy Note 4 (N910V) is carrier version from Verizon, based on Qualcomm Snapdragon 805 CPU and has wide cellular support: GSM, CDMA, LTE.
It is carrier unlocked from the factory - you can use SIM card of any carrier
It has two versions: Retails Edition (RetEd) and Developer Edition (DevEd)
It's likely that you have RetEd. You can check it in the Download Mode (Volume Down + Home + Power)
{
"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"
}
RetEd has locked bootloader and write protection on system partition. That means, that you CAN NOT flash custom ROM, kernel, modifications. Also, there is NO permanent root solution.
Temporary unstable root is available for RetEd both Android Kit Kat and Lollipop via KingRoot 4.8.1. It disappears after reboot.
You can flash any custom firmware to DevEd, including permanent root, but be careful with OTA updates - they may update you to locked bootloader and you'll get Retail Edition.
There is Knox Trip flag. It's 0x0 by default, but once you tried to flash custom firmware - it will set to 0x1. Your warranty is void in this case, and It's impossible to revert that flag back. Also Knox software will stop to work on that cell phone.
Yes, most cool nuts from in this forum are only for DevEd, and not available for RetEd.
Any comments and suggestions are welcomed.

Can someone with Android 5.1.1 and Retail Edition try this APK and place report here: https://github.com/nowsecure/android-vts. I wonder how many vulnerabilities they fix comparing with 4.4 and 5.0.1? I would appreciate it.

Anyone tried to root with Kingroot or other similar apps?

For noobs like me, the current Nokia 5 downgrade and root tutorials are a nightmare. But for me on a personal note, my current irl situation renders the necessary processes difficult.
I'm hastily waiting for HMD Global to roll out support for officially unlocking the phone's bootloader but I'm growing impatient, so I thought of using Kingroot instead, but has it been tried on a Nokia 5 TA-1053 running on Android 8.1.0? I saw a post claiming that the August 2018 security patch has made rooting difficult.. so probably May and below are the best bet on testing Kingroot and other automatic root software. Or perhaps it's just a bootloop waiting to happen?

Try it if you dont have August update... If you get bootloop you can use OSTLA to reinstall firmware, cause your phone TA-1053 Is the most used = More development than 1044,1028... Models, So just try it or rollback to Nougat... Also if you have older build try the method oficina unlock bootloader ($5) tutorial Is posted here

Gemmik said:
Try it if you dont have August update... If you get bootloop you can use OSTLA to reinstall firmware, cause your phone TA-1053 Is the most used = More development than 1044,1028... Models, So just try it or rollback to Nougat... Also if you have older build try the method oficina unlock bootloader ($5) tutorial Is posted here
Click to expand...
Click to collapse
I'm planning on backing up all apps and other data then go test the latest Kingroot APK or KingoRoot in my TA-1053 Oreo with April 2018 update.
Should a bootloop occur, can I simply use OSTLA to reinstall the Oreo or firmware? or is there any steps I should do beforehand? I might as well install the Nougat firmware and root my device on it if Kingroot fails for Oreo.

Just use OSTLA 6.0.2.... you have the correct April build. You can try for first KingRoot or kingo, but I prefer downgrade method ^^

Quick update
{
"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"
}
I tried Kingroot = It gets stuck in 01% and preparing, does not initiate an exploit.
I tried Kingoroot = It goes to 90% then i'm met with a black screen. The phone still functions, i'm using the mobile hotspot tether right now, but I cant seem to do anything like go back to home, or even bring down the notification area. Update: It was just Kingoroot being unresponsive. I was met with a "KingoRoot is not responding" dialogue and an option to close the app, which I did. Now everything is back to normal.

Gemmik said:
Just use OSTLA 6.0.2.... you have the correct April build. You can try for first KingRoot or kingo, but I prefer downgrade method ^^
Click to expand...
Click to collapse
The downgrade method seems to be the only option left if I don't want to wait for the official unlock.
Thanks for the info mate.

Thanks for your info about KingRoot ^^

No OEM unlock option in developer settings

I am somewhat new to this but I can't find any solution to this problem from all the guides out there. I've had my s10+ snapdragon since may 2019, and only recently decided that I wanted to root my phone. The guides for rooting all have a instructions to enable usb debugging (done) and OEM unlocking. However there is no option in the developer settings to toggle OEM unlocking. Other guides say to turn back the system clock to june 2019 to have the OEM unlock option to reappear but when I restart, the date is turned bacl to the last update that I installed (august 2020) and no OEM unlocking toggle.
So it looks like they patched out the OEM unlocking by making it impossible to set the time before that security patch.
Is there another way to root? Or a way to bypass the need for this option? (Maybe im just not understanding how it works enough to proceed without OEM unlocking)
{
"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"
}
Screenshot for context

The only way to root a U.S. galaxy s10 or s10 plus is to pay a guy in China to unlock the bootloader. There is no other way.

StoneyJSG said:
The only way to root a U.S. galaxy s10 or s10 plus is to pay a guy in China to unlock the bootloader. There is no other way.
Click to expand...
Click to collapse
How does one find this man in china?

I am not sure. There used to be info on it here on XDA, but it has since been deleted. There was app too you could use to buy the service, but it's gone as well.
This thread my help you:
How do you root the S10+ SM-G975U Snapdragon?
So basically, I got a S10+ SM-G975U Snapdragon in March and had it until October, when it cracked and the screen broke. However, the phone still functioned but didn't respond to touch, so with the help of a USB-C dongle, an HDMI cable and some...
forum.xda-developers.com

Also found this:
I rooted my US Samsung Galaxy Note 20 Ultra, and here's what I'm doing with it
The Samsung Galaxy Note 20 Ultra has every feature you can think of already and costs $1,299, but I bootloader unlocked and rooted it anyway.
www.xda-developers.com