yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] fanatik85:
i cant open it. is it 64 bit suitable?
[ONE Android Development] bknight99:
Will you be updating this to YOG7DAS2K1?
[ONE Android Development] therohanchawla:
Hi glad you were planning to update but its been a while??

Also I have a feature request ....can you take a iemi/efs backup automatically when the user roots the device for the first time....that would save users a lot of issues ....

IMO that is the reason that bricks a lot of devices......

Hope you play heed to this...

Best,

Rohan
[ONE Android Development] Vaetheran2107:
Is development for Oneplus X still in progress or did you stop?
[ONE Android Development] anubis.genix:
An update for 12.1.1 YOG7DAS2K1 would be much appreciated ;)
[ONE Android Development] jeushyun:
toolkit

i rooted my oneplus with this toolbox. My version is YOG7DAS2K1
[ONE Android Development] dbzkamehameha:
i'm not familiar with the versions, but is this the latest one?

if so shouldn't this be impossible since the tool has been updated yet?

did you manage to do this without losing any data (contacts, app, messages, phone settings,...)
[ONE Android Development] FaNtAsMiCu:
Hello all, will this app be updated? i think there are 2 versions behind now
[ONE Android Development] crisis_trustee:
Will you be updating this to ZNH0EAS26M?
[ONE Android Development] FaNtAsMiCu:
Will you be updating this to ZNH0EAS2JK ?
[ONE Android Development] Assis Brandão:
My friend is no longer developing? I noticed that no longer appears the updated files to 6.0
[ONE Android Development] schubeir:
No support for the latest TWRP or MM?
[ONE Android Development] tantiquanti:
Hi, can someone help me? I never had problem with this program with windows 7, now i have W 10 and I can't connect the phone to bacon root toolkit.

when I try to do the ADB part the pc automatically recognize the portable device and for me is impossible to install the appopriated driver.

have u any idea?
[ONE Android Development] jjdev:
Since 6.0 is not supported, can i use it to return to stock 12.1 and subsequently oem update to 6.0?
[ONE Android Development] marios_ch:
hey guys i am asking for the same thing

any quick help here

thanks
[ONE Android Development] therohanchawla:
Yes.... Flash back to stock one ota away... You can do that....

But back up first...

Or just flash the full official zip in twrp... Its the same...
[ONE Android Development] G3noxide:
bless your ****ing soul :D

Was playing around with my OPO and saw that the original toolkit I was using was basically discontinued. Here you are to save the day!
[ONE Android Development] Akhil916:
Holy crap! You made it work easily. My phone wasn't being detected in the adb shell after trying for an hour or so. Finally, found this. Thanks man and I think you should update it. Anyway, we can find those files ourselves for now.
[ONE Android Development] csurfer:
Thank you WugFresh! Spent two days looking for a way to get my brand new stock OnePlus One with Oxygen OS, flashed to Cyanogen Os. Yours worked!:D:D
[ONE Android Development] romish:
What is this for ? Is it for Mediatek based phones
[ONE Android Development] rohitereddy:
hi,

I unlocked the bootloader, installed twrp recovery and tried to install supersu via twrp, after installation the phone was stuck in the boot animation, then i downloaded this program and followed the instructions shown by the program, it recognized the device and factory reset the device. The final message said to wait for the phone to bootup. Its been more than an hour now and I'm still stuck at the bootup animation. PLs help

---------- Post added at 02:37 AM ---------- Previous post was at 01:53 AM ----------

I unlocked the bootloader, installed twrp recovery and tried to install supersu via twrp, after installation the phone was stuck in the boot animation, then i downloaded this program and followed the instructions shown by the program, it recognized the device and factory reset the device. The final message said to wait for the phone to bootup. Its been more than an hour now and I'm still stuck at the bootup animation. PLs help
[ONE Android Development] ireaper4592:
did u try turning device off manually and boot to stock recovery and do factory reset there that sometimes helps with other devices hope that helps
[ONE Android Development] rohitereddy:
didn't boot to stock recovery, just did a factory reset and also full wipe using twrp. but to no progress. now it's stuck at the oneplus logo.
[ONE Android Development] Vierhetleven:
This is why I stay away from rooting my phone. Worst case scenario is bricking my phone. But I need my phone to have lineageos android 9 version. Who can help a newbie out
[ONE Android Development] dragonsouce:
regular site down mirror https://bacon-root-toolkit.en.lo4d.com/windows
[ONE Android Development] Vonnegut:
Hi [MENTION=3110798]WugFresh[/MENTION],

i'm not a frontends fan but you did a great work there!

