Develop Bugs

ClockworkMod Recovery for Galaxy S (BETA BEWARE)

WARNING: From koush' IRC channel it seems this version may be (permanently?) bricking devices.
At the time of this writing only a single working flash has been reported, and several (full?) bricks.
--Chainfire
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
{
"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"
}
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
932e5f7a9f09c9bc33b14a527f642933
Initramfs source: http://github.com/koush/i9000-leshak-initramfs/tree/koush
Installation instructions:
Install Odin3 v1.0 (MAKE SURE THIS IS THE VERSION YOU USE)
Start Odin3
Press PDA
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads

Wow!... Looks great!
Wanna try after going back home!

I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?

Koush said:
I just finished my recovery for Galaxy S. This requires some testing before I do the final release.
Recovery/Boot TAR download (do NOT extract):
http://bit.ly/czDrPC
Installation instructions:
Install Odin3
Start Odin3
Press PDU
Select the tar file (do NOT extract)
Start phone into download mode.
Press START to flash.
After 20 seconds or so, phone should automatically reboot.
Please join #koush on irc.freenode.net to report bugs. I can't check all 4 XDA threads
Click to expand...
Click to collapse
Can I assume this kernel wasn't compiled with ext3/4 support?

achio1115 said:
I suppose this only works on stock ROM?
My SGS is on JG5 with the following fix...
http://forum.xda-developers.com/showthread.php?t=724251
I followed your instructions, now it won't boot. If I bring it up in recovery mode, I do see all the new options/settings come with your mod. Any suggestions?
Click to expand...
Click to collapse
I'm guessing, but considering this replaces the zImage that mimocan's fix provides anything you have on moved to ext3/ext4 will not be accessible.
To reverse reflash with the mimocan kernel.

Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do

Chainfire said:
Stickyfied for the time being !
Now if only I understood why we needed it... but apparently we do
Click to expand...
Click to collapse
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.

damianarnold said:
Only suitable for those that haven't implemented mimocan's kernel.
Just tried with my 'fixed' ext4 device and it just hangs after the Galaxy S boot screen.
Click to expand...
Click to collapse
I can confirm that, this mod won't work if you have mimocan's kernel applied.

Does it work if you "unapply" it ? Can you get your phone back functional again ?

cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it

raspdeep said:
cos this is also a zImage (aka kernel) update..
flash back mimocan or stock to "unapply" it
Click to expand...
Click to collapse
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid

damianarnold said:
Screws up a little bit more than a reflash of mimocan's kernel I'm afraid
Click to expand...
Click to collapse
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.

Chainfire said:
Can't get it repaired ? In the IRC channel there are a few folks who think they bricked permanently.
Click to expand...
Click to collapse
Every single app. you've installed will need to be reinstalled, it's as if the device is completely cleared of any settings/config.
Basically you need to restore from backup.

If you see this screen
follow these commands while odin3 is opened.
"SIM+SD out, put the battery in. Plug in USB. Hold down both Volume keys, and then push power. Hold it. From the phone > pc screen, hold vol +/- and power, wait til it goes black then returns to that screen. When it goes black the 2nd time release power. " That should put you in download mode so you can install the recovery again.
Then flash this kernel to fix any slowness
http://android.eugenekay.com/Vibrant/LeshakKernel_9_01b9.tar
Eugenekay couldn't link because he only has 4 posts so I'm doing it for him
This might not apply to i9000 users but I posted it just encase.
Also any flashing done in odin formats everything. That is why recovery is needed in order to try and get zip updates. Zip updates wont allow a whole rom flash just modifications.

@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.

so are there gonna be roms in zip ?
or this recovery is gonna handle tars as well?

buddy01 said:
@mod, all the warnings etc about bricking your phone are misleading. If you had the mimocan fix kernel, then naturally this (as it is a different kernel) will make your phone unusable until you apply the mimocan kernel back.
In other words, this is workin, just not if you had the mimocan fix, which changes where all the data is located in the device.
Click to expand...
Click to collapse
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).

