Database Users

ROM Manger + 1.8.3 (Froyo) question?

I was previously on 2.3.4 with CherryBlur, but i downgraded back to 1.8.3 (Froyo) through SBF.
When i boot up it no longer says "Unlocked", but i read around and i believe my Phone still has an unlocked bootloader. (Quick Question: How do i get it back to say "Unlocked" without losing any data?)
Now I installed ROM Manager from the Market, and Installed CWM, because i think i lost CWM when i downgraded.
Question: Am i ready to download and install Roms now. Also when i click Download Roms in the Rom Manager i get an error getting list.

theres a cmd in the unlock thread that let you know if youre still unlocked. and i dont know of any rom that are downloadable from there yet.

primeboss said:
I was previously on 2.3.4 with CherryBlur, but i downgraded back to 1.8.3 (Froyo) through SBF.
When i boot up it no longer says "Unlocked", but i read around and i believe my Phone still has an unlocked bootloader. (Quick Question: How do i get it back to say "Unlocked" without losing any data?)
Now I installed ROM Manager from the Market, and Installed CWM, because i think i lost CWM when i downgraded.
Question: Am i ready to download and install Roms now. Also when i click Download Roms in the Rom Manager i get an error getting list.
Click to expand...
Click to collapse
reflash the pudding for your device and fastboot oem unlock again

joe ferreira said:
reflash the pudding for your device and fastboot oem unlock again
Click to expand...
Click to collapse
all you have to do is reflash the pudding. i've done it multiple times. if you try to fastboot oem unlock again it'll say already unlocked. reflashing the pudding restores the prestigious Unlock text at boot

Help with unlocking and so on

Hello everyone I was hoping I could get some help with my ATT Atrix 4G, as of right now I have my Atrix running 1.5.7 and rooted. For some reason about a week ago my Wifi just stopped working and says error. So I did a little looking around and didnt see a fix besides flashing the phone so I thought I might as well update to the latest and greatest. Now I did my phone so long ago that I have Tenfar's CWM recovery for Motorola Atrix 4G on it. I would like to flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf but Im not sure the steps I need to take. Over all this is what I would like to do.
Number 1. Put CWM Recovery Mod for Atrix 4G and take off Tenfar's CWM
Number 2. Unlock the phone Pudding
Number 3. Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
Number 4. Get wireless tether working.
One thing I don't fully understand is do you need to unlock the phone using pudding before you flash Full 2.3.4 with preinstall root and pudding bootloader unlock or can you just flash and have it unlocked?
So what I really need to know is the order of everything, CWM Recovery Mod for Atrix says you need to be unlocked to use it. So do I need to unlock the phone like in number 2 to before I do number 1 and 3 or can I flash number three and the will unlock the phone? Then do Number 1 and skip number 2 altogether? And as far as number 4 goes if some one could point me in the right direction for working wifi tether on 2.3.4 ATT that would be great.
One other thing I was wondering is it safe to flash for 1.5.7 to 2.3.4 or should I flash to 1.8.3 and then to 2.3.4?
Thanks so much and any and all help is greatly appreciated
Jay

1. You need too unlock first
http://forum.xda-developers.com/showthread.php?p=16018910#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/showthread.php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/showthread.php?t=1186537
or
http://forum.xda-developers.com/showthread.php?t=1160649 from Nav.
Both good roms.

Thanks JayRolla but do I need to flash to Full 2.3.4 with preinstall root and pudding bootloader unlock before I install the 2.3.4 roms you linked to up there?

