yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
Uhmm... it does NOT work with SU4TL-49.

Lots of people have said even with unlocked bootloader, Sunshine no longer gives temp root with SU4TL-49 installed.

Read this thread:

Help Needed From XT 1254 Developers Please

http://xdaforums.com/moto-maxx/help/help-xt-1254-developers-please-t3390557

It's specifically from an XT1254 user with an unlocked bootloader, who installed the OTA SU4TL-49 and no longer could get TEMP ROOT. Luckily, once we figured out he had an unlocked bootloader, he just had to install TWRP to get permanent root!

If you already have an unlocked bootloader, the best way is to get root is to go ahead and install TWRP and then root,

I don't understand the people who unlocked their bootloader prior to SU4TL-49 and did not then go ahead and permanently root their phones... But apparently they are out there. They were constantly using Sunshine temp root and now with SU4TL-49 that no longer works.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SXRXNRR:
Worked on mine. Want pics?

It worked on mine. Want pics of it????

---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------

I did exactly as stated, it is perm root. I dont know why you would challenge that? Im sitting here with it? With sudo terminal, twrp, titanium root, etc....im not delusional dude.

---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------

Seriously, I read these posts, and tried anyway. It worked. Isnt that what we are supposed to do? share our finds?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Yes, I would like to see pics, considering that the developer of Sunshine (who is a professional security researcher) said himself that it would not work on SU4TL-49. That, along with the many, many reports of people saying that it does not work on SU4TL-49, cause reason for suspicion.

And yes, XDA is for sharing findings, but only if those findings are valid and do not lead to other people doing things that they will regret based on bad advice.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
OF course you have TWRP, because you installed TWRP with an unlocked bootloader. But you probably didn't get temp root with SU4TL-49 first. You got root from TWRP.

All I'm questioning is getting temp root first with SU4TL-49 installed -- on an XT1254 with unocked bootloader which had previously never had TWRP or other permanent root before that.

If you got managed to get temp root first with SU4TL-49 first (and had never installed TWRP or rooted before), you must have a magical phone. [MENTION=2376614]jcase[/MENTION] would be very interested.

What would you show me pics of? You've already installed TWRP and rooted -- which can be easily be done with an unlocked bootloader and TWRP. Showing us pictures of that doesn't show us anything.

If you have an XT1254 with an unlocked bootloader and no root, the best way is to go ahead and install TWRP custom recovery and root. (You can only unlock your bootloader with Sunshine prior to instaling SU4TL-49.)
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SXRXNRR:
I dont need kudos from anybody. I shared because I did it. On a factory reset turbo, that was updated. I dont care if you dont believe either. makes no difference to me. Obviously posting here is grounds for attack. I was simply sharing, It worked. Consider the conversation closed. I wont be sharing anything here. TWRP was installed AFTER the temp root. Running sunshine and seeing TEMP root achieved, I installed SuperSU as stated, then TWRP manager, etc...Im a 45 year old security geek. I take offense with your attitude. I wouldnt post it if the steps didnt work. Thanks for the friendly atmosphere. Really. Maybe I do have a magical phone. WTFK?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] jcase:
He probably has the su44 bootloaders
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
See the previous post above from Sunshine dev. The "magical" part is you are somehow the exception if you had an unlocked bootloader, no permanent root, and installed the OTA. It won't work for most other people. Somehow you installed SU4TL-49 update but not the bootloader that goes with it. You must still have the SU4TL-44 bootloader.

Now that you are telling more details "On a factory reset turbo,", it's becoming clear you had root, TWRP installed before. What you are doing has been described in detail before in the thread (from May) I'm quoting below. It's nothing new, nothing fantastic.

But what you seemed to be describing at first was using Sunshine to get temp root when you never had permanent root before (and I wasn't the only one who thought so) . That scenario is impossible.

Posting here is not grounds for attack. We just don't believe you did something no one else has been able to do, without explaining why you were able to do it. Especially when there's no proof at each step, but an easy alternative explanation (TWRP, then root) if you really installed the complete SU4TL-49 update. There's been many, many people including myself who have done stuff, then said, "I'm not sure the exact steps I did to get here." With only 1 post prior to this, we have to question your seeming amazing story.

Now that you have added more details, all you did was re-flash TWRP on an unlocked bootloader phone that already had root and TWRP previously. That's been described since May, see thread quote below. It's for people who previously had root, re-set their phone to install the update. Then afterwards, yes, you can get temp root back with Sunshine. But the important part is at some point you already have permanent root prior to installing the OTA. See steps 11-16, as well as the trouble shooting.

New OTA Available for Droid Turbo

http://xdaforums.com/droid-turbo/general/ota-available-droid-turbo-t3378576
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
Just like in your thread I quoted, it's clear now he had root, TWRP installed prior to a factory re-set to install SU4TL-49. He didn't initially disclose it was a factory re-set, and that he had previous permanent root and TWRP.

Perhaps unintentionally, he made it seem he only had unlocked bootloader and had been using Sunshine to get temp root. At least that's how I read it. Now with SU4TL-49, temp root will no longer works in that scenario. But if you've already gotten permanent root, TWRP and install the update -- even with a factory re-set -- you've made enough changes that Sunshine will still work to give you temp root.

At that point, yes Sunshine will still give you temp root -- just like you posted in your thread. To me, and it's my opinion only it seems your steps, downloading TWRP from Quark thread, using Flashify would seem simpler. You have TWRP and then can use TWRP to get root.

Once we know all the facts, his experience is not fantastic and if he had just read your thread we could have skipped the drama. ;)
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Oops
[Android Q&A, Help & Troubleshooting] jefryvaldez07:
Hi, please help me I put one lock pin on the new update gbwhatsapp. The pin it's on one of my chat. But I can't access because I forgot.