not working on JF7, keeping on rebooting

Chainfire said:
Oh really.
Please also reference: #koush @ irc.freenode.net, http://forum.xda-developers.com/showthread.php?t=732139, http://forum.xda-developers.com/showthread.php?t=732138
Just after this was released immediately a bunch of Vibrant and Captivate guys tried it and none of them succeeded. A number of them couldn't do anything anymore, couldn't get out of some screen and couldn't connect with the PC. Koush himself was absent at the time. There was a lot of *****ing and moaning, and the people in the channel asked to put the notice up until there was more info. So, as it was about 6 AM for me I put up the warning, called it a day, and decided to figure it out tomorrow (now today).
An unneccessary warning is IMHO better than having to risk a large number of users bricking. (Tough if you prefer bricks...) I'm still not sure what happens on the unbranded SGS / I9000. At least it certainly causes issues on the Vibrant and Captivate (though I think Koush by now has mentioned in one of the threads he'll have to make a different version for each of the SGS variants)
Get me some confirmation it works as advertised on the I9000, and a step-by-step guide to get everything up and running - even if using those modified kernels - and I'll remove the warning. If not, you'll have to wait 'til Koush looks over his stuff again and modifies his post (my warning is in his post, he can simply edit it out).
Click to expand...
Click to collapse
fair enough.

