http://www.gsmarena.com/blu_r1_hd-8171.php
BLU R1 HD - 16 GB - Black - Prime Exclusive - with Lockscreen Offers & Ads
This is a Prime stock 6.5 rom, this rom comes from my phone, not rooted unmodified stock rom.
The purpose of this thread is to be able to flash stock or custom roms for Prime R1HD via Twrp.
You need to either have twrp installed or be able to boot into twrp to install this rom.
I currently just boot into twrp, I still have stock recovery installed, my bootloader is unlocked.
I have downloaded @ColtonDRG normal-stock-oob which is V12 non prime version, I checked the permissions on the system to see if 6.5 and V12 used different permission they use the same.
So a V12 rom can be made from my exact stock_rom_R1HD_6.5.zip, I may or may not provide a non prime version, even if I don't all a user has to do it open my stock_rom_R1HD_6.5.zip replace system and boot.img with non prime zip and flash.
There are two twrp recoveries one I just made and one made by @lopestom I had to get the rom compliant with both recoveries, @lopestom was the first recovery available for R1HD and allows backing up and restoring of many partitions, I am going to use his recovery.fstab, but remove the partitions backup and restore I don't use.
both recoveries at one time or other would throw an error
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
I have now fixed that so neither recovery error, any other recovery that might show up, that person will have to fix his own, for now two recoveries can flash my rom, the one I made and @lopestom
To install download rom and recovery if you don't already have twrp.
Rom 0cee0d831502a2a867f036d951c3c78c stock_rom_R1HD_6.5.zip
https://www.androidfilehost.com/?fid=24713784966774808
Twrp recovery fbfe25ff742b2e994e45deeff0e3cfb7 R1HD_TWRP_recovery.img
https://www.androidfilehost.com/?fid=24713784966774807
@ColtonDRG non prime rom 77e85918d63de289423006ee3911f580 normal-stock-oob.zip
https://www.androidfilehost.com/?fid=24713784966774846
stock_rom_R1HD_6.6.zip (stock 6.6 rom is stock 6.6 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 6.6, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=24727338994368677
Modified_rom_R1HD_6.6.zip (Modified_rom is stock 6.6 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 6.6, as well as amazon apps, no ads, updater disabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=24727338994368678
Modified_rom_R1HD_7.4.2.zip (Modified_rom is stock 7.4.2 rom minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img from 7.4.2, as well as amazon apps, no ads, updater enabled, so this rom is safe to use.)
https://www.androidfilehost.com/?fid=313042859668275704
stock_V17_OEM_rom.zip minus the preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img
https://www.androidfilehost.com/?fid=457095661767119968
Settings_V17.zip , This is settings from v12 ported to V17 to allow OEM unlocking and Navigation bar.
https://www.mediafire.com/?ui1r5w1khg8k5j7
place on sdcard
boot into twrp
install
reboot
Credits
@ColtonDRG
@lopestom
@bluefirebird
@onlykhaz
@ss2man44
@AtomicFizzle
I like your recovery. Do you mind if I mirror it?
ColtonDRG said:
I like your recovery. Do you mind if I mirror it?
Click to expand...
Click to collapse
No problem, upload it, where ever you need to.
If it's okay I'll get a non-Prime one up in a bit.
Edit 1: Dang it I can't get the system.img file to extract. Using this tool on Windows 10 Pro x64 - http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
AngryManMLS said:
If it's okay I'll get a non-Prime one up in a bit.
Edit 1: Dang it I can't get the system.img file to extract. Using this tool on Windows 10 Pro x64 - http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Click to expand...
Click to collapse
I just mounted it via Linux it's ext4, I don't use windows, only Linux.
Sent from my NS-P08A7100 using Tapatalk
so, since the rest of partitions have been hidden from new recovery. are they generaly safe from change. or should a backup still be kept for them?
mrmazak said:
so, since the rest of partitions have been hidden from new recovery. are they generaly safe from change. or should a backup still be kept for them?
Click to expand...
Click to collapse
There are two twrp recoveries, use the one that you want, if you want to back up and restore more partitions use first recovery.
Blu has put out official splash tool ROM for Prime version today, will restore entire phone to stock.
Will be sometime before we get it, nothing on non prime.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
There are two twrp recoveries, use the one that you want, if you want to back up and restore more partitions use first recovery.
Blu has put out official splash tool ROM for Prime version today, will restore entire phone to stock.
Will be sometime before we get it, nothing on non prime.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
thats big news. do you have any links, i do see blu website has link for R1 support but cant find anything downloadable
mrmazak said:
thats big news. do you have any links,
Click to expand...
Click to collapse
They are private links right now, once I get the ROM we will go from there.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
I just mounted it via Linux it's ext4, I don't use windows, only Linux.
Click to expand...
Click to collapse
I found an ext4 extract program for Windows. Placed the /system directory into the ROM folder along with the boot.img but it failed to install. I'll investigate further tomorrow unless if you manage to put up an flashable ROM with the stock/OEM non-ad stuff.
AngryManMLS said:
I found an ext4 extract program for Windows. Placed the /system directory into the ROM folder along with the boot.img but it failed to install. I'll investigate further tomorrow unless if you manage to put up an flashable ROM with the stock/OEM non-ad stuff.
Click to expand...
Click to collapse
Uploading now.
77e85918d63de289423006ee3911f580 /home/vampirefo/Downloads/normal-stock-oob/normal-stock-oob.zip
My computer has been running hard today, between son doing his school work, me making roms, recovery, and just now got cm13 to finish compiling, it's for a similar device, it's an mtk phone, the point is to get the source set up to build.
Code:
make: Leaving directory '/home/vampirefo/Desktop/cm13'
#### make completed successfully (05:17:01 (hh:mm:ss)) ####
[email protected]:~/Desktop/cm131$
@ColtonDRG non prime rom has been added to first page.
vampirefo said:
@ColtonDRG non prime rom has been added to first page.
Click to expand...
Click to collapse
thanks for stock flashable zip
vampirefo said:
@ColtonDRG non prime rom has been added to first page.
Click to expand...
Click to collapse
when i try to install
non prime rom 77e85918d63de289423006ee3911f580 normal-stock-oob.zip
i just rename it to test-Ril
getting this error 7
ColtonDRG how to create update script
rameshurfrnd1 said:
ColtonDRG how to create update script
Click to expand...
Click to collapse
It says your system is mounted, your system needs to be unmounted.
Device or resource busy, means twrp can't mount system.
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
It says your system is mounted, your system needs to be unmounted.
Device or resource busy, means twrp can't mount system.
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
after wiping i just reboot to recovery and flashed successfully
rameshurfrnd1 said:
how to fix it
Click to expand...
Click to collapse
Click mount uncheck system, and uncheck mount system as ro
Sent from my BLU ENERGY X PLUS using Tapatalk
rameshurfrnd1 said:
after wiping i just reboot to recovery and flashed successfully
Click to expand...
Click to collapse
What ever works. [emoji2] [emoji2] [emoji2]
Sent from my BLU ENERGY X PLUS using Tapatalk
vampirefo said:
What ever works. [emoji2] [emoji2] [emoji2]
Sent from my BLU ENERGY X PLUS using Tapatalk
Click to expand...
Click to collapse
i am try to get 4g lte band in india
by changing the baseband
kindly help me to fix this
Related
NOTICE: I no longer have a copy of the recovery image since goo.im went down. If anyone still has it, feel free to post a link. I'll leave the instructions here. Also, I won't be updating this since I no longer have a TF201 and ROM development seems to have shifted to a modified bootloader, which requires a different recovery image anyway.
Original post:
Warning: You must be on the 4.1.1 Bootloader to use this. Androwook and other stock based ROMs supply their own recovery.
With 4.4 based ROMs starting to come to our tablet, and official TWRP not flashing them, I thought I'd take a crack at updating it. As some of you may know, attempting to flash a KitKat ROM using the current version of TWRP fails, resulting in a "set_metadata_recursive" error. This updated version, based on the OmniROM fork of TWRP, fixes that.
Latest Version: 2.7.0.0-Voyager2k_v1.2
Instructions:
1.(Highly Recommended) Enable NVFlash if you haven't already. Check here for details.
2. Make sure you are on the 4.1.1 Jellybean Bootloader. If you are already running ParanoidAndroid or CyanogenMod, you're fine.
3. Download the recovery image here. The latest file is recovery1.2.img. EDIT: Links are broken. See above
4. You can use the same instructions that are on the TWRP page, but for convenience, I'll add them here. You have two options:
A. Fastboot. Boot the tablet into fastboot and use "fastboot -i 0x0b05 flash recovery recoveryX.X.img" (no quotes, replace X.X with whatever numbers are in the filename) from your computer to flash the recovery.B. Flash from terminal within the tablet. Open a terminal emulator within android and type "su" (no quotes) to get root access. Then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4" (no quotes, replace X.X with whatever numbers are in the filename) to flash the recovery and reboot normally. This is critical, as the recovery won't flash until the system has rebooted normally.
If successful, the version number should read: "2.7.0.0-Voyager2k-vX.X" (X.X being my revision number)
Known Issues:
1. /system/media doesn't get backed up for some reason. Restoring backups works, but you won't have sounds or a boot animation. (I think this is fixed in the newest version, but I'm waiting on other reports before I remove this item)
Ususal disclaimer: I am not responsible if this messes up your tablet in any way.
Credits:
TWRP for making the recovery
Built from the OmniROM fork. Source is here.
Changelog:
Version 1.1 - 2/19/2014
Added support for the dock keyboard
Fixed /system/media not backing up properly
Synced with latest OmniROM recovery sources
Version 1.2 - 3/25/2014
Updated to TWRP version 2.7.0.0
A little cleanup behind the scenes
one more.
Works Great! Flashed without problems via fastboot :victory:
Thank You!
Now I just need an awesome 4.4. ROM to flash :fingers-crossed:
works also with the second instruction over the tablet
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
thanks, it works through terminal. jut make sure to be root (su) and adjust the path of the recovery image
Sent from my EPAD using Tapatalk
thanks! This rec works and I have flashed cm11. Terminal works. U should insert "su" first
Sent from my GT-N7102 using Tapatalk
To use the second method you need to run su command first before using dd
Sent from my TF300T on OmniROM (4.4.2) using Tapatalk 4
Terminal
Just would like to ditto.
The process worked in the terminal on the device.
Thank you for this!
Bug report!
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Dasdranamin said:
BUG REPORT!
There is a BUG in this version of TWRP:
It does not make any backup folder named media!
For example /system/media.
As result after recovery the folder /system has no this subfolder media and correspondingly missing boot animation and system sounds.
Click to expand...
Click to collapse
Thanks for the report. I'll look in to it.
Cyrozo said:
Excellent news
I tried through the Terminal but despite no error was presented it didn't worked. The recovery presented was the old CWM. After flashing through fastboot the new recovery popped out like a charm
Thanks.
Click to expand...
Click to collapse
Are you sure you placed the new "recovery.img" in the root directory of the sdcard? Won't work if the file is anywhere else.
Note 3 4.4.2
Does it work on note 3 with 4.4.2??
SAMERKAD said:
Does it work on note 3 with 4.4.2??
Click to expand...
Click to collapse
Nope, check your devices fora for compatible recoveries.
Bastaerd said:
Nope, check your devices fora for compatible recoveries.
Click to expand...
Click to collapse
can i bring back backed up data with other recovery?
SAMERKAD said:
can i bring back backed up data with other recovery?
Click to expand...
Click to collapse
You should be able to do so. Anyways, this isn't the recovery for your device.
Bastaerd said:
You should be able to do so. Anyways, this isn't the recovery for your device.
Click to expand...
Click to collapse
yeah i know, but i had it on 4.3 and backed up data via TWRP
now im on 4.4.2 with CWM Recovery...
want to restore my System data
Thankss
What bootloader is this compatible with? Does it work with the TF300T Bootloader? I am guessing not but someone from the Androwook thread might try it and that will not be good.
Seeing this is for kk support/ROMs, why would a wookie fastboot this?
Thank you Voyager for the ongoing support for the prime!
Sent from my VS980 4G using Tapatalk
Hello
After searching the internet for good 30-40 minutes I found the Stock OnePlus 2 recovery image. I am returning my unit so needed it to be fully stock.
Download: https://www.dropbox.com/s/8np35kw71i222as/OPT Stock Recovery.7z?dl=0
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Been searching for this for past hour!!!!!!
Hi,
Thank you very much.
I'm also returning my phone to oneplus and i had unlocked and rooted the phone like you.
May i know how you restore the stock ROM and recovery?
thank you
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
granfot said:
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
werthechamp said:
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
Click to expand...
Click to collapse
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
granfot said:
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Is this the recovery of the international version or chinese?
thx
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
CafeKampuchia said:
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
Click to expand...
Click to collapse
Problem: The signed flashable zips don't contain recovery.img
Spannaa said:
Problem: The signed flashable zips don't contain recovery.img
Click to expand...
Click to collapse
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
CafeKampuchia said:
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
Click to expand...
Click to collapse
I Installed the 2.0 manually...then update ota...now I have stock recovery.
zat0x said:
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
Click to expand...
Click to collapse
Hey, I don't know if you ever found the stock recovery but another member had posted fastboot images in the OnePlus2 Android Development section.
I haven't tested out the recovery myself, but you can check to see if it's the English one.
All Fastboot images: https://www.androidfilehost.com/?w=files&flid=40701
Stock Recovery Image: https://www.androidfilehost.com/?fid=24052804347834210
Hope this helps.
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
Good question! Want to know that too...
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
1:
Flash the full stock rom from OxygenOS 2.1.1: http://forum.xda-developers.com/showthread.php?t=3209863
2: Flash the OxygenOS 2.1.2 zip from the same post
3: flash the stock recovery from tgis thread
Hope I helped you
Download OP2 Stock Recovery from Official Site: https://s3.amazonaws.com/oxygenos.oneplus.net/OP2_recovery.img
It seems OnePlus uses AWS to host all of their OTA's.
E.G. https://s3.amazonaws.com/oxygenos.oneplus.net/OnePlus2Oxygen_14_OTA_012_all_1602261837.zip ( This is for OxygenOS 2.2.1 releases in 2012 26th Feb - 970MB )
Recent ROM Downloads of OP2: http://downloads.oneplus.net/devices/oneplus-2/ ( Includes Marshmallow Beta OxygenOS 3.0 , however, seems the ROM has Battery issue, major )
matrixdefalco said:
I Installed the 2.0 manually...then update ota...now I have stock recovery.
Click to expand...
Click to collapse
I did the same thing and it worked for me If somebody is still facing this issue
anyone knows how the flash the stock recovery from mac???
krishp said:
anyone knows how the flash the stock recovery from mac???
Click to expand...
Click to collapse
One "?" is enough dude..
You have to install adb for Mac (http://stackoverflow.com/questions/31374085/installing-adb-on-mac-os-x), enable USB Debugging on your phone, reboot into bootloader mode :
Code:
adb reboot-bootloader
then go into:
Code:
su
and then
Code:
fastboot devices
fastboot flash <recovery_name>.img
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
Custom Treble-ready TWRP with F2FS encryption
Features:
Code:
* Treblize button for automated Treble conversion;
* New /vendor mount points in place;
* F2FS encryption and decryption support;
* Upstreamed Lambda Kernel tailored down for recovery.
Downloads:
All prebuilt recovery images are available on Github, the current tag is 08062018.
XDA:DevDB Information
Unofficial Treble-ready TWRP with F2FS encryption, Tool/Utility for the LeEco Le Pro3
Contributors
GalaticStryder, codeworkx
Source Code: https://github.com/GalaticStryder/android_bootable_recovery
Version Information
Status: Testing
Stable Release Date: 2018-04-20
Created 2017-03-11
Last Updated 2018-08-07
Reserved
Reserved
It sounds like if you are already rooted and have twrp installed all you need to download the multi rom apk. Is it that easy to have two three rom to jump back and forth?
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
It sounds like if you are already rooted and have twrp installed all you need to download the multi rom apk. Is it that easy to have two three rom to jump back and forth?
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
MultiROM app will install a new TWRP and the trampoline chainloader.
You can have as many as you'd like to test... Just don't put a password on lockscreen to avoid the credentials bug.
The vanilla TWRP is the latest you can get and has decryption support for testing, so it's a good shot flashing it as well if you're not going to multirom.
Sent from my LEX720 using Tapatalk
Does all rom have to be rooted? I usually like rom to be none rooted for work related email dam app checks for root
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
Does all rom have to be rooted? I usually like rom to be none rooted for work related email dam app checks for root
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Only first slot ROM needs root but it's not mandatory as trampoline integrates the Kernel not the system and so won't need root for the basic functions. You'll only need root when using the app to install the modification, manual install doesn't need as I said but it's strongly recommended on first slot.
Sent from my LEX720 using Tapatalk
GalaticStryder said:
Only first slot ROM needs root but it's not mandatory as trampoline integrates the Kernel not the system and so won't need root for the basic functions. You'll only need root when using the app to install the modification, manual install doesn't need as I said but it's strongly recommended on first slot.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Hey @GalaticStryder,
I flashed this Recovery on my x727 but it looks like it's not passing encryption. :crying: Any ideas on what I can do? It asks me to decrypt with password upon booting recovery.
Ascertion said:
Hey @GalaticStryder,
I flashed this Recovery on my x727 but it looks like it's not passing encryption. :crying: Any ideas on what I can do? It asks me to decrypt with password upon booting recovery.
Click to expand...
Click to collapse
Probably system's vold didn't work for decryption. Could you flash previous version on fastboot? I have a script to extract the blobs from system just in case but I wanted to test the built-in feature from TWRP.
I've tested on LineageOS and it worked but my device is Chinese.
Sent from my LEX720 using Tapatalk
GalaticStryder said:
Probably system's vold didn't work for decryption. Could you flash previous version on fastboot? I have a script to extract the blobs from system just in case but I wanted to test the built-in feature from TWRP.
I've tested on LineageOS and it worked but my device is Chinese.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, same thing. I am greeted by a Enter Password screen upon booting either after flashing in Fastboot. I am using command below.
Fastboot flash recovery TWRP_zl1_20170302.img
It looks like it'd work perfect but has the encryption issue on x727 variants. My guess is Lineage is also based on the x720 and doesn't encrypt the OS when it boots?
Ascertion said:
Unfortunately, same thing. I am greeted by a Enter Password screen upon booting either after flashing in Fastboot. I am using command below.
Fastboot flash recovery TWRP_zl1_20170302.img
It looks like it'd work perfect but has the encryption issue on x727 variants. My guess is Lineage is also based on the x720 and doesn't encrypt the OS when it boots?
Click to expand...
Click to collapse
Not actually that way, but we can say that. Does any other recovery decrypt properly on your device? Probably recoveries with built-in blobs or blobs extracted from system.
Hello. I have a problem with the kernel of VillarLeg AOKP. The problem is that as soon as I try to change some parameters of some governor you restart the device. I reported the problem to this Centre dev and he said that without MultiROM there are no such problems. Can it be solved?
Inviato dal mio LEX720 utilizzando Tapatalk
Can someone make a zip file that erases lock screen realted files in data/system folder?
TWRP offers file manger only on primary rom, not on other multi roms. So if you have locks on 2nd, 3rd... roms, you are screwed.
If such zip file can be made, it would be easy to fix the mistake/problem.
4K2K said:
Can someone make a zip file that erases lock screen realted files in data/system folder?
TWRP offers file manger only on primary rom, not on other multi roms. So if you have locks on 2nd, 3rd... roms, you are screwed.
If such zip file can be made, it would be easy to fix the mistake/problem.
Click to expand...
Click to collapse
if you swipe rom?
Inviato dal mio LEX720 utilizzando Tapatalk
GalaticStryder said:
Not actually that way, but we can say that. Does any other recovery decrypt properly on your device? Probably recoveries with built-in blobs or blobs extracted from system.
Click to expand...
Click to collapse
The one from the Lineage thread works fine, but it's TWRP 3.0.2.0. I don't see a source for it though.
Ascertion said:
The one from the Lineage thread works fine, but it's TWRP 3.0.2.0. I don't see a source for it though.
Click to expand...
Click to collapse
My TWRP device tree uses Lineage 13.0 to build but different Kernel and no blobs. Could post here the screens asking for passwd and a dmesg inside recovery?
GalaticStryder said:
My TWRP device tree uses Lineage 13.0 to build but different Kernel and no blobs. Could post here the screens asking for passwd and a dmesg inside recovery?
Click to expand...
Click to collapse
Unfortunately, it looks like /system or /storage doesn't mount either so I'm not able to get a dmesg log or take screenshots. This is a picture from my other phone. Is there a different way to grab the log?
In vanilla TWRP_zl1_20170311 if i choose reboot in recovery mode it always reboot in system mode
Can this new TWRP version be used without MultiROM? I currently use the build of codeworkx (https://forum.xda-developers.com/le-pro3/development/lineageos-development-t3553180).
flotux said:
Can this new TWRP version be used without MultiROM? I currently use the build of codeworkx (https://forum.xda-developers.com/le-pro3/development/lineageos-development-t3553180).
Click to expand...
Click to collapse
Sure. TWRP is vanilla, TWRP_multirom (suffix) is for MultiROM which can also be used without MultiROM without problems.
Vanilla: TWRP_zl1_20170311.img
MultiROM: TWRP_multirom_zl1_20170302-01.img
MultiROM stuff is never pushed to Android File Host because I need a static download URL for the MultiROM app and AFH servers aren't static, they shut down every day and switch the file in their servers so it rotates every time.
giogio1 said:
In vanilla TWRP_zl1_20170311 if i choose reboot in recovery mode it always reboot in system mode
Click to expand...
Click to collapse
Seems to boot fine to recovery for me, not encrypted.
Man every phone I get, I brick!! Im stuck in a BLU boot loop. Can't find any files out there for this model. Well did see one here
http://clangsm.com/ftpdemo/index.php?dir=Flashes/BLU/Studio%20XL%202/
They want $$ for the download :crying:
Anyone a member there that could get me this file?
Thanks for the help
Try this
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
what version is this?
dougunder said:
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
Click to expand...
Click to collapse
is this firmware v08? it rendered my phone inoperable. no cell, no camera and several other issues. the phone came installed with v09
Anyone ever find V09??
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
crmcc said:
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
Click to expand...
Click to collapse
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
mrmazak said:
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
Click to expand...
Click to collapse
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
killer13666 said:
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
Click to expand...
Click to collapse
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
mrmazak said:
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
Click to expand...
Click to collapse
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
killer13666 said:
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
Click to expand...
Click to collapse
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
mrmazak said:
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
Click to expand...
Click to collapse
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
Click to expand...
Click to collapse
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
Click to expand...
Click to collapse
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
mrmazak said:
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
Click to expand...
Click to collapse
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
killer13666 said:
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
Click to expand...
Click to collapse
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
mrmazak said:
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
Click to expand...
Click to collapse
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
killer13666 said:
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
Click to expand...
Click to collapse
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
mrmazak said:
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
Click to expand...
Click to collapse
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
killer13666 said:
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
Click to expand...
Click to collapse
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
mrmazak said:
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
Click to expand...
Click to collapse
So in other words, it won't let you flash anything that'll modify the data partition as well?
killer13666 said:
So in other words, it won't let you flash anything that'll modify the data partition as well?
Click to expand...
Click to collapse
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
mrmazak said:
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
Click to expand...
Click to collapse
Please do let me know how that goes.