Database Develop

[ROM] Stock rooted OTA 4.08.605.19 710RD - 02-10-2013

Stock Rooted OTA 4.08.605.19 710RD Rom​
Stock rooted ota 4.08.605.19 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy ​
[standard flashing disclaimer here]​
Do a full wipe (boot, system, data, datadata, cache, android secure) except for sdcard and emmc, then flash like any other rom. ​
Stock rooted ota 4.08.605.19 rom may be able to be flashed over Stock rooted ota 4.08.605.15 rom, but is untested. If you flash over and have issues, do a full wipe and fresh install.​
DOWNLOAD ODEXED - MD5 - Mirror​
DOWNLOAD DEODEXED - MD5 - Mirror​
_

2-13-2013 - Fixed TWRP flashing issues.
3-13-2013 - Fixed Superuser issues.

Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.

ToyTank said:
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
Click to expand...
Click to collapse
Just grab a root file explorer.
Sent from my Nexus 7 using Tapatalk 2

Osiris19 said:
Just grab a root file explorer.
Click to expand...
Click to collapse
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.

ToyTank said:
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
Click to expand...
Click to collapse
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?

IceDragon59 said:
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
Click to expand...
Click to collapse
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.

cmlusco said:
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
Click to expand...
Click to collapse
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.

IceDragon59 said:
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
Click to expand...
Click to collapse
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.

cmlusco said:
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
Click to expand...
Click to collapse
Deleting them in WinZip. That's how I've always successfully done it before.

IceDragon59 said:
Deleting them in WinZip. That's how I've always successfully done it before.
Click to expand...
Click to collapse
I will try it and see if it does the same for me.

cmlusco said:
I will try it and see if it does the same for me.
Click to expand...
Click to collapse
Any luck?

IceDragon59 said:
Any luck?
Click to expand...
Click to collapse
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.

cmlusco said:
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
Click to expand...
Click to collapse
Thanks so much =), honestly I am surprised updates are still being released. I really need to get to a Verizon store and snag the 4G version but I've been traveling a lot so my Blackberry has been getting a workout thanks to the international SIM support. Regardless I still use my Dinc for Google Auth (2-pass auth FTW!) and other activities everywhere (in network or not).

Fixed issues with superuser. For those who have already downloaded reflash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip thru recovery.

Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.

leo72793 said:
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
Click to expand...
Click to collapse
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.

cmlusco said:
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
Click to expand...
Click to collapse
having pertition error :/

leo72793 said:
having pertition error :/
Click to expand...
Click to collapse
What kind of partition error?
I tested both cwm and twrp with both a flashover from stock rom 605.15 and a clean install and all worked just fine. Did you check the md5? Try redownloading.

Just got my INC back from my little sister after she upgraded and i'm excited to have this as my backup! Thanks for uploading this for everyone!

Rooted phone but says not rooted

So I'm rooted with an unlocked boot loader and a custom ROM installed but when I downloaded some apps it said it can't access root so I checked root checker and it said
My phone isn't rooted even tho I have supersu and a custom ROM on it
Sent from my HTC One using xda app-developers app

Remove the super su and install superSU.zip from recovery.
Sent from my One V using xda app-developers app

Are you sure nothing will happen? Can I just get it from Google play?
Sent from my HTC One using xda app-developers app

Zakdroid said:
Are you sure nothing will happen? Can I just get it from Google play?
Click to expand...
Click to collapse
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.

iElvis said:
If you just moved up to 4.3, root implementation has changed, so you need to flash SU from recovery the first time.
Click to expand...
Click to collapse
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.

ieldra said:
I'm having similar issues with my HTC One, I unlocked and rooted and installed Maximus HD 13 rom - that's when I started getting problems with SuperSu - first the update issue, now it says no binaries.
I tried installing it from recovery, I even tried CWM, then reflashed TWRP. Still nothing, same error. No binaries. Driving me bloody crazy.
Click to expand...
Click to collapse
Do a full wipe and start over, flashing rom and then supersu together.

iElvis said:
Do a full wipe and start over, flashing rom and then supersu together.
Click to expand...
Click to collapse
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !

ieldra said:
Yeah it looks like that's what I'm gonna have to do, should I wipe boot as well ? Maximus HD installs the stock kernel as well, wondering if it also installs hboot. Afaik /boot is split into boot and kernel. Wouldn't wanna wipe the entire device, install the ROM, reboot and find myself with no hboot !
Click to expand...
Click to collapse
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.

iElvis said:
hboot and boot.img are two different things. No rom will touch hboot. Only way to change your hboot is via RUU or OTA, or to s-off and flash in RUU mode.
All roms include a kernel, usually the stock kernel. That will overwrite whatever you had there before but you should still wipe /data.
Click to expand...
Click to collapse
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do

ieldra said:
Thanks for your replies man! Really helpful ! I installed Maximus HD again, formatted everything I possibly could... it comes preloaded with supersu. Still says no binaries... What the hell should I do
Click to expand...
Click to collapse
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.

iElvis said:
Did you flash the supersu zip separately in recovery? I've had to do that every time I installed a 4.3 rom.
Click to expand...
Click to collapse
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...

ieldra said:
Alright, basically what I did today is I wiped every single partition I had access to, so everything but boot and recovery. installed maximus HD 13, installed faux kernel, installed faux kernel camera fix. Maximus installs supersu by default, I opened it up and I got the stupid no binary error. So I went back to recovery and attempted SuperSu 1.65 from zip, still the same problem. Please note that I did all this BECAUSE of my issues with root, funny how after nuking the whole phone I still have the same problem. I've google extensively, and pretty much the only advice I've found involves either rooting from recovery or changing something in SuperSu settings, which I CAN'T ACCESS because the app closes right after the error prompt pops up.
I'm a few desperate attempts short of attempting an exorcism...
Click to expand...
Click to collapse
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.

iElvis said:
I have not used Maximus, so maybe you should move over to that thread. I had the same issues with ARHD, but flashing SuperSU in recovery after the rom flash took care of it. In all likelihood, you're not the only Maximus user to deal with this, so the answer may be over there.
Click to expand...
Click to collapse
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.

ieldra said:
I don't know what changed, but i changed TWRP for CWM, installed the rom, then immediately installed supersu and it worked. I love you. I want you to have my babies.
Click to expand...
Click to collapse
I'm lacking the uterus for that, but feel free to hit the Thanks button.

iElvis said:
I'm lacking the uterus for that, but feel free to hit the Thanks button.
Click to expand...
Click to collapse
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now

ieldra said:
Alright, so SuperSu WORKED. Until I flashed the faux123 kernel, at which point it stopped working again. Same issue, no binaries. So I reformatted the whole phone, installed Rom, then faux123 kernel, then SuperSu. Same issue. No binaries. I can only conclude that installing the kernel causes the issue. Hope this helps someone who has the same problem. Gonna stick to stock kernel for now
Click to expand...
Click to collapse
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.

iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?

ieldra said:
Pretty sure I am, "m7-faux123-Sense43-007m.zip" and "faux123-jb43-sense-camera-fix.zip". Did you have to root again after installing ElemntalX ? Just finished reinstalling ROM for fourth time today, going to check SuperSu works, go back to recovery, make a nandroid backup and perhaps try ElementalX Is there a kernel control app for it ?
Click to expand...
Click to collapse
I only had to flash SuperSU once. I use TricksterMod.

I've experienced this problem on two different ROMs (different variations of the same problem, actually). In both cases, flashing the same SuperSU .zip fixed it. Link here.

iElvis said:
That's odd. Are you sure you're flashing the right kernel? I had no such problems with the 4.3 version of ElementalX.
Click to expand...
Click to collapse
Dude,
Thank you so much for you post, been wondering is this problem bothering me since i saw you post so i tested it out, end up the rom was fine till i flash the faux123 kernal and camera fix, and binary not install issue come out again.
for people who having same problem, this might be the issue
Cheer

[Q] Stuck in boot - can get to recovery. Any ideas?

I've been using ViperOneM8 for the past few months. This weekend I tried to switch to AndroidRevolution, but it got stuck on startup. I decided to cut my losses and go back to Viper. I attempted to restore the backup I had made just before attempting the switch, but that got stuck on startup as well.
I've since tried to restore every backup I have to no avail. I've tried flashing new ROMs. I'm hoping someone smarter than myself has an idea of what to try next...?
When it gets stuck, I see the HTC splash screen, then the ViperOne animation, then nothing changes. All I can do is wait for the battery to die, plug it in, and then I'm able to get to recovery again.
Using TWRP recovery, FYI.

