Database Users

S3 Now available in clockwork recovery

The S3 has been added to supported devices​
{
"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"
}

anyone else having issues flashing CWM Touch from recovery? I can't get it to take even though it successfully completes.

contradude said:
anyone else having issues flashing CWM Touch from recovery? I can't get it to take even though it successfully completes.
Click to expand...
Click to collapse
You downloaded the d2spr version from download.clockworkmod.com?
Sent from my SPH-L710 using Tapatalk 2

:O i know two of those phones!
did the cwm on the connect and lucid

shabbypenguin said:
:O i know two of those phones!
did the cwm on the connect and lucid
Click to expand...
Click to collapse
When are we gonna get an update on the prevail?
Sent from my SPH-L710 using xda premium

Can't backup ROM, "sd marker not found"
Any ideas?

It said that to me when trying to use the app to backup but I did it manualy and it worked fine.

Any advantage/disadvantage of flashing the new CWM through ROM Manager, or manually through ODIN? Btw, do you flash this through ODIN or (old) CWM since this is a .img file?

Just so ppl know, you can find all CWM Recoveries here:
http://download.clockworkmod.com/recoveries/
Our device is d2spr
Towards the bottom you'll find the CWM Touch Recovery, I flashed the img using Mobile Odin and it's working fine
Sent from my SPH-L710 using Tapatalk 2

fergie716 said:
Just so ppl know, you can find all CWM Recoveries here:
http://download.clockworkmod.com/recoveries/
Our device is d2spr
Towards the bottom you'll find the CWM Touch Recovery, I flashed the img using Mobile Odin and it's working fine
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ah... flashed it through mobile ODIN... thanks for the tip, Fergie!

MinimalistChris said:
Ah... flashed it through mobile ODIN... thanks for the tip, Fergie!
Click to expand...
Click to collapse
No problem!
Another tip, backups made with the older CWM recovery (the unofficial one, the one you probably flashed after rooting initially), those older backups may not be compatible with the newer, official versions. I'm using the latest CWM Touch 5.8.4.6 and it seems to backup system and data differently
Sent from my SPH-L710 using Tapatalk 2

Can't seem to get the .img to flash when using mobile odin... I tried to click on Recovery then find the file, but it doesn't list the file, only the folders I have available. Am I doing something wrong?

klarthur said:
Can't seem to get the .img to flash when using mobile odin... I tried to click on Recovery then find the file, but it doesn't list the file, only the folders I have available. Am I doing something wrong?
Click to expand...
Click to collapse
If you downloaded the CWM img file rename it to just "recovery.img" then put it on the root of your SD
Open up Mobile Odin, Select "Open File", then select your recovery.img (I put it on Internal Storage)
After you select your recovery.img, before you select Flash Firmware, it should list the recovery.img in the recovery slot
Then you should be all set. Select Flash Firmware and after it flashes you should automatically be rebooted into recovery (I suggest making a backup ASAP just to be safe)

Phew... Glad to see there is a fix... I thought I was losing my freaking mind when I tried backup of my rom....
EDIT: something is borked...not right ...frustrated user...mad.mad.mad :crying::crying::crying:
Sent from my SPH-L710 using xda premium

Mobile Odin didn't help me much... could I install the touch recovery.img through adb? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 ?

wpjessie said:
Mobile Odin didn't help me much... could I install the touch recovery.img through adb? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 ?
Click to expand...
Click to collapse
The mobile Odin way did not work for me. After I flashed the img file, rebooted and tried to do a backup using Clockwork mod, the phone rebooted and gave me the same errors as posted above! ???Help???
EDIT: Duplicated this same error/issue on my second GS3...so it is definitely CWM related...also..cannot "see" or view the backups on the phone via the Rom Manager app either..very frustrating...hope those smarter than me can fix...I am willing to assist in any way... thanks

I flashed the new touch cwm in the unofficial recovery and it works, but doesn't stick, reverts back to the old recovery after a reboot???
Sent from my SPH-L710 using xda premium