My only concern is about the locking/unlocking script. Since 30O, OnePlus changed the bootloader in a way that might trouble newbies. I'll make it short...

The script overwrite 2 bits in order to relock/unlock the bootloader and turn the tamperbit back to FALSE.

What most ppl don't know is that:

A) they won't be able to unlock it again using the usual fastboot oem unlock command

B) they won't be able to boot a custom recovery in fastboot mode anymore

C) it seems that the tamperbit got back to TRUE after a reboot

D) some ppl couldn't boot in recovery anymore

The only way to unlock the bootloader again is running the script (again) and that (sometime) can't be done because of A)+D)

I've been helping a few guys to get out of troubles for the last 3 months and there are still lots of guys who found/find themselves in that situation after using that script (check the main thread).

I could help only ppl who had root permissions because my technique needs an ADB shell in order to flash the old 25R bootloader using the dd command: in that way they could boot a custom recovery in fastboot mode again, then flash script again.

It's plenty of irrational ppl out there who feel better if they relock everything...and some of them went so far to unroot their OPO too. If so, they won't be able to unlock their OPO never ever again (and i met some of them).

What most puzzle me is that there is no reason at all to relock the OPO because:

1) OnePlus warranty covers unlocked bootloaders and if someone thinks he could deceive a professional software engineer using a a script must be very delusional

2) whenever someone wants to flash a new ROM or update his favorite custom recovery, he will have to unlock the OPO again.

Usually the target for toolkits are the newbies and they rightfully think that if the coder put a "Back to Stock" option, that means because it's safe to use. But that's not the case...

So, i strongly recommend you to remove the script.
[ONE Android Development] WugFresh:
I have an OPO myself and I never ran into these issues, so this is new info to me.

What if, just the tamper reset script was run, and the bootloader was relocked via fastboot oem lock, rather than the script for relocking.

Or, are both the tamper reset, and lock/unlock scripts bad news. In which case, the kit should revert to just fastboot oem unlock/lock - and disregard tamper flags.. as it doesn't matter.

Regards,

{{ WugFresh }}
[ONE Android Development] NCguy:
Sorry to oversimplify but is this only an issue if you relock? Seems like OPO support sent me a "patch" that wiped the works and relocked as well. Fortunately I was able to unlock again.
[ONE Android Development] Vonnegut:
I know what you're talking about..it's an official zip with some batch files.

Open the .zip and check the ONEPLUS ONE - 2.bat file with an editor. You'll see that the last line (before rebooting) is the fastboot oem lock command.

That's fine, you can always unlock you OPO again.

But here we are talking about a script overwriting single bits of the bootloader...

---------- Post added at 07:03 PM ---------- Previous post was at 06:52 PM ----------

Here's a few examples...

A guy who can't boot a custom recovery in fastboot mode anymore --> http://xdaforums.com/showpost.php?p=56875045&postcount=323

A guy discovering that the tamperbit get back back to TRUE after rebooting --> http://xdaforums.com/showpost.php?p=56894238&postcount=325

Here's the start of a long post exchange (read it to the end) --> http://xdaforums.com/oneplus-one/de...tamper-bit-t2820912/post55584653#post55584653

As i wrote, i already helped at least 8 guys so far (who used another toolkit)...
[ONE Android Development] WugFresh:
Ok. Thank you for the notice. Will revert to classic fastboot oem lock in v1.0.1 and aim to push that later today.

{{ WugFresh }}
[ONE Android Development] WugFresh:
[MENTION=5427631]Vonnegut[/MENTION]

Thanks again for the head's up. v1.0.1 is now live with the change and removal of that devs file. I just wanted to clarify one thing though. Assuming the user was able to unlock again (like they didn't completely dig themselves into a hole.. i.e.. no root or recovery), then once they reflash a bootloader.img - the "damage" caused by that script is entirely reversed. So that is an important thing to note that you did not - it is not a permanent thing if the user can reflash bootloader. That said, I see where you are coming from, and recognize the circumstance where that wouldn't be possible. I have just confirmed this though. Used the script, reflashed bootloader - can use fastboot oem unlock/relock as you would except. Either way. I agree with you 100%, it should not be included - and now it is is not :)

{{ WugFresh }}
[ONE Android Development] skizofrenic:
Wug

THANKS !!!!

I owe u another beer !!!!

(Better coffee.... And now go back coding!!!!!)
[ONE Android Development] Pajorve:
[MENTION=3110798]WugFresh[/MENTION] its a best work toolkit ... Easily and faster.

Thanx so much My friend.
[ONE Android Development] Vonnegut:
My pleasure, thank you.

You did a terrific job with your Toolkit. Very impressive!

BTW, what do you mean with 2nd bootloader and trust zone?