hkfriends said:
not working on JF7, keeping on rebooting
Click to expand...
Click to collapse
Does the same thing on JG5...
When I first applied it, it rebooted itself twice in a row and booted fine. It ran for a good few hours... restored apps. from titanium backup. Did a reboot again. (just to be safe.) At that point, it kept rebooting itself... and then I pretty much gave up and flashed the stock JG5. (couldn't head to work w/o a working phone, lol) Anyone got it to work so far?

any word on custom recoveries?

phone will arrive tomorrow. need to know haha

Nothing yet. I got my phone and I've unlocked the bootloader in preparation, but so far no news of recoveries. I have no idea how long this takes because I've never been an early adopter before...

randman2011 said:
Nothing yet. I got my phone and I've unlocked the bootloader in preparation, but so far no news of recoveries. I have no idea how long this takes because I've never been an early adopter before...
Click to expand...
Click to collapse
Could you check the key combination needed to cold boot in to fastboot mode please. Im assuming its volume down and power together from a shut down.
Thanks, Mark.

It is.

randman2011 said:
It is.
Click to expand...
Click to collapse
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.

mskip said:
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
Click to expand...
Click to collapse
It is encrypted with no option to disable it.

mskip said:
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
Click to expand...
Click to collapse
You have a custom recovery and / or modified boot image for the Nexus 5X?!

oscillik said:
You have a custom recovery and / or modified boot image for the Nexus 5X?!
Click to expand...
Click to collapse
No sorry there isn't one available yet but all options apart from recovery based ones are enabled including disabling forced encryption and flashing stock images (or parts of).
I have to go out now but have uploaded the Toolkit and will make a new thread in the Original Android Development section when I get back in a few hours.
Mark.

Waiting for custom recoveries! OP2 got custom recovery faster

mskip said:
No sorry there isn't one available yet but all options apart from recovery based ones are enabled including disabling forced encryption and flashing stock images (or parts of).
I have to go out now but have uploaded the Toolkit and will make a new thread in the Original Android Development section when I get back in a few hours.
Mark.
Click to expand...
Click to collapse
modified boot image - bullhead-mdb08i-boot.zip http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i did a factory reset after i fastboot flashed the boot image for encryption to be off. https://goo.gl/photos/Wq6bMCqD1XVBWQdQ9
dees_troy said he might be able to take a stab at making a recovery later today, if he can get around to it and figure it out, rooting should be easy. otherwise i was thinking about repacking the system.img with su and seeing if that works.
{
"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"
}

renzyyy said:
modified boot image - bullhead-mdb08i-boot.zip http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i did a factory reset after i fastboot flashed the boot image for encryption to be off. https://goo.gl/photos/Wq6bMCqD1XVBWQdQ9
dees_troy said he might be able to take a stab at making a recovery later today, if he can get around to it and figure it out, rooting should be easy. otherwise i was thinking about repacking the system.img with su and seeing if that works.
Click to expand...
Click to collapse
I have a no encyption patched stock kernel included in the Toolkit with automation to make it easier for the average user.
You can certainly repack the system image to include root but if you are publishing it you will also need to include chainfires patched kernel (the one you linked to) to flash with the modified system image or the system will go in to a bootloop (requirement of Android 6 root at the moment. I may look at it later but I have no Nexus 5X to test anything on.
I have published the new Toolkit with the Nexus 5X added and made an xda thread *HERE*.
One thing, does the Nexus 5X suffer from the same problem as other Nexus devices, where the USB mode switches back from PTP mode (for adb commands) back to Charging only on EVERY reboot. Its a pain in the ass and always switches back even if the mode is set in developer options.
Mark.

roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625

renzyyy said:
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
I'll give you a cookie for that root

just a word of advice - make sure your phone is already running build MDB08I, and not any other build, before you flash that modified boot img: I just tried flashing it, and it just sticks on boot animation. My Nexus 5X is currently running MDA89E

renzyyy said:
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
Any idea if it is safe to re-enable encryption after flashing the modified boot.img, factory wipe, TWRP flash?

bqq100 said:
Any idea if it is safe to re-enable encryption after flashing the modified boot.img, factory wipe, TWRP flash?
Click to expand...
Click to collapse
my guess is that you can, but then you wont be able to use recovery again. dont quote me on that, ive never tried re-enabling it.

oscillik said:
just a word of advice - make sure your phone is already running build MDB08I, and not any other build, before you flash that modified boot img: I just tried flashing it, and it just sticks on boot animation. My Nexus 5X is currently running MDA89E
Click to expand...
Click to collapse
I modified the mda89e and mda89f stock boot images for no-force encryption and re-packed them for use with the android toolkit. If you have MDA89E try flashing *THIS* image and see if it fixes the bootloop problem.
Mark.

mskip said:
One thing, does the Nexus 5X suffer from the same problem as other Nexus devices, where the USB mode switches back from PTP mode (for adb commands) back to Charging only on EVERY reboot. Its a pain in the ass and always switches back even if the mode is set in developer options.
Mark.
Click to expand...
Click to collapse
Yes it still makes you do that Although my N6 did not require it to be toggled after every reboot like the N5X does. It needs to be in PTP to get ADB commands to work, on my windows machine that is, not on the Mac.

mskip said:
I modified the mda89e and mda89f stock boot images for no-force encryption and re-packed them for use with the android toolkit. If you have MDA89E try flashing *THIS* image and see if it fixes the bootloop problem.
Mark.
Click to expand...
Click to collapse
The link doesn't seem to work , need a username and password.

Hayth said:
The link doesn't seem to work , need a username and password.
Click to expand...
Click to collapse
He put it up as an sftp:// (protocol for secure ftp) link. Try this one instead: http://skipsoft.net/tempuploads/boot_images/boot-noforce-encrypt-mda89e-bullhead.img

N5X shows only colorful static when turned on

Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: RMA'd the phone, they had to replace the screen / touch unit (obviously) and the camera (?) for some reason

dbahn25 said:
Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
Click to expand...
Click to collapse
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?

dbahn25 said:
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?
Click to expand...
Click to collapse
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?

dbahn25 said:
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?
Click to expand...
Click to collapse
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Alright, thanks! Unfortunately, I've already shipped my phone back to repair / replacement. But I wonder, is there any advantage of using sideload over using fastboot to flash the stock image?
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).

dbahn25 said:
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).
Click to expand...
Click to collapse
It can be done, just need to look at screenshots someone else posts of the recovery menu and count.