Please help me
[Android Q&A, Help & Troubleshooting] Jefryvaldez:
i have the same problem. help me please.
[Android Q&A, Help & Troubleshooting] Ruth700:
I forget my Gb WhatsApp pin to unlock my chat
[Android Q&A, Help & Troubleshooting] shrazy:
Make backup of chats, uninstall gb whatsapp and install normal whatsapp. Should fix the problem
[Android Q&A, Help & Troubleshooting] Rosy111:
Gb whatsApp

Please I forgot my gb whatsApp unlock pattern. How can I unlock it?
[Android Q&A, Help & Troubleshooting] Vivwood:
Goodday all Please I forget my gb WhatsApp pin to unlock chat
[Android Q&A, Help & Troubleshooting] Lasharon:
I forgot my pattern for a chat in my GB WhatsApp
[Android Q&A, Help & Troubleshooting] kisakye:
hello

i put a pin on a particular chat,which now incorrect and i forgot the answer to the recovery qustion

Thank you
[Android Q&A, Help & Troubleshooting] Dikenkem:
I forgot my gbwhatassp chart password and answer to my recovery question, please I need assistance on reset it.
[Android Q&A, Help & Troubleshooting] Muhammad Khan1200:
Please help me i forget my lock pattern on gb whats app
[OnePlus 2 General] krishna442:
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8994/tree/oneplus/6.0.1

Legit!
[OnePlus 2 General] DaRkRhiNe:
It is legid, check grarak's tweet.
[OnePlus 2 General] Ribery771:
Offical cm comes in 4 days.
[OnePlus 2 General] izzikiorage:
For the noobs among us. What does this mean? Is the oxygen OS going to be replaced by CM. Will the fingerprint sensor and laser autofocus start working on CM
[OnePlus 2 General] fburgos:
It means cm started using latest bootloader and official status to get ota, posible improvement in forum, camera, and sound quality (not that was an issue before)
[OnePlus 2 General] JoinTheRealms:
Finger print senor and laser autofocus has been working for a long time, but there are kernel side improvements in the MM source for at least the finger printer sensor.

This means we are getting official CyanogenMod (starting with nightlies). Nothing to do with OnePlus or OOS, their OTA will come in the next couple of weeks AFAIK.

Additionally, our kernel developers get to have fun fixing OnePluses *presumably* rushed kernel code :p
[OnePlus 2 General] izzikiorage:
Nice, so after a proper flash i can start using the snapshots for CM? (nightlies are a little too unpredictable for me)

And this is CM 13? the marshmallow one
[OnePlus 2 General] djdana:
Shibli Aftab:

https://mobile.twitter.com/Grarak/status/738825631266394112

Verstuurd vanaf mijn ONE A2003 met Tapatalk
[OnePlus 2 General] mclarenvj:
Looks like it's building already!

http://jenkins.cyanogenmod.com/view/android/job/android/164352/
[OnePlus 2 General] Guihardrock:
http://download.cyanogenmod.org/
[OnePlus 2 General] CJOS100:
Can someone please explain to me how to go from Grarak's last CM13 Build to these nightly builds?
[OnePlus 2 General] flo071:
i downloaded nightly build and dirty flashed it :)

Regards,

flo071
[OnePlus 2 General] CJOS100:
That definitely worked? Because I wasn't sure after what Grarak said on twitter: http://i.imgur.com/NlWt5qn.png
[OnePlus 2 General] flo071:
i was on graraks 3rd june build :)

i flashed the oos3.0.1 firmware and twrp hybrid before that :)

Regards,

flo071
[Galaxy Note 4 Q&A, Help & Troubleshooting] saqibriaz123:
Hi,

Recently my phone autoupdated to marshmalow, and since then it keeps freezing and crashing. I read somewhere that the final fix to this is to reflash the firmware, so I tried and since then odin gives me an error message and the phone wont start.