Jay Dogg said:
Thanks JayRolla but do I need to flash to Full 2.3.4 with preinstall root and pudding bootloader unlock before I install the 2.3.4 roms you linked to up there?
Click to expand...
Click to collapse
As far as I understand, at the moment you are on 1.8.3.
In that case the very first thing you should do is flash pudding (BL unlock sbf).
After that install CWM and do a full backup.
When you have that you can install whichever room you want (don't sbf back to 1.8.3 tho - hard brick), you can install stock 2.3.4 via CWM and root it afterwords manually if you want. It's all a matter of which rom you prefer. Hell, you can try them all as CWM makes it all really easy.
Pudding needs to be flashed only at step 1 and it stays with your forever as long as you dont' SBF. Which you really don't need to do since we have CWM and fastboot.

Have a quick question, what is the difference between the automatic unlock script and the SBF that unlocks and roots via preinstall?
I am on stock 4.5.91 OTA with no modifications at all. Which method should I use? Which is safest/easiest.
I am on win7 64 bit with latest moto drivers installed.

dcarpenter85 said:
Have a quick question, what is the difference between the automatic unlock script and the SBF that unlocks and roots via preinstall?
I am on stock 4.5.91 OTA with no modifications at all. Which method should I use? Which is safest/easiest.
I am on win7 64 bit with latest moto drivers installed.
Click to expand...
Click to collapse
Automatic script is supposed to automate (duh ) some of the unlocking steps for you, but I personally wouldn't recommend it. It failed for me and for many other people too if you read their thread.
With the manual pudding unlock - you can't screw up if you follow all of the steps precisely. But you do have to do all the steps manually, which is a good learning process if you ask me.
If you are on 4.5.91, after flashing pudding and doing the fastboot unlock commands you will get failed to boot error. This is normal and all you have to do is repeat the fastboot commands for the second time and all will be fine.
Do not under the fear of death SBF back to 1.8.3 or you will brick your phone.
Here is the link to the pudding SBF -
http://forum.xda-developers.com/showthread.php?t=1136261
Here are the specific steps laid out in a very straightforward way -
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you install the drivers before doing them. For example, you can download Windows 7 x64 drivers here -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277

xploited said:
Automatic script is supposed to automate (duh ) some of the unlocking steps for you, but I personally wouldn't recommend it. It failed for me and for many other people too if you read their thread.
With the manual pudding unlock - you can't screw up if you follow all of the steps precisely.
Here are the specific steps laid out in a very straightforward way -
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you install the drivers before doing them. For example, you can download Windows 7 x64 drivers here -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Click to expand...
Click to collapse
Thanks for the info
One last question, should I use the small (10mb) pudding sbf or the full SBF that does unlock + root all in one?

dcarpenter85 said:
Thanks for the info
One last question, should I use the small (10mb) pudding sbf or the full SBF that does unlock + root all in one?
Click to expand...
Click to collapse
I would recommend using the smaller pudding sbf, since that's what I used. But from what I read, both SBFs work without problems.
You can root manually afterwords. It's very easy.

xploited said:
As far as I understand, at the moment you are on 1.8.3.
Click to expand...
Click to collapse
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?

Jay Dogg said:
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Click to expand...
Click to collapse
Nope. The process slightlt differs between 2.3.4 and prior.
But besides that you can unlock 1.5.7 just fine.

Jay Dogg said:
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Click to expand...
Click to collapse
No you don't need to be on 1.83 but for easy I would recommend also if it helps these are the steps I took.
1. Unlock bootloader using auto script http://forum.xda-developers.com/showthread.php?t=1182871 (I was running 1.83) (**I did have an issue after doing this where it wiped my phone and wouldn't let me go past the MOTOBLUR login so I just flashed back down to 1.26 OTA back to 1.83 then reran the script just to make sure I was still unlocked now I only read about that happening to one other person on their forum so chances are slim of it happening**)
2. Using RSD (the latest one 5.x.x) I flashed the 2.34 sbf that comes prerooted/unlocked although the root doesn't actually work then you have to follow the preinstall root method they describe on that same post for the sbf.
I never installed CWM but I would suggest doing that one last
**Edit: yes I did forget to mention my circumstance where I flashed back to 1.26 was Im sure pure luck that I did not hard brick my phone. This is not recommended. Why my phone did not brick is still unknown.
From unlocked/rooted GB Atrix

I'm on 1.8.3, unlocked, rooted, with Gingerblur and webtop hacks (web2sd, without dock, full ubuntu).
So I'm confused as to why I cant just flash ATT-2.3.4_Pudding_preroot.sbf, it has 2.3.4/2.5.91, unlocked, root preinstalled.
Would this not give me unlocked 2.3.4 with root ready to set-up? Would I have to "clean" it or is that just optional?
People are saying to install pudding using the automatic script first, but then why create the above sbf file?
What about the 1.8.3, unlocked, root preinstall sbf file?
So if I cant use the unlocked 2.3.4 sbf file, I would first flash pudding on my phone then which 2.3.4/4.5.91 sbf file would I flash with since the OTA update won't work due to mods, and because I didnt think we should use OTA.
I want to do the method that will prevent any bricking, but I also dont want to waste time or do unnecessary flashing.

BE CAREFULLY .... IT SEEM HE/SHE WAS LUCKY WHEN HE/SHE FLASH BACK TO 1.26... IF YOU RUN THE SCRIPT AND PASS STEP 3 YOU HAVE PUDDING SO IF YOU FLASH BACK TO 1.26 YOU WILL END WITH A HARD BRICK... IT IS WELL DETAILED IN THE SCRIPT ONCE YOU HAVE PUDDING YOU CAN NOT RSD ANY DOWNGRADE VERSION OF MOTO SBF FOR EX 1.26 1.57 OR 1.83
drock212 said:
No you don't need to be on 1.83 but for easy I would recommend also if it helps these are the steps I took.
1. Unlock bootloader using auto script http://forum.xda-developers.com/showthread.php?t=1182871 (I was running 1.83) (**I did have an issue after doing this where it wiped my phone and wouldn't let me go past the MOTOBLUR login so I just flashed back down to 1.26 OTA back to 1.83 then reran the script just to make sure I was still unlocked now I only read about that happening to one other person on their forum so chances are slim of it happening**)
2. Using RSD (the latest one 5.x.x) I flashed the 2.34 sbf that comes prerooted/unlocked although the root doesn't actually work then you have to follow the preinstall root method they describe on that same post for the sbf.
I never installed CWM but I would suggest doing that one last
From unlocked/rooted GB Atrix
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

I flashed the full SBF of 2.3.4 with pudding and preroot already installed and I was left with a 0x1000 error which i was able to fix by simply rebooting into fastboot mode and then running 'fastboot oem unlock'. I was really scared when I saw the error but I was able to fix it. Just an fyi for anyone else that might run into that problem.

A few weeks ago when the bootloader was unlocked, and hktw craze began I was happily running GB, a couple days into it my phone started acting crazy, would constantly act if someone was touching it, and I noticed a very small portion of the touch screen quit responding, this happened out of no where, I took the phone back to at&t and they shipped a new one to me.
Now that has nothing to do with your phone but what I am trying to say is that if hardware on your phone randomly quit working more than likely having nothing to do with mods you've done to it.. take it back, get a new one, if you can.
Goodluck
Sent from my MB860 using XDA Premium App

dcarpenter85 said:
I flashed the full SBF of 2.3.4 with pudding and preroot already installed and I was left with a 0x1000 error which i was able to fix by simply rebooting into fastboot mode and then running 'fastboot oem unlock'. I was really scared when I saw the error but I was able to fix it. Just an fyi for anyone else that might run into that problem.
Click to expand...
Click to collapse
This is a known issue and you resolved it correctly by redoing fastboot commands.
Many other people weren't so luck (didn't read instructions) and opted for an SBF back, causing them to hardbrick.