What's the name of the partitions you are referring to?

Number Size(Kb) Name Device
1 65536 modem /dev/block/mmcblk0p1 (*) FAT16
2 512 sbl1 /dev/block/mmcblk0p2 (*)
3 32 dbi /dev/block/mmcblk0p3 (*)
4 32 DDR /dev/block/mmcblk0p4
5 1024 aboot /dev/block/mmcblk0p5 (*)
6 500 rpm /dev/block/mmcblk0p6 (*)
7 16384 boot /dev/block/mmcblk0p7 (*)
8 500 tz /dev/block/mmcblk0p8 (*)
9 1024 pad /dev/block/mmcblk0p9
10 1536 modemst1 /dev/block/mmcblk0p10
11 1536 modemst2 /dev/block/mmcblk0p11
12 10240 oppodycnvbk /dev/block/mmcblk0p12
13 10240 oppostanvbk /dev/block/mmcblk0p13
14 1355776 system /dev/block/mmcblk0p14 (*) EXT4
15 32768 persist /dev/block/mmcblk0p15 EXT4
16 524288 cache /dev/block/mmcblk0p16 (*) EXT4
17 16384 recovery /dev/block/mmcblk0p17 (*)
18 1536 fsg /dev/block/mmcblk0p18
19 1 fsc /dev/block/mmcblk0p19
20 8 ssd /dev/block/mmcblk0p20
21 1024 misc /dev/block/mmcblk0p21
22 16384 LOGO /dev/block/mmcblk0p22 (*)
23 32768 DRIVER /dev/block/mmcblk0p23
24 32768 reserve1 /dev/block/mmcblk0p24
25 16384 reserve2 /dev/block/mmcblk0p25
26 8192 reserve3 /dev/block/mmcblk0p26
27 65536 reserve4 /dev/block/mmcblk0p27
28 58510540 userdata /dev/block/mmcblk0p28 (*) EXT4
29 294895 grow /dev/block/mmcblk0p29

Exactly!

Even just running the script again fixes everything.

Frankly speaking, the 22R bootloader and the 30O bootloader are about the same..
[ONE Android Development] WugFresh:
Thank you!

2nd Bootloader = sbl1

trust zone = tz

bootlaoder = aboot

If you mouse hover over the buttons, a tooltip should pop-up with more info.

{{ WugFresh }}
[ONE Android Development] WugFresh:
I never really explained the new "modem management" feature that is specific to this Bacon Root Toolkit.

If you use advanced utilities, "Fastboot Flash" > "Modem". You will see a GUI that looks like this:

For every factory package cyanogenmod releases, I hash and upload their modem files. I name them like this stock_modem_bacon_XXXXXX.bin <- where the XXXXXX is the first few characters of the MD5 value. I did it this way because some packages have the exact same modem file. It is known that flashing the "latest" modem file may not always yield the best service (per user/location) - so the kit provides a simple way to chose any of the modem files ever released - flash them, and test them out. The button "Default Modem" will change the entry in the pull-down menu to the modem file that shipped with your current build.

Also, some other things unique to BaconRootToolkit, are the features like "restore stock kernel" and "restore stock recovery" are still included, but rather than having a dedicated button on the advanced GUI, you first hit the "Fastboot Flash" "Boot" or "Recovery" buttons, and you will be presented with new GUI windows that look like this (respectively):

Cheers.

{{ WugFresh }}
[ONE Android Development] Vonnegut:
Nice, i've learned something about the real names of those partition :good:

If you don't mind, i'd like to share a bit more infos which could be useful for the users.

The 44S flashes the oppostanvbk partition too...along with a new sbl1, the new modem and a new resource power manager (rpm) http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH44S-bacon-signed-fastboot.zip

I guess you might add that partition too.

The latest original reserve4 is inside this official zip containing the 38R https://account.onepluscontent.com/downloads/tools/oneplus-one-reflash.zip (the one mentioned by other guy previously).

---------- Post added at 08:04 PM ---------- Previous post was at 07:47 PM ----------

Very nice feature!

Anyway, it looks like that changing modem it's not that simple anymore.

Since the 44S release, old modems (or the find7 one) doesn't seem to work anymore.

Ppl posted here consistent experiences (starting with this post reply http://xdaforums.com/oneplus-one/ge...collection-t2858734/post56580600#post56580600 )

Unfortunately there's not an official oppostanvbk partition before 44S (tho i have one 'cause i dumped it) and i feel that in order to flash a working older modem, the old sbl1+rpm+oppostanvbk must be flashed too (not sure if all of 3 are needed tho).
[ONE Android Development] WugFresh:
Credits to [MENTION=3183886]bigxie[/MENTION] for knowing those partition names. I had asked him in chat.

