As many of us have took the recent Kitkat OTA we have a variety of questions. Since there have been many threads asking the same question or related to the same question, I will be making this thread to keep this from continuing.
Question: I have took the Kitkat update, is there any way I can root?
Answer: No, no known exploit works on the RAZR M, unless you have a unlocked bootloader. Then you can flash a custom recovery and flash a superuser.zip and gain root access (Credits - fredsky2)
Question: Can I unlock my bootloader now that I have the kitkat update?
Answer: No, the bootloader has been patched ever since the JB OTA. No exploits will work with the RAZR M.
Question: Will Rootkeeper keep root after the OTA?
Answer: I've yet to see it work so I assume no.
Question: When I take the OTA, will it lock my bootloader?
Answer: No, once the bootloader is unlocked, it cannot be relocked.
Question: Can I downgrade to Jellybean after the Kitkat OTA?
Answer: No, the bootloader is locked, meaning you cannot downgrade or even touch the kernel.
Question: How can I return my phone to stock so I can receive the OTA?
Answer: RSD back to stock.
Question: Where can I get the SBF Files for the DROID RAZR M?
Answer: Here: http://sbf.droid-developers.org/phone.php?device=8
Question: My phone won't let me take the Kitkat ota, what do I do?
Answer: Most likely it's because apps are disabled or root is present. RSD back to stock is typically the solution to the problem. If you want to RSD back to stock but don't want to lose your data, look for the question below.
Question: Can I sim unlock after I take the Kitkat update? (Suggestion Credits - gtmaster303)
Answer: Yes! There is a tutorial with video on how to do it found here: http://forum.xda-developers.com/showthread.php?t=2487863 . MAKE SURE YOU HAVE PROPER DRIVERS INSTALLED!
Question: Can I flash a custom recovery after the Kitkat update?
Answer: No, unless your bootloader is unlocked.
Question: I'm getting a getvar error, how do I fix it?
Answer: In the xml file found in the zip, delete any getvar lines at the beginning of the file.
Question: Can I RSD without clearing data?
Answer: Yes! I asked myself and I'm adding this for others sake. Delete the <step operation="erase" partition="userdata" /> line in the XML file found in the zip. I suggest using it only for when you're on the same version of the update. So 9.30.1 to 9.30.1. Give credits to lem22 for helping me out! http://forum.xda-developers.com/showthread.php?t=2755924
Question: What's are the overall changes/problems with Kitkat? (Suggestion Credits - Strife89)
Answer: There has been a full list provided here: http://forum.xda-developers.com/showpost.php?p=52736453&postcount=1 , click the show button below to see Strife89's list!
Strife89 said:
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
Click to expand...
Click to collapse
If there are any extra questions needed to be added, let me know and I'd be more then willing to add them!
If there is a user having problems that are listed in this thread, just link him here!
I posted both here and Q&A because questions seem to pop up in both places. I'm doing this to clean up the forums a bit better and keep questions from being asked multiple times. Hope this helps and have a great day!
You should add info about Sim unlocking on KK too. Great write up. I will get this thread stickied
Sent from my Droid RAZR M
megaghostgamer said:
As many of us have took the recent Kitkat OTA we have a variety of questions. Since there have been many threads asking the same question or related to the same question, I will be making this thread to keep this from continuing.
(SNIP)
Click to expand...
Click to collapse
May I suggest merging some of the info from this into the post? Linked post is intended to be helpful for those who haven't taken the update yet and are asking what it's like. (Not as numerous as the threads from those who DID take the OTA, but they're there.)
Since I wrote said post: feel free to chop it to bits as needed, if you use it.
gtmaster303 said:
You should add info about Sim unlocking on KK too. Great write up. I will get this thread stickied
Sent from my Droid RAZR M
Click to expand...
Click to collapse
Sim information has been added and credits have been given!
Thank you for the sticky!
Strife89 said:
May I suggest merging some of the info from this into the post? Linked post is intended to be helpful for those who haven't taken the update yet and are asking what it's like. (Not as numerous as the threads from those who DID take the OTA, but they're there.)
Since I wrote said post: feel free to chop it to bits as needed, if you use it.
Click to expand...
Click to collapse
I added your list to the thread, just click the show button and it shows all of your listings of Kk enhancements / disadvantages . Credits were given to you!
This is the response I got from our lovely mod when I tried to get this stickied: The acting moderator in charge of your case has marked the issue as resolved due to the following reason(s):
Not necessary, thread will stay afloat if used actively.
Click to expand...
Click to collapse
. Like he knows what's best for a device that he doesn't use... Oh well I tried
Sent from my Droid RAZR M
gtmaster303 said:
This is the response I got from our lovely mod when I tried to get this stickied: The acting moderator in charge of your case has marked the issue as resolved due to the following reason(s):
. Like he knows what's best for a device that he doesn't use... Oh well I tried
Sent from my Droid RAZR M
Click to expand...
Click to collapse
Typical. I couldn't expect any less. Let there be more pointless threads then. More for them to "monitor".
Also if anyone has any questions that aren't on the list don't be afraid to ask
Sent from my Dell Venue 8
Less KitKat related but since most of the Q/A are root related: What's the last version that the bootloader is unlockable? My on contract phone met a watery death so I snagged a used Razr M, I know it's a long shot but what should I be looking for when it comes? I'm seeing a few different #'s but it looks like 9.8.1Q-66, 98.15.66.xt907.verizon.en.us is the last one right?
(deleted the quote code by accident)
Question: I have took the Kitkat update, is there any way I can root?
Answer: No, no known exploit works on the RAZR M
---------------------------
Imho i think it would be nice to point out if you can or cannot have root if your bootloader is unlocked
Like, 'question: my bootloader is unlocked, does that means i have a green card?'
=p
Overall awesome thread op, thanks for doing this for the razrm community
seasonone said:
Less KitKat related but since most of the Q/A are root related: What's the last version that the bootloader is unlockable? My on contract phone met a watery death so I snagged a used Razr M, I know it's a long shot but what should I be looking for when it comes? I'm seeing a few different #'s but it looks like 9.8.1Q-66, 98.15.66.xt907.verizon.en.us is the last one right?
Click to expand...
Click to collapse
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
GnatGoSplat said:
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
Click to expand...
Click to collapse
Thanks, I know the odds aren't great I just want to be sure before I update, could come with kit kat making version pretty irrelevant.
seasonone said:
Thanks, I know the odds aren't great I just want to be sure before I update, could come with kit kat making version pretty irrelevant.
Click to expand...
Click to collapse
Even if you don't update, be sure to unlock that bootloader before you forget!
Thank you all for suggestions and thank you for answering questions while I was gone camping! I'm back and will be updating thread with credits!
GnatGoSplat said:
Yes, you're correct, that's the last one with unlockable BL. If that's what you have, you are LUCKY!
Also, I've just discovered it's not possible to downgrade to JB after flashing KK even with an UNLOCKED bootloader!
Click to expand...
Click to collapse
It is possible. Just tz partition and one other can't be. If you remove command to flash them from xml, you'll be able to downgrade via RSD.
Odesláno z mého ZTE V807 pomocí Tapatalk
KitKat has root and bootloader unlock!
http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Happy dance!
Update op please
Sent from my Droid RAZR M
Klen2 said:
It is possible. Just tz partition and one other can't be. If you remove command to flash them from xml, you'll be able to downgrade via RSD.
Click to expand...
Click to collapse
Thanks, someone else pointed that out in another thread and I was able to get it to work by removing gpt and tz from the xml.
Related
is current xperia z1c lollipop still have memory leak issue ?
I used lollipop for 2 days already. and it always restart my game (minimized to background) after I open browser to use google (yeah only 2 recent apps displayed. chrome and game apps).
I hate this because my game need long time and heavy bandwidth at loading screen. I never get this problem when I used kitkat. I heard there's xposed module to fix this memory leak issue but my phone isnt rooted.
or is there a way to return to default OS (kitkat) like when I first bought it ? maybe I'll do this way. reset it to kitkat again. but I dont know how.
thanks.
You can flash stock kitkat with flashtool. I should have stock EU . 157 rom somewhere on my pc and can upload it if you want.
Flashing stock rom is pretty easy. Watch a tutorial or something. I can help you a bit more when back home.
Back to your question. I have no idea I'm still running kitkat as L is still not available in my country.
Ephixi4 said:
You can flash stock kitkat with flashtool. I should have stock EU . 157 rom somewhere on my pc and can upload it if you want.
Flashing stock rom is pretty easy. Watch a tutorial or something. I can help you a bit more when back home.
Back to your question. I have no idea I'm still running kitkat as L is still not available in my country.
Click to expand...
Click to collapse
is it working to use your stock rom at my country ? I thought different country have different kind of rom. not sure about this if this is true or not.
flashing stock rom doesnt need root access, right ? and maybe can I also backup current lollipop OS that I have so I can reflash it when it has been fixed ?.
so far what I like from lollipop is when someone call me, I can still use other app because call notification only use small box on top of my current running app. I like this feature very much.
It depends where do you live. If in EU it should be fine. If not I can find a rom good for your location.
No, flashing custom rom does not require rooted device.
I think you don't have to do the backup as you'll be able to just update it again ( at least I think so)
-Vermillion- said:
is it working to use your stock rom at my country ? I thought different country have different kind of rom. not sure about this if this is true or not.
Click to expand...
Click to collapse
Yeah..some features change county wise..
flashing stock rom doesnt need root access, right ? and maybe can I also backup current lollipop OS that I have so I can reflash it when it has been fixed ?
Click to expand...
Click to collapse
Yes. But you dont have to backup the OS. You can download the Firmware using the XperiaFirm Tool >> http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
And here is how to convert the files >> http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Ephixi4 said:
It depends where do you live. If in EU it should be fine. If not I can find a rom good for your location.
No, flashing custom rom does not require rooted device.
I think you don't have to do the backup as you'll be able to just update it again ( at least I think so)
Click to expand...
Click to collapse
is that mean I can flash pre-rooted rom, shared from Xperia Z1 Compact General subforum without unlock bootloader ?
wow then I better use that. I want lollipop+root+xposed but dont want to unlock my bootloader :victory:
getvaisakh said:
Yeah..some features change county wise..
Yes. But you dont have to backup the OS. You can download the Firmware using the XperiaFirm Tool >> http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
And here is how to convert the files >> http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Click to expand...
Click to collapse
wow this is nice info. I've just tried using that xperiafirm tool and it shows my country firmware.
Generally you can root your phone without unlocking bootloader. It worked for me, at least on kitkat. I'm not sure what about the Lollipop though.
You should better ask someone else too as I'm not as experienced and don't want to give you false info.
But if there's pre-rooted rom here and it's working for android L you don't have to unlock bootloader to flash it.
-Vermillion- said:
is that mean I can flash pre-rooted rom, shared from Xperia Z1 Compact General subforum without unlock bootloader ?
wow then I better use that. I want lollipop+root+xposed but dont want to unlock my bootloader :victory:
Click to expand...
Click to collapse
Please give a feedback to me as I also want Lp+root+xposed. *cheers*.
btw, if u wish to stay in KK (since xposed in LP wont work perfectly, seen people commenting on that) there is an easy method to root..
http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-fw-14-4-0-157-lb-ubl-t2977774
Ephixi4 said:
Generally you can root your phone without unlocking bootloader. It worked for me, at least on kitkat. I'm not sure what about the Lollipop though.
You should better ask someone else too as I'm not as experienced and don't want to give you false info.
But if there's pre-rooted rom here and it's working for android L you don't have to unlock bootloader to flash it.
Click to expand...
Click to collapse
yeah. I've tried root without unlock bootloader and it worked. as long as I use correct kernel that can be rooted.
getvaisakh said:
Please give a feedback to me as I also want Lp+root+xposed. *cheers*.
btw, if u wish to stay in KK (since xposed in LP wont work perfectly, seen people commenting on that) there is an easy method to root..
http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-fw-14-4-0-157-lb-ubl-t2977774
Click to expand...
Click to collapse
okay I can get lollipop with root+xposed (all day tried this. I read some tutorial how to do it properly because this is my 1st time doing something like this. so tired ). although I dont know if xposed wont work perfectly like you said because I only use 3 modules so far. App Settings (keep screen on for game I'm playing) and Fix Lollipop Memory Leak and gravitybox (LP).
what I've done :
- downloaded kitkat 14.4.A.0.157 from XperiFirm. and flashed it using flashtool.
- I've realized .0157 can't be rooted for now. so I've used your link that you gave (Root FW 14.4.A.0.157 (LB/UBL) ).
- after get root access, then I installed recovery using Z1C-lockeddualrecovery2.8.11-RELEASE.installer.zip from http://nut.xperia-files.com/
- after that I flashed 14.5.A.0.242_CustomizedFR_Pre-Rooted_Dualrecovery 2.8.10 + Fix Xposed for Lollipop using recovery.
- and flashed Massive debloating and Xposed. links and procedure are also from that pre-rooted rom thread.
so far, no bootloop. dont know if I add some xposed modules again. I heard it will get bootloop if too many xposed modules is installed (?)
-Vermillion- said:
yeah. I've tried root without unlock bootloader and it worked. as long as I use correct kernel that can be rooted.
Click to expand...
Click to collapse
:good:
okay I can get lollipop with root+xposed (all day tried this. I read some tutorial how to do it properly because this is my 1st time doing something like this. so tired ).
Click to expand...
Click to collapse
I know that feel :angel:
I have found a way to root stock LP having ULB. http://forum.xda-developers.com/showpost.php?p=60188952
Now going to try xposed. Since you have, tell me how.. Here is the official thread http://forum.xda-developers.com/showthread.php?t=3034811. Is this where you get info?
although I dont know if xposed wont work perfectly like you said because I only use 2 modules so far. App Settings (keep screen on for game I'm playing) and Fix Lollipop Memory Leak (still dont know if this module will work.)
Click to expand...
Click to collapse
Xposed worked perfectly in KK. I tried more than five modules at a time without the bootloop issue. What I fear is the LP. Havent you checked the dev/Q&A thread of the modules?
what I've done :
- downloaded kitkat 14.4.A.0.157 from XperiFirm. and flashed it using flashtool.
- I've realized .0157 can't be rooted for now. so I've used your link that you gave (Root FW 14.4.A.0.157 (LB/UBL) ).
- after get root access, then I installed recovery using Z1C-lockeddualrecovery2.8.11-RELEASE.installer.zip from http://nut.xperia-files.com/
- after that I flashed 14.5.A.0.242_CustomizedFR_Pre-Rooted_Dualrecovery 2.8.10 + Fix Xposed for Lollipop using recovery.
- and flashed Massive debloating and Xposed. links and procedure are also from that pre-rooted rom thread.
Click to expand...
Click to collapse
wow so much struggle... I have a doubt, why not simply flash that pre-rooted ftf file over the KK? [being lazy to search for the thread]
So how is it feels? Dont forget to share your views and link to the thread..
I heard it will get bootloop if too many xposed modules is installed (?)
Click to expand...
Click to collapse
I dont know that. But I heard that activating some module(s) when some other module(s) is(are) active may cause bootloop in KK.
Hey there, the XperiFirm dev here.
No one answered your question so I will. The answer is: No.
Sony made sure to include the memory leak fix built in (the exact fix that the Xposed module offers) for their Lollipop releases. The Xposed module is pointless.
See attached screenshot. Basically the Xposed module replaces the AOSP function with exactly the same function but with this additional "release()" line. As you can see, Xperia already has this line included.
IaguCool said:
Hey there, the XperiFirm dev here.
No one answered your question so I will. The answer is: No.
Sony made sure to include the memory leak fix built in (the exact fix that the Xposed module offers) for their Lollipop releases. The Xposed module is pointless.
See attached screenshot. Basically the Xposed module replaces the AOSP function with exactly the same function but with this additional "release()" line. As you can see, Xperia already has this line included.
Click to expand...
Click to collapse
wow thanks to coming here :victory:
lol. so it's pointless to install that module because they are same thing exactly. time to uninstall.
actually my game is still restarted after I browsing a little. although I still see a lot of free memory in here. before, I thought this is because of that memory leak issue but I'm wrong.
if only there's module that can prevent lollipop refresh/restart/clear my game at memory when I minimized it at background.
I have the same problem, only with audio apps in the background. Pocket Casts, Stitcher and BeyondPod all crash and stop playing when running in the background, after I do something else like load the game Threes. This never used to happen with KitKat. I've also noticed that iplayer radio gets very jerky and skips back and forth by a quarter of a second continuously as soon as I turn off the screen. [edit - I just listened to it for a few minutes with the screen off and it suddenly cut out. I turned the screen on an the app was no longer in my notifications tray]
If Sony fixed this particular memory leak, what's going wrong with my phone? Could it be related to the fact that I've encrypted if for the first time? I'm getting desperate enough to consider factory resetting and losing everything, because listening to podcasts and playing threes is one of my favourite activities. It's not a demanding game for my year old, top of the line phone. My cheap tablet manages it, and so did the phone on KitKat!
[Q&A] [ROOT] [ROM] [LP] [5.0.1] Stock ROOTED Lollipop for Retail Edition [N910VVRU1B
Q&A for [ROOT] [ROM] [LP] [5.0.1] Stock ROOTED Lollipop for Retail Edition [N910VVRU1BOAF]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] [ROM] [LP] [5.0.1] Stock ROOTED Lollipop for Retail Edition [N910VVRU1BOAF]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
What has this method been tested on?
ODSTZ3RO said:
What has this method been tested on?
Click to expand...
Click to collapse
You seem to be all over the place asking this same question, I'll answer it with the answer I got just by reading the threads that you've posted this question on.
1. He is testing it on the Verizon Note 4 (Non-Dev Edition) FIRST
2. Once its successful ( which it isn't as of this post) he will Attempt to make it work For you AT&T Note 4 Users.
I'm sorry if this seems rude, but you've literally asked this 5 times to my knowledge and I've only been aware of this ROM being developed for 30 minutes as of this post, and I was able to answer your question.
hsbadr said:
IMPORTANT INFORMATION: THE METHOD USED IN THIS THREAD IS SUCCESSFUL ON UNROOTED DEVELOPER EDITION WITHOUT USING A RECOVERY OR AUTOROOT. FOR RETAIL EDITION, IT IS NOT A KINGROOT ISSUE AT ALL. THE LOCKED BOOTLOADER SENDS A FLAG TO UFS CONTROLLER TO WRITE PROTECT PARTITIONS INCLUDING SYSTEM. I AND @gatesjunior ARE INVESTIGATING A WORKAROUND TO REMOVE WRITE PROTECTION.
THIS MAY TAKE A LONG TIME AND IS NOT GUARANTEED !
Click to expand...
Click to collapse
@hsbadr has been very busy trying to get this work for us, I know that you're excited, but please have some more patience.
toxict33n said:
You seem to be all over the place asking this same question, I'll answer it with the answer I got just by reading the threads that you've posted this question on.
1. He is testing it on the Verizon Note 4 (Non-Dev Edition) FIRST
2. Once its successful ( which it isn't as of this post) he will Attempt to make it work For you AT&T Note 4 Users.
I'm sorry if this seems rude, but you've literally asked this 5 times to my knowledge and I've only been aware of this ROM being developed for 30 minutes as of this post, and I was able to answer your question.
@hsbadr has been very busy trying to get this work for us, I know that you're excited, but please have some more patience.
Click to expand...
Click to collapse
I've only referred to this twice one in here and the other in the root progress thread. Also his initial post about this was sent 19 h ago ,I was kind of hoping he'd have all of this sorted out before posting anything. I'm glad he didnt give up like others did ,but even the Dev root thread was closed due to his post and other reasons. Thanks for answering though I actually wanted to know if anyone else was daring enough to test this on their own behalf using the at&t model ,I wasn't referring to him directly. I guess asking the simplest of questions annoys people very quickly ,I'll make sure to be specific and only post once next time.
ODSTZ3RO said:
I've only referred to this twice one in here and the other in the root progress thread. Also his initial post about this was sent 19 h ago ,I was kind of hoping he'd have all of this sorted out before posting anything. I'm glad he didnt give up like others did ,but even the Dev root thread was closed due to his post and other reasons. Thanks for answering though I actually wanted to know if anyone else was daring enough to test this on their own behalf using the at&t model ,I wasn't referring to him directly. I guess asking the simplest of questions annoys people very quickly ,I'll make sure to be specific and only post once next time.
Click to expand...
Click to collapse
Yeah, no hard feelings, next time more info would be better. Don't ever be afraid of writing a long post, If anyone comes to XDA, they know that the more INFO the better they can help you.
do you think he will be able to get the final touches on this method?
I've been following this thread since I first bought my note 4 in December I never posted because I don't have anything informative but I'm very phyced never had a device longer then a week without root; do you guys actually think root will be fully accomplished it seems like we keep hitting roadblock after roadblock? And what's up with this king root v4.0 who developed this and was it actually made for the note t or does it just happen to kind of work for vzw note ?
Flyin350z said:
I've been following this thread since I first bought my note 4 in December I never posted because I don't have anything informative but I'm very phyced never had a device longer then a week without root; do you guys actually think root will be fully accomplished it seems like we keep hitting roadblock after roadblock? And what's up with this king root v4.0 who developed this and was it actually made for the note t or does it just happen to kind of work for vzw note ?
Click to expand...
Click to collapse
Kingroot works for various devices and happened to give temporary root for the note 4. That added a huge filling of the root progress bar for the note 4. Temporary root can lead to good things. These devs work hard and I am sure it will be root-able soon. As for an ETA, "It'll happen when it happens". I'm being positive about it.
I was gong to mention this earlier. Hopefully temp root could assist in removing security from the boot loader, from what I've read the boot loader is what is preventing full root. This would also allow us recovery and ability to flash roms/kernels hopefully unlocking the bootloader is easier now!
m0j0j0j0 said:
I was gong to mention this earlier. Hopefully temp root could assist in removing security from the boot loader, from what I've read the boot loader is what is preventing full root. This would also allow us recovery and ability to flash roms/kernels hopefully unlocking the bootloader is easier now!
Click to expand...
Click to collapse
I wish it were that simple. Sadly, I don't think we will ever have a bootloader unlock. I am sure that we will have root, though. I am fine with just root. XDA devs have worked like crazy to get it and they are so very close.
Patience is the key to success trust me.....
should I do this method
I'm not 100 percent sure should I not do this method yet I don't mind testing it but will I achieve root If done correctly on my Verizon note 4
Flyin350z said:
I'm not 100 percent sure should I not do this method yet I don't mind testing it but will I achieve root If done correctly on my Verizon note 4
Click to expand...
Click to collapse
Temp root only on retail edition. Bootloader fsends a flag to kernel and it write protects cetrain partitions including system, the way I read it. And THAT (write protection) is keeping us from full root because we cant write superuser to system partition
(im dumb and may not have pieced it all together right, but thats how I understand it)
YouTube video kingroot??
Theres a video on youtube posted a few hrs ago by droidmodderx the same guy whp did the april fools joke with note 4 root method: he is claiming the kingroot qorks for note 4 on lollipop with no issues and even roots it on camera with his verizon note 4, i cant tell though if he's running lollipop but it Def is a Verizon note 4; I can't post links cuz I'm a newbie the funny think is I've been using XDA for 2 years just never posted I'm sure if you search YouTube for Verizon note 4 root and change the search options for videos in last week it will pop up from Droidmodderx Root
A DevEd Note4 can be done, Retail can not because of the write protection... Unless you can see if its dev or retail I wouldnt buy into the hype. Read what our devs here are saying about it in the root rom and multisystem threads
Comments on video are filled with people saying it doesnt work and that root is lost on reboot, and that this causes random reboots...
lexbian said:
A DevEd Note4 can be done, Retail can not because of the write protection... Unless you can see if its dev or retail I wouldnt buy into the hype. Read what our devs here are saying about it in the root rom and multisystem threads
Comments on video are filled with people saying it doesnt work and that root is lost on reboot, and that this causes random reboots...
Click to expand...
Click to collapse
What video ? On lolipop ?
Sent from my SM-N910V using Tapatalk
Yes, the video mentioned in OP... this one. You see no real info about the phone other than the word verizon on the backplate, and the fact that he ran Kingroot and Root Checker. But the comments are a mixed bag of claims. Lots say it doesnt work or stops halfway, or causes random reboots..
https://www.youtube.com/watch?v=QicDqTKb_sU
lexbian said:
Yes, the video mentioned in OP... this one. You see no real info about the phone other than the word verizon on the backplate, and the fact that he ran Kingroot and Root Checker. But the comments are a mixed bag of claims. Lots say it doesnt work or stops halfway, or causes random reboots..
https://www.youtube.com/watch?v=QicDqTKb_sU
Click to expand...
Click to collapse
Oh this video yea I saw this one. I thought that was from the LP thread here.
I see the instructions however I would prefer seeing video so I don't screw anything up
@hsbadr has said to wait for final instructions and the accompanying video. Im twitchy... I wanna try it anyways, but I dont fancy the idea of a (possibly) compromised device. Ill wait til we get fixed up with the prerooted rom and multisystem. Hell... I've waited this long already. Ive almost forgotten what i wanted root for with some of the non-root replacements Ive found.
lexbian said:
@hsbadr has said to wait for final instructions and the accompanying video. Im twitchy... I wanna try it anyways, but I dont fancy the idea of a (possibly) compromised device. Ill wait til we get fixed up with the prerooted rom and multisystem. Hell... I've waited this long already. Ive almost forgotten what i wanted root for with some of the non-root replacements Ive found.
Click to expand...
Click to collapse
The instructions have been already updated (works perfectly on unrooted Developer Edition), but Samsung implements write protection on the system partition for Retail Edition only (tripped by the locked bootloader) & so, all our changes get lost after a reboot (even if you deleted directories in /system, they'll come back after rebooting the device). We're working on a workaround...
lexbian said:
@hsbadr has said to wait for final instructions and the accompanying video. Im twitchy... I wanna try it anyways, but I dont fancy the idea of a (possibly) compromised device. Ill wait til we get fixed up with the prerooted rom and multisystem. Hell... I've waited this long already. Ive almost forgotten what i wanted root for with some of the non-root replacements Ive found.
Click to expand...
Click to collapse
Same never went this long without it. Lollipop got me a little further but I'm already getting twitchy
Verizon Wireless Technician and Samsung Galaxy Note Series Owner
Hello, I am new to XDA and I have an un rooted HTC 10 international unlocked model on software 3.16.401.2. My HTC used to have excellent battery before the Oreo update. I did multiple tests and checks to see what the issue could be and have ruled out rogue apps or hardware issues.
I have never rooted any of my phones before but I am desperate as the battery has tanked so badly
NOW TO THE POINT
I am looking for advice on:
1. If rooting my device and using a custom version of Oreo will actually improve battery issues. (Are there others who rooted for the reason I'm considering, if so did you actually notice an improvement?)
2. If so, what is the safest/most newbie friendly method of me doing this.
PLEASE NOTE: I am very satisfied otherwise with the standard features. I have switched between htc sense launcher and smart launcher but otherwise use the phone very conventionally. I am not opposed to different features but I essentially would like to have as close to what I have now without the battery issues.
(Sorry in advance if there are 100 similar threads I'm already very concerned I'll mess
this up and manage to brick my phone so I am just trying to get clear information in a thread that's not oversaturated and is written in a layman friendly (PLEASE ) way)
Thank you everyone!
SMSJA said:
Hello, I am new to XDA and I have an un rooted HTC 10 international unlocked model on software 3.16.401.2. My HTC used to have excellent battery before the Oreo update. I did multiple tests and checks to see what the issue could be and have ruled out rogue apps or hardware issues.
I have never rooted any of my phones before but I am desperate as the battery has tanked so badly
NOW TO THE POINT
I am looking for advice on:
1. If rooting my device and using a custom version of Oreo will actually improve battery issues. (Are there others who rooted for the reason I'm considering, if so did you actually notice an improvement?)
2. If so, what is the safest/most newbie friendly method of me doing this.
PLEASE NOTE: I am very satisfied otherwise with the standard features. I have switched between htc sense launcher and smart launcher but otherwise use the phone very conventionally. I am not opposed to different features but I essentially would like to have as close to what I have now without the battery issues.
(Sorry in advance if there are 100 similar threads I'm already very concerned I'll mess
this up and manage to brick my phone so I am just trying to get clear information in a thread that's not oversaturated and is written in a layman friendly (PLEASE ) way)
Thank you everyone!
Click to expand...
Click to collapse
1: No, routing your OS won't be the fix for your battery problems.
2: it's the way everybody had to do it, unlock the bootloader, flash TWRP with fastboot and flash a custom rom. It's all explained in the guides section.
Mr Hofs said:
1: No, routing your OS won't be the fix for your battery problems.
2: it's the way everybody had to do it, unlock the bootloader, flash TWRP with fastboot and flash a custom rom. It's all explained in the guides section.
Click to expand...
Click to collapse
Thanks for your response! I am currently doing more research now after reading your helpful comment ?. Would I still be able to use the phones default launcher (HTC sense in my case) after unlocking the bootloader and flashing a custom rom or will every part of the UI now be different?
Mr Hofs said:
1: No, routing your OS won't be the fix for your battery problems.
2: it's the way everybody had to do it, unlock the bootloader, flash TWRP with fastboot and flash a custom rom. It's all explained in the guides section.
Click to expand...
Click to collapse
What about gaining S-Off and reverting to Nougat and Nougat firmware? Seems with all the battery complaints that came along with the Oreo update, there is some validity in asking such a question.
SMSJA said:
Thanks for your response! I am currently doing more research now after reading your helpful comment ?. Would I still be able to use the phones default launcher (HTC sense in my case) after unlocking the bootloader and flashing a custom rom or will every part of the UI now be different?
Click to expand...
Click to collapse
Yes as long as you flash a sense based rom the UI will not change.
product26 said:
What about gaining S-Off and reverting to Nougat and Nougat firmware? Seems with all the battery complaints that came along with the Oreo update, there is some validity in asking such a question.
Click to expand...
Click to collapse
You can also downgrade without s-off but it's a bit trickier, there is a dedicated thread in the guides section that covered this. Have a look there for all info, there is also a video in that specific thread that shows how to do it.
https://forum.xda-developers.com/htc-10/how-to/downgrade-problems-downgrading-htc-10-t3735658/page48
But the basic question is also relevant, yes you can gain s-off and downgrade by flashing the firmware and then the ruu or a custom nougat rom.
Guides will be published shortly
Credits to
@j4nn
@Inerent
@漠云
@Markus
@vlad48
Permanent Root, Magisk, Twrp and Bootloader Unlock was achieved for all V50 koreans
Other LG Snapdragon 855 should follow in the next days/week. Stay tuned for guides and news.
until then follow our telegram channel for more chat like discussions...
Any news on this, here in Oz we've been abandoned by LG to having only Android 9...
Everytime we ask about it LG says it's up to Google to release the update... What a crock since the rest of the world has it, we are the ONLY country yet to get Android 10...
This might give a little love to our forgotten, EXPENSIVE FLAGSHIP...
Last time I'm buying LG I'll tell you that...
ultramag69 said:
Any news on this, here in Oz we've been abandoned by LG to having only Android 9...
Everytime we ask about it LG says it's up to Google to release the update... What a crock since the rest of the world has it, we are the ONLY country yet to get Android 10...
This might give a little love to our forgotten, EXPENSIVE FLAGSHIP...
Last time I'm buying LG I'll tell you that...
Click to expand...
Click to collapse
He's already shown that it's possible, give them time to develop the steps/guide to do it. Don't ask for ETAs, basic XDA rule.
Hi guys! Please be patient as there were some bricked devices.
All korean V50 can have this and also some G8.
If you dont have patience, join telegram group V50 and ask for help from Vlad48 aka VL48. White user also has the knowledge and also contributed a lot to this, but he doesnt speak english that good and you may get confused in doing things that will brick your phone.
I'm waiting to make an ALL IN ONE guide with everything in that ADB folder so that we will donwload just one file.
Almost all bricked devices so far were because of WRONG file placement inside adb folder if you believe it ...
That's no worries, not wanting an ETA.
Sorry, went off on a tangent there earlier due to overwork and night shift.
As I said, here in Oz we've been stranded with Android 9, security update is for Oct 19, with no Android 10 release in sight and only excuses and buck passing from LG.
Do we know if this will allow Android 9 to be rooted and, finally, be updated to the latest OS?
Cheers guys...
ultramag69 said:
That's no worries, not wanting an ETA.
Sorry, went off on a tangent there earlier due to overwork and night shift.
As I said, here in Oz we've been stranded with Android 9, security update is for Oct 19, with no Android 10 release in sight and only excuses and buck passing from LG.
Do we know if this will allow Android 9 to be rooted and, finally, be updated to the latest OS?
Cheers guys...
Click to expand...
Click to collapse
Yeah, there may be an issue there... You can only use temp root on Android 10. Specifically what phone model (carrier/region that the phone is from) do you have? I don't mean your current carrier necessarily, just the branding of your model.
antintin said:
Yeah, there may be an issue there... You can only use temp root on Android 10. Specifically what phone model (carrier/region that the phone is from) do you have? I don't mean your current carrier necessarily, just the branding of your model.
Click to expand...
Click to collapse
It's the LM-V500EM, like Europe, however, it is distributed exclusively through Australia by Telstra.
This means we can't upgrade using another country's firmware but also, as we aren't part of Europe and UK, we can't unlock the bootloader. :crying:
Again, every time LG is asked about newer firmware the finger is pointed at Google.
When Telstra is asked, mostly just the sound of silence but if you do hear whispers it's no firmware has as yet been supplied and to check with the manufacturer of the device.
Google also has the advice Telstra give about the updated firmware which puts LG in the drivers seat and they're still sitting at the bar at the start of happy hour as far as Australia is concerned, and every hour is happy hour..
Hence we need to be able to unlock the bootloader and root to update our expensive and, supposedly flagship device.
You understand the frustration and impatience...
should we be looking for a brand in particular of the phone beside the korean one? Plannign to upgrade my v30
kventura said:
should we be looking for a brand in particular of the phone beside the korean one? Plannign to upgrade my v30
Click to expand...
Click to collapse
Hi, i recommend v50 koreans due to battery life and 5g.
G8 Sprint is now bl unlockable at lower price and nice compact form factor
Just got my v50 u+ recently
Cant wait for the script
Can't wait for these guides, thank you to all involved!
If I may make a request, perhaps a guide on how to hide root, using Magisk, so that banking apps can still be used?
Thanks again
shadders said:
Can't wait for these guides, thank you to all involved!
If I may make a request, perhaps a guide on how to hide root, using Magisk, so that banking apps can still be used?
Thanks again
Click to expand...
Click to collapse
That's a pretty generic guide; just use magisk hide and the props config module, but lots of modules may break safety net
antintin said:
That's a pretty generic guide; just use magisk hide and the props config module, but lots of modules may break safety net
Click to expand...
Click to collapse
I see thanks. If a module breaks safety net, does uninstalling that module mean the device passes safety net again? Or is the device just permanently marked as unsafe?
shadders said:
I see thanks. If a module breaks safety net, does uninstalling that module mean the device passes safety net again? Or is the device just permanently marked as unsafe?
Click to expand...
Click to collapse
You might have to wipe data for all the Google apps (or possibly even factory reset), but it shouldn't be permanent
antintin said:
You might have to wipe data for all the Google apps (or possibly even factory reset), but it shouldn't be permanent
Click to expand...
Click to collapse
I see thank you
Inerent said:
Guides will be published shortly
Credits to
@j4nn
@Inerent
@漠云
@Markus
@vlad48
Click to expand...
Click to collapse
Not to sound like a jerk, but I do think it's a valid question... what is the point of creating a thread promising a comprehensive 'All in one guide' to be 'released shortly', and also posting in the other root thread that a guide will be available, and then nearly a month later, there is still no guide? Again, I don't want to sound like a jerk because you're trying to help, but so far, you have just made empty promises and gotten peoples hopes up but not actually provided anything
(again, not trying to sound harsh, just posting as someone who has been keeping an eye on this for a month and now feeling frustrated)
Sorry, dont have time for this, anyone can make a new thread or admin delete this...
Until then, all is available on telegram.
Inerent said:
Sorry, dont have time for this, anyone can make a new thread or admin delete this...
Until then, all is available on telegram.
Click to expand...
Click to collapse
very disappointing after waiting so long...
antintin said:
Yeah, there may be an issue there... You can only use temp root on Android 10. Specifically what phone model (carrier/region that the phone is from) do you have? I don't mean your current carrier necessarily, just the branding of your model.
Click to expand...
Click to collapse
Samsung A715F telcel mexico (Android 10)
Can we root it , unlock it. Etc? Thanks in advance
Sent from my [device_name] using XDA-Developers Legacy app
I have just unlocked bootloader on the latest Fold 3 F926b Beta and the camera is fully functional!!! - Seems sammy have finally done away with this silly thing lol!!
Please see vid below - i will upload another showing proof of boot splash red text then camera working
here is a video showing the angry warning text and the device booting and me using the camera
So there we have it! hopefully development will take off a bit now and also apologies!!!
Had i bothered to tinker in the last couple of weeks we may have known this earlier!!!!
Finally........
After testing i now know which file can fix the camera on B1 - its to risky to flash it on android 11 as i almost lost download mode SO I AM NOT GOING TO BRING ATTENTION TO THIS FILE JUST YET - THERE WILL BE ONE LOON WHO FLASHES IT ON A11 WHILST ROOTED AND LOOSES DOWNLOAD FOREVER
The camera issue was actually "fixed" in beta 2 ZUKA!!!
- i have tested this on B1 where camera broke on BL unlock and also on android 11 fixing the camera issue but causing download mode issuses.
What this means is that we have something to possibly bite back with should sammy lock down the cameras again
Big thanks to @dr.ketan for the help in finding this
Does f926n have to wait until Android 12 is updated to brush the machine normally, and the camera will not be locked
MartinJiao said:
Does f926n have to wait until Android 12 is updated to brush the machine normally, and the camera will not be locked
Click to expand...
Click to collapse
Flash beta2 or 3 for the N model and you should hopefully find you can unlock bootloader and camera will work.
We do not have root on beta yet though so it maybe a week or two till we can be rooted and use camera
Great for international folks. Meanwhile *cries in US*
domineus said:
Great for international folks. Meanwhile *cries in US*
Click to expand...
Click to collapse
do you still have cam lock on the US variant on Beta 2 or three?
Can anyone in Korea who has had the stable OTA please try and unlock bootloader to see if camera works?
exocetdj said:
do you still have cam lock on the US variant on Beta 2 or three?
Click to expand...
Click to collapse
it doesn't show up in the settings but that isn't a huge surprise
I'm pretty sure the ZUKG rom is the beta, isn't it?
You may find once the stable release hits out Folds this will once again be locked down and the cameras won't work once the bootloader is unlocked.
exocetdj said:
I have just unlocked bootloader on the latest Fold 3 F926b Beta and the camera is fully functional!!! - Seems sammy have finally done away with this silly thing lol!!
Please see vid below - i will upload another showing proof of boot splash red text then camera working
Click to expand...
Click to collapse
Awesome
exocetdj said:
I have just unlocked bootloader on the latest Fold 3 F926b Beta and the camera is fully functional!!! - Seems sammy have finally done away with this silly thing lol!!
Please see vid below - i will upload another showing proof of boot splash red text then camera working
Click to expand...
Click to collapse
Please can you post a link to the F926B rom that you used?
I cant find it anywhere.
Thankyou in advance
ParadoxLogic said:
Please can you post a link to the F266B rom that you used?
I cant find it anywhere.
Thankyou in advance
Click to expand...
Click to collapse
Yeah, I can't find that either.
I would also love a simple guide of some sort for stupid old people like me, how to root that unlocked boot loader beta version
Thanks in advance
Edit:
I wonder if that's the link for Beta 2 for 926B
Edit 2:
Aaaand I wonder if this is the link for Beta 3?
we cannot root beta yet (or i have been unable too and no one else has even bothered trying lol)
I think we will stand a better chance when we have full firmware and source code but early indications from the "stable" korean version is that Samsung are still killing cameras on bootloader unlock
exocetdj said:
we cannot root beta yet (or i have been unable too and no one else has even bothered trying lol)
I think we will stand a better chance when we have full firmware and source code but early indications from the "stable" korean version is that Samsung are still killing cameras on bootloader unlock
Click to expand...
Click to collapse
I tried unlocking BL of F926N (not B) after installation of OTA update a12 (BUL4) released on 12/15, but camera was still dead as mentioned above. And rooting via magisk didn't work well either. So I reflashed firmware of a11 (AUJ7) using Odin and rooted without TWRP.
EDIT: Samsung have really redeemed themselves! my moaning below is now moot
This all confirms that this has been a deliberate move by Samsung to impede the modding community
yes they have done this before with knox etc etc but killing a fundamental piece of the device's hardware just because they don't like rooting is wrong and also probably ILLEGAL if they are not advising in the Download mode screen that this is what will happen.
There has been no statement as to why, they are behaving like the insulting kid in class who hides behind the teacher when the class revolts at their actions lol.
I invite Someone from Samsung to explain whats going on and why they are doing this of course, but silence will prevail with all things Fold 3 (much like it did with the first "fix" that was trumpeted on twitter months ago)
I am hopeful that the workaround i have found with @dr.ketan will see us good for a bit when the release firmware for android 12 eventually lands in Summer of 2022 (yes im being a grumpy sarcastic child today lol) but that will no doubt be patched by these Sammy psychopaths against modding eventually.
Edit - now moot
exocetdj said:
Ill be selling my entire "samsung ecosystem" for a Pixel 6 pro come January i expect -> especially if this retarded madness spills over onto the S22 line
Click to expand...
Click to collapse
VERY much looking to jump the Sammy ship as well. Just seems like they aren't interested in listening to the customers...even us. I truly believe they are butt-hurt that the dev community makes better ROMs and improves their products.
But the Pixel and Sony are looking WAY better.