Now just so make sure before I do this, should I take path a or b
PATH A
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
PATH B
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3 .Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
4. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.

Jay Dogg said:
Now just so make sure before I do this, should I take path a or b
PATH A
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
PATH B
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3 .Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
4. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
Click to expand...
Click to collapse
Path A. After flashing pudding i would avoid SBFs entirely, unless there's no other way. Any rom can be flashed via fastboot or CWM, so use that as it's much safer.

Is there a way to tell if a bootloader is unlocked?

Hello everyone?
My brother just emailed me a question the question in the topic. I told him to ask himself here, but hes at work at XDA is a site he cant access from work.
He had unlocked his bootloader and installed a version of Ginbergread. He then decided to flash back to stock and install the official Gingerbread OTA update, and it worked. Now when he starts his phone up the unlocked indicator is gone, so is he still unlocked and if so, how does he tell?
I think his main goal here is installing CWM Recovery so he can then root using the CWM Recory Root, but honestly, I dont know. Im simply asking the question. So with all that being said, is there a wait to tell if his bootloader is still unlocked or is it always going to be unlocked even if it no longer says unlcoked during the phones start up process?
Now, just in case he asks me, can he install CWM and the CWM Root with official OTA GB Update if he had previously unlocked his bootloader?
I (and my brother) appreciate any info.