This may be a dumb question but, couldn't we just install ROM Manager and flash the CWM recovery with it, like I used to do on my EVO 4G?

w8setter said:
I flashed the new touch cwm in the unofficial recovery and it works, but doesn't stick, reverts back to the old recovery after a reboot???
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
the team epic guys has set us up with a recovery that would stick cause the first samsung ota automatically reverted to their own recovery instead of cwm. maybe this issue is related. it just keeps overwriting what you flashed thinking that it's a bad (Samsung) recovery. don't know for sure as i haven't tried it yet.

gtpdjw said:
It said that to me when trying to use the app to backup but I did it manualy and it worked fine.
Click to expand...
Click to collapse
that defeats the purpose of this new, "supported" recovery as i would like the option to flash things and manage backups via rom manager.
jf11time said:
This may be a dumb question but, couldn't we just install ROM Manager and flash the CWM recovery with it, like I used to do on my EVO 4G?
Click to expand...
Click to collapse
thats what i did.
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
mine sticks, just rebooted 2 times, and after booting into recovery again still version 5.8.4.6 which is latest.
installed via rom manager
about to try touch

Firmware-update JLS36I (Android 4.3.1) Nexus 7 2013 LTE available

This morning I was suprised to find a new update for my Nexus 7 2013 LTE; it brings the Android-version to 4.3.1
No changelog found yet...
{
"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"
}

Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?

Jacktheskipper said:
Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?
Click to expand...
Click to collapse
It's broken my root, though that's probably because I used the OTA update rather than flashing in recovery.

I got it too.
in the update file a some changes at:
keymaster / keystore
camera firmware
framework
services and telephony-common
what exactly has changed I do not know.
root + recovery need to be flashed again. but no problems.

if root and recovery need to be flashed again, did you just do the ota update from the sytem or did you sideload the zip and flash it from recovery?

I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
You won't be able to until someone puts out a custom ROM for Flo/Deb.

jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.

jak3z said:
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.
Click to expand...
Click to collapse
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!

jmone said:
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!
Click to expand...
Click to collapse
That was totally unnecessary,

I've updated European nexus in Russia without any problem
Have a trwp recovery and supersu binary. Check ota survivalable mode in supersu and just apply update. Trwp updates all stuff. Root works, recovery didn't check for now

jak3z said:
That was totally unnecessary,
Click to expand...
Click to collapse
Thanks.... Next time!

Update :lost trwp recovery and need to flash it again.
Отправлено с моего...

oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

keplenk said:
oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
You can run the OTA perfectly fine, you will lose Root and Recovery after you OTA, but you can get back those 2 anytime you want. Grab the CF-Auto-Root of chainfire (its on the Android Original Dev forum) and you will get root back.

keplenk said:
or can i just update while rooted?
p
Click to expand...
Click to collapse
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.

Jacktheskipper said:
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.
Click to expand...
Click to collapse
http://download.chainfire.eu/supersu

1. Go into SuperSu settings to enable survival mode.
2. Download the OTA directly on your Nexus as you would without root and restart to install.
3. It will be installed by TWRP, root will be kept, but TWRP will be gone.
4. Reflash TWRP in Fastboot.

[Q] getting back to stock after cwm

Hello everyone,
today I rooted + bootloader unlocked my N4 with Towelroot and after that I installed Multirom because I wanted to try the Android L developer Preview.
After realizing that a rooted device with a custom recovery won't get official OTA updated anymore I want to have my stock N4 back
I did not install any rom.
Is there a way I can get my stock recovery back WITHOUT having to set up my device again?
I mean, only the recovery should have changed.
I have a mac and a Win XP PC for any tools. I am running stock Android 4.4.4 and kernel 3.4.0-perf-ga6edd5e
Very thankful for any help

If all you need to do is get the stock recovery back you can do that in fastboot. The factory image includes recovery.img. Flash that
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Free mobile app

will this bring me back the ability to get OTA updates?
If so.. is there a tutorial or anything like that I can follow? I have not worked with ADB and fastboot before but thanks a lot for your quick answer!