Unofficial Build Thread... (Magisk, TWRP, etc.)

By request this is now the Unofficial Build Thread
This thread has been created to help clear up the confusion in the official threads.​
That's right, everything here is just built. I am not the author of this code, I simply build current commits and provide them after having tested them myself on the most current Google provided factory images. I do not test these on betas. I will update this OP with more detailed instructions as deemed necessary.
Ok, so no more :good: Magisk is fixed :good: tomfoolery because I don't believe it anymore... From now on I am just going to provide solutions and assume that official is going to be broken again. What I am referring to is the dtbo image being patched and displaying the nasty "operating system on your device has been modified" message on every boot.
I have been told by typically competent developers that removing dtbo patching is stupid and makes no sense. I have been told that we cant run low level audio mods etc without it being patched. BlaBlaBla... Well, I can run everything I want without it being patched. Viper works, and anything else I have tried has worked. So, enough with that. More information on dtbo here...
I personally hate the message, and if you are here then you probably hate it too. So, if you like the message and want to keep it... Leave.
Unless something changes (oh and I am sure it will again) we only need a Magisk Manager app that does not patch dtbo without our permission. That is what I compile and provide. In the future if the actual root zip starts patching again, I will compile that too. But for now, it is just the app...
Here we go again...
1.) Uninstall official manager app
2.) Install this one. ...Unofficial Magisk Manager...
3.) If dtbo was patched and you are seeing the message then reboot to bootloader and 'fastboot flash dtbo dtbo.img' (factory dtbo)
4.) You are done.
Currently 15.2 root does not patch dtbo, Magisk Manager does.
I will release new modified Magisk Manager apps here as new commits are made. It is not necessary to update right away as there are rarely earth shattering changes released and most of the time the commits do not even apply to our device. I will compile new builds in as timely of a manner as I can. If something major does drop, it will be quick.
Happy New Year!!!​
Join the Telegram Group!
https://t.me/Pixel2XLXDA​

Reserved
...Because everyone else does it....
{
"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"
}
...Look HERE for stuff...
*until google tells me otherwise*
(I don't care if you share/take credit for/mirror bla bla bla)
Suggestions
1.) Be current but not to current... (Run current non-beta factory images)
2.) Make sure you are running current adb/fastboot binaries. (Provided)
3.) Make sure your usb/usb-c cable is not from Toys R Us (They don't carry one : See Amazon)....
4.) You are not on a PS/1 (My first system )
5.) Don't exhibit behavior similar to mine...
..WIP..

Right on man. Thanks.

thedude420 said:
...Because everyone else does it....
...Look HERE for stuff...
*until google tells me otherwise*
(I don't care if you share/take credit for/mirror bla bla bla)
Suggestions
1.) Be current but not to current... (Run current non-beta factory images)
2.) Make sure you are running current adb/fastboot binaries. (Provided)
3.) Make sure your usb/usb-c cable is not from Toys R Us (They don't carry one : See Amazon)....
4.) You are not on a PS/1 (My first system )
5.) Don't exhibit behavior similar to mine...
..WIP..
Click to expand...
Click to collapse
#3 made me chuckle. :laugh::laugh::laugh::laugh::laugh:
On a serious note though, I tried flashing this last night and my phone would not stop rebooting on its own. It would restart and would just reboot. I tried grabbing some logs but the app (MatLog) would just load and not show any output.
Will probably see if I can try again and see if anything changes. Will also try the APK method you mentioned in the Magisk 2XL thread.

nexus_man12 said:
#3 made me chuckle. :laugh::laugh::laugh::laugh::laugh:
On a serious note though, I tried flashing this last night and my phone would not stop rebooting on its own. It would restart and would just reboot. I tried grabbing some logs but the app (MatLog) would just load and not show any output.
Will probably see if I can try again and see if anything changes. Will also try the APK method you mentioned in the Magisk 2XL thread.
Click to expand...
Click to collapse
Flash factory Nov images without -w to save your data then start over with twrp beta 2 and this magisk...