Thank you for the info. I have a moment now, so I am adding that oppostanvbk partition, along with a few other things. Regarding the modem stuff, that is interesting. Any idea of devs who would know the answer to that? If we know what items are required, I could probably bundle up flashable zips. Like, dump that partition, and add the other stuff, etc.

I appreciate the information and suggestions. I am trying to design these tools to be both newb and developer friendly, and provide a software solution that delivers adb/fastboot functionality nicely with the desktop experience.

I don't know how much you have messed around with this yet. But you should also check out the "file associations" options in the toolkits options menu. With this, you can associate filetypes like apk's, .ab, .mbn, .bin, .img with BRT, so they can be managed with the program by just double clicking the file without BRT open (or using "Open with...). For flashable img's/mbn's/bin this opens a new "quick flasher" interface, where you can chose the partition to flash it to. I use this feature all the time for dealing with flashable files. If its an apk, you get a msgbox, and then you can just hit ok and it will install it to your device. Just some features that are less known that can be really useful.

Cheers,

{{ WugFresh }}
[ONE Android Development] Rapscallion16:
Temporary recovery boot doesn't appear to be working. It reboots me into fastboot, then the fastboot screen goes to maximum brightness and does nothing else.
[ONE Android Development] WugFresh:
How long do you wait? It takes particularly long on opo compared to other devices I have owned.
[ONE Android Development] Rapscallion16:
I don't know how long I'm supposed to wait, but I gave it a good 15 minutes before I rebooted. Does it matter if I already have a custom recovery flashed or not?
[ONE Android Development] WugFresh:
Ok. Yeah, that's way too long. No that doesn't matter. Are you sure your bootloader is unlocked? You can check with the cmd 'fastboot oem device-info' while your device is in bootloader mode. Use advanced utilities 'launch cmd prompt'

If you are unlocked, please try again with an alternate USB port.
[ONE Android Development] Rapscallion16:
It looks like it was the USB port. Neither of the front USBs on my PC worked, so I plugged it into a back USB and it booted the recovery fine. Thanks for the help.
[ONE Android Development] WugFresh:
Ok, I think I will ditch the pull-down menu thing then, and just make the "modem" button open a file select window, so users can flash whatever file they want to that partition (if they want). Yeah, personally, I wouldn't bother with flashing alternate modems unless a bug in one was clearly documented.

Thank you, that means a lot. For sure, as someone myself who is very happy with cmd line, I totally understand. I tried to implement features that I still like to use, and I also try and be very clear about what actions each feature performs. I appreciate your comments about my dir structure as well. :) For sure, will do. Cheers.

{{ WugFresh }}
[ONE Android Development] DooshPastesh:
This is the best toolkit. I've got it also for my nexus 4. Good work!
[ONE Android Development] flucks:
I use this for my Nexus 7. The BEST toolkit ever. Thank you so much!
[ONE Android Development] WugFresh:
Rooting requires you to unlock the bootloader. Unlocking the bootloader wipes data. That said, after root you will be on the stock ROM without any additional modifications.
[ONE Android Development] kdkinc:
So glad that I now have a device that you support with this tool kit.

This should be pinned as it's the best all around tool kit out there.

I don't want to learn a bunch of code I just want to root my phone and flash stuff.

I'll leave the code crap to the smart people. I sleep well at night.

Thank You $$ Confirmation number: 97D22682T1580931X.
[ONE Android Development] Sir_gpm:
Does this tool flash custom recovery?.
[ONE Android Development] Spannaa:
Yes

Sent by Bacon...
[ONE Android Development] WugFresh:
Thanks :)

I like this OnePlus One device, I will be sure to update this kit with new cool features soon.

{{ WugFresh }}
[ONE Android Development] Gorillazz:
Happy

Man so happy to see you!! I've been using your rootkit since Nexus 4. Glad you made for Oneplus you :)
[ONE Android Development] nedooo:
Best toolkit from old days of Nexus 4 and Nexus 5 now I see OPO support :)

Great!!!
[ONE Android Development] Gorillazz:
ADB drivers

I tried rooting oneplus but seems there is something wrong with the drivers. So I tried automatic installation but no avail. I can't go past step 3b. I can't see ADB interface and Android Device when trying to update it using the step 3b. Please help!
[ONE Android Development] kdkinc:
I had similar issues first time out try this .

Full reboot of phone and PC .

Use usb port from back of PC.

start tool kit before you plug in usb cable to phone.

