BLUBOO S1 - Development & Support

[SubwayChamp]

Hi, i just tried to use Substratum but it seems not to be working. It compiles themes fine, but no layers are applied at reboot (even those you say that are working). Substratum has root permissions from Magisk.
Maybe there's something wrong in the root procedure, since i cannot manage to install magisk modules too...
- unlocked bootloader;
- flashed via fastboot cwm no touch recovery;
- rebooted in recovery and flashed magisk-v14.0.zip

Looking in MagiskManager logs i see an error mounting 'loop0' at boot.
Any idea?

Better use this TWRP softly modded https://goo.gl/KiHWPL cause CWM is an older version and like developer said it is not totally adapted to ours device. when you flash this recovery you have basically two methods to flash some zip/mod;
1. Obviously through same recovery using an otg mouse, and
2. Using FlashFire app from PlayStore, this app need a working recovery but you go to flash through same app and it will redirect its own scripts to your recovery rebooting when process finishes.

What Substratum theme you are using? A simple way to verify if themes were install if looking for with a root file explorer in /system/vendor/overlays and you´ll find here an app for every themed app.

 

[Whitesnake386]

Substratum

Better use this TWRP softly modded cause CWM is an older version and like developer said it is not totally adapted to ours device. when you flash this recovery you have basically two methods to flash some zip/mod;
1. Obviously through same recovery using an otg mouse, and
2. Using FlashFire app from PlayStore, this app need a working recovery but you go to flash through same app and it will redirect its own scripts to your recovery rebooting when process finishes.

What Substratum theme you are using? A simple way to verify if themes were install if looking for with a root file explorer in /system/vendor/overlays and you´ll find here an app for every themed app.

I tried different themes, including the ones you mentioned earlier in the thread but no luck.

I'll try with TWRP (maybe it has better support for the device than CWM) and flashfire, as i don't have an adapter for otg mouse.

 

[Whitesnake386]

Better use this TWRP softly modded cause CWM is an older version and like developer said it is not totally adapted to ours device. when you flash this recovery you have basically two methods to flash some zip/mod;
1. Obviously through same recovery using an otg mouse, and
2. Using FlashFire app from PlayStore, this app need a working recovery but you go to flash through same app and it will redirect its own scripts to your recovery rebooting when process finishes.

What Substratum theme you are using? A simple way to verify if themes were install if looking for with a root file explorer in /system/vendor/overlays and you´ll find here an app for every themed app.

No way. Both CWM and TWRP lead to the same results. Magisk modules are flashed/installed without errors but at reboot they're not showing up, and Substratum still not working (same as Magisk, they compile fine but no .apk in /system/vendor/overlay/). Maybe i shall try mounting /system r/w when compiling substratum layers...
Could it be some differences in firmware? I'm running L_V04, the one that came with OTA updates (phone was shipped with L_V02)...
What firmware are you currently running?

 

[SubwayChamp]

No way. Both CWM and TWRP lead to the same results. Magisk modules are flashed/installed without errors but at reboot they're not showing up, and Substratum still not working (same as Magisk, they compile fine but no .apk in /system/vendor/overlay/). Maybe i shall try mounting /system r/w when compiling substratum layers...
Could it be some differences in firmware? I'm running L_V04, the one that came with OTA updates (phone was shipped with L_V02)...
What firmware are you currently running?

I´m on V07 and works too in V01, my device is from the second batch distributed from company and I guess that V02,03 and 04 are the first batch although I don´t think that the issue should be for this reason.
Sometimes we install a system over other and maybe works a clean install. How these recoveries don´t made a good work they leave some trash files with any flashing.
If you try a clean install erasing first system through fastboot and then installing a new maybe you get best results although you can install too V07, if you can´t through SPFlashTool then install system through fastboot.
Also you can try other theming app like "Layers manager" based on RRO layers from Sony that do a similar job like Substratum.

 

[Whitesnake386]

I´m on V07 and works too in V01, my device is from the second batch distributed from company and I guess that V02,03 and 04 are the first batch although I don´t think that the issue should be for this reason.
Sometimes we install a system over other and maybe works a clean install. How these recoveries don´t made a good work they leave some trash files with any flashing.
If you try a clean install erasing first system through fastboot and then installing a new maybe you get best results although you can install too V07, if you can´t through SPFlashTool then install system through fastboot.
Also you can try other theming app like "Layers manager" based on RRO layers from Sony that do a similar job like Substratum.

From what i know V01, V06, V07, V10 are from the first batch where sensors were fake or not working (then patched to mimic their functionality), L_V02, L_V03, L_V04 are from the second batch with real sensors. But i may be wrong.

I think mine is from second batch, cause light and proximity sensors were working right out of the box. I think your's from first batch... Is adaptive brightness working on your device?