I am quite new to all this, but I followed instructions from many different youtube tutorials and other online tutorials. ODIN keeps giving me a write error.

I am using different versions of odin, different usb ports and even different cables with the same end result. ODIN flash ends with error.

My note 4 has reactivation lock off, and never been rooted before. It is a UK N910F model and usually on Three mobile.

I really hope someone can help as I have struggled with this for past 2-3 days with no luck.

Here is the details from odin.

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N910FXXU1DPE1_N910FEVR1DPE1_N910FXXU1DPB1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> SingleDownload.

<ID:0/006> aboot.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006> sbl1.mbn

<ID:0/006> rpm.mbn

<ID:0/006> tz.mbn

<ID:0/006> sdi.mbn

<ID:0/006> NON-HLOS.bin

<ID:0/006> boot.img

<ID:0/006> recovery.img

<ID:0/006> system.img.ext4

<ID:0/006> modem.bin

<ID:0/006> cache.img.ext4

<ID:0/006> hidden.img.ext4

<ID:0/006> FAIL! (Ext4)

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note 4 Q&A, Help & Troubleshooting] night-mayor:
firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .

second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )

cheers
[Galaxy Note 4 Q&A, Help & Troubleshooting] saqibriaz123:
Odin kept failing at the hidden.img.tar.ext4 file so i googled, and found that extracting the hidden file and then flashing that file separately in odin may work. I tried that and worked!

Phew!
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
Hello people. My device is not listed in DEVDB options, so I must have to create this thread instead a DEVDB project. If it is wrong, please advice me.

-----------------------------------------------------------------------------------

I'm creating this thread to give us more space to create a ROM for our device, like a step-by-step to things we have to do or not. I'll edit this thread with more details when I have more time, but for now, thats what we have done, and I think we need to do:

Root (Thanks to Chainfire)

Custom recovery (thanks to Shreps)

Choose a kitchen to manage the ROM

Discover kernel options

Choose apps to add/remove

A custom app to manage various phone settings, like kernel options, battery settings, and others

Edit build.prop to get right device management

Edit boot.img to have unsecure boot

Help me to add or remove things to the list above, to have a structured plan to build the whole ROM (boot, recovey, system), because last time I manage a ROM was a long time ago, I think about 2010 (was on Xperia X2), and was only for me (my "project" wasn't public). From that time for actual days, I don't manage/create nothing "solid" and structured anymore... And I'm sure all things have changed/updated/died/etc...

To help start familiar with new kitchens (the last was DSIXDA Kitchen), I have choose SuperR's Kitchen. I try to use it inside Cygwin, but it gives me an error while opening, I'm investigating this. So, I setup a virtual machine with Ubuntu in my house, and I have remote access to it from my work. In this VM, I setup the kitchen and (after a time to setup the right Java) it is running fine.

So, let's go, people. I'll edit this post as news are coming.

[UPDATE]What I have found:

If "Google Photos" is removed, then Gallery don't crop wallpapers, or adds a image to a contact;

Titanium Backup can't uninstall/integrate some apps and updates. It says "apk not found". I'm trying to use Link2SD;

SuperSU "lose" the configuration, forcing me to remove the apps I added, then run the app again. I'm looking for this

If you remove "Theme Center", you can't change wallpaper and Lenovo Home gives an error!

If you remove "Google App", "Now Launcher" gives errors about force close.

If you remove LenovoID, Settings force close when try to enter "accounts".

If we integrate "Google Play Services" and hard reset the phone, it force close at second stage of first registration.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] munchys91:
nice thread
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] nandakalyan:
I randomly found this thread and noted that you are facing this issue with TB being unable to uninstall some apps. I had the same issue with my device. If you are rooted, navigate to /Cust/Channel/Preinstalled/apps folder (sometimes the "channel" folder may not exist) from your file explorer, you will find the apks for the apps that TB fails to find apk for. Remove the APKs that you don't need and/or move them wherever you feel is right for them, all set :)
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
Yeah, I already see that folder. Seems TB can't handle with folders different from /system/app and /data/app
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] nandakalyan:
Yes, that seems to be the case for LP and MM factory images that have this folder, it is a TB limitation even on my device, unless I am running CM or AOSP based ROMs :) hope the workaround helps
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
You have A6020 with CM??
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] nandakalyan:
No, I have an Honor 5x L-22, we have a CM build for our device but I chanced on this issue when I was running stock and wanted to get rid of all that bloat. So just sharing what I discovered
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
Ok!! Thanks!
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] sudheer4188:
Can you please tell me how the camera quality is..I'm planning on buying this mobile...so please let me know
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] llxll4ever:
It's not great but for the price is quite good
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] lucasdeeiroz:
Did you see kernel source code from lenovo's website for Vibe K5?
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
Yes
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] nayakdinesh:
hey can you tell me how root it and install TWRP.. thanks
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] lucasdeeiroz:
Please, do not quote OP. Here is the link for what you requested: http://xdaforums.com/showthread.php?t=3391100