Hope this helps....
[ONE Android Development] Gorillazz:
Thanks for replying mate! I finally made it work. Don't know exactly what I did coz I literally tried all possible steps mentioned in the Google and youtube lol
[ONE Android Development] abhifusion:
Super simple & quick !

Awesome toolkit man.

Thanks a lot !
[ONE Android Development] Kenshiro79:
I do not understand why but, i drver are installed but the ADB NO !! So therefore I can not come out anything !!!
[ONE Android Development] TechExhibeo:
Tool says successfully rooted

But root checked app says your device not rooted.

I have OPO indian version

Help me
[ONE Android Development] slaxy:
opo flashing global version

Iam using opo global version (non indian) 4.4.4 cm version 11.0-XNPH44S 64 GB.

Would like to know if i can flash or root it via bacon tool kit v1.0.2
[ONE Android Development] Criton30:
I have no problem with it on stock 44S ROM.
[ONE Android Development] Assassin27:
I am on stock 44s ROM and when I tried to root, it said it was successful, but when I open busybox, it gives me an error saying my device may not be rooted. Also when I use a root checker app, it says it isn't rooted. Any way I can fix this?
[ONE Android Development] TechExhibeo:
I also have same problem
[ONE Android Development] junk!e:
Hey small doubt here. If I unlock and relock the boot loader ,is there anyway to find out if boot loader was unlocked once.
[ONE Android Development] s327374:
I spent a great deal of time today messing around with the instructions that are given in the Root guide here: http://xdaforums.com/showthread.php?t=2788632

Also had all the files downloaded last night in preparation for a quick easy root etc.

I had no luck at all even though I followed the instructions to the letter. Maybe it was because I was using a 64gb, maybe because it wasn't on CM11, but the Chinese Color Rom. I wonder if the fact that there was no developer recovery option might have been the problem, but it just wouldn't work.

Anyway, finally tried this and it took less than 10 minutes...

If you have OS color and can't remove it, than this thing works. Don't even bother with the instructions elsewhere. They might work if you're coming from CM11, but not for me.

Cheers to the dude who made this and I just wish I'd tried this first.
[ONE Android Development] WugFresh:
Site is temp down. For mirrors: https://plus.google.com/113329792100896065459/posts/cTJeV68ChFJ

{{ WugFresh }}
[ONE Android Development] Albieri[SPAM]:
If you received the 44s OTA, reinstalling from scratch ROM 44s already with root. I also had problems trying to apply the root to the 44s ROM distributed automatically via OTA.
[ONE Android Development] TechExhibeo:
U mean to say

I have to flash a pre rooted rom?
[ONE Android Development] Albieri[SPAM]:
Yup!

I had the 38R and received the OTA for the 44S, lost root and it seemed that nothing could get to the root again. Soon had to reinstall a pre-rooted ROM.
[ONE Android Development] WugFresh:
? This makes no sense.
[ONE Android Development] kaneelias:
Hi,

How long does the rooting process take? I have been stuck on the Fastboot Screen for 15 minutes with the program saying waiting for your device. I just received a message saying waiting for device has timed out.

I successfully unlocked the phone so not sure why it is failling.
[ONE Android Development] gb_Texas:
where did it fail, what part of the process ?

---------- Post added at 07:07 PM ---------- Previous post was at 07:02 PM ----------

@wugfresh thanks so much for the tool... big fan of yours on the NRT

I was able to install BRT on my system as your NRT... (so to support my Nexus 5&9, and now my OPO)

appreciate you doing this... :D
[ONE Android Development] Albieri[SPAM]:
Wug probably is not a problem of your tool. And yes with the ROM I was. So to save time, I've installed a ROM with root.

I have tested their tool and it is 100% functional for the ROM 44S.
[ONE Android Development] Deacon-Frost:
I've rooted my device and also flashed some mods with your toolkit. Everything went as expected and that was excellent. Thanks man. :thumbup:
[ONE Android Development] miglio1990:
are you on XNPH44S?
[ONE Android Development] Deacon-Frost:
Yep
[ONE Android Development] zeyoner:
Awesome really happy to see Wug is developing for our very much loved Oneplus ONE! I've used this toolkit for my Nexus devices and it has always been on point! Good ish :good:
[ONE Android Development] kenhicg:
Thank you for all you work. It went off perfect. Donation sent.
[ONE Android Development] Criton30:
[MENTION=3110798]WugFresh[/MENTION]: could you please update the app for 05Q?
[ONE Android Development] Spannaa:
Not sure that's possible until Cyanogen release the XNPH05Q fastboot zip
[ONE Android Development] pctechdroid:
Anyone had an issue where the toolkit will see fastboot normally but when you try to root and it wants to boot into fastboot, it doesn't see the device?