yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S6 Edge+] crowlaw:
I have tried several versions of custom recoveries to flash via Odin to root the new tmobile 6.01 fireward that was released today and have not had any luck so far.

So far I have tried using the recommended versions of twrp 3.0.2-0 with no luck:

https://dl.twrp.me/zeroltetmo/twrp-3.0.2-0-zeroltetmo.img.tar.html

https://dl.twrp.me/zenlte/twrp-3.0.2-0-zenlte.img.tar.html

Has anybody successfully rooted with the 6.01 T-mobile firmware that was released today? If so could you please provide a link with the exact custom recovery file you used.

Thank you in advance.
[T-Mobile Samsung Galaxy S6 Edge+] anhqn91:
Search for 3.0.2 nobleltezt twrp and download latest version (This recovery is for Note 5 but works awesome, and S6 Edge+ TWRP stuck or won't boot)

Flash in Odin but remember to uncheck auto-reboot then reboot manually with volume down and power button combo.
[T-Mobile Samsung Galaxy S6 Edge+] stevew84:
So follow those instructions after already on the edge plus 6.0 firmware? So we would be flashing Note5 over existing edge stuff, right?
[T-Mobile Samsung Galaxy S6 Edge+] Misterjunky:
Proper TWRP and SuperSU for S6 Edge+

Here are the links to the proper versions of TWRP and SuperSU for

the Marshmallow 6.0 update/firmware for the G928T S6 Edge+ and

the Note 5 N920T phones. - Courtesy of @Chainfire and @bigbiff -

TWRP-3.0.2-1-G928T-N920T.tar

https://www.androidfilehost.com/?fid=24499762636003370

SuperSU-v2.71-G928T-N920T.zip

https://www.androidfilehost.com/?fid=24499762636003371

These work 100% on both phones, they have been

fully tested and they even work perfectly for me. LOL

Good luck,

Have a great day!
[T-Mobile Samsung Galaxy S6 Edge+] Venal_System:
Correct, I odined MM from Sammobile for the TMO S6edge+, this morning but could not get rooted and Titanium up and running all day, flashed and odined probably 15 times. Long story short, both firmwares are DPD1, and work fine.
[T-Mobile Samsung Galaxy S6 Edge+] stevew84:
Ok that makes sense. I'm using a COKC 5.1.1 note5 ROM on my edge plus so I guess it's the same principle just on a different Android version.

Thanks
[T-Mobile Samsung Galaxy S6 Edge+] crowlaw:
Worked perfect, thank you so much, Mr. J.

Venal_System, I did not have a chance to try your link, but thank you as well.
[T-Mobile Samsung Galaxy S6 Edge+] SkyVsTheWorld:
when i try to flash TWRP in odin i fails but it says custom binary(recovery) blocked by FAP lock on my phone when its in downaload mode and im on Stock OTA of 6.0.1 for the SM-G928T ? does any buddy know what im doing wrong?
[T-Mobile Samsung Galaxy S6 Edge+] Misterjunky:
re: odin flashing

I know exactly what you are doing wrong...

Go into Settings>Developers options and enable the OEM unlock.

By default the OEM unlock is always enabled so you must have

disabled it!!! LOL

That's why you are having issues with odin flashing twrp.

Keep the OEM unlock ENABLED all the time.

Good luck,

Have a great day!
[T-Mobile Samsung Galaxy S6 Edge+] eeekim33:
Is there an odin tar for mm yet or bootloader and modem

Tia
[T-Mobile Samsung Galaxy S6 Edge+] crazygerz:
I have 2 questions

1. Always private mode is lost by making root in 6.0.1?

2.in g928t 6.0.1 you do not need a custom kernel?
[T-Mobile Samsung Galaxy S6 Edge+] fordfx2:
I just got this phone (SM-928T) and switched to Tmobile 2 days ago. Much happier with-mobile by the way. Anyway, I am on 5.1.1 AOGD and was weary about installing OTA updates so I didn't take incase I wouldn't be able to root. I currently have root via CF-Autoroot for 5.1.1 but, for whatever reason I cannot get TWRP installed on it though. Once I do it, it soft bricks and upon rebooting I get an error in the top left stating "RECOVERY IS NOT SEANDROID ENFORCING" I can only get back into ODIN. Recovery doesn't boot. I have to reflash with CF-Autoroot in order to get my phone to boot again. So my question is, if I install stock 6.0 firmware via ODIN or Smart switch returning me to stock 6.0 and "unroot" then flash then these files I should be on 6.0 and achieviable root again? Thanks for any info!

- Sorry If this is a dumb question, but I haven't been in the rooting scene in awhile since I had a Note 4 that couldn't be rooted on Verizon for about 2 years.
[Mate 8 Q&A, Help & Troubleshooting] OcazPrime:
Hello! So I've tried many different methods to root my Huawei Mate 8 NXT-L29. I've even attempted using Rayglobe's Italian Knife tool and i only got as far as installing and accessing TWRP at which i got lost because it wanted a password for something. I'm tech savvy, but not familliar with android as much as I am with Windows so i gave up on that only to wipe my phone by accident. I'd like to try again if I could get some help... Could someone list some steps for me? I got lost because Rayglobe had some very loose translations on the page for his tool. Things got complicated to the point where i was trying to figure out what I was doing on my own. If any information is required I'll post it here. I hope the kindness of strangers helps me through this. Haven't had that hard of a time since Kingo Root worked for all my other devices.

EDIT: Any steps for any root method will do. Like a root process for dummies would be pretty cool actually. I just wanna get it done cuz i have gotten pretty frustrated with this. Fastboot method, Rayglobe Knife method I don't mind either one :(

I love whoever takes the time to read this and whomever responds to it. Im sure if someone with the great knowhow would help more people than just me!
[Mate 8 Q&A, Help & Troubleshooting] ajsmsg78:
You need to install twrp, boot into it, go to Wipe, then format data, then type in yes. That will remove encryption on your phone. Then flash SuperSU 2.71 from here:

https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip?retrieve_file=1

That's it, you're rooted.
[Mate 8 Q&A, Help & Troubleshooting] OcazPrime:
can i backup and restore my crap when im done doing this?
[Mate 8 Q&A, Help & Troubleshooting] OcazPrime:
well the root worked but now it wont boot anymore
[Mate 8 Q&A, Help & Troubleshooting] OcazPrime:
My phone is rooted but now it gets stuck at the Huawei Logo when i boot it. The sounds cuts out and it sits there just flashing the huawei logo over and over not doing a single thing. The Rayglobe tool doesnt recognize it. What do i do now?
[Mate 8 Q&A, Help & Troubleshooting] jbmc83:
have u tried doing a cold reboot again?

also, try and flash the decrypted boot image found over in the original android dev section, that might help.

also, maybe try and use a different supersu version, say 2.65 or 2.67 beta
[Mate 8 Q&A, Help & Troubleshooting] bluheart:
Always read each and every step carefully.

To restore flash using dload method
[7" Kindle Fire HD Q&A, Help & Troubleshooting] doodguy:
Hello,

I'm working on a friends kindle fire, but can't seem to pinpoint which one this is. It only has a power buton on the bottom with Micro USB port. Says Kindle on the back horizontally, and has model # D01400 on the back.

Can anyone help identify exactly which kindle this is? I think its 1st Gen
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Krunk_Kracker:
Sounds like a first or second gen.

http://www.lovemyfire.com/kindle-fire-tablet.html
[Nexus 6 Q&A, Help & Troubleshooting] cbase2013:
Hey, trying to flash back to stock, when this happens.

Error code: Unable to load " bootloader. Img"

Is it because im on a custom rom?

The laptop im on is pretty ****ty, could it be that?

Trying not to be a dummy,

Sebastian

What up yall

Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] suhridkhan:
could be a bad download on that bootloader file. could be poor usb connection. what is your flashing process? You need to provide more details.
[Nexus 6 Q&A, Help & Troubleshooting] cbase2013:
Downloaded latest iso from google, unzipped the tgz, ran the flash-all.bat, first time said that recovery and boot were missing. Tried manually flashing using adb, with the "unable to load" message

What up yall

Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
you can not flash via adb, only using fastboot while in the bootloader. try flashing each individual partition again, or update your fastboot to the very latest and use flash all again.
[Nexus 6 Q&A, Help & Troubleshooting] cbase2013:
Heard.

Silly question; i can't download MobileOdin or Flashify and flash it all from my phone, can i?

What up yall

Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
Odin is for Samsung devices, and to flash a factory image you need to use fastboot. fastboot is what nexus devices use. and no, you can't do it from your phone. once that is done, and flashing twrp recovery, you can use only your phone for everything else.
[Nexus 6 Q&A, Help & Troubleshooting] cbase2013:
Thanks!

What up yall

Nexus 6
[LG Leon Questions & Answers] a1smkshp:
Is it possible to change a boost mobile leon to metro pcs
[Off-topic] CJSnet:
I'm going to simply present a few facts and see if I am the only one reaching the same conclusion.

1. On 14 April 2016 I ordered the first of 2 "Live Cases" for the Nexus 6P, and the order was sent to Google's factory.

2. On 16 April 2016 I received an alert from my bank (which never happens) asking me to review suspicious transactions:

These were the transactions, all in the city of "Shenzhen", China, including a hotel stay costing me $1,892:

Plotting the locations on a map shows where the fraudster traveled between:

3. On 18 April 2016 I received a tracking update from Google revealing the order had shipped from "Shenzhen", China. In addition, the tracking website displayed a map of the pick-up location (presumably the Google factory). Note the proximity of the pick-up pushpin to the fraudulent purchases above:

Obviously setting up my new card everywhere has been hugely inconvenient, not to mention nearly being defrauded by some $2000.

I do not believe Google share the credit card info with the factory. But it is not impossible that there may be some vulnerability in the order system whereby a factory order processing worker may have been able to access the info. Or the info may have unintentionally been included on a docket, etc. Plenty of possibilities, including coincidence.

I have notified the Google Store team and await their response. I will update this thread if anything of substance comes back from them.
[Off-topic] M_T_M:
Or, or maybe just maybe your WiFi connection wasn't protected. Or, someone stole your card number whilst shopping some places else and this was just a major coincidence...

We may never know! :eek:
[Off-topic] ironman38102:
I highly doubt that the OP could be that stupid enough to do those things above but I would wanna know how this goes on
[Off-topic] M_T_M:
OP will for sure deliver on a resolution mate...let's wait!!:highfive:
[Off-topic] CJSnet:
I never purchase on unsecured connections.

No reply from the Google Store team yet, oddly enough. Not even acknowledgment that they're looking into it.

Cheers!
[Off-topic] ironman38102:
Not sure if trolling me or actually serious. You're slacking in terms of trolling.
[Off-topic] CJSnet:
First response from Google which I've challenged:

Cheers!
[Off-topic] LastStandingDroid:
Seems like you been scanned or getting your credit card info stolen.

This can be due to

1. Open WiFi

2. Bad applications installed.

3. Really bad luck?

4. Hijacked session?

Sorry to hear that too, we should wait and see if someone has the same issues.

Maybe the site was hijacked? Idk
[Off-topic] _Dennis_:
One major question.

Why would Google send your credit card information to a manufacturer? That makes no sense. You pay Google, Google pays the manufacturer some of the money, you get your case made. The manufacturer doesn't get the whole $35, Google gets it, then pays a rate per order probably at the end of the month/quarter, never should the factory see your credit card number.
[Off-topic] CJSnet:
Yes I covered that in my original post.

Cheers!
[Off-topic] ztmike:
Well we do know one thing.. Someone had a good time for almost 2gs at a hotel stay.
[Off-topic] _Dennis_:
You did, with one sentence. I'm not sure why it would be on a docket slip, since the CC info would not be useful, that would be a major screw up, one that would cost a few people their jobs. Also it could be a vulnerability in the order processing, but same with any order you placed online, so it would not necessarily be from ordering at Google. It just seems highly unlikely that your card would be stolen by Google or leaked by Google, much more likely it was a coincidence.

I once had my credit card info stolen, was used to by pizza in Richmond VA which is on the other side of the US. I assumed an ATM skimmer or some other technique was used, for my ~$60 back and had to input my new info for s month or so when I paid bills. I didn't assume some company with a tie to Richmond stole it.

Also, almost everything you buy is manufactured in shenzen China.
[Off-topic] CJSnet:
Thanks for your input guys.

Latest update:

Exciting times! They're going to 'fix my issue'. Time travel perhaps.

I'll keep you posted.

Edit: They don't get back to me in 72 hours, but 6 days.

Cheers!
[Off-topic] LastStandingDroid:
Yeah let's hope they get your money back :)
[Off-topic] CJSnet:
6 days after they promised a reply in 3 days, a reply from someone who can barely speak English:

Nice to see Google taking this so seriously. [emoji15]

Cheers!
[Off-topic] ironman38102:
I'm kinda disappointed with Googles responses so far. I'll be ordering a Nexus 6p from them coming June and I am having second thoughts because if something like this happens, my dad will never let me buy anything off from Google Store.
[Off-topic] CJSnet:
Cheers!
[Off-topic] CJSnet:
Final response from Google:

Cheers!
[Off-topic] Svid:
Did you made the order on public place or your home?
[Off-topic] CJSnet:
Home.

Cheers!
[HTC Desire 510] denny.hell:
BETA testers for OTA updates

I have managed to enable a function for our ROM to receive OTA updates directly from me. This will make updates more easy to be deployed and cuts down the time for me to upload the whole ROM and for you to download it and flash it. Be advised that this is for testing purposes only (for now). I don't know how much stable the ROM will be after receiving an update.

By flashing the ZIP file below you acknowledge that you are wiling to become a BETA tester and that you do this at your own risk.

Step 1.

You need to download the ZIP file below this post and flash it like any normal flashable ZIP.

The ZIP file contains a new app for OTA Updates, a new lib file for proper functioning of the app and an edited build.prop file. The build.prop file contains information to tell the app where to check if new updates are available, so please do not edit it yourself.

The app will say that there are no updates. That is not a bug, error or a glitch. Currently there are no updates. When an update is deployed the app will send you a notification.

Step 2.

Send an email to denny.hell.dp@gmail.com to confirm that you have downloaded and flashed the ZIP file and that you are willing to be a BETA tester. Please use a valid email because I will be contacting you to share feedback about the new updates and discuss any issues you might have.
[HTC Desire 510] denny.hell:
Reserved
[HTC Desire 510] Benik3:
Thanks a lot for the sharing!

I will definitely test it ;)
[HTC Desire 510] Benik3:
BTW you say that you have problem - bootloop with the .zip, did you tried to flash boot.img manually after flashing of the .zip?