if the unlocked text is gone during boot then he will have to unlock the bootloader again but this is not necessary if he only wants to install CWM.

neotekz said:
if the unlocked text is gone during boot then he will have to unlock the bootloader again but this is not necessary if he only wants to install CWM.
Click to expand...
Click to collapse
When bootloader is unlocked, it remains unlocked. You do not have to unlock it again! The word unlocked disappears when you flash back.
Once unlocked, always unlocked!

Sounds good. So if he wants to install CWM, can he just follow this guide: http://forum.xda-developers.com/showthread.php?t=1138541 to install CWM?
I had assumed thats what he wanted to while I was waiting for a reply I emailed him and I was right. He plans on installing CWM and then then root.zip. Will that work?

JohnnyDanger said:
Sounds good. So if he wants to install CWM, can he just follow this guide: http://forum.xda-developers.com/showthread.php?t=1138541 to install CWM?
I had assumed thats what he wanted to while I was waiting for a reply I emailed him and I was right. He plans on installing CWM and then then root.zip. Will that work?
Click to expand...
Click to collapse
he can follow instructions in that post or he can root, download rom manager from market and install cwm recovery from within the app.
although tenfar's recovery works flawlessly on ATRIX and cwm can't wipe or read from external sd card.
to reiterate, ONCE UNLOCKED, ALWAYS UNLOCKED!!!
hope this helps.
Sent from my MB860 using XDA App

That does help. Thanks a lot. Im hoping to get him involved here. I think he can learn a lot. The Atrix is his first smartphone and I think he is just starting to really dig in. Hes not so concerned with messing things up as he has a lot of expendable income, but I think the more he knows, the more he will enjoy his phone.

With this one you can not fool around, why I said this, because if you unlock your bootloader and have the "unlocked" tag at boot but then you flash by RSD MOTO 2.3.4/4.5.91 sbf you will lost the tag at boot, actually your bootloader still unlocked but not funtional until you reflash pudding again. But my point if someone want to service their phone and want to reflash MOTO 2.3.4/4.5.91 sbf so the simple customer service guy did not figure out that you mess with your phone unlocking it, yeap it work for the simple CS guy but for tech guy nope because of the following statement:
If you want to confirm your status:
adb->su->and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000100004000
Here is the mean of some of those numbers:
10000000000010001000100004000
4= BL "unlock" Bootloader Unlock out of warranty unit
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW (fruit cake, etc)
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB MOTO OTA<- this guy can NOT RSD ANY MOTO SBF DOWNGRADE 1.26 / 1.57 / 1.83
I hope it help!

CaelanT said:
When bootloader is unlocked, it remains unlocked. You do not have to unlock it again! The word unlocked disappears when you flash back.
Once unlocked, always unlocked!
Click to expand...
Click to collapse
Yeap TRUE , but when you lost the "unlocked" tag because you reflash 2.3.4 SBF you will lost the "unlocked" tag, so unit still with bootloader unlocked but is not 100% functional, you will not able to moto-fastboot partitions until you reapply pudding again and I think this due to the microboot partition (I think CG47)

rafkong said:
he can follow instructions in that post or he can root, download rom manager from market and install cwm recovery from within the app.
although tenfar's recovery works flawlessly on ATRIX and cwm can't wipe or read from external sd card.
to reiterate, ONCE UNLOCKED, ALWAYS UNLOCKED!!!
hope this helps.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
tenfar's CWM can read both the internal and external SD card, you must have the most up-to-date version though. 4.0.0.2 i believe.

mramirezusa said:
If you want to confirm your status:
adb->su->and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000100004000
Here is the mean of some of those numbers:
10000000000010001000100004000
4= BL "unlock" Bootloader Unlock out of warranty unit
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW (fruit cake, etc)
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB MOTO OTA<- this guy can NOT RSD ANY MOTO SBF DOWNGRADE 1.26 / 1.57 / 1.83
Click to expand...
Click to collapse
That was brilliant, thanks! My Atrix reports the following:
cat /sys/firmware/fuse/ReservedOdm
30000000000030001000300004000
so is it safe to assume that it's unlocked. I'm curious to know what the starting digit (3 in my case) means, as it's different from your example.

