Database Users

Rooting/Flashing a Rom

Hey guys I'm about to attempt to root/flash my G2 with the cyanogen (spelling?) ROM. This is my first time ever so before I begin I wanted to know if their was a guide with the basics? (rooting, nandroid (still clueless as to what this is) , how to back up what I have now)
Also is their any advantage to rooting? I heard it gives big speed increases, I'm a little worried though because 2.3 should be coming out soon? and I'm stuck between waiting for the original 2.3 or updating from a Cyanogen mod

Kasaki said:
Hey guys I'm about to attempt to root/flash my G2 with the cyanogen (spelling?) ROM. This is my first time ever so before I begin I wanted to know if their was a guide with the basics? (rooting, nandroid (still clueless as to what this is) , how to back up what I have now)
Also is their any advantage to rooting? I heard it gives big speed increases, I'm a little worried though because 2.3 should be coming out soon? and I'm stuck between waiting for the original 2.3 or updating from a Cyanogen mod
Click to expand...
Click to collapse
Yes there are advantages with rooting and also risks, but if your only worried about the gingerbread update, there is already an unofficial Cyanogen CM7.0 rc0 and GingerVillian beta versions of Gingerbread for the HTC Vision out right now.
As far as a guide for rooting, nandriod etc. there are a few ways of rooting, Rage, Visionary and gfree. My suggestion would be if you know how to use ADB, to root(Rage)+gfree which can be found here:
Starting in the sub-section: Rooting the Vision (G2/DZ) and DHD
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Next way No adb needed.
If your not familiar with ADB, you can always root with Visionary. The following links will help walk you thru rooting your phone using visionary r14. I have not had any problems with it, many people have rooted this way. If something goes wrong it is usually operator error. This method is for after the OTA. All needed files and links are in the video instructions.
Visionary has bricked phones before when not properly used, the videos show how to use it properly, use all the settings in the videos.
This is the visionary method, but works perfectly when done correctly..
Follow the videos to a "T", remove visionary and superusers from you phone if you already have them installed from a previous temp root before following the videos, start fresh, follow the videos starting with temp root then onto perm root then onto flashing a rom. Do everything just like the videos start to finish and you should have no problems.
Temp-root first:
http://theunlockr.com/2010/10/20/how-to-root-the-t-mobile-g2-htc-vision-visionary-method/
Perm-root second:
http://theunlockr.com/2010/11/30/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-g2-htc-vision/
Nandriod and flashing a rom last:
http://theunlockr.com/2010/11/30/how-to-load-a-custom-rom-on-the-t-mobile-g2-htc-vision/
Remember don't assume you know how to temp root properly, follow all three videos start to finish and you should have no problems
The cerdit for the videos goes to Daivd Cogen from the unlockr.
As far as nandriod once you flash ClockWorkMod recovery you will be able to back up your existing rom, the last video link I gave you shows you how to do this.

I recommend using the guide found in the Wiki, which is the most up-to-date. See http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Although a lot of people have used Visionary successfully, another lot of people have ended up semi-bricking their phone when it somehow went wrong. You will find plenty of threads about this. Whereas with the method in the Wiki, if something goes wrong then you will just get an error message and/or the root won't stick, but your phone will still work fine.
It's easy to get adb working on your PC, which is needed for the Wiki procedure, if you follow this guide - http://forum.xda-developers.com/showthread.php?t=865685
"nandroid" is the term for a backup/restore done via ClockworkMod, a custom recovery which can be installed via the ROM Manager app (or even flashed separately). However, you will need to have S-OFF to flash a custom recovery, so that's not going to help you for backing up stuff before you do root. Although rooting won't lose any data/settings. Once you have root/S-OFF then you can do a nandroid backup, and you should definitely do one before you flash any custom ROM like Cyanogen.
You can sync contacts/calendar etc to Google to back those up. If you want to backup texts, then you will need to do that separately - e.g. I use the "SMS Backup" app to send my texts to my Google Mail account, though that app won't restore them (but that doesn't bother me).
Rooting won't change anything noticeable about how your phone works, but combined with S-OFF (security off), it unlocks your phone so there are more things you can modify on it - e.g. overclocking, root-only apps. One of the main advantages if you S-OFF is that you can then flash custom ROMs. Though I have root/S-OFF and am still running a stock ROM. You can stay with a stock ROM and overclock once you have root, or flash a new custom ROM which also has overclocking potential plus other features.

Thanks alot , I'll most likely use the gfree method as it seems easiest. When I flash a new rom I don't need to wipe my phone completely? but it's recpmended

Kasaki said:
Thanks alot , I'll most likely use the gfree method as it seems easiest. When I flash a new rom I don't need to wipe my phone completely? but it's recpmended
Click to expand...
Click to collapse
Full Data and cache wipe when flashing between different ROMS, and not needed when flashing the same ROM or updates.