Also instead of gallery I use simply photos by google :)

Or there is also lightweight Gallery app by google (com.android.gallery3d). You will probably find it in GAPPS ;)
[HTC Desire 510] denny.hell:
Thanks for those tips. I will definitely take a look at the lightweight gallery. :)

I tried flashing the boot.img manually but nothing. I've got it to boot up just once but there was no wi-fi. That leads me to belive that the permissions in the updater-script are not set up properly but also could be something else. If you have experience with updater-script do you think that you could help me out? :)
[HTC Desire 510] Benik3:
Unfortunately I don't have any bigger experiences with updater-script :(

Few times I edited it, but never so big one like installing ROM...

Anyway can you sand me the zip? I will try to look, but I don't promise anything :P
[HTC Desire 510] pashangi:
hi,

thanks so much for this Debloate.:good:
[HTC Desire 510] Knxed_:
Well done developer! Phone itself is 10x faster without the bloatware apps on! Thank you so much developer!
[HTC Desire 510] margosre:
Thanks a lot for your sharing. I finally have a nice going device. Its the best solution currently for this phone.
[HTC Desire 510] myke_angell:
Hello mates i have an question

This version has fix that permision for sd card ?
[HTC Desire 510] Moki1:
4. Now you should see the backup folder. Open it.

I do not see anywhere