Enviado de meu pac_A6020 usando Tapatalk
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] nayakdinesh:
is there any custom kernel for this phone which cn provide dt2w ...
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] jrfirmino:
heeeelpp

I need rom L35 and not of a40 , my phone is stuck in the screen lenovo without TWRP and without backup
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] lucasdeeiroz:
Do not spam at XDA or you won't get any help. Search an appropriate thread to make your question AFTER reading all posts from there.

Here isn't the appropriate thread.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] louiscypherbr:
Why did the OP marked [kernel] if there's not a kernel available here? That's not fare.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] Hnk1:
[MENTION=4291832]romulocarlos[/MENTION]

No kernel yet ?
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
The original idea was build a kernel, too.

No. Now we have CM13, thanks to Shreps, so this thread is obsolete.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] louiscypherbr:
I respectfully disagree. Cm have more bugs than stock (on my stock all including video works eg), and it would be wonderful to have stock based kernels with some extras, as cpu, gpu and memory controls.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
I don't know the variant you have, but stock rom of mine (L36 variant) have some very irritant bugs, like no notification or no led, volume down without reason and others.

Because of this and other stuff, I prefer PAC ROM.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] louiscypherbr:
I have L36 also. The notifications don't show up because the app is force closed by memory management; all you have to do is uncheck "restrict startup" and check "notifications" on app details. Mine works as expected. Or, if you like to completely disable that weird memory management, just freeze that app with titanium backup.

The volume down is related with earphones, so you just have to check it after removing earphones, or better, make tasker to do it automatically for you every time you remove it.

But the problems with noise audio and no video record on pac/cm you can't solve. That's unacceptable to me.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
I don't want to be a "devil's lawyer", but let me say with all respect...

Unacceptable to me is a product developed by a multinational company, with a huge team of people payed to develop a product which consumers expect to be 100%, and it don't. This is stock rom.

Is A LOT different from a product developed by enthusiasts, often specialized people in the subject and who love to do this sort of thing for pleasure, and even non-profit. This is PAC.

Don't take me bad, is only my opinion, as you have yours.

That sayed, let me explain a thing: unchecking "restrict to start" don't work for all apps, and may vary from phone to phone. I'm a member of a Brazilian facebook's group related with K5, and a lot of people already unchecked it and still not working. Instagram, facebook, OLX, ColorNote, MercadoLivre are some apps people report don't have notifications.

This is a bug, as volume problem and some minor are. Yes, I can't solve PAC bugs, as I can't solve stock bugs also. But can YOU solve the stock rom bugs also? I mean SOLVE THE PROBLEM. Using third part apps to have functions working as they have to be is a palliative, not a solution.

In case of PAC, devs are here almost all time listening us, and they try to solve problems ASAP. Let's make a comparison:

PAC: in early versions, wifi and bluetooth don't work. Two days later, we receive an update, and almost all big problems was solved.

STOCK: Some days ago some users received an update from OTA. Was a long waited update. But... It don't solve the major bugs, and for some users is worse: LED don't lit when a notification comes, and battery life is worse. Some of them report only 4 cores are working.

So, are Lenovo acting like our devs here? I don't think so.

At time: PAC is still in ALPHA stage, so, bugs are expected. Is different from stock, a product (supposed) to be working out-of-the-box. When PAC reaches BETA or higher stage, I believe it will work lighyears better than stock.

Again, don't take me bad. Cheers!
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] lucasdeeiroz:
LOL

"PAC ROM is unacceptable". And bugged stock ROM isn't? That is a weird concept.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] louiscypherbr:
No, I do not think that pac's devs are making a bad work in any way! Actually I'm waiting for stable cm and I'll change from stock for sure!

What is unacceptable to me is to live with such big bugs, making some resources unusable as video and, the worst imo, the possibility of having problems in phone calls (I use it for dozens of calls/day on my work). Lenovo's is a trash but everything works and I never got any call problem.

As soon as cm team solve this bugs, I'll go for it.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] romulocarlos:
I don't have problems with calls. The only way to know if you will have, is make a full backup (very important), install PAC like explained in first post, and test.

If something gets wrong, just restore the backup.
[Lenovo Vibe K5 ROMs, Kernels, Recoveries, & Other ] louiscypherbr:
No, not with that bug list yet.

Actually I don't have any problem with stock rom! I've made a simple tasker app to change volume to max after earphones plugged out, and frozen the Lenovo's AppRestriction. Look on task manager that all opened apps just stay as it should be (that screenshot was taken after +1/2h with screen off). And of course as well as notifications.

Backing to topic, that's why it would be great to have stock kernel.