I have stock lollipop rooted with safestrap, but am wondering if it's possible to unlock the bootloader on my CID 11 to put a custom ROM on this. This thread from Mar 2016 was only for CID 15, but maybe there's been a breakthrough since then. Thanks!
androidman807 said:
I have stock lollipop rooted with safestrap, but am wondering if it's possible to unlock the bootloader on my CID 11 to put a custom ROM on this. This thread from Mar 2016 was only for CID 15, but maybe there's been a breakthrough since then. Thanks!
Click to expand...
Click to collapse
There is talk on a few other forums regarding this question for Unlocking the Bootloader on a G900V with CID 11 also with KitKat installed but, there's no Guides/Tutorials on how to do this.
The following thread is one of the more prominent threads i, personally, monitor from time to time.
https://forum.xda-developers.com/showthread.php?t=3561529
Based upon what I've seen within the XDA Forum, as well as a few other Forums, the final verdict is (basically the bottom line)...
It's a work in progress with some promising chatter and ideas but, nothing solid has been announced or mentioned.
Those with the G900V and CID 11 are still only able to Root the device and unable to unlock it yet.
Keep in mind that this looks like it's still something that is continuing to be discussed and as long as there's still a want/need for it, only time will tell.
I hope i had explained this okay...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
I have bought verison Droid razor m already on kitkat 183.46.15 and now I want to unlock its bootloader.
I have searched a lot but didnt find any thing but bricked it three times. please help me with complete process My phone is rooted.
Thanx
any developer here can't wait now
See this post.
"If your kernel date is June 3rd or later, you cannot unlock your bootloader."
There's a link in that post that will tell you how to determine the date of the kernel.
See the first post in the first Sticky in the General section: If you have firmware 182/183.46.15, there is currently no way to unlock your bootloader.
Dogora said:
See this post.
"If your kernel date is June 3rd or later, you cannot unlock your bootloader."
There's a link in that post that will tell you how to determine the date of the kernel.
See the first post in the first Sticky in the General section: If you have firmware 182/183.46.15, there is currently no way to unlock your bootloader.
Click to expand...
Click to collapse
Annoying my kernal build date is july 29th with a locke bootloader my phone is usless Developers please do something find a way
You don't need developers, you need security professionals.
Motorola has had the hardest bootloaders to exploit. In fact, Dan Rosenberg was the first to unlock moto bootloaders starting with the Droid Razr M/HD & Atrix HD.
The exploit he used was quickly patched by Motorola on the 2nd Jellybean firmware. So the users that were unlucky and missed the Motopocalypse exploit were S.O.L. for a very long time.
When KitKat finally came out, it was discovered that Motorola forgot to include the TZ patch (with the first .10 firmware) which allowed for Motopocalypse to work again . When discovered, Moto quickly patched and pushed the second build of .10 and finally closing it off with the last .15 firmware.
At this point Razr M users are really lucky to even have root, and I doubt anybody is working on, or planning to work on, a bootloader unlock exploit for this aging device.
Sent from my XT1031
There was one root process that changed the kernel date to may something for a couple days. I never thought about it. But seems how I'll be unbrick in my phone and rerooting with the same method I'll be giving it a go this time to double check if it's possible by any means and will post the results for everyone later today
Like I promised. I used hydrogen to root. Re ran it after it rebooted the first time it changed the kernel back to July 29th and this time since I was rooted I didn't reboot. Now trying to figure out how to keep the kernel this time
Rooted my Verizon s5 with the working method on this site, CID 11, now running android 5.0, PB1....I am wondering what updates I need to install to keep my phone and info secure since I do a lot of online purchases..thanks
adrian4064002 said:
Rooted my Verizon s5 with the working method on this site, CID 11, now running android 5.0, PB1....I am wondering what updates I need to install to keep my phone and info secure since I do a lot of online purchases..thanks
Click to expand...
Click to collapse
Your best bet is to post this question within the following thread.
http://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
So I wanted to discuss this with you guys, if you've been flashing phones for a while you've probably seen this error once or twice or maybe a 100 times
I guess this thread is a bit missplaced but seeing as there is no TWRP forum I guess I have to post it here
So what I want to do here is to discuss error 7 and se if there's any way to get around it
For example right now I have a Galaxy S5 Verizon (SM-G900V) which i cant install official lineage build on because of error 7 even though this model is officially supported by LOS and I'm sure that im not the only one having this problem
I have tried this 'solution' on several phones but I have never gotten it to work, it always leads to some other errors
https://forum.xda-developers.com/showthread.php?t=2522762
So yeah I wanna hear what you guys have to say, have you ever encountered it? Have you ever gotten around it? Why is there no way to just force install an update seeing as the end responsibility is on the user anyways?
Eklondh said:
So I wanted to discuss this with you guys,.........
Click to expand...
Click to collapse
Regarding TWRP for the G900V device...
The following link is to the Official TWRP site specific for the klte downloads that should be where you need to obtain the Recovery download images.
https://dl.twrp.me/klte/
The following is the Official TWRP thread that's specific to your device and variants for support and guidance as well.
https://forum.xda-developers.com/showthread.php?t=2727406
The following is the FAQ page from the Official LineageOS Wiki that includes the Error 7 topic as well.
https://wiki.lineageos.org/faq.html
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
I'm trying to unlock the bootloader of my LG v20 h918 I just picked up this phone yesterday and would love to root it but it came already updated to Oreo and the latest security patch is this phone still rootable?
Please look for similar threads/guides to answer your question before posting, this was literally just asked and answered yesterday, just a couple of threads before yours. Anyway its still perfectly rootable, unlock the bootloader in fastboot mode and then proceed to the guide or reworded guide of the same process
This is a Bug bounty thread to get root on ZTE Blade A5 2019.
Thanks to ZTE this model doesn't have bootloader unlockable, so root should be made through an exploit. I'm sick of their excuses, i personally believe they were instructed by the governement to do things this way and use eula and "security" as excuse, same happened to axon 7, they said, it's because of security, and i think this is a lie (and i would say i'm not the only). Is unacceptable that experienced people that want to mod their devices can't because to unlock the bootloader you need a signed image, is unacceptable, unlocking bootloader is to flash unsigned images and you tell me that to unlock it i need a signed image from zte or the signature itself? Well i call this "lock users out of their own devices".
But returning on the root topic: I would suggest or CVE-2020-0041:https://github.com/bluefrostsecurity/CVE-2020-0041 that allowed some xperia to get root or CVE-2019-2215:https://github.com/grant-h/qu1ckr00t that has a 32bit version available here:https://forum.xda-developers.com/t/root-with-cve-2019-2215.3979341/post-80748711 another thing that could be tried is this:https://research.nccgroup.com/2022/09/02/theres-another-hole-in-your-soc-unisoc-rom-vulnerabilities/ (note that if we use this maybe would be possible to make an universal root method for unisoc getting bootrom context, but i'm not sure about that.
I also extracted kallsyms so the dev doesn't have to:https://www.mediafire.com/folder/uvde49kcna40o/ZTE_A5_2019_Stuff
Kernel Sources included since zte mirror is really slow.
N.B. Is suggested to flash an old firmware, for example Claro one has 5 January 2019 patch and because of this is vulnerable to qu1ckr00t, also it has fastboot and no updates at all.
if some dev is interested please contact (i'm not a dev so i would need one), also if people want this root to go ahead donate (I will also obliviously), you can tell how much you want to donate and after you can donate to the developer directly (these rules can be changed if the dev is trusted i guess), nb i'm not responsible for any issues, i hope won't succeed nothing badly.
I say this because i also had bad experiences.
About donations i would suggest to do those after the root process is verified to work.
I would stay fine with only a temp root
Hello, I noticed your thread while I was using my fresh script to warp pages fast. I was a person who was involved into exploiting several devices, and You can get yourself a root on this device if I put in enough time into this, Please, provide contacts so I could get in touch with you. We will discuss prices and other stuff somewhere else privately.