what to do with the zip file that I downloaded from the above link

My bad, I did not read everything you've written
[HTC Desire 510] denny.hell:
Yes...I don't have any trouble with my SD card :)
[HTC Desire 510] denny.hell:
No problem, if you have any further problems don't hesitate to ask :)
[HTC Desire 510] X-77:
would be nice to have HTC Sense UI and email app left and htc foto editor and gallery removed and replaced by Google Photos, I don't understand why stick to ES File Explorer which does have in app ads rather have native file explorer, also I don't understand why I need that clean tool when android is managing ram just fine in this version.

Sorry if that sound rude, language barrier :)

Keep up with good work.
[HTC Desire 510] denny.hell:
No problem, any feedback is more than welcome. ;) The Sense UI will remain, the theming I'm gonna make will only be on the icons and maybe the QuickSettings layout of the buttons, nothing too big to ruin the Sense feel. I might get back the e-mail app if I can't find a descent replacement for it. In the next update the HTC Gallery, alongside the Photo Editor will be replaced by Google Photos. Also the ES File Explorer, I'm gonna replace it with something that is adds free, simple to use but versatile. The Clean tool is not much for RAM as it is for Junk removal. Here is an example: Yesterday I was listening to some music on YouTube for about two hours. After that, I run the Junk Removal tool....It removed somewhere around 900Mb of useless data. You see how you can free up some space with it. ;) I plan to keep it, but If I get negative feedback about it I will remove it. :)