Which version of TWRP are you using? Have you verified md5's on ROM downloads?

EVOuser94 said:
Which version of TWRP are you using? Have you verified md5's on ROM downloads?
Click to expand...
Click to collapse
Thanks for the reply! Yes, I verified MD5s for the new ROMs. I'll have to get back to you re:TWRP version in the next hour or so. It's roughly 3-4 months old I believe.

EVOuser94 said:
Which version of TWRP are you using? Have you verified md5's on ROM downloads?
Click to expand...
Click to collapse
looks like TWRP v2.7.0.2

Update to latest twrp and try again

As far as I know ARHD is not Sprint compatible, by flashing it you messed up the partitions, you will have to RUU and start fresh and only flash roms from the Sprint section.

EVOuser94 said:
Update to latest twrp and try again
Click to expand...
Click to collapse
Flashed 2.8.3.0, but it didn't work. Got stuck loading into recovery (bizarre)
Flashed 2.8.1.0 just fine though. That did the trick! Thanks EVO! I should have thought of that... oh well.

BD619 said:
As far as I know ARHD is not Sprint compatible, by flashing it you messed up the partitions, you will have to RUU and start fresh and only flash roms from the Sprint section.
Click to expand...
Click to collapse
This surprised me so I checked - it was actually an InsertCoin I tried to flash. AR was one I was looking at, probably wasn't able to find it in the Sprint section so I went for a different one. My mistake. Thanks for the response though!

Cannot get M Preview 2 rooted

Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!

jonzey231 said:
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
Click to expand...
Click to collapse
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.

simms22 said:
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
Click to expand...
Click to collapse
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.

jonzey231 said:
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
Click to expand...
Click to collapse
well, then its odd, you should have gotten root after flashing both in recovery.

simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
I know, right? I'll give it another shot. I'm getting ready to do it now. I'll update in a few minutes when I've finished up.
Edit: Grabbed Elemental from here: http://forum.xda-developers.com/showpost.php?p=61931417&postcount=3921&nocache=1
Updated last night so it should be the absolute latest version. So I'll flash twrp in fastboot, then boot into twrp and flash the kernel first, and then supersu and I should be good to go.

The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.

jonzey231 said:
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
Click to expand...
Click to collapse
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.

simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
It's been in a bootloop for like 5 minutes. It would get the the Android is Starting screen and loan for about 30-40 seconds, then reboot.
Then it would hit the validation screen and reboot.
Then it would boot back to Android is Starting, freeze, and reboot lol
It is very erratic, all of this has been going on without any interference from me. Just letting it sit there trying to work through it's issues.
Then all of a sudden as I was typing "adb reboot-bootloader" the thing boots right into my existing lockscreen haha. So I guess I'll just do my best to not have to reboot this thing in case it wants to have a seizure like that again lol.

simms22 said:
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
Click to expand...
Click to collapse
It's finally up and loaded and yes, I've got root now. Thanks for your help today.

jonzey231 said:
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
Click to expand...
Click to collapse

simms22 said:
Click to expand...
Click to collapse
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.

jonzey231 said:
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
Click to expand...
Click to collapse
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.

simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.

jonzey231 said:
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
Click to expand...
Click to collapse
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18

simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
simms22 said:
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
Click to expand...
Click to collapse
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.

jonzey231 said:
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
Click to expand...
Click to collapse
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053

simms22 said:
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
Click to expand...
Click to collapse
Awesome, I didn't really he'd made a ROM for Preview 2 yet. I'll make a backup and give it a shot, thanks for pointing this out to me.
I'll let you know how it goes as well!
Update: it worked!!! I wiped the system partition and flashed the ROM. It failed the first time so I tried again after mounting the system and now I've got too with system write access!! Spread the word my friend.

dm verity boot error cb9 fixed..

I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249

First flash this file and then Rom. That's right?? Or its other way around

karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..

Wouldn't this procedure downgrade some performance on the device?

Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..

Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted

Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..

Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?

cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.

I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs

Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk

puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..

snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..

This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.

cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice

cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.

snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?

cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus

snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk

it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)