unrealmac said:
will this bring me back the ability to get OTA updates?
If so.. is there a tutorial or anything like that I can follow? I have not worked with ADB and fastboot before but thanks a lot for your quick answer!
Click to expand...
Click to collapse
It's easy to do. First Google 15 second adb install xda. That'll set up fastboot on your pc. Then Google nexus 4 factory image. Download that and then extract it using winrar or 7-zip. In there you'll find a zip file. Extract that too and you'll find recovery.img.
Boot your device into the bootloader and then in a command prompt opened in the same directory as recovery.img is located run the commands I gave you earlier. You'll then have the stock recovery on your device.
Sent from my Nexus 5 using XDA Free mobile app

I do not find a second archive in there.
Could it be that the recovery.img is also called 'boot.img' ?

unrealmac said:
I do not find a second archive in there.
Could it be that the recovery.img is also called 'boot.img' ?
Click to expand...
Click to collapse
no. Boot.img is the kernel. There should be a zip file in there. In there is recovery.img
Edit, out should be called image- something or other
Edit, edit. If you found boot.img, recovery should be in the same directory as it
Sent from my Nexus 5 using XDA Free mobile app

Thanks again for your fast help.
Okay I found the recovery.img
just to be sure: this will not any of my data/apps on the phone, right?
If so I think I am ready to proceed

unrealmac said:
Thanks again for your fast help.
Okay I found the recovery.img
just to be sure: this will not any of my data/apps on the phone, right?
If so I think I am ready to proceed
Click to expand...
Click to collapse
It won't delete any data
Sent from my Nexus 5 using XDA Free mobile app

I tried it several times with fastboot on mac (the 15 sec installer on Win XP did not work) but everytime I open fastboot I am not able to type anything in.
In the last row of the screenshot it says something like "process closed"
Is the any other tool I can use for that?
{
"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"
}

unrealmac said:
I tried it several times with fastboot on mac (the 15 sec installer on Win XP did not work) but everytime I open fastboot I am not able to type anything in.
In the last row of the screenshot it says something like "process closed"
Is the any other tool I can use for that?
Click to expand...
Click to collapse
I'm not familiar with the Mac, but another alternative is to do it from your phone. Get flashify from the play store and flash the recovery.img in it. Just copy recovery.img to your phone
Sent from my Nexus 5 using XDA Free mobile app

Ha! This worked instantly. After pressing "reboot now" it tried to reboot but a screen with "no service" appeared.
After rebooting the device manually everything booted normally.
Is there Any way I can now check if I now have the "stock recovery" again?
What are the criteria to get official OTA updates again from Google?
Thanks so much!

unrealmac said:
Ha! This worked instantly. After pressing "reboot now" it tried to reboot but a screen with "no service" appeared.
After rebooting the device manually everything booted normally.
Is there Any way I can now check if I now have the "stock recovery" again?
What are the criteria to get official OTA updates again from Google?
Thanks so much!
Click to expand...
Click to collapse
To check just boot into the bootloader and go to recovery. The stock recovery should be there.
To get the ota you can not have any modified or deleted system files.
Sent from my Nexus 5 using XDA Free mobile app

Mmh the stock recovery is the Android lying on the back, correct?
So If I have the stock recovery+no rom installed I should get updates, correct?
Root and an open bootloader has no effects to it?

unrealmac said:
Mmh the stock recovery is the Android lying on the back, correct?
So If I have the stock recovery+no rom installed I should get updates, correct?
Root and an open bootloader has no effects to it?
Click to expand...
Click to collapse
You are correct. You will lose root when you get the ota
Sent from my Nexus 5 using XDA Free mobile app

Thank you very much.
I think in the past 24 hours I have learnt more than I have reading in the forums silently.
You have really helped someone very desperate

unrealmac said:
Thank you very much.
I think in the past 24 hours I have learnt more than I have reading in the forums silently.
You have really helped someone very desperate
Click to expand...
Click to collapse
Glad i could help
Sent from my Nexus 5 using XDA Free mobile app

