yashsingh1/xdaforums huggingface dataset:
[HTC Vox] gibsonk:
I have flashed your spl, but i have never been able to get my phone into bootloader unless done by the update. Is it possible to use a bkondisk backup from another phone ??? hard reset does not work phone does not get that far. will try with battery out :o
[HTC Vox] jockyw2001:
:confused: Unplug usb, pull battery out, put it in, keep camera button pressed and shortly press power. You should see the tri-color bootscreen.
[HTC Vox] gibsonk:
:) :) :) I managed to get into bootloader following your instructions and flashed it with a good rom and my Vox is working fine. Thankyou for your help and time Jocky Much appreciated. Guess i need to take some more time when cooking and look more at the info from the cooked rom.

Thankyou

Thankyou

:)
[HTC Vox] iceberg2403:
I am having the same problem!! except the only thing is i cant flash an original signed HTC rom because i changed the CID in my cooked rom :( (STUPID!!)

I flashed my cooked rom using Jockyw's USPL. I can connect to the bootloader using MTTY. When i try to flash another custom ROM with a CID the same it says corrupt (this is the check for the signed ROM??).

Please help!

Thanks
[HTC Vox] alllof:
VOX.

Hello,

could you please attach the instructions to this post?

My VOX is bricked! Please, help.
[HTC Vox] baz0927:
I have the same problem, but can`t get the bootloader screen,just a black balnk screen and the phone beeps.any ideas?
[HTC Vox] baz0927:
fixed

have fixed my phone
[Pixel C Q&A, Help & Troubleshooting] DrKaotica:
This is my first pure Google device. I've owned several Samsung devices and I'm familiar with using Odin to flash the device with recovery and then whatever you want from there.

I keep seeing references to fastboot. I'm really not familiar with how you flash or root your Google device using this.

Is there an all-inclusive guide on how to flash this device? I understand you have to unlock the bootloader first.

Thanks.
[Pixel C Q&A, Help & Troubleshooting] tbcpn:
I've not rooted my Pixel C, but this http://www.wugfresh.com/nrt/ works seamlessly on my Nexus 7 2013. Page suggests that it supports Pixel C.
[Pixel C Q&A, Help & Troubleshooting] DollarUsername:
Yes, you have to unlock the bootloader-- I found a posting here on doing it-- it's pretty straight forward.

After that all you basically need to do is boot into TWRP to install supersu. I had the bootloop issues actually flashing TWRP for whatever reason however I found another posting here noting that you don't actually HAVE to *flash* TWRP, you just need to boot into it.

First get a version of SuperSU-- I *may* have used UPDATE-SuperSU-v2.76-20160630161323.zip that I got from here somewhere-- not sure now exactly-- probably just get the latest one.

Push that to the pixel via something like "adb push UPDATE-SuperSU-v2.76-20160630161323.zip /sdcard/" from your Mac, Linux or Windows box.

So I've got a stock bootloader now ( I had to revert the whole thing to make it usable again) and to boot into TWRP I first put the pixel into fastboot mode (boot up and hold down power and volume down, then select fastboot), then go:

fastboot boot recovery.img

..where recovery.img is one of the files like TWRP-3.0.2-0.recovery.img or twrp-3.0.0-0-dragon-ryu-02112016-1.img

After you are booted into TWRP you then select (I believe, from memory) "INSTALL" and select the supersu zip file you put on the device earlier. After it installs that reboot and you are root.
[AT&T LG G3] note2root:
Hi is there a root for lg g3 d852 android 6.0 i wanna flash some roms and kernels see if i can speed this pos phone up a bit
[AT&T LG G3] hyelton:
You need to downgrade first.
[AT&T LG G3] note2root:
Downgrade to 5.1? And not quite sure how to do that would you be able to point me in the right direction please or is there a forum for it?
[Xiaomi Redmi Note 3 Questions & Answers] ybregeon2016:
All is in the title. My bootloader is officialy unlocked but I can't find a way to install a custom recovery and to root the last Marshmallow Beta rom. Any help?:confused::confused:
[Xiaomi Redmi Note 3 Questions & Answers] Zrzahid:
If you flash the fastboot rom with miflash , you can do everything like before. Otherwise, this is the guide-

http://en.miui.com/thread-344450-1-1.html
[Xiaomi Redmi Note 3 Questions & Answers] candiesdoodle:
[MENTION=7464704]ybregeon2016[/MENTION] were you successful on rooting and twrp? What method did uou use and which twrp did you install? Thr number of different versions and the overly complicated methods are too confusing...

Thanks in advance
[Xiaomi Redmi Note 3 Questions & Answers] NVDX11:
[MENTION=4457482]candiesdoodle[/MENTION]

Flashing miui8 6.9.9 MM relocked my bootloader,so i suggest to check whether your bootloader got relocked again or not.

If its locked unlock it via mi unlock tool.

I am using alka twrp , and rooted my rom by flashing supersu zip from twrp.

To install twrp i used fastboot commands.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
No tests have been done on this rom, I compiled it remotely it may or may not boot, I am unable to test due to my work, I work away from home, no computer and can't risk phone while away from home, I will do my own test once I get home and have complete access to computer.

Again this is untested alpha, all risks are on you, I can't provide and help, make sure you know how to get your phone in and out of bootloops, make sure splash tool is working for your phone, if something goes wrong you may need it to restore your phone.

To all that test this rom good luck, and post back your results, those that choose not to test, not a problem I fully understand, this is not to be taken lightly.

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

your bootloader will need to be unlocked

you need twrp recovery

Good Luck.

Kernel source

https://github.com/vampirefo/android_kernel_mediatek_mt6735

device tree is based on

https://github.com/vampirefo/android_device_elephone_p8000
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Device tree/source files pls :)

Also good job on finally getting this to work! Gonna download soon.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] bullet25:
+1 for the device tree please.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Before I flash, was this ROM built off the 6.6 image that locks us out of using SPFT? I don't know if it even works that way but I just figured I'd ask to be safe.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] ColtonDRG:
Gr8 m8 8/8

Release the device tree on GitHub.

Do it.

Please.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
Currently trying it out, will report back later.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Getting a status 7, saying this device was made for "R1_HD" and not "P6601". Gonna remove the updater script line that checks that and flash again.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
I got that too, that should work too but I just switched to vampire's TWRP and that worked for me.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
How's the ROM? Did it boot yet?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
Doesn't look like it. It's hanging on the logo.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Mine kept getting status 7, even with vampire's TWRP. Leave it booting at the log, let me know if it changes. Sometimes initial boot can take like 10-15 mins.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] RainofOranges:
I'll let it sit for a while, then. I don't think anything will change, though.

Edit: Nope. Back to stock ROM for now, this doesn't boot yet.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
Usually thats because of a bad download from my experience , since i used to get that error alot.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Thanks for testing, When I get home, I will test it on my phone, check logcat and see what I can find.

This will probably be my last public testing, The next test ROM I release will be private.

I will post notice here when ready, and those that tested this version and still want to test any future versions will receive a download link via pm.

Thanks to all that tested ROM.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
any progress update?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Due to work, I haven't had time to even look at it.

I am debating and what to do.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
We understand. and man it really bothers me alot due to the fact i dont understand none of this yet because I could of been working on kernels or helping since i have so much free time.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] aaceaze:
Eagerly waiting for a stable version. I am no tech geek so dont wanna risk on Alpha version :D
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Well, we all have a to start somewhere... An actual "stable" version of CM may never really happen. I'd be happy to try the first build that actually boots up. No matter how buggy it might turn out, just so I can give you feedback and get a general sense of what this phone should feel, look like and behave out of the box.

I really miss the several options and customizations from CM ROMs... But above all, I really miss having a nicely made custom kernel with a good kernel manager app (like EX kernel manager) to set it up exactly the way I like it... I have faith in this device. Particularly because this phone is selling so well. I really hope for an official CM development for the R1 HD. Hopefully even a good custom kernel...! That would be awesome! Maybe then I'd be able to retire my Nexus 5. I have really missed having an external SD card... 64GB vs 32GB makes a huge difference.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I think the problem is in the boot.img, the init.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] n3kf:
Hope this isn't too far off topic, but I have compiled a ton of Linux kernels in the past. Is the process somewhat similar? Might be a fun thing to do now that I am retired. Well, fun is relative!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Kernel source is available, plus my build script, you setup stuff up, run my script, it builds kernel , packs boot.img then you just flash boot.img.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
Please do take a crack at it...PLEASE!!!!:crying:
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] aaceaze:
As I understand only the surface level of root n custom Roms, I'm sure I will get stuck in bootloop or maybe brick or some unknown problem. I had serious issues when I confidently tried to flash custom roms on my Note 2. So I have to wait for at least Beta version to flash. 8-)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Alpha is well alpha, and not for many people.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Latest version will boot to CM13 boot screen and I can get logcat logs, slow but progress.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
awsome awsome awsome
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] bullet25:
Hey Vamp, Can I ask what you changed/did to get the device to at least the boot screen so I can get mine to the boot screen too?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I had to force kernel into permissive mode
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
so making the kernel permisive and the rom permisive = boot ?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
I don't have boot, my Rom goes to cm13 splash screen, no farther.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
was the rom set to permisive as well?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Permissive is done via kernel.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
Im a noob but idk check this out : http://xdaforums.com/g2-mini/general/guide-how-to-set-selinux-to-permissive-t3329439

2- http://www.mtkroms.com/2016/04/stable-cyanogenmod-13-v2-for-mt6582.html

idk for sum reason i tought the rom as well had to be set to permisive.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
They are claiming they already have cm13 running on this phone, so no need to work on it any further.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
This project is now dead, [MENTION=5238428]superdragonpt[/MENTION] claims to already have a working cm13, he is much more experienced with mtk than I am, so no need for this project.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] bullet25:
Vamp, really quick. If you are willing could you please explain how you got the kernel to be permissive?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
can you direct us to the post where i claimed that he got it working on the Blu R1 HD?

---------- Post added at 04:56 PM ---------- Previous post was at 04:44 PM ----------

the question now is will he upload the cm13 for the R1 HD.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jrk190:
Surely he will. He's been really busy wth MTK devices, he's still due to release an AOSP ROM for the Asus memopad as well!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] CircularApex:
http://xdaforums.com/showpost.php?p=68751325&postcount=5504
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jrk190:
I like how immediately about 6 people ask for the upload.

That, kids, is how you don't get an upload. I've seen superdragon get upset over that before and not release stuff. So behave unless you want to wait again.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Can't blame us for being excited, considering how much work some of us have put into this with no results.

If you want to stick with the children analogy, imagine saying you have some candy to a 4 year old that's tried to get some in the past and couldn't, and getting upset when he asks for some.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jrk190:
Didn't mean to come across like that, it's just that he always releases when he wants. That and the golden rule of XDA for not asking for ETA's. I get where you're coming from, I want cm13/14 on this phone more than anything else, but I'm not gonna bug him.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] AndroidBR:
Okay people, let's not turn against each other alright... We all have been longing for the same thing here. After all, none of us expected to be so excited about a $60 phone. I confess I've become quite fond of this phone. So much so that, if an unofficial nightly of CM ever gets released for it, I'm planning on ditching my Nexus 5 for good, simply because I have been missing having access to an SD card for over two years. Dual SIM and decent battery life is really great as well on the R1 HD. The other day I had over 7h of SOT.

Going back to that developer's attitude / behavior...

I mean... Seriously...?! The guy successfully builds CM 13 and keeps it all for himself? What's the point? Just so he can brag about it and be the coolest kid on the block? Come on now. That's just sad and quite frankly, somewhat pathetic.

I have never seen that kind of behavior, lack of communication and friendless from any other developer here.

I really wish I had the knowledge and skills to make CM builds and custom kernels. Like most of the users here on XDA, I'm just a mere mortal, when compared to some of the few Android legends that have have been blessing my life and the lives of literary - thousands of people out there - for several years with their continued development and generosity. Looking back, I know I have a lot to be thankful for. (@stratosk [MENTION=2784807]DooMLoRD[/MENTION] [MENTION=4684315]flar2 [/MENTION] [MENTION=3117667] pawitp[/MENTION])

By the way, if one of these developers mentioned above would be willing and interested in developing for the R1 HD, just PM me so we could start a conversation about the possibility of me shipping you a device, as most of you live abroad and don't have access to this phone sold in the USA. That would be my treat, with a very obvious string attached to it. Haha!

Cheers everyone! :svetius: ;)
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
+1 to that :good:
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jrk190:
Yeah, sorry if I sounded rude, we all want custom Roms. It's just a matter of waiting now!
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Can I make this my sigline
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] bullet25:
This has literally been my issue trying to get CM to work on this phone. Anybody with knowledge almost never wants to help. The people who supposedly have working CM don't want to release anything for god only know why. The people who had working device trees before me, don't want to show it to anybody.

I have never seen this ANYWHERE on XDA before. I don't understand why I am seeing it for the R1HD/Mediatek.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
The main issue is cm13 needs to be patched correctly, you are never going to get cm13 working on this phone.

Why? well you don't have the patches, only certain people have them, and won't share.

That is the problem, had the people who have the patches shared, almost every mtk device would have cm13.

They simply don't want other's to build cm for other devices.

A working tree or source will never be released for R1HD, a broken tree or source that can't be compiled may be released.

As far as cm13 ROM being released, that is completely up to the person who built it.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Didn't you have a working tree before where you could compile kernel (or something else)?

Perhaps we can compare yours and bullet's and see what changes or revisions to make
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
This has been the norm on XDA for a very long time for mtk devices, you don't know or notice cause you haven't had a mtk device or never tried to develop for one.

One simply can't just download cm13 source and compile it for any mtk device, you need to patch the source.

Well the people that have the patches, are the ones that decides which mtk device get a custom ROM or not.

If the patches were available to everyone 99% of all the problems people ask for help wouldn't exist.

It is what it is.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
You guys are just forking trees, pushing a tree to GitHub is much different. requires a computer, which I don't have, as I work on the road.

However my tree base is on my GitHub, I used my cm12.1 energy x plus tree, just made changes to 6735.

https://github.com/vampirefo/android_device_blu_E030U
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
A device tree is one of the essential components to compiling things like ROMs. Device trees are what's supposed to contain proprietary blobs, which CM13 won't boot without on the R1.

Anyway, thanks for putting that out there about your tree. I'll see if bullet can make anything of it.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
You are confused, you have to pull the blobs from your phone, the tree simply tells the compiler what to build from.

No matter, it won't work without the cm13 patches, no matter what.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] jasonmerc:
Yes, I am confused. Never built ROMs before, figured I'd get this phone to learn how. Hey we all start somewhere.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
Correct, the blobs don't just come out of thin air though, you pull them from your phone, and place them in vendor, the problem with blobs is you have to look at other trees and guess what files you need there is no guide that says use this file don't use that file.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
So cm13 looks like it might be a no-go , well im one step closer of bringing an MIUI to the R1 , got it to boot but getting stuck in animations and not for enough to get logs , im working on it still , surprisingly it booted with the R1 stock boot-img without unpacking -modding-repacking.....so on a side note if anyone else is familiar or might know how to help me out with this port that would be nice...at least we could enjoy a different rom for the moment until we get CM13 or CM14 on the R1.

P.S i think this might be a great time to improve/add more features to the kernel if thats possible.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
It's not that cm13 is a no go, the person who compiled it has the cm13 patches, he won't share the patches, is he going to share the ROM? Only he could answer that.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] KazuDante:
The reason I said its a no-go is because as he stated , he had it working fine since at least 2 weeks or more and did not share it with the community...again that's totally he's choice and I respect that 100% but i dont have to agree. to better understand the situation did he make the patches from scratch ?
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] vampirefo:
No, they were leaked he did nothing but received them. Someone gave them to him.
[BLU R1 HD ROMs, Kernels, Recoveries, & Other Devel] emkorial:
Don't kill the project. Anyone who "claims" to have it working but won't share the rom might as well not exist. No one cares about an alleged CM13 that no one can get. If they don't share it, just assume they are lying/faked it and keep moving forward with the project.