Btw, i even tried reflashing a clean system through SPFlashTool but no way, Magisk v14 installs fine and grants root permissions, but no modules can be installed nor preferences are stored. I guess this is because /data/magisk.img cannot be mounted at boot (error in log is 'mount /dev/block/loop0 -> /magisk failed with 13: permission denied').
I didn't try with a different firmware version other than L_V04 though. I'll try V07 too, just in case...

Xposed is the only thing i can make work perfectly.

Today i even tried Magisk-v15.0, it gets stuck on Orange State screen and adb logcat tells me there's no 'sh' binary :silly::silly::silly:
I'll make some experiments in the next days

 

[lyhoangthai1993]

From what i know V01, V06, V07, V10 are from the first batch where sensors were fake or not working (then patched to mimic their functionality), L_V02, L_V03, L_V04 are from the second batch with real sensors. But i may be wrong.

I think mine is from second batch, cause light and proximity sensors were working right out of the box. I think your's from first batch... Is adaptive brightness working on your device?

Btw, i even tried reflashing a clean system through SPFlashTool but no way, Magisk v14 installs fine and grants root permissions, but no modules can be installed nor preferences are stored. I guess this is because /data/magisk.img cannot be mounted at boot (error in log is 'mount /dev/block/loop0 -> /magisk failed with 13: permission denied').
I didn't try with a different firmware version other than L_V04 though. I'll try V07 too, just in case...

Xposed is the only thing i can make work perfectly.

Today i even tried Magisk-v15.0, it gets stuck on Orange State screen and adb logcat tells me there's no 'sh' binary :silly::silly::silly:
I'll make some experiments in the next days

Did you try to install on v01? I'm in v10 but I use x-plore to delete the system is not. The v01 is erased, can even do everything. Did you try on v01?

 

[SubwayChamp]

From what i know V01, V06, V07, V10 are from the first batch where sensors were fake or not working (then patched to mimic their functionality), L_V02, L_V03, L_V04 are from the second batch with real sensors. But i may be wrong.

I think mine is from second batch, cause light and proximity sensors were working right out of the box. I think your's from first batch... Is adaptive brightness working on your device?

Btw, i even tried reflashing a clean system through SPFlashTool but no way, Magisk v14 installs fine and grants root permissions, but no modules can be installed nor preferences are stored. I guess this is because /data/magisk.img cannot be mounted at boot (error in log is 'mount /dev/block/loop0 -> /magisk failed with 13: permission denied').
I didn't try with a different firmware version other than L_V04 though. I'll try V07 too, just in case...

Xposed is the only thing i can make work perfectly.

Today i even tried Magisk-v15.0, it gets stuck on Orange State screen and adb logcat tells me there's no 'sh' binary :silly::silly::silly:
I'll make some experiments in the next days

I read some place about that sensors are fake or not working properly in some versions but if the physical sensors modules are present can be solved.

In Aliexpress Sellers from China first root and then reinstall firmware in all devices before sending to proof all details (maybe they don´t made a good job and it´s difficult for final users know if the version that device brings is the correct or not). I noted that in my device works proximity sensor although not properly to screen on again in a call and sensor lights I guess not, I didn.t find correct thread in chinese to solve this.

You can install system.img from any of the versions through fastboot, obviously with SPFlashTool doesn´t accept this but fastboot has only a size image limitation and I guess that this device supports at least 2,8 gb in system partition.

Correct way to do the clean flashing process for me is:
- First going to recovery and doing a complete wipe/format data except ext-sd if you have one (maybe need delete in your sdcard manually all the files related with the rom cause at first boot devices takes some data apps of your old rom)
- Then going to fastboot and perform "fastboot erase system" then "fastboot erase boot"
- Then install system image and boot patched with Magisk (important)
- Install TWRP through fastboot (I trust more in fastboot for performing some installation when the file it´s not a stock created for device)
- Do a first boot
- Install Magisk (going to recovery through adb)
- Then install Xposed/substratum/layers.

Also maybe your rom is odexed that sometimes refuses to be modified/themed cause framework restrictions and v07 is not odexed.

 

[sonhiep]

Did you try to install on v01? I'm in v10 but I use x-plore to delete the system is not. The v01 is erased, can even do everything. Did you try on v01?

Hi, you can download nvram.img of rom V10 (for vietnam) at here:
https://drive.google.com/open?id=1HZJVw_QyE-jqFS64x2MTBdxWuwNZRCkN

 

[lyhoangthai1993]

Hi, you can download nvram.img of rom V10 (for vietnam) at here:
https://drive.google.com/open?id=1HZJVw_QyE-jqFS64x2MTBdxWuwNZRCkN

Help. I can not downkoad

 

[sonhiep]

Help. I can not downkoad

Sorry, now you can download it.

 

[sonhiep]

Hi mod.
Please help me update live wallpaper and face lock for Bluboo s1.
Thank!

 

[jemmini]

TWRP 3.2.1 for BLUBOO S1

TWRP 3.2.1 for BLUBOO S1

Based on Android 7.0 firmware ver.BLUBOO_S1_Helio_P25_L_V04_20170908 / 2017年 09月 11日 星期一 15:57:08 CST