thedude420 said:
Flash factory Nov images without -w to save your data then start over with twrp beta 2 and this magisk...
Click to expand...
Click to collapse
Thanks dude for the prompt response. I'll give it a shot later today.

nexus_man12 said:
Thanks dude for the prompt response. I'll give it a shot later today.
Click to expand...
Click to collapse
Rite on! Here it is flash-all.bat. Not trying to be a douche but I once made changes to this file, flashed then realized that I did not save them prior... Ended up with a brand new device, it was great... Obviously this would only work with Nov factory images for Google "taimen" 8.0.0 ((OPD1.170816.025, Nov 2017) (not tested with the verizon ones..))
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-taimen-tmz10n.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00122-1708311414.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-taimen-opd1.170816.025.zip
echo Press any key to exit...
pause >nul
exit

Any word on ROMs being built for xl2? I'm waiting with bootloader til there are some ROMs
Sent from my Pixel 2 XL using Tapatalk

What do you mean? Waiting with bootloader?
Sent from my Pixel 2 XL

patt2k said:
Any word on ROMs being built for xl2? I'm waiting with bootloader til there are some ROMs
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I don't get it either. Unlock your bootloader now and get it over with. Going to have to wipe your data at some point. Also note that unlocking critical is NOT necessary. Just do a 'fastboot flashing unlock' and your good to go.
As far as ROMS go, I am not really sure. Syncing googles source tree today then I am going to do some test builds. Then go from there. They are coming :good:

thedude420 said:
I don't get it either. Unlock your bootloader now and get it over with. Going to have to wipe your data at some point. Also note that unlocking critical is NOT necessary. Just do a 'fastboot flashing unlock' and your good to go.
As far as ROMS go, I am not really sure. Syncing googles source tree today then I am going to do some test builds. Then go from there. They are coming :good:
Click to expand...
Click to collapse
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Sent from my Pixel 2 XL

abuttino said:
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Click to expand...
Click to collapse
The dev site says "may be necessary"... I have never unlocked critical and have not had one problem. Only thing I can tell it does is allow modifications to the actual bootloader which we do not need to do.

abuttino said:
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Sent from my Pixel 2 XL
Click to expand...
Click to collapse
it's needed if there's an updated bootloader in the factory image.
8.1 DP1 has an updated bootloader so Unlock Critical is needed to fastboot flash that.

drewski_1 said:
it's needed if there's an updated bootloader in the factory image.
8.1 DP1 has an updated bootloader so Unlock Critical is needed to fastboot flash that.
Click to expand...
Click to collapse
Really? Google bootloader's will not flash without critical unlocked???

thedude420 said:
Really? Google bootloader's will not flash without critical unlocked???
Click to expand...
Click to collapse
It seems that way.
Sent from my Pixel 2 XL

Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
So it appears Substratum theme was causing Magisk Manager crashing issues. I recommend not theming Magisk Manager!

Thanks for the effort and time put into this thread! Looking forward to having the time to sit down and play
Seriously though, the hard work is very much appreciated!

thedude420 said:
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
Click to expand...
Click to collapse
What are the circumstances? I'm running out with nothing happening yet. Can you help me reproduce it? Maybe we can figure something out.

CyberpodS2 said:
What are the circumstances? I'm running out with nothing happening yet. Can you help me reproduce it? Maybe we can figure something out.
Click to expand...
Click to collapse
Yeah, I have some stuff I need to do for the wife but then I will get some time and collect logs etc...

thedude420 said:
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
Click to expand...
Click to collapse
No crashing here. Did you try wiping data?
Sent from my Pixel 2 XL

OTA failure problem.