Hello @jd1639
I was just trying to sideload the lollypop OTA file via fastbootand I does not install correctly. There is always an error.
Could this have anything to do with the root access and the unlocked bootloader?
I think I read somewhere something like rooted devices will get the OTA update but will not be able to install them correctly.
Is there a way to get that to work without erasing my data?

unrealmac said:
Hello @jd1639
I was just trying to sideload the lollypop OTA file via fastbootand I does not install correctly. There is always an error.
Could this have anything to do with the root access and the unlocked bootloader?
I think I read somewhere something like rooted devices will get the OTA update but will not be able to install them correctly.
Is there a way to get that to work without erasing my data?
Click to expand...
Click to collapse
Are you flashing it in the stock recovery? If not flash the stock recovery in fastboot and try it again. To use adb sideload you need to be booted into recovery not fastboot
Sent from my Nexus 5 using XDA Free mobile app

Yeah I did that.
I got everything stock but have been flashing the recovery back to stock (like I described in the thread).
Getting something like a "status 7" error.
I am booted into recovery mode. The sending process works and then it tries to install the update on my phone and then the installation process stops..

unrealmac said:
Yeah I did that.
I got everything stock but have been flashing the recovery back to stock (like I described in the thread).
Getting something like a "status 7" error.
I am booted into recovery mode. The sending process works and then it tries to install the update on my phone and then the installation process stops..
Click to expand...
Click to collapse
I got that status 7 error myself. I fastboot flashed recovery, system, boot, and cache from 4.4.4. It won't wipe anything. Then the sideload worked
Sent from my Nexus 5 using XDA Free mobile app

[Q] SuperSU can't detect su binary after reboot

I rooted my phone with Kingroot, and ran this script to replace the Kinguser with SuperSU: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
After launching SuperSU it updates the binary and everything works fine until I reboot my phone. Now when I launch SuperSU it says no su binary installed. Using es file explorer I can see the su is in /system/xbin where it should be but SuperSU can't see it.
After rerooting with Kingroot and doing the same process over SuperSU will once again work fine until I reboot my phone. Anyone know what's going on and how I can get SuperSU to work properly?

Anyone?
I tried flashing the SuperSU.zip, but when I launch the app it fails to update the binary. I've also tried installing ChainsDD Superuser but it also fails to update the binary. I've even tried manually copying, setting permissions, and symlinking the files found in the SuperSU.zip, but it still fails to update.
I don't like using Kingroot because apps like Titanium Backup and Lucky Patcher don't work with it's su binary. Has anyone encountered this before? Why won't SuperSU update? And when it does update why can't it survive past a reboot? This is stressful ha. Any help is very much appreciated.
By the way I'm using a Cricket Galaxy S4 (SGH-I337Z). It's a weird model that few people seem to know about (I337ZTUUBOA1). The only root method that works on it is Kingroot otherwise I would have just rooted it some other way.

I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted

xstokerx said:
I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted
Click to expand...
Click to collapse
I've got twrp flashed. How do I use the built in root installer??

When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.

xstokerx said:
When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.
Click to expand...
Click to collapse
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app

Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Sorry to hear was worth a shot I can't think of any thing else right now :crying:

Klown80 said:
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Still no luck I think it's an issue with the SuperSU app. Something during a reboot causes it to break for some reason. I really hope it can be fixed :/

Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......

xstokerx said:
Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......
Click to expand...
Click to collapse
Finally found a working custom rom and everything is working. Thanks

Nihilian said:
Finally found a working custom rom and everything is working. Thanks
Click to expand...
Click to collapse
Awsome to hear u found something that works for u and ur welcome ?

I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
{
"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"
}
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?

jabre said:
I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?
Click to expand...
Click to collapse
I'm sorry but I probly can't help I know nothing about your phone this is the att/Canadian s4 forum how did u get your phone rooted? U can try unrooting and rooting with a different method or retry with same method

MMB29K 6.0.1 OTA Lottery Wait Room : Here We Are Again!

Please post below when you got the OTA and what carrier you're on!
I always love to watch how the OTA's hit peoples devices. From where they're located to what carrier they're on, its interesting to see who gets it first and sadly last.
I am stock, MDB08L 6.0.0, T-Mobile US. The wait begins.

Here we go again! People *****ing about updates!

Hahaha [emoji23]
Sent from my Nexus 5X using Tapatalk

Updated via fastboot. Root + xposed work just fine

mymusicathome said:
Updated via fastboot. Root + xposed work just fine
Click to expand...
Click to collapse
Which type of root and which boot image are you using?

mymusicathome said:
Updated via fastboot. Root + xposed work just fine
Click to expand...
Click to collapse
Did you wipe your data of did you just flash the system?

kbbeer said:
Which type of root and which boot image are you using?
Click to expand...
Click to collapse
Chainfire systemless boot+root
Alaris said:
Did you wipe your data of did you just flash the system?
Click to expand...
Click to collapse
Nope. Flashed everything but userdata

Thinking about manually flashing this since I'm rooted on the modified boot.img.
What steps do I need to take? Unroot then flash everything then reflash modified boot then reroot?

Flash bootloader, radio, boot, cache, system, vendor and then systemless root boot. No need to unroot. Flashing the OEM boot might not be needed but I do it anyway. I boot into Android and then boot to recovery and flash superuser

good 6.0.1 factory image flash-all install
Sent from my Nexus 5X using Tapatalk
{
"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"
}

antiseen said:
Thinking about manually flashing this since I'm rooted on the modified boot.img.
What steps do I need to take? Unroot then flash everything then reflash modified boot then reroot?
Click to expand...
Click to collapse
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.

windows8k said:
good 6.0.1 factory image flash-all install
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Niceeee

ING3NIEUR said:
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
Click to expand...
Click to collapse
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?

Encrypted11 said:
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Click to expand...
Click to collapse
Yes. Beware, doing so will wipe your phone.
Sent from my Nexus 5X using Tapatalk

Encrypted11 said:
How did you get the flash-all.bat script to work? It never did for me.. Do you have to get bootloader unlocked?
Click to expand...
Click to collapse
Bootloader must be unlocked. It's even in the flashing instructions on the Factory Images download page.
---------- Post added at 06:38 PM ---------- Previous post was at 06:29 PM ----------
PiousInquisitor said:
Yes. Beware, doing so will wipe your phone.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No wipe if you delete "-w" from the script.

PiousInquisitor said:
Here we go again! People *****ing about updates!
Click to expand...
Click to collapse
He wasn't *****ing at all.

I'm on Telus but I bought it from the google store so carrier-free. no OTA yet, currently on build MDB08L. Please hurry googs, I want the new emoji

ING3NIEUR said:
Bootloader must be unlocked. It's even in the flashing instructions on the Factory Images download page.
---------- Post added at 06:38 PM ---------- Previous post was at 06:29 PM ----------
No wipe if you delete "-w" from the script.
Click to expand...
Click to collapse
I was warning him about unlocking the bootloader.

Just updated via fastboot and regular root using BETA SuperSU 2.52 with the modified boot.img from the MDB08I/MDB08M builds and everything was working well but I just now noticed my camera shows a black screen. Rebooting didn't help so I'm wiping cache in TWRP and if that doesn't work going to redownload and reflash the images.
Edit: Seems to be an issue with using the old modified boot image from MDB08I/MDB08M for root from Chainfire, exploring now....
Edit 2: Just loaded the boot.img from the MMB29K build but now it seems like I'm in a bootloop. Going to reflash everything again to confirm it's the modified boot.img from MDB08I/MDB08M causing the camera not to work.
Edit 3: Reflashed System and Boot from MMB29K build which obviously removes system root but the Camera is working again. Looks like we will need a modified boot.img from the MMB29K build for system root to work.

ING3NIEUR said:
I flashed using the flash-all.bat script. Deleted "-w" from the script to get rid of the data wipe. Reinstalled TWRP and re-rooted using the traditional root method. I used the modified boot image for MDB08M.
Click to expand...
Click to collapse
I manually flashed everything, but essentially the same process. I also used the 8m modified boot.img