joemm said:
Full Data and cache wipe when flashing between different ROMS, and not needed when flashing the same ROM or updates.
Click to expand...
Click to collapse
Just out of curiousty, Is their a guide to wipe the phone? or is that done form the recovery window? I'm about to start the rooting process now. Currently backing stuff up

Kasaki said:
Just out of curiousty, Is their a guide to wipe the phone? or is that done form the recovery window? I'm about to start the rooting process now. Currently backing stuff up
Click to expand...
Click to collapse
Once you have ClockworkMod Recovery Flashed and you boot into recovery there is an option to wipe Data and option to wipe cache from recovery. The picture below is what it looks like from recovery, note this is not the current recovery version for the HTC G2 but it looks exactly the same. The current recovery is v.2.5.1.3 for the G2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

To root go to unlockr. Com which shows it very easily and then pocketnowvideo on you tube has full walkthroughs of rom manager which makes everything very easy
Sent from my HTC Vision using XDA App

When i get to the cmd on my pc what do I type out
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse

Thanks everyone just successfully flashed cyanogen !!!
theunlockr.com was the most helpful website ever!!

This seemed like an excellent place to ask my question:
There is a very new OTA update for the Desire Z (1.72 ROM) which prevents current methods of rooting.
See: Rooting/S-OFF with the new 1.72 Desire Z ROMs - currently not possible
I live in the US and I am looking to purchase the T-mobile G2 and then root it.
So I was wondering if I buy a completely new G2 within one week, if it will be the old rootable version instead the new unrootable one on the Desire Z.

thecarbine said:
This seemed like an excellent place to ask my question:
There is a very new OTA update for the Desire Z (1.72 ROM) which prevents current methods of rooting.
See: Rooting/S-OFF with the new 1.72 Desire Z ROMs - currently not possible
I live in the US and I am looking to purchase the T-mobile G2 and then root it.
So I was wondering if I buy a completely new G2 within one week, if it will be the old rootable version instead the new unrootable one on the Desire Z.
Click to expand...
Click to collapse
The G2 and the Desire Z have diffrent updates, so to awnser your question the G2's are still rootable even with the G2 OTA, which is not the Desire Z 1.72 OTA.

joemm said:
The G2 and the Desire Z have diffrent updates, so to awnser your question the G2's are still rootable even with the G2 OTA, which is not the Desire Z 1.72 OTA.
Click to expand...
Click to collapse
Excellent.
I will be receiving my T-mo G2 within the coming weeks. It'll be rootable for at least this long, presumably? (like the Desire Z update won't migrate or anything?)
Cheers, pal

thecarbine said:
I will be receiving my T-mo G2 within the coming weeks. It'll be rootable for at least this long, presumably? (like the Desire Z update won't migrate or anything?)
Click to expand...
Click to collapse
I imagine it will be ok, but I would be very suprised if the extra security in the 1.72 DZ OTA doesn't find its way to the G2 via an OTA at some point. Though hopefully by that point it will have been cracked anyway.

Is it Unlocking, rooting, or both that wipes my device?

