Bootloader unlock and simplicity probably.
Congrats to whoever Ryan is, I'm assuming that's a successful build and boot of a kernel, one step in the right direction
Blu R1 HD is ready for the devs!
- Thread starter onlykhaz
- Start date
Congrats to whoever Ryan is, I'm assuming that's a successful build and boot of a kernel, one step in the right direction
Your reply doesn't make sense to me.
Why run older version of software?
Sent from my R1 HD using Tapatalk
Probably just didn't bother to update. It's a dev phone, probably not daily used.
Again your reply doesn't make sense to me, he used my script to build kernel says he lives on the edge yet runs out of date firmware.
Sent from my R1 HD using Tapatalk
The point being, he successfully built and has the custom kernel. That in itself is a milestone. The kernel can always be updated and improved, it was likely just for proof.
Just give it time and it can only get better from here
He only did so cause I told him how, I guess you skipped right over my posts, as I was the one who compiled the kernel and posted the kernel, and gave instructions and script on building the kernel my point is why run out of date firmware, my guess you don't know why.
Sent from my R1 HD using Tapatalk
Last edited:
Oh sorry, I read the posts but think I skipped over the names. Thanks for clearing that up.
Not a problem, see when developing people who are developing should be using and developing on the latest firmware.
I work on many devices, always use the latest firmware.
Sent from my R1 HD using Tapatalk
vampirefo is correct. I could not have figured out packing the boot image without his assistance. Credit where credit is due. As far as why I'm running 6.4 and not 6.5, I just got the phone yesterday and didn't bother updating it before flashing TWRP, rooting and unlocking the bootloader. When going through that process, all of the tools seemed to be built for 6.4 firmware and I didn't want to risk losing the ability to do so. My general approach to any device is that OTA updates are BAD BAD BAD and you should never do them. Here's a blog post I wrote last year that explains my stance on OTAs http://ryancuda.blogspot.com/2015/05/why-ota-updates-are-bad.html Besides, with any luck, I'll be flashing custom firmware on it soon. firmware 6.5 wasn't even a point release for Android (still build MRA58k, the FIRST release of Marshmallow which is nearly a year old now), so defer to rule #1 NEVER ACCEPT OTA UPDATES. And yes this is not my main phone. daily driver is a jailbroken iPhone 6S+, this phone is just for dev purposes.
I disagree OTA are the best, you get almost all the info you need from them, to develop on a particular device correct placement of partitions, correct permissions, security updates.
Thanks to the OTA I know the correct permissions to place in my update script for my flashable stock rom and or any custom rom.
Correct permissions are the key to successful flashing firmware.
As far as root tools and so forth.
How I rooted my device.
I unboxed the phone, charged phone, after an hour, started flash tool loaded unlock.img hooked phone up to computer pressed power.
Phone was immediately flashed, this was the first start of phone.
Now let phone boot up, skip everything that can be skipped only do the least possible to get to developer options, check USB debugging.
adb reboot bootloader,
fastboot oem unlock
reboot, setup phone.
adb reboot bootloader
fastboot boot twrp
make backup
Reboot system download OTA, after download copy OTA to computer, now allow OTA to install, after installed.
adb reboot bootloader
fastboot boot twrp
make backup
now flash SuperSU zip and reboot.
I now have two completely stock back ups one that came with phone other one 6.5 updated via OTA.
Now with rooted file manager remove, amazon crap, and anything else you want to remove.
If at anytime another OTA is available.
adb reboot bootloader
fastboot boot twrp
use twrp to restore the system and boot from 6.5, reboot.
Download new OTA save to computer, then install, once installed make a backup of it.
Just repeat the process for every OTA,
These backups can be transferred to your computer.
Always have the most current firmware without any problems.
Sent from my R1 HD using Tapatalk
---------- Post added at 09:45 AM ---------- Previous post was at 09:44 AM ----------
My next step is to make a flashable stock rom, I figured out adb remount last night.
Sent from my R1 HD using Tapatalk
Last edited:
Thanks for the info. OTA updates may be useful to gather info from, sure. but there is a very distinct possibility that an OTA update in the future can break things like the bootloader unlock, recovery, root, etc. Case in point; The LG G3. druing the time I owned the phone, the Lollipop bootloader was never unlocked, so to flash CM12 or above you had to roll the bootloader back to the kitkat one. Not worth losing root over. In my opinion, staying on the lowest (and thus most exploitable) firmware is best if you modify your device. Not only that, but as I pointed out on my blog, most OTA updates are inherently designed to slow your phone down.
I'm not saying that either policy is more or less correct than one or the other. But in my case, as a practice I do not ever accept OTA updates.
All you have to do is look inside the OTA update and see what it does, say for example it replaced bootloader, thus would prevent bootloader unlocking.
In that case simply remove that part of the OTA, zip and flash modified OTA via twrp now you have the update minus the bootloader part.
You can always review the OTA zip make changes if needed then flash it.
Too each their own.
Anyway we are off topic, my fault.[emoji12] [emoji12] [emoji12]
Sent from my R1 HD using Tapatalk
Last edited:
Wich file or files are need to be modified to attempt enabling a few more 4G bands?
Sent from my R1 HD using Tapatalk
Sent from my R1 HD using Tapatalk
That is the modem, up to BLU on what bands they allow.
Sent from my R1 HD using Tapatalk
Sadly i cant return this phone...my stupid contry refuse to share info on which bands 4g they work on, and Blu reponded to me that they dont have futur plans on unveiling more bands
Sent from my R1 HD using Tapatalk
Sent from my R1 HD using Tapatalk
Well no more Band 12 for us then. Probably no more Nougat as well.
Exciting! I wonder with our current sources if it'll be possible to build nougat and later versions of Android. It's always confused me as to why some devices have kernel sources but can't be updated via custom Roms... I guess too much code changes between kernels? I don't know.
band 12 is already released tho.
---------- Post added at 04:12 PM ---------- Previous post was at 04:09 PM ----------
Sent from my R1 HD using Tapatalk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone