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

[Q] Help Nexus 4 stuck at boot logo, I think I wiped everything off my phone.

Im sorry if i am repeating a post but upo hours of searching and trying methods i've come to posting my issue here. I am a complete noob to android phones, Bought the nexus 4 recently and had it rooted by a friend. There was a ROM on it that made phones louder which I did not want. I tried to get rid of it in recovery mode and I believe I formated the system and sd card. Now the phone stays stuck on the boot animation. I have re-rooted the phone and put in the clock world recovery rom so that works. But trying to put jellybean 4.2.1 back on is seeming impossible because the phone dosent get past the boot animation and adb isnt recognizing the device. I would highly appreciate some help! Anything would be a contribution. Thank you!

Do you have a backup? If so, then restore it in recovery. If not, then you should have zip. Custom rom in your sd card. Find it in recovery under (install Zip From SDCad) flash the rom file.
Sent from my Nexus 4 using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=2010312

droidmeup said:
Do you have a backup? If so, then restore it in recovery. If not, then you should have zip. Custom rom in your sd card. Find it in recovery under (install Zip From SDCad) flash the rom file.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunatley I did not have a backup, and when I try to get to the custom rom in the sd card, it says no files found. Since you are a nexus 4 user would you by any chance know if the nexus 4 all in one tool kit can flash a stock build through fast boot mode?

Can u get into boot loader ? Just fastboot stock ROM http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ there's the IMG u can find instructions how to do it everywhere . goodluck . U CANT BRICK THIS PHONE RELAX just call it learning experience
U prob lost your **** but u still have a phone
---------- Post added at 11:44 PM ---------- Previous post was at 11:41 PM ----------
ak0409 said:
Unfortunatley I did not have a backup, and when I try to get to the custom rom in the sd card, it says no files found. Since you are a nexus 4 user would you by any chance know if the nexus 4 all in one tool kit can flash a stock build through fast boot mode?
Click to expand...
Click to collapse
Ya u could but ur better off leading how do it yourself stay away from toolkits

Same issue
Hello, the same issue occurred with me. I formatted all the data through CWM and now the phone is stuck on google logo. It does go to the recovery mode.
Is there any way I can mount the phone so that I can transfer a flashable zip of any custom rom?
Or anyway to return to stock?
Please help..:crying:

huntish said:
Hello, the same issue occurred with me. I formatted all the data through CWM and now the phone is stuck on google logo. It does go to the recovery mode.
Is there any way I can mount the phone so that I can transfer a flashable zip of any custom rom?
Or anyway to return to stock?
Please help..:crying:
Click to expand...
Click to collapse
Load a rom by pushing it with adb, command : adb push NameRom.zip /sdcard/NameRom.zip and flash with recovery. Place the rom in fastboot folder (platform-tools) first .

gee2012 said:
Load a rom by pushing it with adb, command : adb push NameRom.zip /sdcard/NameRom.zip and flash with recovery. Place the rom in fastboot folder (platform-tools) first .
Click to expand...
Click to collapse
I had same issue,
Was stuck on a bootloop,
Which I'm still stuck,
Downloaded Android SDK, extracted the Google System Image and placed it in the Platrorm_tools folder,
Flashed the System image, but still no luck :'(
Still I'm stuck on this boot logo.
Can someone help me please??
Its been almost 8 hours I'm with this stupid animation.

Rockstar600 said:
I had same issue,
Was stuck on a bootloop,
Which I'm still stuck,
Downloaded Android SDK, extracted the Google System Image and placed it in the Platrorm_tools folder,
Flashed the System image, but still no luck :'(
Still I'm stuck on this boot logo.
Can someone help me please??
Its been almost 8 hours I'm with this stupid animation.
Click to expand...
Click to collapse
Reboot in recovery - factory reset. You can actually try to clean cache first and see if it helps, if it doesn`t- factory reset!

BigDig said:
Reboot in recovery - factory reset. You can actually try to clean cache first and see if it helps, if it doesn`t- factory reset!
Click to expand...
Click to collapse
Thank you for your patient reply,
I cannot still boot, I have tried what you have mentioned :'(
Please someone guide me

Rockstar600 said:
Thank you for your patient reply,
I cannot still boot, I have tried what you have mentioned :'(
Please someone guide me
Click to expand...
Click to collapse
OK. Download factory image 4.3 from Google, extract twice , find the flash-all.bat, put your phone in fastboot mode, execute!
Sent from my Nexus 4 using Tapatalk 4

Rockstar600 said:
Thank you for your patient reply,
I cannot still boot, I have tried what you have mentioned :'(
Please someone guide me
Click to expand...
Click to collapse
You need to flash the new bootloader, modem, and also boot.img (kernel) if you come from different version of Android. i.e. 4.2.2 to 4.3.

BigDig said:
OK. Download factory image 4.3 from Google, extract twice , find the flash-all.bat, put your phone in fastboot mode, execute!
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I did that too!
Its still stuck on the X logo!!
I cannot just do anything!
One thing I would like to ask you here,
You told me to extract files TWICE??
I extracted only once,
I didn't extract the image_occam_XXXXX which is present inside the zip file.
I saw a video guide on YouTube by OODE, and he too did the same!
I would also like to tell you that, when I was installing this Rootbox ROM, I accidentally also WIPED SYSTEM in TWRP,
Is this the reason for me to suffer now??

Rockstar600 said:
I did that too!
Its still stuck on the X logo!!
I cannot just do anything!
One thing I would like to ask you here,
You told me to extract files TWICE??
I extracted only once,
I didn't extract the image_occam_XXXXX which is present inside the zip file.
I saw a video guide on YouTube by OODE, and he too did the same!
I would also like to tell you that, when I was installing this Rootbox ROM, I accidentally also WIPED SYSTEM in TWRP,
Is this the reason for me to suffer now??
Click to expand...
Click to collapse
Yes wiping system left you with no OS. Extract twice in order to get to the flash-all.bat file! Once you see that file you can proceed. And remember that you have to be in fastboot mode
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 12:10 PM ---------- Previous post was at 11:18 AM ----------
Rockstar600 said:
I did that too!
Its still stuck on the X logo!!
I cannot just do anything!
One thing I would like to ask you here,
You told me to extract files TWICE??
I extracted only once,
I didn't extract the image_occam_XXXXX which is present inside the zip file.
I saw a video guide on YouTube by OODE, and he too did the same!
I would also like to tell you that, when I was installing this Rootbox ROM, I accidentally also WIPED SYSTEM in TWRP,
Is this the reason for me to suffer now??
Click to expand...
Click to collapse
Did it work?

BigDig said:
Yes wiping system left you with no OS. Extract twice in order to get to the flash-all.bat file! Once you see that file you can proceed. And remember that you have to be in fastboot mode
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 12:10 PM ---------- Previous post was at 11:18 AM ----------
Did it work?
Click to expand...
Click to collapse
Nothing at all!
I'm feeling so stupid right now,
I got this error when I tried another way to flash all the files separately via Android SDK
Any idea??
Thank you for replying me, I really appreciate your help
See this
{
"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"
}

Rockstar600 said:
Nothing at all!
I'm feeling so stupid right now,
I got this error when I tried another way to flash all the files separately via Android SDK
Any idea??
Thank you for replying me, I really appreciate your help
See this
Click to expand...
Click to collapse
What you`re trying to do won`t work because you`re trying to apply the zip for the OTA update to 4.3. You need the FULL factory image from google. The update won`t apply because you have newest radio and older bootloader and that`s a problem. Just do what I told you to and you should be good to go in no time

BigDig said:
What you`re trying to do won`t work because you`re trying to apply the zip for the OTA update to 4.3. You need the FULL factory image from google. The update won`t apply because you have newest radio and older bootloader and that`s a problem. Just do what I told you to and you should be good to go in no time
Click to expand...
Click to collapse
HELL YES!!!!!!!!!!!!!!!!!!!!!!!!!
It worked!!!
Thank you man!!!!!
THANK YOU SO MUCH!!!!!!
It worked with 4.2.2!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I FREAKING LOVE YOU!!
---------- Post added at 10:11 PM ---------- Previous post was at 10:01 PM ----------
BigDig said:
What you`re trying to do won`t work because you`re trying to apply the zip for the OTA update to 4.3. You need the FULL factory image from google. The update won`t apply because you have newest radio and older bootloader and that`s a problem. Just do what I told you to and you should be good to go in no time
Click to expand...
Click to collapse
Okay its booted,
But I have no signal and no wifi,
How shall I make it work??

Rockstar600 said:
HELL YES!!!!!!!!!!!!!!!!!!!!!!!!!
It worked!!!
Thank you man!!!!!
THANK YOU SO MUCH!!!!!!
It worked with 4.2.2!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I FREAKING LOVE YOU!!
---------- Post added at 10:11 PM ---------- Previous post was at 10:01 PM ----------
Okay its booted,
But I have no signal and no wifi,
How shall I make it work??
Click to expand...
Click to collapse
Grrrrr. Go to settings-about phone and see what baseband you have

BigDig said:
Grrrrr. Go to settings-about phone and see what baseband you have
Click to expand...
Click to collapse
My phone restarted itself,
And again I'm here in a bootloop :/
Okay it restarted, it says baseband is UNKNOWN

Rockstar600 said:
My phone restarted itself,
And again I'm here in a bootloop :/
Okay it restarted, it says baseband is UNKNOWN
Click to expand...
Click to collapse
WTF!? Ok do the same procedure but with the 4.3 Google image. This will flash newest bootloader and radio! Seems like something went wrong with the 4.2.2,,,,
---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------
BigDig said:
WTF!? Ok do the same procedure but with the 4.3 Google image. This will flash newest bootloader and radio! Seems like something went wrong with the 4.2.2,,,,
Click to expand...
Click to collapse
or just try to flash only one of the radios via fastboot

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.

Root & 6.0.1

Friends--I'm not a noob, but I'm confused.
I just updated by phone to the newest image by fastboot flashing vendor, system, boot.
how, in this situation, do i obtain root? Or is that impossible if I am on 6.0.1?
Sorry...still trying to conceptually understand the root situation in marshmallow.

After that, I flashed chainfire's latest SuperSu 2.60 in TWRP and it auto-patched the files for root. Now I'm on systemless root and on the newest firmware.
Sent from my Nexus 6P using Tapatalk

caifan said:
After that, I flashed chainfire's latest SuperSu 2.60 in TWRP and it auto-patched the files for root. Now I'm on systemless root and on the newest firmware.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Can you tell me how to update trough fastboot without erasing everything? I mean, what are the commands? Thank you in advance.

GKti22 said:
Can you tell me how to update trough fastboot without erasing everything? I mean, what are the commands? Thank you in advance.
Click to expand...
Click to collapse
These are the commands https://i.imgur.com/P3QOfxU.png

If only there was a guide for you. Please check the general forum.

"i'm not a noob"
yet you do not know how to perform a basic search
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
FOR THE MAGIC SEE ITEM #9!!​

caifan said:
After that, I flashed chainfire's latest SuperSu 2.60 in TWRP and it auto-patched the files for root. Now I'm on systemless root and on the newest firmware.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I did the same, but it causes the camera not to work since it installs a 6.0.0 kernel. Plus, I lost root and had to reflash SuperSu in TWRP every time I rebooted.

geoff5093 said:
I did the same, but it causes the camera not to work since it installs a 6.0.0 kernel. Plus, I lost root and had to reflash SuperSu in TWRP every time I rebooted.
Click to expand...
Click to collapse
Same here camera just shows shutter icon but no screen. This is most probably because of we're flashing 6.0.0's k modified image not latest kernel with modifications. We hope chain fire updates kernel asap

OsmDroid said:
Same here camera just shows shutter icon but no screen. This is most probably because of we're flashing 6.0.0's k modified image not latest kernel with modifications. We hope chain fire updates kernel asap
Click to expand...
Click to collapse
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1

Last week I finally unlocked my bootloader, rooted using BETA-SuperSU-v2.52.zip. Could I get some help/instructions on how to flash the new 6.0.1 and retain my root (as well as making sure my camera works)? I just want to make sure I don't brick my phone.

steveo17 said:
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Click to expand...
Click to collapse
Do you confirm that systemless root works on stock kernel without any problems of camera or loosing root after reboot or any such ?! It it works flawless then i am ready to install some stuff on 6.0.1
---------- Post added at 09:06 PM ---------- Previous post was at 08:54 PM ----------
steveo17 said:
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Click to expand...
Click to collapse
OsmDroid said:
Do you confirm that systemless root works on stock kernel without any problems of camera or loosing root after reboot or any such ?! It it works flawless then i am ready to install some stuff on 6.0.1
Click to expand...
Click to collapse
Fk i was searching for proper method for perfect root and chain fire gave it since he released 2.61 all i had to do is to just read whole post. Even Chainfire confirms
{
"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"
}

steveo17 said:
this. you cannot use the 6.0.0 kernel on the 6.0.1 build.
SuperSU 2.61 which is sytemless works fine on the stock 6.0.1 kernel.
I flashed the latest update last night via fastboot. let the phone boot up, then flashed 2.61 SuperSU (did not install a modified boot.img). this morning i installed elementalx which was updated for 6.0.1
Click to expand...
Click to collapse
*dumbass question*
DO you lose any data doing so ?
I want to update to 6.0.1 +root but I'm lazy af if I need to reinstall all my ****

kauemelhado said:
*dumbass question*
DO you lose any data doing so ?
I want to update to 6.0.1 +root but I'm lazy af if I need to reinstall all my ****
Click to expand...
Click to collapse
no, you do not lose any data via fastboot so long as you do not flash the data portion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
OsmDroid said:
Do you confirm that systemless root works on stock kernel without any problems of camera or loosing root after reboot or any such ?! It it works flawless then i am ready to install some stuff on 6.0.1
---------- Post added at 09:06 PM ---------- Previous post was at 08:54 PM ----------
Fk i was searching for proper method for perfect root and chain fire gave it since he released 2.61 all i had to do is to just read whole post. Even Chainfire confirms
]
Click to expand...
Click to collapse
yes, i simply installed supersu 2.61 after updating to 6.0.1 and it worked flawlessly

steveo17 said:
no, you do not lose any data via fastboot so long as you do not flash the data portion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
yes, i simply installed supersu 2.61 after updating to 6.0.1 and it worked flawlessly
Click to expand...
Click to collapse
So,
If I need to instal the update + root + ex kernel...
First I'll flash de update without the data partition (via adb), then I'll flash the kernel and then supersu 2.61, right? :silly:

kauemelhado said:
So,
If I need to instal the update + root + ex kernel...
First I'll flash de update without the data partition (via adb), then I'll flash the kernel and then supersu 2.61, right? :silly:
Click to expand...
Click to collapse
no. see below
1. The update will be flashed via Fastboot via these steps
These steps assume the files are in C:\angler\images, but you can also drag and drop into terminal or command prompt.
If you have not done this before, be careful to do these exactly as follows or else you will have to factory reset (and lose data).
also, you will download the factory image, extract once, and then extract the zip within it to find the cache, recovery, system, vendor, etc...)
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
2. Flash TWRP via Fastboot
Fastboot flash recovery "TWRP"
3. Reboot to Recovery
4. Install SuperSU 2.61
5. Install ElementalX
6. Install Xposed

steveo17 said:
no. see below
1. The update will be flashed via Fastboot via these steps
These steps assume the files are in C:\angler\images, but you can also drag and drop into terminal or command prompt.
If you have not done this before, be careful to do these exactly as follows or else you will have to factory reset (and lose data).
also, you will download the factory image, extract once, and then extract the zip within it to find the cache, recovery, system, vendor, etc...)
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
2. Flash TWRP via Fastboot
Fastboot flash recovery "TWRP"
3. Reboot to Recovery
4. Install SuperSU 2.61
5. Install ElementalX
6. Install Xposed
Click to expand...
Click to collapse
Hmm, so I need to re-flash TWRP =(
Thank you bro :victory::good:

kauemelhado said:
Hmm, so I need to re-flash TWRP =(
Thank you bro :victory::good:
Click to expand...
Click to collapse
honestly i am not sure if the factory recovery needs to be flashed, i just did because that's what people said worked in the past.
only takes a few seconds to flash TWRP again

steveo17 said:
honestly i am not sure if the factory recovery needs to be flashed, i just did because that's what people said worked in the past.
only takes a few seconds to flash TWRP again
Click to expand...
Click to collapse
Better safe than sorry, right? hehehe
Thank you!!

If you have encryption disabled, will flashing 6.0.1 change it to encrypted?

ShaunWinSC said:
If you have encryption disabled, will flashing 6.0.1 change it to encrypted?
Click to expand...
Click to collapse
I had some difficulty coming from stock, rooted and unencrypted. I manually flashed the images then went straight into twrp and flashed su 2.61. Using this method I was still unencrypted but I lost root upon every reboot. I then reflashed the images and booted into system before flashing supersu. During that boot it encrypted my data partition. I then flashed twrp then supersu 2.61 and now my root sticks. I don't know if the issue was being unencrypted but just wanted to give a heads up and hopefully someone else can chime in.

Rooted phone, OTA update (YOG4PAS9IG)

Hieveryone,
last night i've tried to update my phone using OTA, but it still not work. I have TWRP recovery and supersu installed. I believe this is because of root. My phone restart in recovery mode and says something like "zip file is corrupted". What's the solution?
Thanks in advance and sorry for My bad english!

Lorenzo Benevento said:
Hieveryone,
last night i've tried to update my phone using OTA, but it still not work. I have TWRP recovery and supersu installed. I believe this is because of root. My phone restart in recovery mode and says something like "zip file is corrupted". What's the solution?
Thanks in advance and sorry for My bad english!
Click to expand...
Click to collapse
https://s31.postimg.org/w6twfqivv/66957ed3_9534_4de8_9804_64a80d21a259.jpg
for me this error comes

I have also same problem in my zuk z1 Indian version. Cyanogen recovery and kingroot. OTA install failed during recovery. I manually download the file then apply update in recovery. It also failed. Please anyone help me

The ota not work on twrp n kingroot n supersu its work only on
Stock recovery only bro
---------- Post added at 07:20 PM ---------- Previous post was at 07:15 PM ----------
The ota not work on twrp n kingroot n supersu its work only on
Stock recovery only bro I m from india

So if I select "Update cyanogen recovery" it should work. I'm right? And I can keep SuperSU

I am having the and problem. I have a rooted phone, I had SuperSu, Root Browser, ROM Toolbox and Busybox. I uninsta]lled then all, I don't know know of my phone is still rooted or not, of it is I have to unroot it, though I don't know how, but till now uninstalling all those apps didn't help, while updating it's still getting failed at Verifying Current System.
Since in new here, I can't post an image here, sorry.

Lorenzo Benevento said:
Hieveryone,
last night i've tried to update my phone using OTA, but it still not work. I have TWRP recovery and supersu installed. I believe this is because of root. My phone restart in recovery mode and says something like "zip file is corrupted". What's the solution?
Thanks in advance and sorry for My bad english!
Click to expand...
Click to collapse
{
"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 help me
Sent from my Z1 using XDA-Developers mobile app

I have twrp and super su also on my phone I tired updating the ota with FLASHFIRE but got stock at boot...I need to flash and download a new stock ROM
U can try FLASHFIRE might work for u?
Sent from my Infinix X510 using Tapatalk

Attention everyone
You'll need latest signed zip to update your device to latest version.
Interested one can read this for reason.

I flashed the zip from recovery skipping the md5 verification. It has worked for me! I have only losed my root permission!

Lorenzo Benevento said:
I flashed the zip from recovery skipping the md5 verification. It has worked for me! I have only losed my root permission!
Click to expand...
Click to collapse
Oh nice, Please tell me how to skip verification
Sent from my Z1 using XDA-Developers mobile app

vishnuchandh said:
Oh nice, Please tell me how to skip verification
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you are on stock recovery then just flash signed zip. Zip signature verification is only for custom recovery like TWRP. To disable zip signature verification in TWRP recovery, goto TWRP setting and uncheck 'zip file signature verification' and while flashing don't select 'zip file signature verification'. File will be falshed without checking for any MD5 file checksum.

saurav007 said:
If you are on stock recovery then just flash signed zip. Zip signature verification is only for custom recovery like TWRP. To disable zip signature verification in TWRP recovery, goto TWRP setting and uncheck 'zip file signature verification' and while flashing don't select 'zip file signature verification'. File will be falshed without checking for any MD5 file checksum.
Click to expand...
Click to collapse
Sorry I have not twrp. I'm in stock recovery n rom but rooted with kingroot
Sent from my Z1 using XDA-Developers mobile app

vishnuchandh said:
Sorry I have not twrp. I'm in stock recovery n rom but rooted with kingroot
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Flash signed zip from stock recovery then.

saurav007 said:
Flash signed zip from stock recovery then.
Click to expand...
Click to collapse
Thanks a lot. Problem solved. Updated without erasing data.
Sent from my ZUK Z1 using XDA-Developers mobile app
---------- Post added at 02:12 PM ---------- Previous post was at 02:04 PM ----------
After the above update no root in my phone
Sent from my ZUK Z1 using XDA-Developers mobile app

vishnuchandh said:
After the above update no root in my phone
Sent from my ZUK Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, signed zip revert /system partition to completely stock. Flash latest SuperSU.zip to get back root access.

Thank you very much.
Sent from my ZUK Z1 using XDA-Developers mobile app

I'm in cm recovery so can't flash supersu.(signature problem). Need to change twrp recovery
Sent from my ZUK Z1 using XDA-Developers mobile app

vishnuchandh said:
I'm in cm recovery so can't flash supersu.(signature problem). Need to change twrp recovery
Sent from my ZUK Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Obviously, you'll need a custom recovery. Flash TWRP recovery and afterwards flash SuperSU from TWRP recovery.