I just released Loki, a set of tools for developers and users to flash custom kernels and recoveries on the AT&T and Verizon branded Samsung Galaxy S4.
The tool is available at:
https://github.com/djrbliss/loki
The technical details on how the exploit works are described at:
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
This is a support thread that I will check regularly until I decide to hand over support to the community. Feel free to ask any questions, and I may add the answers to this post. As a guideline, if it's a question that's already been answered in this thread or in the README for Loki, I will ignore it.
Does this make any permanent changes to the device?
No permanent changes are made to your device when using loki_flash. The bootloader itself is untouched. By restoring the original system, boot, and recovery images (via Odin or otherwise), the device will be in a stock state.
Can this be patched?
Absolutely. Any update that includes a new aboot will almost definitely cause your custom kernel or recovery to fail to boot without running it through loki_patch again, and if the update contains a fix for the vulnerability Loki exploits, it may permanently prevent using the tool. It's possible for Samsung to ship an update that prevents downgrading aboot to a vulnerable version, so I recommend avoiding installing any OTA updates without confirmation that it's safe.
What about the bounty?
As usual, I encourage anyone looking to donate (as part of the bounty or otherwise) to give their money to a reputable charity organization instead. If you insist on donating to me, I'm sure you can find my Paypal account somehow.
This all seems complicated. What about a step-by-step guide?
These tools are primarily intended for developers, who will be able to use them and provide ordinary users with easy ways to flash custom ROMs. Be patient, I'm sure your favorite ROM developer will come up with something for you.
I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
So this is just like kexec?
This is similar to kexec in that it works around a locked bootloader, but this approach is much more flexible and robust. Kernel and recovery developers can build their projects just as they would for an unlocked device, run the final result through Loki, and then it's ready to be flashed. No hackery and brokenness required.
Thanks!!
Sent from my SAMSUNG-SGH-I337 using xda premium
is this similar to htc dev which doesn't truly unlock "s-off" the device? i assume your method just circumvents the locked bootloader? the way i read what your tool accomplishes is for us to flash a recovery and kernels but doesn't actually touch the locked bootloader status?
thanks for your work. also let the games begin!
Thank you very much!!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Very much appreciated!
By the time I get back from work, I'm pretty sure there'll be at least two recoveries and three roms prepared
Wooooot!!! Thanks man.
Awesome! Finally devs can start releasing some ROMs!
hopefully someone can make a toolkit and make this a one-click unlock/root
Thanks so much! :good:
thanks dude.
RawisTheGameHhH said:
hopefully someone can make a toolkit and make this a one-click unlock/root
Click to expand...
Click to collapse
This or a step by step guide.
Theres already recovery available...
But thank you Dan, now all this bootloader madness can finally stop!
so we can flash a recovery and kernels with this tool but what about radios? can those be flashed with a locked bootloader? i swore they couldn't.
You are the MAN. A charity will be finding my donation per your recommendation.
Thanks again for all the great work.
Oh man, I'm dying here. I don't get off work for another ~6 hours! And I don't have admin access on my work computer, so no adb.
So, we have a patched recovery now, but custom kernels also have to be patched, correct? So it would be a bad idea to adb the recovery and then immediately try to use it to flash one of the roms that are already out there?
mattdm said:
Oh man, I'm dying here. I don't get off work for another ~6 hours!
So, we have a patched recovery now, but custom kernels also have to be patched, correct? So it would be a bad idea to adb the recovery and then immediately try to use it to flash one of the roms that are already out there?
Click to expand...
Click to collapse
i wouldn't try flashing any roms yet.
YES!YES!YES!
Dan, You are The Man!!! Thank you so much. May your thanks meter need a fire extinguisher before the day is done....lol.:good::good::good::highfive::highfive::highfive:
did a nadroid backup, and it is doing multiple archives, is there a setting I missed?
nevermind, I stand correct, nice, very nice, thanks goes out to everyone involved.
Solid.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Related
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Skrilax_CZ said:
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Click to expand...
Click to collapse
No problem. I'll try to put it in "laymans" terms.
Manufacturers don't want you mucking with things. It causes more tech support for them, and also a bad image reputation when stupid people screw things up.
So what they do, is change bootloaders, the part that tells the tab, that the os they are loading, is 100% Acer. If it's not, it's just going to give you a silly face.
So we, here in the Acer community, try to find a way around the bootloader. And invent ways to install a operating system other than Acer.
It's an ongoing battle it seems. We find a way around it, Acer changes the rules, so we have to find another way.
The thing is, our dev's are smarter than their devs. Even HTC gave up, and just offer bootloader unlocks. Besides, they take our innovations, and incorporate them into their newer releases.
So the point is, if you buy a 500, or a 501, XDA community will give the means to unlock it. Root, so we say. And people will help you get it running right.
Here at XDA, we have many roms, from plain rooted stock roms, to cooked roms with OC kernels.
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Currently on a new A500 with root and kernel. Manufactured in December 11. whole process took an hour. Hope this helps.
Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
IIRC, only 3.2.1 locked the bootloader, so even if your a500 comes with 3.2 you're safe.
That said, even with 3.2.1 and a locked bootloader, there is a downgrade trick that allows you to go from 3.2.1 (or 3.2, or 3.1) to 3.0 and run an app called iconiaroot and acer recovery installer. Iconiaroot is like z4root, VISIONary, gingerbreak, etc and recovery installer installs CWM recovery from within android. After doing all this you can flash any rom or kernel you want.
Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
YES if your a500 has Stock android 3.2 or above.. you will have to fallow the downgrade rom flashing.Then you can flash any rom of your choice . there are several threads on this forum explaining how to do this..
Do a search for the thread by Timmy Dean.. his method i think has been called the easiest. It flashes your tablet to a rooted 3.21 stock rom thru adb . from your windows computer..
Acer has yet to plug this hole. So i would not take ANY OTA UPDATES. Im looking for ics if ever releases to plug such holes in the boot loader and stop its magic .
Happy Flashing just please understand everything before proceeding.. there are enough help i bricked my iconia threads.. Boohoo i hate to see anyone do that to such a expensive device..
Thanks. Ordered a piece
So basically I need to store UID, first x bytes in mmcblk0 (for the mmcblk0_start) from sc2k thread (http://forum.xda-developers.com/showthread.php?t=1129873) and I'm pretty much brick safe (should I screw both kernel & recovery).
Happy Flashing
That in theory will give you the resources to recover . BUT BY NO MEANS A Get of of trouble free pass..
do not flash nothing you don't trust and Fallow all instructions Carefully.. You sound well on your way to Making the best of your tablet...
Enjoy your time on xda Iconia forum. There are some awesome people on here. NO im not including myself in that .. Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
erica_renee said:
Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
Click to expand...
Click to collapse
Aren't we all..... Not necessarily a chic though...
Allright, all went smooth (was 3.2 preinstalled). Thanks all.
you are very welcome..
Its simple easy with just a bit of reading up front..
Hey guys. If the title didn't apply, I am new to this forum. I just came from The evo 3d. Switched to this phone. While I think its very cool, I noticed that this forum does not have many ROMs or mods to play around with. That's ok. This phone is only a couple months old so I'm sure with time, more and more development will occur.Anyway to my point. I noticed that my phone is very different than my evo 3d than what I was used to as far as just flashing a recovery and installing a rom or kernel inside recovery. Gaining full s-off etc..
My questions is can someone show me what's different as far as gaining s-off
Method of installing roms
If someone would be kind to point me in the right direction that would be great. Thank you.
Jsparta26 said:
Hey guys. If the title didn't apply, I am new to this forum. I just came from The evo 3d. Switched to this phone. While I think its very cool, I noticed that this forum does not have many ROMs or mods to play around with. That's ok. This phone is only a couple months old so I'm sure with time, more and more development will occur.Anyway to my point. I noticed that my phone is very different than my evo 3d than what I was used to as far as just flashing a recovery and installing a rom or kernel inside recovery. Gaining full s-off etc..
My questions is can someone show me what's different as far as gaining s-off
Method of installing roms
If someone would be kind to point me in the right direction that would be great. Thank you.
Click to expand...
Click to collapse
Welcome to the RAZR m....sorry i can't help you, i would if i could
Sent from my XT907 using xda app-developers app
Root is here: http://forum.xda-developers.com/showthread.php?t=1940630
Safestrap and a rom here: http://forum.xda-developers.com/showthread.php?t=2012093
Hope this helps. I'm a newb to android, but I think I got this right
What is safestrap if you don't mind me asking?
Jsparta26 said:
What is safestrap if you don't mind me asking?
Click to expand...
Click to collapse
Its the recovery that we use with Motorola devices without an unlocked bootloader similar to twrp. We can flash basically anything but kernels and radios I believe. It also forces us to partition our internal memory unfortunately...but it also allows us to boot into multiple different roms without losing settings or apps
Sent from my XT907 using Xparent Blue Tapatalk 2
Yoo Sparta follow antp121's thread in the general forum for a complete guide on how to use safe strap for installing cm10 or any other rom for that matter. It will really help you! Helped me a lot... Especially me coming from the droid 3 with clockwork mod and no safe strap. Hope this helps.
http://forum.xda-developers.com/showthread.php?t=1997229
Sent from my XT907 using xda premium
jarzy00 said:
Yoo Sparta follow antp121's thread in the general forum for a complete guide on how to use safe strap for installing cm10 or any other rom for that matter. It will really help you! Helped me a lot... Especially me coming from the droid 3 with clockwork mod and no safe strap. Hope this helps.
http://forum.xda-developers.com/showthread.php?t=1997229
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Thank you guys for all if your very informative information. I will look into these links that were provided for me. I usually go and learn everything I can about a device before attempting to gain root, s-off, or unlocking boot loaders. So far I learned that its not possible to unlock boot loader or gain s-off. Believe me when I was on evo 3d. HTC made it very difficult for us to get s-off by patching up the exploits in the hboot by updating it with every ota update. Luckily, we had some very talented devs to get past the patches and come up with solutions.
I only hope the same could be done with the droid razr's boot loaders. I am just spit balling but would it be possible to petition Motorola to come up with an unlock method and post it on their website like HTC did. Again just spit balling lol
I finally rooted my Xperia Z, using recovery. I upgraded my firmware to .253 and flashed this:
-Root by recovery by Emerald
in CWM (TWRP aslo works, obviously).
Screens:
http://img195.imageshack.us/img195/5804/screenshot2013051723013.png
http://img69.imageshack.us/img69/6540/screenshot2013051723012.png
Hey mate,
This seems great.
Can you provide more details pls.
And some instructions?
I am on 1.253 very stock without CWM.
Regards
Sent from my C6603 using xda app-developers app
andreipga85 said:
Hey mate,
This seems great.
Can you provide more details pls.
And some instructions?
I am on 1.253 very stock without CWM.
Regards
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I am using DooMKernel v6 (cause I like it), with this kernel you have CWM just flashing by fastboot boot.img (guide in that topic) and then you can flash .zip file in first post here
1. Is it for Locked or Unlocked bootloader?
2. Is it Deodexed?
So you need to unlock the BL. With not rooted stock fw you can't backup your ta partition before doing that
mmamedov said:
1. Is it for Locked or Unlocked bootloader?
2. Is it Deodexed?
Click to expand...
Click to collapse
Of course is an Unloocked bootloader!
Just stock rom, no edit
unistalled systems app with link2sd, so it works great
ccab said:
So you need to unlock the BL. With not rooted stock fw you can't backup your ta partition before doing that
Click to expand...
Click to collapse
I have UNLOCKED bootloader, root and TWRP recovery.
Anyway, I've got an answer. Thank you, EmeraldTimer for uploading rom. I will try to deodex it
Dude none of that is what gave you root. Flashing DooMKernel is what gave you root access. You will never loose root with a unlocked boot loader and a custom kernel.
EmeraldTimer said:
I finally rooted my Xperia Z, using recovery. I upgraded my firmware to .253 and flashed this:
-Root by recovery by Emerald
in CWM (TWRP aslo works, obviously).
Screens:
http://img195.imageshack.us/img195/5804/screenshot2013051723013.png
http://img69.imageshack.us/img69/6540/screenshot2013051723012.png
Click to expand...
Click to collapse
Yes you will lose root, but you may get it back anytime and in no time by simply flashing a superuser zip (which this effectively is, it's simply a superuser flashable zip). Preferrably one of the newer superuser management tools like SuperSU or Superuser by Koush. Superuser by ChainsDD is showing it's age and doesn't work properly anymore.
I flashed doomlords 1.25 supersu zip from his doomkernel thread and I hav root as well..
Sent from my C6602 using xda premium
This is common knowledge
While we don't have an exploit, can we not just flash .434 then root, backup TA, unlock, flash or upgrade to .253, root again then relock and restore TA?
Sent from my C6603 using xda premium
alexp999 said:
While we don't have an exploit, can we not just flash .434 then root, backup TA, unlock, flash or upgrade to .253, root again then relock and restore TA?
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
This would work. However messing with TA can hard brick your phone if something goes wrong. There is a less risk way to root .253 without touching TA.
1. Install .434 and root
2. Install CWM or TWRP recovery for locked bootloader
3. Flash pre-rooted 253 zip from bootloader
4. Use flashtool to flash .253 kernel, baseband and FOTA
Now you got a rooted .253
pre-rooted .253:
http://forum.xda-developers.com/showthread.php?t=2279661
http://forum.xda-developers.com/showthread.php?t=2282415
alexp999 said:
While we don't have an exploit, can we not just flash .434 then root, backup TA, unlock, flash or upgrade to .253, root again then relock and restore TA?
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Can, I am doing that but still need flash fixed root auto restart issue when locked back.
Michealtbh said:
This is common knowledge
Click to expand...
Click to collapse
not THAT common ive been buzzing around these forums since it came out thinking i couldnt root and was waiting for people to crack the root.
Now this thread actually explained to me that with my UL ill never loose root. So yea it was good to know, and its not like im a noob on these forums.
I used this method and it worked so thank you OP.
Why unlock for stock rom? It can be already done without unlocking. Even the latest firmware.
Also OP should modify the posts title to iclude "unlocked". It is misleading now.
exekias said:
not THAT common
Click to expand...
Click to collapse
Well, uuhm... how can the knowledge, that putting a su binary and a su rights management program on your device via a flashable zip results in root access, NOT be common? Isn't that what it really is all about?
I'm a 100% with @Michealtbh on this one. Too many peeps which know very little to nothing about the very basic must-know-how-it-works-things around these days. Guys "doing stuff" to their devices should possess a very basic understanding of system mechanics, IMHO.
schaggo said:
Well, uuhm... how can the knowledge, that putting a su binary and a su rights management program on your device via a flashable zip results in root access, NOT be common? Isn't that what it really is all about?
I'm a 100% with @Michealtbh on this one. Too many peeps which know very little to nothing about the very basic must-know-how-it-works-things around these days. Guys "doing stuff" to their devices should possess a very basic understanding of system mechanics, IMHO.
Click to expand...
Click to collapse
I really don't think you have the right to dictate what people do and don't know. Not to mention commenting on what people don't know it's the opposite to the aim of these forums.
At least for people benefited from this thread so it's served a purpose. This is a forum not a Wiki you can't attack people for what they do and do not know the intrinsic knowledge needed its quite alot and can only acquired through time and Redding the right threads.
In my own situation my previous Sony was an arc that at the time needed an exploit to root. After that I had a nexus that needed no exploits due to its nature. Now I'm back on Sony and I just assumed we still needed per -software exploits. The thread is filled with people talking about losing root with this upgrade so I just assumed and waited for a new exploit to be discovered. I did not know that the exploit was not needed if your unlocked. So sorry for not knowing all that you know I'll make sure to petition for a sticky that you can dump your worldy knowledge their and so we implement a criteria that you cannot post on this forum until you know everything in the post. How does that sound?
Sent from my C6603 using XDA Premium HD app
exekias said:
not THAT common ive been buzzing around these forums since it came out thinking i couldnt root and was waiting for people to crack the root.
Now this thread actually explained to me that with my UL ill never loose root. So yea it was good to know, and its not like im a noob on these forums.
I used this method and it worked so thank you OP.
Click to expand...
Click to collapse
If you have an unlocked bootloader the easiest and most common method of rooting for pretty much every Android device is flashing a recovery then flashing a su.zip. Easy. I assumed 90% of XDA users knew this.
Michealtbh said:
If you have an unlocked bootloader the easiest and most common method of rooting for pretty much every Android device is flashing a recovery then flashing a su.zip. Easy. I assumed 90% of XDA users knew this.
Click to expand...
Click to collapse
Well sorry for being the 10% who didn't next time I'll save my inquiries for a a place on the internet where we are allowed to ask questions about topical instances like a forum or something, I'll leav you guys and your elite group of know-it-all's alone shall I.
Hey XDA! Just picked up new Droid RAZR M (XT907) and immediately messed it up on the first day. So here's the deal:
- I'm an idiot.
- Got it with 98.30.1 FW, so I used this method to root it: http://www.droidviews.com/root-verizon-droid-razr-m-razr-hd-maxx-hd-latest-firmware/
- Forgot to unlock the bootloader
- Installed ROM Manager and flashed CWM recovery
And this must have messed up something, because now I'm not able to:
- Unlock my bootloader
- Get into recovery, it returns this error: "failed to hab check for recovery 0x56"
I'm clueless now, since I have not much knowledge in this stuff...
I'd be so thankful if anyone could help me
Thanks!
Edit: Will this help me? http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Edit 2: Okay, so that didn't help, but I used "DROID RAZR M Utility 1.20" from mattlgroff and I was successful with bringing OG recovery back. However, I found out that the bootloader on my build just can't be unlocked. I also tried to install Safestrap and install CM on another slot, but it failed with status 6. Why is that? Or is there just any other way how to install any ROM?
krYshuT said:
Hey XDA! Just picked up new Droid RAZR M (XT907) and immediately messed it up on the first day. So here's the deal:
- I'm an idiot.
- Got it with 98.30.1 FW, so I used this method to root it: http://www.droidviews.com/root-verizon-droid-razr-m-razr-hd-maxx-hd-latest-firmware/
- Forgot to unlock the bootloader
- Installed ROM Manager and flashed CWM recovery
And this must have messed up something, because now I'm not able to:
- Unlock my bootloader
- Get into recovery, it returns this error: "failed to hab check for recovery 0x56"
I'm clueless now, since I have not much knowledge in this stuff...
I'd be so thankful if anyone could help me
Thanks!
Edit: Will this help me? http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Edit 2: Okay, so that didn't help, but I used "DROID RAZR M Utility 1.20" from mattlgroff and I was successful with bringing OG recovery back. However, I found out that the bootloader on my build just can't be unlocked. I also tried to install Safestrap and install CM on another slot, but it failed with status 6. Why is that? Or is there just any other way how to install any ROM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, I don't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
krYshuT said:
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, IFon't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
Click to expand...
Click to collapse
Simple answer.
Do you know how many times it has been summed up! For you to find if you just searched! Or just browsed the thread titles in the general forum!
That page is all YOU need.
We need it sticked.
There is an old ss cm btw. See dev section.
aviwdoowks said:
Simple answer.
That page is all YOU need.
We need it sticked.
There is an old ss cm btw. See dev section.
Click to expand...
Click to collapse
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
krYshuT said:
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
Click to expand...
Click to collapse
I wanted...
We do not need the likes of you!
krYshuT said:
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
Click to expand...
Click to collapse
I do apologize you fell this way about the members here at xda... Here at xda we help a lot of people, take time from our day away from our loved ones to assist those in need... Avi helps a lot members a lot of members... You have to understand that your issue your question has been answered and resolved several times prior to this post... I'm sure just scrolling through the topics reading the titles you would have found the answer/s to your question/s (probably answered by Avi)... I understand the search feature of xda may not result in what you are looking for but google will... We do get very tired of answering the same questions over and over again... So i apologize for the "negativism" but Why help those who won't help them selves... knowledge is power and reading is the key...
Sent from my XT907 using xda app-developers app
krYshuT said:
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, I don't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
Click to expand...
Click to collapse
To answer your question, yes to all. And before you jump so quick as to label this typical xda attitude, keep in mind I can label you typical self entitled noob expects everything on a silver platter. People get tired of answering the same question a hundred times over... Guess your number in line. Anytime you're dealing with a locked BL it's a good idea to learn all the intricacies of your phone, which is precisely where you were referred to.... And precisely where I had to start too. That said, politeness and gratitude will get you farther in getting noob answers quicker, which none of your posts contained.
Thanks! I'm sorry if it sounded rude, I'm really grateful for any type of help. I've spent like 5h in all kinds of threads, but most of the time I just get "half-answers" from just reading and reading and reading. I'm not expecting any type of extremely thorough answer, just a direct answer with confirming of what I said. Sending me another link (which I already read) just makes me even more confused. I just found out for example, that Koush's Helium doesn't work on Motorola devices. Does that apply for root method, too? If so, are there any other alternatives to backup & restore on my RAZR M (without and with root)?
Dear XDA members,
I'm very new to rooting/flashing/unlocking, so I'm sorry if I'm asking this questing when maybe 100 others already did, but I couldn't find the answer I'm looking for. I also searched in the topic of Heisenberg (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928), but didn't find the answer, or I just maybe didn't understand it.
My questing is: is it necessary to root your Nexus 6p in order to load (or do you say flash) another ROM on it?
And do I understand it right that if you would like to root your device, you first need to unlock the bootloader in order to install a custom recovery, and after that you are able to install a custom ROM?
Hopefully somebody could answer this answer, thank you very much!
Best way to get into it and start to understand is to install Wugfresh Nexus toolkit.
Sent from my Nexus 6P using Tapatalk
Unlocking is necessary to root or flash a custom firmware or custom recovery. Simply
Welcome to the flashing community.. Hope u enjoy it
If u need more clarification let me know.. Im glad to help.. All of us were noob at one time...
BTCtest said:
Dear XDA members,
I'm very new to rooting/flashing/unlocking, so I'm sorry if I'm asking this questing when maybe 100 others already did, but I couldn't find the answer I'm looking for. I also searched in the topic of Heisenberg (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928), but didn't find the answer, or I just maybe didn't understand it.
My questing is: is it necessary to root your Nexus 6p in order to load (or do you say flash) another ROM on it?
And do I understand it right that if you would like to root your device, you first need to unlock the bootloader in order to install a custom recovery, and after that you are able to install a custom ROM?
Hopefully somebody could answer this answer, thank you very much!
Click to expand...
Click to collapse
Root has nothing to do with being able to flash a ROM, root means you have privileged access and system control on an already existing operating system, it plays no part in flashing partitions on your device. But yes, you must unlock your bootloader. In order to flash a ROM you need a custom recovery, and in order to flash a custom recovery you need an unlocked bootloader. If you need instructions or any help don't be afraid to ask in my thread:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Delboyd12 said:
Best way to get into it and start to understand is to install Wugfresh Nexus toolkit.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'd have to strongly disagree with you there, that's probably the worst way for a beginner to start out. Toolkits may seem convenient but they'll keep a beginner at the beginner level. They allow you to do things to your phone without actually knowing what's going on, without developing an understanding of the process. They allow a user to bypass some crucial learning experience, which in turn stops them from developing the knowledge and skills required to modify a phone. It's also these knowledge and skills that will get you out of hot water when something goes wrong. Then there's the issue of toolkits causing many problems for users. So no, I'd never recommend anyone use a toolkit to accomplish what what can be done very easily if you have a understanding of fastboot; this should be a basic requirement if you're messing with your phone.
Sent from my Nexus 6P