Again thank you for your feedback. ;)
[HTC Desire 510] Benik3:
E.g. Total Commander is simple and nice explorer without adds ;)

BTW now when you have root, you can install "adblocker" app :)
[HTC Desire 510] lucyr03:
deodex is not good for this device beacuse have small memory and charge it useless, odex files have sufficient space in system.

my oppinion :)
[HTC Desire 510] denny.hell:
Thank you for your opinion. :) The main reason that I deodexed the ROM is to save up on the size of the actual download. I'm currently running the deodexed version on my phone and it works just fine. But still it will remain in BETA version unless I get positiv feedback about it. :)
[HTC Desire 510] X-77:
Guys, I recall what I said, don't listen to me I'm a noob :P
[HTC Desire 510] Benik3:
Finally installed the first version of ROM.

It's so fast compared to stock sh*t! :)

Only I still get message to update SUbinary.

I tried it twice through TWRP and nothing (but it looks like installation was successful).

Maybe I will try to download and install it manually...

For others: Be careful that it will not download HTC sense home screen app after restore. If yes, delete it! :)

EDIT: Even after manual updating of SuperSU binaries the message is still here. But SU looks working fine...

It looks like problem with busybox, because when I try to update libraries, it's not installed in standard path /system/xbin and when I tried to use Viper4Android it say it's not able to install drivers because of bad busybox :(

When I try to update busybox to /system/bin it says that it was successfull, but after restart it's back on v1.22.1

Even updating directly from recovery didn't help :(

BTW I recommend to add this ROM into DevDB ;)
[HTC Desire 510] denny.hell:
Thank you for this extensive review. I really appreciate it. Regarding the su binary... It won't update...I've tried all kind of approaches but non of them worked. Regarding the busybox...I have no idea how that got in there....It must have been in the original stock rom I got. :D :D But I will be very grateful if you could find a fix for the busybox issue. I have my hands full with this. I'm learning a lot of new stuff about how this works and I simply can't find time to accomplish all goals in short time.