Mine looks nothing like your lol
20000000000020002000200004000
I can downgrade all the way back to 2.2

My boot loader is unlocked

I have unlocked my boot loader on day one. Never done that before so now I'm wondering if I will still be getting OTA updates. I unlocked in case I wanted to flash so I don't lose user data.
Will I still be getting OTA updates with an unlocked boot loader?

Yes. You would still get OTA update notifications with a rooted/modified system, but it won't let you install it. If you never modified anything other than simply unlocking, you will be able to install the OTA without issue.

Lepa79 said:
I have unlocked my boot loader on day one. Never done that before so now I'm wondering if I will still be getting OTA updates. I unlocked in case I wanted to flash so I don't lose user data.
Will I still be getting OTA updates with an unlocked boot loader?
Click to expand...
Click to collapse
yes, you'll get OTA, assuming you didn't do any modification to any partitions (other then user) you can take OTA.. I just did myself and now I'm on 6.0.1)

Thank you guys. I'm still waiting on 6.0.1. Nothing has been done except unlocking boot loader and I am not rooted.

Lepa79 said:
Thank you guys. I'm still waiting on 6.0.1. Nothing has been done except unlocking boot loader and I am not rooted.
Click to expand...
Click to collapse
you can just download it from google without waiting, you know that right?

Yes, and if I don't flash the user file then I won't lose my data, right?
Just running short on time.

Lepa79 said:
Yes, and if I don't flash the user file then I won't lose my data, right?
Just running short on time.
Click to expand...
Click to collapse
flash everything but user, and it's like you just took OTA - just without waiting)

a1exus said:
flash everything but user, and it's like you just took OTA - just without waiting)
Click to expand...
Click to collapse
Good. That's the reason I unlocked boot loader when I got the phone. Awesome. Might play with that this weekend. Loving 6p and huawei watch. I'm all set

Same here, enjoying phone with watch)
Sent from my Nexus 6P using Tapatalk

Just make sure when you flash them you follow the directions. For many of the files you have to flash them, reboot to bootloader, flash the next one, reboot to bootloader, etc. If you miss a reboot or reboot to system instead of bootloader, you could have problems.
Another option if you're not super familiar with flashing is to wait for the OTA ZIP to be posted (not sure if it is yet or not, I used the factory image) and flash that with ADB Sideload mode, which is more similar to a traditional OTA than flahsing the files on your own.

Thank u guys. I got all of the images flashed and in the correct order. Up and running on 6.0.1. Love good old command line commands .

can't update to marshmallow

Hello friends
My phone is HTC One m8w
There isn't "update" in
Setting
About
Android version,
5.0.1
Software number
1.0.0.m8w
Build number
4.19.1402.15 CL458284 release-keys
Please help me for this problem
How can I update my phone?
Thanks a lot

Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps

Ta3miyyasandwich said:
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Click to expand...
Click to collapse
There isn't any update for my build number
Sent from my HTC_M9pw using Tapatalk

if you are willing to, just root your phone and flash the marshmallow rom on to your phone and use titanium backup to backup everything before you do so.

you can root your phone,flash twrp recovery,flash Marshmallow rom.

lmentor said:
you can root your phone,flash twrp recovery,flash Marshmallow rom.
Click to expand...
Click to collapse
That's exactly what I just said

justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom on to your phone
Click to expand...
Click to collapse
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.

redpoint73 said:
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
Click to expand...
Click to collapse
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone. Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.

justinchao740 said:
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone .
Click to expand...
Click to collapse
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
justinchao740 said:
Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
Click to expand...
Click to collapse
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.

redpoint73 said:
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
Click to expand...
Click to collapse
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access

justinchao740 said:
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
Click to expand...
Click to collapse
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.

redpoint73 said:
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
Click to expand...
Click to collapse
Agreed plus my post never stated anything about rooting.

justinchao740 said:
Agreed plus my post never stated anything about rooting.
Click to expand...
Click to collapse
While my intent is not to be the guy that always has the last word; I also can't let you state a complete falsehood.
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom
Click to expand...
Click to collapse