TD;DR Since I already have the bootloder unlocked, would re-rooting my N7 wipe it?
I know it's a noobish question, I've already rooted my device once, but it was fresh out of the box, I had nothing important on it.
I accidentally updated to 4.2.2 and it screwed up my Bluetooth.
I rooted on 4.2.2 and rolled back to 4.1.2.
Decided that Bluetooth wasn't such a huge deal (got tired of carrying around a Wiimote and Nunchuck everywhere,) so I updated back to 4.2.2, which made me lose my root.
(I even used a root protecting app, didn't work :/ )
So yeah, It's unlocked, I can get to the bootloader and all that jazz.
So does Rooting wipe the N7, or is it just when you first unlock it?

Exact same happened to me I would appreciate an answer too.
Sent from my Nexus 7 using XDA Premium HD app

blahman179 said:
TD;DR Since I already have the bootloder unlocked, would re-rooting my N7 wipe it?
I know it's a noobish question, I've already rooted my device once, but it was fresh out of the box, I had nothing important on it.
I accidentally updated to 4.2.2 and it screwed up my Bluetooth.
I rooted on 4.2.2 and rolled back to 4.1.2.
Decided that Bluetooth wasn't such a huge deal (got tired of carrying around a Wiimote and Nunchuck everywhere,) so I updated back to 4.2.2, which made me lose my root.
(I even used a root protecting app, didn't work :/ )
So yeah, It's unlocked, I can get to the bootloader and all that jazz.
So does Rooting wipe the N7, or is it just when you first unlock it?
Click to expand...
Click to collapse
javajava14 said:
Exact same happened to me I would appreciate an answer too.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Rooting wipes data, its best you make a nandroid backup or backup to PC......correct if I'm wrong hope this helps

I don't think so.
The unlocking generally wipes it.
I've rooted many a device (that weren't locked) and they weren't wiped.
Now, installing a ROM generally calls for a wipe unless you're updating the same....

If you use a root method that calls for an unlocked bootloader, unlocking the bootloader wipes. Any root method that does not require an unlocked bootloader will not wipe the device.
Sent from my SPH-D710 using xda premium

graydiggy said:
If you use a root method that calls for an unlocked bootloader, unlocking the bootloader wipes. Any root method that does not require an unlocked bootloader will not wipe the device.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This is very correct that's why I just throw in the.......correct me if I'm wrong!

Unlocking bootloader wipes data, not rooting....

dalanik said:
Unlocking bootloader wipes data, not rooting....
Click to expand...
Click to collapse
Yep. Agreed.
Rooting and Unlocking the Bootloader have seemingly become synonymous with each other, and confusion has crept in. Because the 'traditional' method of Rooting the Nexus 7 necessitates an unlocked Bootloader (in order to run the required Fastboot commands).
Unlocking the Bootloader (which for security reasons wipes the device) and Rooting are two completely different procedures (but the success of one, is contingent upon the success of the other).
And of course you can now Root the N7 without unlocking the Bootloader at all (and thus no wipe), with this 'exploit'...
http://forum.xda-developers.com/showthread.php?t=2233852
Rgrds,
Ged.

although if you want to install a different rom, a wipe is highly suggested for stability. not 100% required, but much better if you wipe. i highly suggest Helium (also known as Carbon) to back everything up, along with a nandroid just in case. enjoy ur n7!

You certainly should be wiping between ROM flashes, but keep in mind that OP's bootloader is already unlocked. At this point, more or less any root exploit will work without OP losing data, since they can skip unlocking the bootloader.
All you should have to do, OP, is download a custom recovery and root zip, put your device into fastboot, and then run fastboot flash recovery <path-to-recovery-img>, then flash your root zip.

Rirere said:
You certainly should be wiping between ROM flashes, but keep in mind that OP's bootloader is already unlocked. At this point, more or less any root exploit will work without OP losing data, since they can skip unlocking the bootloader.
All you should have to do, OP, is download a custom recovery and root zip, put your device into fastboot, and then run fastboot flash recovery <path-to-recovery-img>, then flash your root zip.
Click to expand...
Click to collapse
Edit: Tried that one-click root that was referenced earlier, didn't work.
It hung up on "daemon started successfully," for like, 10 minutes before I stopped.
It can't be that it doesn't see my tablet, so.
I'm trying it again right now, but I doubt it'll do anything.

Drivers.
Sent from my Nexus 7 using xda premium

graydiggy said:
Drivers.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
NOPE.
No root access, Superuser fails to gain it to update it's binary...
BUT.
I go into the Terminal Emulator, type "su," and it sends back a #, which signifies that I have this thing Rooted, as shown here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Left the Checker running, and it says, after all this BS, that I don't have proper root access...

[Q] Alright.. Help me root my NC4 note 3..

I've got a Verizon Note 3 now with the NC4 ota on it already. I need root. Not want need. I use my hotspot religiously. Tried towel root. Busy box wont install because of superuser permissions. I uninstalled all of them etc.. Nothing.. Factory reset my phone. Towelroot'd again. Then busybox. same message. "there was a problem opening a shell with root access. This is either being caused by a superuser/supersu or by a device that is inproperly rooted. Try removing superuser permissions, uninstalling this app reinstalling this app then regranting permissions. Well After rooting a factory reseted nc4 with towel root busybox showed this. So then i proceded to supersu. Tries to install shows option to disable knox fails. Installed superuser and tried to update binary, failed and crashed superuser.
Ever phone i've had has been rooted. thunderbolt/s3/n2/s4.. the note 3 has became the b*tch of the family that doesnt want to listen. Please help. I feel these threads overpopulate the forums but i've tried multiple times. given up waited a few months and tried again. This being my fourth attempt owning the phone im to the point where i want to give up and get my old s4 back.. So please help me with any information you can give.
Thanks
edit: yeah signature is old.. havent been on in a while sorry.

clark707 said:
I've got a Verizon Note 3 now with the NC4 ota on it already. I need root. Not want need. I use my hotspot religiously. Tried towel root. Busy box wont install because of superuser permissions. I uninstalled all of them etc.. Nothing.. Factory reset my phone. Towelroot'd again. Then busybox. same message. "there was a problem opening a shell with root access. This is either being caused by a superuser/supersu or by a device that is inproperly rooted. Try removing superuser permissions, uninstalling this app reinstalling this app then regranting permissions. Well After rooting a factory reseted nc4 with towel root busybox showed this. So then i proceded to supersu. Tries to install shows option to disable knox fails. Installed superuser and tried to update binary, failed and crashed superuser.
Ever phone i've had has been rooted. thunderbolt/s3/n2/s4.. the note 3 has became the b*tch of the family that doesnt want to listen. Please help. I feel these threads overpopulate the forums but i've tried multiple times. given up waited a few months and tried again. This being my fourth attempt owning the phone im to the point where i want to give up and get my old s4 back.. So please help me with any information you can give.
Thanks
edit: yeah signature is old.. havent been on in a while sorry.
Click to expand...
Click to collapse
Make sure usb debugging is enabled. then retry towel root

RomsWell said:
Make sure usb debugging is enabled. then retry towel root
Click to expand...
Click to collapse
Enabled USB debugging. Uninstaller Chinese superuser crap. Install supersu from play store. Try to update. Failed knox.

clark707 said:
Enabled USB debugging. Uninstaller Chinese superuser crap. Install supersu from play store. Try to update. Failed knox.
Click to expand...
Click to collapse
Go back to towelroot. After rooting use a root checker to verify root. Don't worry about updating SU Binaries or disabling Knox, if you are planning to flash a custom rom this will all get taken care of as pretty much every rom has done this for you, you should still be able to grant permissions without updating. If the busybox app you are using doesn't work, try another one, the one I always use is created by a Steven something (can't remember last name).
If you are not going to flash a custom rom follow the instructions in the 3rd post found here.

kinstre11 said:
Go back to towelroot. After rooting use a root checker to verify root. Don't worry about updating SU Binaries or disabling Knox, if you are planning to flash a custom rom this will all get taken care of as pretty much every rom has done this for you, you should still be able to grant permissions without updating. If the busybox app you are using doesn't work, try another one, the one I always use is created by a Steven something (can't remember last name).
If you are not going to flash a custom rom follow the instructions in the 3rd post found here.
Click to expand...
Click to collapse
alright. UNinstalled everything and reinstalled towel root. Ran towelroot no errors. downloaded root tester and no root access. The busybox I download is the first one that comes up by Stephen. Still gives me the same error.
Something is wrong with superuser. I UNinstalled them all and I've tried them all. Superuser by chains fails to download manifest. Busybox X says no root or bad superuser.idk what to freaking do its pissing me off

clark707 said:
alright. UNinstalled everything and reinstalled towel root. Ran towelroot no errors. downloaded root tester and no root access. The busybox I download is the first one that comes up by Stephen. Still gives me the same error.
Click to expand...
Click to collapse
Just to make sure, you did install SuperSU prior to running root checker? Permissions are required to verify root.
If so, I would reflash the stock firmware via Odin and start over. The firmware file can be found here. After flashing through Odin boot into recovery and factory reset/wipe cache. Then try rooting again, make sure you have the latest towelroot.

kinstre11 said:
Just to make sure, you did install SuperSU prior to running root checker? Permissions are required to verify root.
If so, I would reflash the stock firmware via Odin and start over. The firmware file can be found here. After flashing through Odin boot into recovery and factory reset/wipe cache. Then try rooting again, make sure you have the latest towelroot.
Click to expand...
Click to collapse
For an obvious answer I just did towelroot then root checker. Because none of the super users work.. and I'll have to do that when I get off work tonight. Would prefer a different route though.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

clark707 said:
For an obvious answer I just did towelroot then root checker. Because none of the super users work.. and I'll have to do that when I get off work tonight. Would prefer a different route though.
Click to expand...
Click to collapse
As I tried to say before, you don't need to update the binaries for SuperSU to do its job. Just install it, don't worry about opening it or trying to disable Knox. Something about NC4 OTA doesn't like rooting as Verizon continues to try to lockdown our phones as much as they can.
ATM, Towelroot is the best root method I know of as it is a one click method that works, I haven't seen anywhere on these forums that it has failed for our device short of users missing some important link in the chain. I haven't tried kingo or the chinese version of rooting since being on KitKat so I don't know if they work on the current firmware nor have I seen anyone talking about them since Towelroot was discovered for our device.
Steps to successful root, busybox, safestrap, custom rom are in the second post of this thread. My only addition to the steps would be to install a switch user app (i.e. SuperSU) in between Steps 1 & 2. You can switch out any 4.4 rom for the Stock rom provided by BeansTown106 as long as you make sure to flash the NC2 kernel in the appropriate step. The only exception would be if you are planning on using Jasmine Rom as hsbadr has recently rebuilt his 2 versions on the NC4 kernel, in which case you don't need to do anything special, simply flash via Safestrap following the instructions in his OP. (I apologize if you already understand all this, just trying to be thorough so we don't have to keep going back and forth).

Alright well with just supersu installed and towellroot ran busy box fails each time.

These are the steps I took with a fresh factory reset. USB debugging. Towelroot install supersu install busy box run busybox get that error I showed above. Rage quit.
Interesting enough this busy box installer shows that my phone has root but fails to install busybox

clark707 said:
These are the steps I took with a fresh factory reset. USB debugging. Towelroot install supersu install busy box run busybox get that error I showed above. Rage quit.
Interesting enough this busy box installer shows that my phone has root but fails to install busybox
Click to expand...
Click to collapse
At this point I don't know what else to try other than reflashing the stock firmware via Odin and starting again.

kinstre11 said:
At this point I don't know what else to try other than reflashing the stock firmware via Odin and starting again.
Click to expand...
Click to collapse
I'm gonna try this later tonight.

kinstre11 said:
At this point I don't know what else to try other than reflashing the stock firmware via Odin and starting again.
Click to expand...
Click to collapse
Worked!!
Root [X]
Busybox [X]
Safestrap [X]
In the process of downloading jasmine's port from the s5 on my phone so i can set up a partition for it. Never really used safestrap so this is a new world for me. Any advice is much welcomed!

clark707 said:
Worked!!
Root [X]
Busybox [X]
Safestrap [X]
In the process of downloading jasmine's port from the s5 on my phone so i can set up a partition for it. Never really used safestrap so this is a new world for me. Any advice is much welcomed!
Click to expand...
Click to collapse
Only use the stock slot, there are problems with battery drain and other things on rom slots.

kinstre11 said:
Only use the stock slot, there are problems with battery drain and other things on rom slots.
Click to expand...
Click to collapse
Wait wouldn't using the stock slot be dangerous? And I'm coming across another problem. Every rom in the forums I try does not boot up accept for jasmine rom 2.3 I'd like to use a different rom but it's not liking me lol. But it's safe to flash a rom in the stock slot? If so I'll have jasmine in slot one as a backup. Battery drain is outrageous. Even with zero lemons 10,000 nah battery it blows through it.

clark707 said:
Wait wouldn't using the stock slot be dangerous? And I'm coming across another problem. Every rom in the forums I try does not boot up accept for jasmine rom 2.3 I'd like to use a different rom but it's not liking me lol. But it's safe to flash a rom in the stock slot? If so I'll have jasmine in slot one as a backup. Battery drain is outrageous. Even with zero lemons 10,000 nah battery it blows through it.
Click to expand...
Click to collapse
Using the stock slot isn't really dangerous... You can always boot into download mode and reflash the stock rom with Odin. You will need the unified Kitkat kernel with most roms. And each rom should have instructions including flashing it at some point.

sardonicpriest said:
Using the stock slot isn't really dangerous... You can always boot into download mode and reflash the stock rom with Odin. You will need the unified Kitkat kernel with most roms. And each rom should have instructions including flashing it at some point.
Click to expand...
Click to collapse
I kinda understand, what if I flash jasmine 2.3 s5 port for stock

clark707 said:
I kinda understand, what if I flash jasmine 2.3 s5 port for stock
Click to expand...
Click to collapse
I would recommend using 2.4.1 instead, it is a more recently updated version of the S5 port. I believe you can flash the unified kernel in Odin before you install the rom (as long as you are already running Kitkat, otherwise wait until you have a Kitkat rom installed). As for 2.3, I don't remember if it needed the unified kernel, but it shouldn't hurt anything to use it anyways on Jasmine roms. If you do go with 2.3 I would look into the patches (2.3.1 - 2.3.4 i think) for stability/bug fixes, although I am not sure if they all need to be flashed or just the last one as I never used 2.3 (I am happily using 1.9 lol).

Does anyone have the current link for downloading TR v3? I can't seem to find it, and I am debating picking up a note 3 in place of my S5...

[WARNING] DO NOT Install PRIME V6.6 OTA Update

It has come to light that a new update has been released for the Prime version stock ROM. This update is called V6.6 (duh), and the update replaces the preloader. Some people have reported bootloops, one has gotten a brick, and I am all but certain that Amazon is trying to patch the preloader to remove any chance of rooting or converting to OEM ever again. It also replaces the boot image, which we believe is a way to re-lock the bootloader, or possibly even make fastboot ignore the unlocked status. This could also destroy your ability to root, run TWRP, or run any custom ROM ever again. If you are on the Prime stock ROM, DO NOT take the OTA to V6.6. It's really not worth it for the security patch. I also encourage all users of V6.1, V6.4, or V6.5 to go ahead and convert your phone to the non-Prime variant while you have the chance. Amazon is known for jamming updates down people's throats so I would not be surprised if they have a way of installing that update without your approval.
The conversion guide is here: http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
There is some discussion about the OTA in the last few pages of the general discussion thread here: http://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-t3418354/post68565531#post68565531
We can use this thread to further dissect and discuss the update.

The boot img can lock the Bootloader.

Thanks for the warning. I would have taken it as I think V6.5 was a good update and improved performance (at the expense of battery life).

DarkBlood. said:
The boot img can lock the Bootloader.
Click to expand...
Click to collapse
No, but some kernel/ramdisk shenanigans could lock it at boot.

We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.

With the fire tablet they disabled the preloader and changed the pid

ColtonDRG said:
We've now confirmed that this update breaks SPFT. It is currently unknown if we will be able to recover from this, but I'm hoping we can.
http://forum.xda-developers.com/showpost.php?p=68578922&postcount=1319
It doesn't appear to relock the bootloader or break fastboot in any way, so if your bootloader is already unlocked you might be okay. I still highly recommend against it.
Click to expand...
Click to collapse
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.

I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.

I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.

DarkBlood. said:
With the fire tablet they disabled the preloader and changed the pid
Click to expand...
Click to collapse
You cannot simply "disable" the preloader. We discussed what exactly Amazon did with the Fire a little bit in the private hangout the other day. The bottom line is that we still don't know exactly what shenanigans Amazon is up to, or what tricks they have up their sleeve. Knowing Amazon, it can't be good for us.

jacewt said:
I am sticking to the prime version. I had disabled OTA. Bootloader unlocked. Hopefully someone can see if 6.6 has anything to offer.
Click to expand...
Click to collapse
It has the August security patch and some things that lock things down. Nothing else that I'm aware of.

bionictoothpick said:
I installed V6.6 OTA update...not sure if I'll regret it. The amazon ads haven't bothered me because I always have notifications, and the ads are smaller than them...plus I was on a CHEAP phone ($10.00) from best buy via slickdeals ad about a year ago...so now I feel like I'm on a contender...it's all relative...Compared to http://www.lg.com/us/cell-phones/lg-LS620-realm I'm flying.
Click to expand...
Click to collapse
If you unlocked your bootloader (fastboot style) via one of the methods before, you should still be able to gain root. If not, you are probably hosed, at least for now. Weather or not you will end up regretting that is up to you, but I certainly would.

kal250 said:
So, I wonder then, if we dont get a custom rom soon, can the security updates be pulled from the prime OTA and be incorporated into non Prime. I bet if 6.6 plugged SPFT and makes it near impossible for new users to switch to non prime or debloat, that will be the last OTA we see for awhile.
Click to expand...
Click to collapse
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".

ColtonDRG said:
I agree. By the way, I will be releasing a TWRP version of the image for people who did manage to unlock their bootloader to use to convert after taking the update. I will also try to get a TWRP image of the old-school preloader image working once I've figured out if it's safe.
As for mixing the ROMs, I've considered doing it before. I worry about breaking some of the advantages of the OEM ROM. If this continues for too much longer, I'll consider it more seriously and start looking into it, but I think for now it remains a case of "there are more important things to do".
Click to expand...
Click to collapse
Fortunately, I had OTA blocked and as I said the other day when i get downtime(hopefully Sunday), I'm back to OEM, to hell with security patches!!

@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
The zip is available in https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/

bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
Go for it, but I'm not interested in taking any of Amazon's **** either way.
As @DarkBlood. said, the zip file is mirrored on https://na.mirrors.coltondrg.com/coltondrg/r1hd/stockota/prime/

I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....

ariesgodofwar said:
I am curious, and we may already know, but did they fail to properly implement the version check in their OTA updater script? Just looking at the reviews on Amazon, it seems a few have suddenly been borked, and only able to boot to stock recovery since Sept 6th or so. I am curious as one of the recovery system check failure messages appears to be hanging up on the v6.1 files and refusing to boot saying they were modified. Was wondering if those are devices that updated from v6.1 straight to v6.6 whereas it seems Amazon/Blu should have ensured the updater abort if device was not v6.5. Thoughts? They may have created a real mess for themselves....
Click to expand...
Click to collapse
A handful of people around here actually got their phone bootlooped just after taking the upgrade straight from 6.5 to 6.6. At first I figured it was a fluke because their phones were altered, but at this point it's getting very suspicious (almost like it's a hit or miss thing for everyone, even those that haven't touched anything). I hope this doesn't damage the device's reputation too bad, and Amazon better get their **** together. Chopping off their nose in spite of their face. I guess I shouldn't be surprised at this point. This is Amazon we're talking about here.

bibikalka said:
@ColtonDRG, @DarkBlood., @waingro808, @kal250, @ jacewt
Do we have the zip file for the OTA update yet ?
It's usually very trivial to repackage the update zip in order to make it update only /boot and /system, and nothing else (I've done this back with V6.5 since I wanted to keep the oldest bootloaders available). This way one gets all the updates, without any impact on the preloader, unlock status, etc.
This is kind of similar to how it's done for Fire 7 :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Click to expand...
Click to collapse
If the zip can be modified, can we inject the 6.1 preloader and bootloader into the 6.6 OTA and modify it to run over current 6.6 installs allowing those who have been locked to at least unlock themselves?? I'm not savy enough to try....

About disabling "Secure Boot" (S-ON) on the N5X.

Secure Boot (aka S-ON, aka other names) is the responsible for checking and validating the entire chain of trust from the psychical bootloader (BootRom) to the Android Bootloader (aboot). From there on, validating boot.img (kernels) and recoveries are checked via the lock/unlock state of the device, and validating system is duty of the Verified Boot (dm-verity) feature on the kernel.
Unlike the old days with the Nexus One and its S-OFF achievement (for reformatting the nand and others), I haven't seen any S-OFF or bootloader/radio development on any Nexus device from that point. Has been any exception for the N5X for some rare chance?
I know that disabling Secure Boot wouldn't be much useful considering there doesn't seem to be any radio or bootloader development at all, but the truth is that without the chance to flash and test it no development can appear from the nothing either. I honestly do not have any idea if by chance secure boot was disabled, anyone will jump into developing a better radio or more feature rich bootloader..
Just wondering, has this been ever attempted or anything? It seems that any HTC is attacked in this sense, but others aren't, even if Nexus are considered development freely, the truth is that they're all S-ON by default and no development of a radio or a bootloader seems to be in place ever. If It was able to happen with the Nexus One, why not for latter nexus devices?
And I don't agree to the point of "we don't need Secure Boot disabled because we would be able to really brick our Nexuses!!", because you can still brick any nexus by flashing any (signed) bootloader or radio from another device, for example N5 bootloader into a N5X (and a ton of more examples with other signed images, and let's not talk about inside android with root.. literally the first Nexus 5/5X were bricked by kernel auto uploaders because they had hardcoded the partition for the kernel, and it happened to be the bootloader one on the new device..). The S-ON check is only to guarantee you don't flash unauthorized stuff from the point of view of Google, not for your security of not bricking the device at all.

Agree
Sent from my Pixel using Tapatalk

there is really no point here because we can actually flash anything without any problem...
on htc devices (I had last 5 year's flagships, so I know something about it) you need it to flash unsigned factory images, zips with firmware files, change your phone's id and in some cases (htc one x) even flash a kernel from recovery! yes, you had to flash manually boot.img every time you change kernel/rom
but here...really....no need, unless some really crazy guy wants to make a bootloader from scratch and load something like windows phone

throcker said:
there is really no point here because we can actually flash anything without any problem...
on htc devices (I had last 5 year's flagships, so I know something about it) you need it to flash unsigned factory images, zips with firmware files, change your phone's id and in some cases (htc one x) even flash a kernel from recovery! yes, you had to flash manually boot.img every time you change kernel/rom
but here...really....no need, unless some really crazy guy wants to make a bootloader from scratch and load something like windows phone
Click to expand...
Click to collapse
I agree on that we don't "need" it for basic rom flashing stuff, but your last line defines why it would be awesome to have it. It would give out options not only to "boot Windows", but also add features to the bootloader, repartition as we please (reduce system partition after debloating), adding a mechanism to prevent any bricking by adding a safe first bootloader sequence (like it was done for the N7 2012, via nv flashing if I don't remember bad), stuff like removing the damn bootloader unlock orange or other warnings (not only changing the images but also deleting the damn timeouts at boot), being able to add passwords for bootloaders, and a ton more **** could be done.
And let's not talk about "Radios". That garbage partition is a GIANT security hole and for the worse it boots BEFORE the main cpu and controls everything, from the application cpu to the memory it's using. Literally the radio controls the phone, it's the most important partition, it's FULL of backdoors (like the Replicant guys demonstrated for the Nexus S/Galaxy S2), it's FULL of unintended security holes (because no one develops for it decently, there have been some hacking conferences having fun at them) and it's the worst we all having running on the phone right now. It doesn't matter your Android Version or security patch date, you have security holes that date from years ago opened and being probably exploited by goverments as we speak.
There are great devs around, the bootloaders are usually decompiled to find exploits to be unlocked, for S-OFF and a lot of stuff. I'm sure people could jump on radio cleaning and fixing. There is a great community and great potential unused.
Until we fix the radio and the BL, "our" N5X is not our phone. Secure Boot should be killed and development would take place.

Really interesting ! Thanks

Aww, no one is interested in this .
Sometimes I wish that the Nexus weren't so unlocked and that we would need S-OFF to even flash custom roms, so a lot more development would appear, like it did for the Nexus One.

Well, I really dont see such a point of locking down the choice. If I buy something, then its mine. So what I do with mine should really be mine choice, dispite warranty. If I break it, its still mine.
Sent from my Pixel using Tapatalk

jugoslavpetrovic said:
Well, I really dont see such a point of locking down the choice. If I buy something, then its mine. So what I do with mine should really be mine choice, dispite warranty. If I break it, its still mine.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yes, this is the point, but we are accepting nowdays devices that are full-locked except some partitions for us to play with. All is good while the bootloader is completely locked on and the radio is even more untouchable, literally making everyone able to spy on us.
The funniest part is that only "we", the users, are locked. Because I am expecting malware to grow up to the point that it will be able to get root, then unlock, then turn secure boot OFF, and then overwrite the bootloader and radio in a ransomware form blocking the boot of the device until payment is done or something like that.

RusherDude said:
Yes, this is the point, but we are accepting nowdays devices that are full-locked except some partitions for us to play with. All is good while the bootloader is completely locked on and the radio is even more untouchable, literally making everyone able to spy on us.
The funniest part is that only "we", the users, are locked. Because I am expecting malware to grow up to the point that it will be able to get root, then unlock, then turn secure boot OFF, and then overwrite the bootloader and radio in a ransomware form blocking the boot of the device until payment is done or something like that.
Click to expand...
Click to collapse
Exactly. Scary. That reminded me of a movie I have seen recently called Zero Day.
Sent from my Pixel using Tapatalk

jugoslavpetrovic said:
Exactly. Scary. That reminded me of a movie I have seen recently called Zero Day.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I wonder if it's as easy as flipping some bits like for unlocking bootloader..
@segv11 @osm0sis , hey guys! you both worked for BootUnlocker, so you may know something about this : do you know if a value is stored in memory to control "Secure Boot enabled" or "Secure boot disabled" like for bootloader locked or unlocked? Have you ever found this or something related by accident? Thanks!

RusherDude said:
I wonder if it's as easy as flipping some bits like for unlocking bootloader..
@segv11 @osm0sis , hey guys! you both worked for BootUnlocker, so you may know something about this : do you know if a value is stored in memory to control "Secure Boot enabled" or "Secure boot disabled" like for bootloader locked or unlocked? Have you ever found this or something related by accident? Thanks!
Click to expand...
Click to collapse
Don't think so.. that's all secure bootchain stuff.. some is open source and some is not.
Google the following: lk bootloader
That's what the LG devices use if I recall correctly. Checking out some of the public source will be your best bet of finding if it even possibly can be disabled.

osm0sis said:
Don't think so.. that's all secure bootchain stuff.. some is open source and some is not.
Google the following: lk bootloader
That's what the LG devices use if I recall correctly. Checking out some of the public source will be your best bet of finding if it even possibly can be disabled.
Click to expand...
Click to collapse
Thanks a lot for the input! I think it can be disabled because apparently some N5 users made it, and considering that the N5 is the N5X's brother from LG, it should be doable too:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image is from http://bbs.gfan.com/android-7753460-1-1.html , apparently a chinese site about a tool? for disabling secure boot? no idea honestly
So it probably is doable on N5X too, the question is how . If its a bit flip for unlock, it is probably just another value for secure boot, I wonder if adjacent to the unlock one or something like that. I'll search for lk bootloader stuff but I have not the bootloaders knowledge (or tools like IDA2 pro to get it done anyway, which sucks ) for making it anyway
Thanks a lot!

I definitely think it can be disabled and I found some rather interesting things by reading up on a site, where someone has actually spent time reverse engineering what's most likely a signed and compiled version of ABoot (LK Bootloader). I thought it was interesting as it covers the actual process of disassembling the image, which may expose the values that need to be changed to actually achieve a true state of disabled secureboot.
http://newandroidbook.com/Articles/aboot.html
What worries me however, is if the signature is checked upon flashing, as if that's the case then replacing the bootloader may in fact be next to impossible. I'm not all that interested to try it out either, as I simply don't want to risk ending up with a hardbricked phone as that wouldn't be all that great so to say. However, if someone is successful making a patch that really works and release it, I'll definitely give it a go after it has been comfirmed to work.

Doenms't the PixelROM flash a custom bootloader?
So what's the "fastboot unlock bootloader" command for?

LazerL0rd said:
Doenms't the PixelROM flash a custom bootloader?
So what's the "fastboot unlock bootloader" command for?
Click to expand...
Click to collapse
No it doesn't.
Unlocking the bootloader is the ability to ask the bootloader it self to boot a different/custom rom.

scr60 said:
No it doesn't.
Unlocking the bootloader is the ability to ask the bootloader it self to boot a different/custom rom.
Click to expand...
Click to collapse
Well, actually it does. It's using the Google Pixel Bootloader. Check is files. It's a custom bootloader.

LazerL0rd said:
Well, actually it does. It's using the Google Pixel Bootloader. Check is files. It's a custom bootloader.
Click to expand...
Click to collapse
It's not a custom bootloader, it only changes the imagdata, the graphical aspect of it that you see when the phone boots. Iit's far from being a custom bootloader

Gr0vk said:
It's not a custom bootloader, it only changes the imagdata, the graphical aspect of it that you see when the phone boots. Iit's far from being a custom bootloader
Click to expand...
Click to collapse
Okay. Thank you for correcting me there!

LazerL0rd said:
Okay. Thank you for correcting me there!
Click to expand...
Click to collapse
Should exist more people like you on the internet

I haven't been able to find a way. Probably have to burn your own bootloader onto the emmc board.