WARNING!! Strictly follow these installation instruction!

Install:
1. Enter to fastboot mode, Unlock bootloader using "fastboot oem unlock" command
2. Reboot to the system
3. Enter to fastboot mode again, and flashing TWRP using "fastboot flash recovery recovery.img" command
4. Enter into TWRP and Install the "Magisk-v15.1.zip" path
5. Reboot to the system
6. Install the MagiskManager-v5.5.2.apk

 

[SubwayChamp]

TWRP 3.2.1 for BLUBOO S1

Based on Android 7.0 firmware ver.BLUBOO_S1_Helio_P25_L_V04_20170908 / 2017年 09月 11日 星期一 15:57:08 CST

WARNING!! Strictly follow these installation instruction!

Install:
1. Enter to fastboot mode, Unlock bootloader using "fastboot oem unlock" command
2. Reboot to the system
3. Enter to fastboot mode again, and flashing TWRP using "fastboot flash recovery recovery.img" command
4. Enter into TWRP and Install the "Magisk-v15.1.zip" path
5. Reboot to the system
6. Install the MagiskManager-v5.5.2.apk

Thanks for the tool, at last a touch recovery. Just if it´s possible provide a link to know how you get touch; I found a lot of devices with mediatek that has same issue. I´m in v07 and works perfectly.

 

[tnsantos]

Hi, I had twrp installed on my bluboo s1 and tried to do a format data factory reset from recovery, nothing did happended. Than I went to configuration and did a factory reset from android. The phone restarted and only boots into recovery. How can i fix this? Please help.

 

[jemmini]

Hi, I had twrp installed on my bluboo s1 and tried to do a format data factory reset from recovery, nothing did happended. Than I went to configuration and did a factory reset from android. The phone restarted and only boots into recovery. How can i fix this? Please help.

flash original recovery.

 

[tnsantos]

flash original recovery.

Hi, thank for your help. Do you know where I can find it? Do you think that I need to flash stock rom or only flash original recovery?

Edit 1: It jumps right to CWM. Even if I boot the phone with vol + and power. @_@

 

[jemmini]

Hi, thank for your help. Do you know where I can find it?

recovery :

 

[tnsantos]

recovery :

Hey thanks again. I downloaded the file you attached and boot the phone into CWM, next went to power menu and selected reboot to recovery. The phone is now in FASTBOOT mode... only this text is showing at the bottom of the screen.

Next I started SP Flash Tool by doing sudo ./flash_tool, selected the scatter file you also sent, selected download only and click Download at SP Flash Tool.

Next I plugged the phone into the USB, SP Flash Tool console output looks like:

Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 36000000 ms
add@/devices/pci0000:00/0000:00:12.0/usb4/4-5
add@/devices/pci0000:00/0000:00:12.0/usb4/4-5:1.0

nothing is really happening.

Edit1:
after a few minutes:
Timeout for searching USB port.

What am I doing wrong? @_@


Edit 2:
I'm trying now by 'fastboot flash recovery', the console looks 'sending 'recovery' (11790 KB)... and nothing else, the bluboo s1 screen looks like: 'USB Transfering...' and everything is stopped.

Edit 3:
OMG I'm so dumb I'm sorry.
fastboot flash recovery ./recovery-verified.img did the trick. I'm now waiting for the device to get out of the bluboo boot screen. It played the boot animation and is stuck at boot image. Maybe bootloop?

Edit 4:
YAYYYYYY it booted! OMG! I thought I've lost my phone.

 

[unkash]

TWRP 3.2.1 for BLUBOO S1

Based on Android 7.0 firmware ver.BLUBOO_S1_Helio_P25_L_V04_20170908 / 2017年 09月 11日 星期一 15:57:08 CST

WARNING!! Strictly follow these installation instruction!

Install:
1. Enter to fastboot mode, Unlock bootloader using "fastboot oem unlock" command
2. Reboot to the system
3. Enter to fastboot mode again, and flashing TWRP using "fastboot flash recovery recovery.img" command
4. Enter into TWRP and Install the "Magisk-v15.1.zip" path
5. Reboot to the system
6. Install the MagiskManager-v5.5.2.apk

Thanks for the tool, at last a touch recovery. Just if it´s possible provide a link to know how you get touch; I found a lot of devices with mediatek that has same issue. I´m in v07 and works perfectly.

In this twrp works fine touch?

Is twrp better than cwm?

I'm using cwm, can i flah twrp directly over cwm? Or i need flash stock recovery first ??
Thx

 

[SubwayChamp]

In this twrp works fine touch?

Is twrp better than cwm?

I'm using cwm, can i flah twrp directly over cwm? Or i need flash stock recovery first ??
Thx

Yes, in general TWRP is better than CWM thas is officialy abandoned from years ago although most of the new roms use scripts based on TWRP.
Touch in this works fine.
You can flash it over CWM directly.