My Lenovo Vibe K5 Plus (3GB RAM) has OTA update problem.
I'm attaching some Screenshots.
Its not rooted or modified in any way.
{
"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"
}
Phone will reboot normally and show "OTA Update failed".
My question is can I update it to latest build by using Lenovo Update Assistant or should I go in order to avoid bricking?
Can I flash the latest build using "Lenovo Smart Assistant" or QFIL?
Will it create any problem like bricking?
Please help.

Your problem is quite classic, the way to solve it is quite simple, but you'll have to lose your data anyway.
The first way is to check if in your internal storage you have a "/0/carrier" folder. If it's the case, you should flash the file <your_country>.ota.zip (via "apply update from sdcard", if it's not accessible, you should copy this file on your external SD card). It will take some time but then you should download and update your phone
In my latest experience, you can try to use Lenovo tools, but I did not succeed to flash my phone this way (never found the right model)
Personnally, when I want to get back to "updatable stock", I usually do this :
Flash a stock ROM via QFIL, but not the last version (I'm on K5 Plus 2GB, and I flash S042)
Just after success, I reboot to booloader via "Power + Vol -"
Using my PC, I reboot to a TWRP recovery, without flashing it, and without changing the readonly filesystem (via TWRP you can access both internal and external storage) : fastboot boot <path to twrp img file>
Here I flash the /0/carrier/<my_country>.ota.zip
Then I reboot and my ROM is installed, and updatable without the carrier problem
Tell me if you need further explanations.

@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
I don't have anything in 0 folder. Its empty even after downloading OTA update.

Apocalypse0 said:
@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
Click to expand...
Click to collapse
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs

adinechin said:
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs
Click to expand...
Click to collapse
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.

Apocalypse0 said:
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.
Click to expand...
Click to collapse
Ok so you can flash any ROM with QFIL, and if you are not comfortable with TWRP, you can try removing your sdcard after flashing ROM, reboot to recovery and flash the OTA.zip.file.
Be aware that flashing with QFIL will also wipe your internal storage.
Sent from my Lenovo K5 Plus using XDA Labs

@adinechin thank you. I have updated to latest version.
Thankyou so much.
I have few questions.
1. Why we can't flash latest version directly from QFIL?
2. My phone gets shut down automatically if not in use. Is it something hardware related because it was fallen down once and I'm getting this annoying problem even after updating to newer build? Earlier I was thinking it is something software related but now I think its hardware problem. Do you have any idea to share on this?
It gets shut down only after not in use. If I use it for hours it works correctly but as soon I lock the screen it gets switched off and only after removing and reinserting the battery it will on again. No matter how long you press Power button it won't get on. Even recovery combination won't work until I remove and reinsert the battery.
Thanks a ton for helping me.

Apocalypse0 said:
@adinechin thank you. I have updated to latest version.
Thankyou so much.
Click to expand...
Click to collapse
Glad I helped you
Apocalypse0 said:
1. Why we can't flash latest version directly from QFIL?
Click to expand...
Click to collapse
You can, but I personally prefer to update via the phone to be sure all is back to normal stock
Apocalypse0 said:
2. My phone gets shut down automatically if not in use.
Click to expand...
Click to collapse
I have no idea on this subject, but with what you describe, it seems more likely to me that the phone is "stuck" than "off". I know it can happen some times if an app takes much memory, especially when you just installed the ROM, it takes some time to stabilize. Have you tried to wait a little when it was stuck like that and unlock it a bit later ? Another remark, instead of removing battery (which can be very annoying), try holding Power Vol+ and Vol- during around 10 seconds : you should reboot to download mode (black glowing screen like with QFIL), and then do it again, you should reboot your phone.

It was happening even on older build. Yes I waited and tried everything (key combinations) but nothing worked. That's why I feel its a hardware problem because of the fall the device took. No problem if I keep using it, no hanging problems or other things, but as soon I lock the screen it just gets switched off Very irritating.
Anyway, you've helped me a lot and I really appreciate the way you've kept everything simple because these things go really above my head.
Thanks again.