I plan to contact a forum moderator as soon as I get a working update.zip. At this point this tread is only informational. ;)
[HTC Desire 510] Benik3:
Thanks for reply.

I will try to find something about busybox, unfortunately I'm not also so deep in Android :D

If I will find something, I will let you know ;)
[HTC Desire 510] lucyr03:
For SU fix flash this boot.img

Busybox issue will solve this app but first flash boot.img.
[HTC Desire 510] denny.hell:
The boot.img contained in my download already has write-protection removed. :) The su binary is working just fine a minor issue is that it won't update to the latest version. As for busybox....I'll try to find the newest release somewhere on the internet or extract it from that app. :)

Thank you for your suggestions. ;)
[HTC Desire 510] lucyr03:
Just flast this boot.img and you will thank me ;)
[HTC Desire 510] denny.hell:
Thank you.... ;) This seems to resolved the su binary issue. Do you mind telling me were you got this from and what other modifications there are? It seems rather small in size... If this doesn't effect the stability of the ROM It will be added in the next update. :)
[HTC Desire 510] lucyr03:
I only remove su binary and busybox from it(rbheromax used for root when no recovery available)

Sorry for my bad english :D
[HTC Desire 510] denny.hell:
So let me get this straight....rbheromax implemented the su and busybox binaries in his kernel. And when ever I use his kernel the outdated version form his kernel were forced on the system besides the system already having the binaries. If this is the case I'll be happy to add this new kernel in the next update. :) You seem like you are using it for some time, does it have and side effects, like random restarts, force closing apps, crashes etc. ? I've been using it just for a day and it seems pretty good. ;)

Again thank you for this ;)
[HTC Desire 510] lucyr03:
I use about as old as the first custom recovery for this phone and I had absolutely no problem.

"Again thank you for this" No problem man, I'm happy to help desire 510 64bit community ;)
[HTC Desire 510] Benik3:
So you solved it finally.

Me too, but not so clean way :D

I used busybox On Rails app. After clean&install with option through recovery, I was able to install Viper4A drivers without problem (otherwise Busybox app by Stericsson still saying v 1.22.1)

EDIT: I flashed the boot.img. Now it looks that it works OK (also the Busybox app by stericson). Thanks a lot! :)

I'm going to test Xposed :D
[HTC Desire 510] denny.hell:
Looks like the kernel I used it had su and busybox with older versions and it was forcing them on the system despite the system already having them. :P

Xposed works perfectly....already installed it and I'm trying to figure out what are the modules changing in order to add them as native with out the need of the framework.
[HTC Desire 510] Benik3:
I just installed Xposed too, but I had to use modified app from here: http://xdaforums.com/showpost.php?p=64063168&postcount=62

Otherwise I got error with no compatibility of our processor :)

EDIT: I looks working fine.

I'm just testing Sense toolbox :D

BTW I would like to also learn, how to modify mixer_paths.xml to get sound from front speaker together with the back one and also to louder the back one a little...