Latest video: https://youtu.be/o6cpMa2Fo_c
Since 01.16 update Gigaset Me and Me pro use same ROM. So read carefully and take responsibility what you are doing on you device.
Gigaset Pure is not supported here.
GPL Source codes:
Me/MePro/ platform tools full : http://www.gigaset.com/de_de/cms/lp/open-source.html
Me/MePro platform tools uploaded in 1 file (gdrive): https://drive.google.com/uc?id=0B_81lkQEKce4bFlaRXk3dFFwQzA&export=download
Me/MePro kernel source (my repo on github): https://github.com/Eddie07/GIgaset_Me_MePro_3.10._kernel
Terms of Usage:
1. Everything posted on this post should be reposted with links to original post.
2. I'm not responsible for any damage to your phone.
3. If you are aware of bricking device by this or you don't understand some of processes described below - close this thread and leave it alone.
4. If you agree with p.1,2,3 go on to Step2.
GIGASET secret codes:
*#*#4636#*#* - phone info
*#*#2580#*#* -engineer mode (wif, bt tests, usb ports, adb root (pass:gigaset001), ota settings.
*#*#708#*#* - float system info (cpu speeds, m|b temp), shake test.
*#*#801#*#* - wifi test.
*#*#802#*#* - bt test.
*#*#803#*#* - bt test 2.
*#*#2588#*#* - factory hardware tests.
*#*#2581#*#* - Camera callibration??.
(Only ME/MEPRO)TWRP CUSTOM RECOVERY, UNBRICKING:
-FLASH CUSTOM RECOVERY ON ME/MEPRO HERE
-UNBRICK SOLUTION back to rom EU00_V1.1.20160616R ME/MEPRO (if you deleted system, recovery, boot) : BACKUPS--- UNBRICKING
(Only ME/MEPRO)CUSTOM ROMS:
LAST CM 12.1
(Only ME/MEPRO)PATCHES TO STOCK ROM TO BE INSTALLED VIA CUSTOM RECOVERY:
LAST MY "TUNED" TWRP BACKUP https://forum.xda-developers.com/showpost.php?p=71180342&postcount=371
-PATCH#1 TWRP PATCH ME/MEPRO for CPU speeds uncap (1,9ghz), Thermal config fix, Fix of display size MePro HERE
-PATCH#2 Enable 4K video recording in stock camera app HERE
-PATCH#3 Enable Callrecording button in stock dialer app HERE
-PATCH#4 READ DESCRIPTION HERE
-PATCH#5 SystemUI patch HERE
ADB ROOT FOR STOCK ROM WITHOUT ROOT AND CUSTOM RECOVERY:
- Unlocking Me/Pro abd root via factory tool hidden in rom. (usage for Gigaset Me/Pro/Pure)
1) Type in dialer: *#*#2580#*#* to get in Engin. tool
2) Select "priviledge" tab.
3) Type "gigaset001" in pw field.
Get adb root
to check if is done enable USB debugging and try adb command from PC:
"abd shell" if command prompt ends with "#" then adb is rooted, if "$"-isn't!
4) Turn off adb root- type password again.
Thank friend
GaulCrixus said:
Thank friend
Click to expand...
Click to collapse
You are able to install Supersu via abd (you can find manuals on internet).
But if you copy wrong files, or even update binary on purpose in SuperSU gui, you are risking to get bootloop or stuck on ANdroid logo.
There is no way to recover (YET). But im on my way to test something.
So you are warned!
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
I emailed Gigaset support and asked about the Marshmallow update and they said its not ready yet but would be at some point, I have read on German forums that no one replies when asked about updates.
Getting CM or PacROM for this would be great.
imkrl said:
Having Gigaset ME with newest update:
"Engineering tool" could be open with *#*#2580#*#* , but pw is not accepted.
Do you have another Password ?
Click to expand...
Click to collapse
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
heineken78 said:
Moded boot.img for Me/Me pro with enabling of 1,9 ghz cpu speed.
tweaked thermal engine for Me/Me pro .
Seems like me/me pro have same firmware.
modified boot image (ver. EU00_v1.1..20160616R) https://drive.google.com/open?id=0B3Wy4Ok3qGszdXdPSjRvOGVfTlE
thermal engine modded (any version) https://drive.google.com/open?id=0B3Wy4Ok3qGszX2hRQ3ZhazBQQWM this paste to system/etc folder and overwrite.
Click to expand...
Click to collapse
I cant expand the images in your post.
typos1 said:
I have a Gigaset Me. When I type the password nothing happens on the phone, but a new window opens on my pc.
Click to expand...
Click to collapse
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
# #ifdef GIGASET_EDIT
# /*[email protected], 2015/08/20. added. add root mode for release build */
#ifeq ($(TARGET_BUILD_VARIANT),user)
persist.sys.root.enable=none
# /* [email protected], 2015/10/29. added. add feature to reserve pictures when doing 'Factory data reset'.*/
sys.root.wipedataless=false
#endif
# #endif /*GIGASET_EDIT*/
Click to expand...
Click to collapse
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
heineken78 said:
Right. Its switches off/on root enabler for adb. Check adb shell command on pc if its ended by"$" is non rooted, by "#" you have adb root. (check video)
here is the part of build.prop regarding this eng menu:
So basically this password changes value of persist.sys.root.enable.
By reading of German forums I figured out that Gigaset Me support ended this summer.
If you succeed with adb rooting, I need you to dump for me boot and recovery partitions, to be sure if they are same for Me Pro.
how to dump in adb shell:dd if=dev/block/platform/f9824900.sdhci/by-name/recovery of=sdcard/recovery_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/boot of=sdcard/boot_original_me.img
dd if=dev/block/platform/f9824900.sdhci/by-name/devinfo of=sdcard/devinfo_default_me.img - to check if your device bootloader is unlocked.
dd if=dev/block/platform/f9824900.sdhci/by-name/system of=sdcard/system_me.img - to backup whole system partition.
system, boot, recovery is all can be changed, needs to return to original factory state as new phone in case of warranty case.
Click to expand...
Click to collapse
Yes, I realise that, I do get a #, I was just pointing out to @imkrl that nothing appears to happen on the phone from looking at the screen, but something does actually happen
After removing from adb and installing SuperSU, SuperSU says its not rooted.
I ll do the dump and upload later.
On the German forums people say that no one from Gigaset replies to messages and that support has been dropped, but that is not official, it is just people's assumptions, when I contacted Gigaset I DID get a reply saying "it will happen automatically", not "we have dropped support", so maybe support has been dropped, maybe not, nothing has been officially said by Gigaset.
But dropped or not getting support for custom ROM like CM of PACrom would be good.
typos1 said:
After removing from adb and installing SuperSU, SuperSU says its not rooted.
Click to expand...
Click to collapse
Right, root is only for adb. But advanced users could push some files in device via adb root# and get supersu working too.
But its quite risky, if you made a mistake, then device can no boot to android anymore (ex. bootloop). Then is bricked.
-You cant access partitions from fastboot - is completely factory locked. (even :"fastboot reboot" doesn't work. fastboot don't listen to any command)
-factory recovery not allows to use adb or view files.
Everything points to have custom recovery.
Another thing if you got su working by pushing files, some system files became modified by supersu and with next OTA update, by security check, OTA will fail to update (patch). So you need system partition backup to restore it on demand.
There is one way to hard unbrick to use "edl" mode (QUALCOMM 9008) (switched phone, hold vol-down, connect usb). I have idea how to but I didn't test, cos I don't want to take a risk to erase memory of my working phone.
To avoid all risks, have to flash custom recovery TWRP from android, within you will be able to restore everything and install supersu normal way. What ever you change from recovery: flashing zip's, installing backups or getting bootloops after, you will be able to load custom recovery again and fix from it. Before installing of custom recovery, backing up of recovery, boot and system partitions should be done, also have to check devinfo partition of your device to be insured that bootloader is unlocked, because if bootloader is locked it will ignore not signed recovery or any boot images.
Yes this is all backdoor and hard to do if you are rokkie in this, but 100% working methode. There is no any Kingaroot or other working roots for Gigaset, cos android security of Gigaset is very high, even with 5.1.1 version.
Why I need your files, typos1: recovery, boot and devinfo. To check them if they are same with Me pro, if not to make another custom recovery for me device.
Sure I will try to make rom ports, may be someone else will do it, cos root is found by me after on second day of device usage, while device was one year on market and lost interest of many. Btw custom recovery source was taken from OnePlus2, hardware +- is similar.
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
xueyaotianxia said:
step 2 cannot find devinfo.img
when backup files takes forever
step 4 when installing recovery takes forever and adb not responding
what should i do
Click to expand...
Click to collapse
Device?
reply
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
Mine came from China (they ALL do, thats where theyre made !!) and mine does have the Playstore.
xueyaotianxia said:
device is Gigaset Me (GS55-6).....I bought it from China, so it doesn't come with google play store. I wanted to root it in order to use play store...any ideas if I can root it? i tried a lot of root software (kingroot, kingoroot, iroot etc..), no luck.
Click to expand...
Click to collapse
No way to root yet with common ways. Only via adb shell or via recovery.
But Me and Me Pro have same platform, so take a look what you have at ls dev/block/platform/f9824900.sdhci/by-name/. Use this command in adb shell and write me the list of partitions.
If you get error, Gigaset Me may have different storage name (not f9824900.sdhci as me Pro I own). so try ls dev/block/platform/ and find right name of storage, then ls dev/block/platform/STORAGENAME/by-name/ shows list of partitions.
Guys I need partitions of Me!
After I typed ls dev/block/platform, it shows this:
f9824900.sdhci
f98a4900.sdhci
what should I do now?
Thank you..
---------- Post added at 09:25 PM ---------- Previous post was at 09:22 PM ----------
I would guess your device is made for oversea's market...so that is why it has playstore pre installed...I bought mine in China (which made for Chinese market, by law no google)...it makes life so much more difficult, as I have to install 3rd party app store...cannot root the phone now so whenever I open play store it shuts down immediately.
---------- Post added at 09:39 PM ---------- Previous post was at 09:25 PM ----------
After I typed this ls dev/block/platform/f9824900.sdhci/by-name, it shows:
DDR
aboot
abootbak
apdp
bluetooth
boot
cache
config
devinfo
dpo
fsc
fsg
hyp
hypbak
keystore
limits
misc
modem
modemst1
modemst2
msadp
persist
pmic
pmicbak
recovery
rpm
rpmbak
sbl1
sbl1bak
sdi
sec
splash
ssd
system
tz
tzbak
userdata
that is all.
I went back tried step 2 again, it shows 01. But when I tried step 4 to do the recovery it says:
aset-me.img of=dev/block/platform/f9824900.sdhci/by-name/recovery <
0 records in
0 records out
24 bytes transferred in 2.347 secs <10504398 bytes/sec>
recovery seems still the old factory one.
---------- Post added at 09:51 PM ---------- Previous post was at 09:39 PM ----------
Hahaha I tried step 4 again it worked!! Now I am in Team win recovery project v2.8.7.0
What should I do now to root the phone??
Thank you very very much you saved the day!!!
xueyaotianxia said:
Thank you very very much you saved the day!!!
Click to expand...
Click to collapse
Download and install supersu.zip
Notice, you have to disable engineering menu root (type password again), because factory adb root and another (supersu) will have conflicts.
So confirmed that this recovery works on Gigaset Me too!
thank you
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
xueyaotianxia said:
thank you thank you thank you...i have disabled the engineering mode. awesome man!
I installed gapps zip from recovery instead of rooting, play store works 100%. but it seems some other old system apps stopped working, all became that android robot icon like camera and sms etc, I download google cameras and google message etc as alternatives, they work fine.
just would like to ask, if i wipe the data and cache from recovery, will all the older system apps work again? and is it possible to install a custom rom? any ideas??
Click to expand...
Click to collapse
You have messed up. Suggest to restore system.img or if you done system backup in twrp and try root again.
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
xueyaotianxia said:
Have I messed up...
I did backup the systembackup.img
when I am in the recovery to flash it, it let me choose either boot or recovery, which one should I choose?
is it possible to find an EU gigaset me Rom? or to install other roms?
Click to expand...
Click to collapse
You should do backwards procedure to restore system image. Better if you do it while in TWRP recovery.
1) Open TWRP recovery and connect to PC
2) In adb shell on pc: dd if=sdcard/systembackup.img dd of=dev/block/platform/f9824900.sdhci/by-name/system
Where systembackup.img name of backup image you done stored on internal memory. This will overwrite system partition to previous state.
For next time I suggest you to make backup in TWRP normal way. It will be faster.
Related
WARNING: Performing the actions decribed here will void your warranty and possibly brick your device. This was not written for complete noobs and assumes some prior experience. I will not be held responsible if you ruin your device.
NOTE: This was all tested on a stock iWork 10 Flagship dual boot (aka iWork 10 Ultimate) purchased from the manufacturers website. Device model is "i15 T", Device serial number starts with "i15TD": if you have another variant such as i15TL i can not vouch for any of this working the same way.is tablet
UPDATE: @popcorn2404 modified the boot.img on his USB Type-C variant if this tablet (i15-TCL), confirmed everything working well and was nice enough to provide the modified boot image. See downloads at end of post.
OTA: Most likely this will break OTA. Dont know yet...
Prerequisites:
PC with working ADB/Fastboot
Device properly recognized.
I'm using ubuntu 15.10 so I just added an entry to /etc/udev/rules.d/51-android.rules to get things going properly
(EDIT: Windows 64 bit usb drivers attached to post -thanks @Jade.J.Munkey)
TIP: I would highly recommend extracting your stock recovery, boot and system images for safekeeping. These can easily be flashed back in fastboot if something goes wrong. Some may say this is overkill as you will be able to backup and recover with TWRP, but one never knows...
Unlocking bootloader
WARNING: this will erase all data, settings, etc... AND system default language will be chinese when you reboot
Go to settings, about tablet and tap 5 times on the Build number to activate developer options
Go to Developer options and enable OEM unlocking & USB debugging
Plug in your device while booted into android, then open a terminal
just to make sure adb is good type
Code:
adb devices
my output looks like this
Code:
List of devices attached
0123456789ABCDEF device
reboot tablet into fastboot mode
Code:
adb reboot fastboot
The device will now reboot to the OS selection screen. Select android and then it will boot into fastboot mode
once again just to be sure all is good type
Code:
fastboot devices
once again, my output
Code:
0123456789ABCDEF fastboot
then to unlock the bootloader
Code:
fastboot oem unlock
you then should see something like:
Code:
...
(bootloader) Unlock protection is set
(bootloader) Unlocking anyway since this is not a User build
OKAY [ 15.330s]
finished. total time: 15.330s
This is what you should see now in the bootloader if all went well:
SECURE BOOT - DISABLED
LOCK STATE - unlocked
Your bootloader in now unlocked. When you reboot it will take some time for the first boot and the system language will have defaulted back to chinese. Not too difficult to sort if you're familar with Android settings. Otherwise just google "android change system language from chinese to english".
Tip: At this point you may want to already download/copy the supersu zip to internal storage of the tablet so you're all set up for flashing it later...
Modified boot.img
Because of built in security, if you make any changes to system the device will not boot, so you need a modified boot image.
If you have the exact same kernel version as I do you can download the provided modified boot image here. Otherwise you can look HERE for instructions on how to make your own modified boot image. Personally I used SuperR's Kitchen to unpack & repack the image and did the modifications manually with gedit.
Kernel version 3.14.37-x86_64-L1-R429 made on Wed Mar 2 18:22:46 CST 2016
-if you have that one you are good to go ahead and use the image provided here.
Boot device into fastboot connected to PC. From the directory where you have the modified boot image type:
Code:
fastboot flash boot i15TDboot.img
Obviously if you made your own boot image you'll need to replace "i15TDboot.img" with the name of yours...
That's it, now on to recovery and rooting...
Flashing custom TWRP (compiled by @vampirefo)
Assuming you are still connected to the device in fastboot and the custom recovery is in the same directory:
Code:
fastboot flash recovery i15t_recovery.img
Now use volume buttons to select recovery mode and tap power button.
You should now be in TWRP. First, please be smart and make a backup!
Because this device has an unusual mount point, the supersu script will fail to properly mount system (thus failing to flash) so:
From TWRP main screen select "mount" then select system, then return to main screen
Select "install" and then the supersu zip you should already have on the tablet.
Boot system. Now there is one thing left to do:
To prevent the system from overwriting TWRP with the stock recovery on the next reboot:
With a root enabled file manager mount system r/w and navigate to /system/etc
Rename install-recovery.sh to install-recovery.sh.bak
That's it. Enjoy!
If you're looking for more info on this device, check out Laura's great thread
Thanks
@vampirefo - for taking the time to compile TWRP for this device, you rule man!
Laura - for all the info she's made available for this device
@SuperR. - for his kitchen
@Chainfire
@popcorn2404
Downloads
TWRP recovery
Modified boot image (i15-TD)
Modified boot image (i15-TCL)
SuperSU
There will be additional resources for this device here
Delete
Windows 10 64bit fastboot driver for Cube iwork10 Ultimate
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?
Cube iwork10 Ultimate Fastboot driver for Windows 10 64bit
Jade.J.Munkey said:
When the device is at fastboot, Windows Device Manager says "Cherry Trail CR" with a yellow exlamation point. abd works fine when it is booted in to normal android. Anyone have this driver or could tell me where to aquire it ?
Click to expand...
Click to collapse
Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.
Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:
onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNIfrlvxfvI&ithint=file%2czip
if anyone needs it. (remove space from url before pasting in to browser)
Jade.J.Munkey said:
Thanks very much for the good work, I am successfully rooted. The only deviation from the instructions that occurred for me was that /system/etc did not appear in the TWRP file manager, fortunately the .sh did not run upon rebooting after installing the SU zip. So I just I just renamed the .sh in NextApp File Explorer with Root Add-On installed once booted in to android; I have since tested booting in to recovery and then back to android and it is working fine.
Here is the driver I found to enable the Cube iwork10 Ultimate to be seen by Windows 10 64bit whilst in fastboot:
onedrive.live.com/redir?resid=96BA73741E4680ED!5237&authkey=!ALGigNIfrlvxfvI&ithint=file%2czip
if anyone needs it. (remove space from url before pasting in to browser)
Click to expand...
Click to collapse
Glad it worked out for you. Based on your experience I changed the instructions in the OP. Actually that's the exact same I did after doing this the first time but I thought it would be easier to do before first boot in TWRP. Anyhow thanks for pointing this out.
Attached windows usb driver to OP. Thanks!
Stock based, recovery flashable ROMs now available:
http://forum.xda-developers.com/android/development/rom-stock-cube-iwork-10-flagship-i15-t-t3372281
Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.
Will the recovery work with i15-TL?
Thank you in advance
flubber1911 said:
Will the recovery work with i15-TL?
Thank you in advance
Click to expand...
Click to collapse
From what I understand from reading at http://techtablets.com/forum/forums/cube/iwork-10-ultimate/
-it *should* work as my understanding is that the TD and TL are virtually identical other than different flavors of windows installed. But I can NOT personally confirm this as I have not tested on the TL variant.
What I can say with a higher level of certainty is that the procedure for unlocking the bootloader should be exactly the same. Once the bootloader is unlocked it is easy to reflash the stock recovery via fastboot should the custom recovery not work properly. (Assuming one has previously extracted an image of the original recovery to begin with. Same for boot and system images.)
So if the custom recovery does not work, it is pretty easy to reflash the original, as well as the original boot or system images should something else get messed up.
Hope this helps. Feel free to ask anything else if anything is unclear...
Sent from my OnePlus2 using XDA Labs
Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.
geryalvi said:
Can someone please make like a video for this or something more lames terms (user friendly). Cause i have a cube iwork 10 Ultimate Dual Boot (i15-TL) and am having issues on Android side where i do not have an option to move apps to sd card in apps settings. Also in storage there is no tab showing all apps on sd card. Im guessing i would need to root my device right? Can someone please help me i just want to get this working properly... i would show screenshots but i don't know how to attach them.
Click to expand...
Click to collapse
The stock android on this device does not offer the option to move apps to sdcard.
Tools such as link2sd require a rooted device.
Sent from my OnePlus2 using XDA Labs
flubber1911 said:
Thank you for your precise answer. I already successfully rooted my Cube. I need the recovery to flash the latest xposed sdk. I' ll have a look if someone extracted the original recovery.
Click to expand...
Click to collapse
Yeah, no problem man. I'm curious to see how xposed works out, I've not got around to trying to install yet. Let us know here how that goes.
A copy of the original recovery from my i15-T(D) can be downloaded here: https://www.androidfilehost.com/?fid=24499762636003042
Sent from my OnePlus2 using XDA Labs
I installed an app called Rashr - Flash Tool on my phone. It says it can backup the recovery.
So I did; lets see then if your custom recovery works out
jetfin said:
The stock android on this device does not offer the option to move apps to sdcard.
Tools such as link2sd require a rooted device.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Ok so i have i15-TL, with the instructions provided will i be able to root my Android? Also if i Root Android does anything happen with the Winows side? (I still would like a Dual Boot) So im looking to be able to move apps to my sd card, can someone please help me understand how to Root my device and be able to move apps to sd card? Any help would be greatly appreciated, and also thanks to Jetfin for replying my last post. Plz hlp...
geryalvi said:
Ok so i have i15-TL, with the instructions provided will i be able to root my Android?.
Click to expand...
Click to collapse
As clearly stated in the OP, I do not know for sure because I have not tried on that variant, but it *should* work. If you read a few posts back, you can see that another TL owner seems to have successfully rooted his device. Hot tip: *reading* is very important here before asking questions.
geryalvi said:
Also if i Root Android does anything happen with the Winows side? (I still would like a Dual Boot)
Click to expand...
Click to collapse
No, this will not affect the windows side of things. Dual boot is unaffected.
geryalvi said:
So im looking to be able to move apps to my sd card, can someone please help me understand how to Root my device and be able to move apps to sd card?
Click to expand...
Click to collapse
The instructions for unlocking and rooting in the OP are very simple and straightforward. If you are inexperienced in general with rooting android or with adb/fastboot, those answers can easily be found on XDA and elsewhere by searching.
As far as moving apps to SD, since nobody seems to have done it yet (or posted that they have) the only way right now would be to root your device and try out one of the specific apps for that like link2sd. I will try to check this out ASAP but can not promise how soon because I'm focusing my efforts right now on porting another ROM to this device...
Sent from my OnePlus2 using XDA Labs
I could cry right now ... At first I have to say that flashing the TWRP recovery worked flawlessly But always when I tried to flash the Xposed SDK I got an error saying: Updater process ended with error: 255 ( I have no idea how to fix that yet
flubber1911 said:
I could cry right now ... At first I have to say that flashing the TWRP recovery worked flawlessly But always when I tried to flash the Xposed SDK I got an error saying: Updater process ended with error: 255 ( I have no idea how to fix that yet
Click to expand...
Click to collapse
Did you manually Mount system in TWRP before flashing xposed?
Sent from my OnePlus2 using XDA Labs
jetfin said:
Did you manually Mount system in TWRP before flashing xposed?
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
No, do I have to do that? D
---------- Post added at 10:55 PM ---------- Previous post was at 10:51 PM ----------
Ok I manually mounted System, but it still doesn´t work ...
jetfin said:
As clearly stated in the OP, I do not know for sure because I have not tried on that variant, but it *should* work. If you read a few posts back, you can see that another TL owner seems to have successfully rooted his device. Hot tip: *reading* is very important here before asking questions.
No, this will not affect the windows side of things. Dual boot is unaffected.
The instructions for unlocking and rooting in the OP are very simple and straightforward. If you are inexperienced in general with rooting android or with adb/fastboot, those answers can easily be found on XDA and elsewhere by searching.
As far as moving apps to SD, since nobody seems to have done it yet (or posted that they have) the only way right now would be to root your device and try out one of the specific apps for that like link2sd. I will try to check this out ASAP but can not promise how soon because I'm focusing my efforts right now on porting another ROM to this device...
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply, so my question before i attempt to root my device is: if i follow the steps provided on OP will i loose any of my current information on my Android side? If so would i need to backup my android (How so). Sorry for all of hte questions but i am a noob on how to do this..
Thanks again
Hello Friends
A little background first !!
QiKU Q Terra (CP8692_I02) which was sold in India and came pre-installed with 360 OS v21, Android 5.1. The OEM went back to China hence there haven not been any software update for our device. I had been trying to boot latest Chinese 360 OS on Indian Qiku Terra to get updates but after flashing the Chinese version the device would not boot at all and would get stuck in fastboot mode. To revive the device, I had to flash back the V21, I had tried several times but no success.
I even got in touch with the 360 OS engineers over mail with the help of an administrator of Qiku Chinese forum but the engineers said it's not possible to flash Chinese 360 OS on Indian Qiku Q Terra.
I had also been trying to root QiKU and I was able to figure it out all recently.
Check out my post -- https://forum.xda-developers.com/an...i02-unlock-t3493636/post69455878#post69455878
This tutorial is also useful for users of CP8692_M02 who had flashed the v21 on their devices and now are not able to go back to CP8692_M02.
Warning !! Try this own your on risk although it's very safe if you follow the instructions without missing any steps. Don't blame me if you still manage to kill your phone and loose your job :laugh::laugh:
Let's begin !!
Just ensure your device bootloader is unlock before you follow the instructions as it's required to boot 360 Chinese OS on the Indian QiKU.
Download the latest firmware and flash the same with YGDP or Qiku Download Assistant tool. When finished, the device won't boot and still be in fastboot mode. Now boot TWRP recovery from your pc, go to the folder where you have the TWRP recovery and press shift and right click and select "open command window here" and type the following
fastboot -i 0x1ebf boot (recovery name).img
This should boot TWRP on your device.
You can also flash TWRP recovery if wish to,
fastboot -i 0x1ebf flash recovery (recovery name).img
Now boot TWRP
fastboot -i 0x1ebf boot (recovery name).img
When in recovery mode you can use cmd to extract params partition which contain your device model name. Open cmd on your pc and type the following command
dd if=/dev/block/mmcblk0p30 of=/sdcard/params.bak
Once done, you'll have a file name params.bak on your phone's internal memory, copy the same to your pc. Download NotePad++ and install it, link - https://notepad-plus-plus.org/
Only use NotePad++ to edit the params, don't use NotePad. Plus make a copy of your params.bak file and keep it somewhere safe in case you mess up with original params file.
Right click on params.bak and open it with NotePad++, now search CP8692. The device model name would be CP8692_I02 just change I to M and save the changes, now it should be CP8692_M02.
The system partition size is not enough to flash Gapps hence you need to use TWRP recovery resize option.
In TWRP recovery and select > Wipe > Advance Wipe > System > click FS Option > click Resize FS now you shall have more free space in system partition
In TWRP now click reboot then click bootloader, in bootloader press volume up for fastboot mode. On pc open cmd in the folder where you have params.bak saved and type the following command:-
fastboot -i 0x1ebf erase params
fastboot -i 0x1ebf flash params params.bak
fastboot -i 0x1ebf reboot
If everything went well your device should boot Chinese 360 OS, Android 6.0.1 normally.
Now flash modified Gapps in TWRP which you have downloaded. The modified Gapps has Gmail & Hangout beside core apps and rest you can download from play store later.
If you flash bigger Gapps, the device will not boot or it shall be in bootloops coz of Gapps size and if you don't flash Gmail and Hangouts with the modified Gapps and download the same from Play store then it would give you connection trouble.
In case you wish to root then flash SuperSU.zip in TWRP.
Back to the booted device:-
To Activate VoLTE, download QuickShortcutMaker app from play store. Open the app and locate MBN test > click on the dropdown menu > click Try > Tick Volte_OpenMkt-Commercial-CMCC > and last click Activate.
Close the app and go to phone setting > Call settings > and enble VoLTE and you're done. You should see HD sign in the status bar of your phone. Now you can enjoy VoLTE calls.
Download the latest 360OS 2.0 V18 stable version: http://pan.baidu.com/s/1slCmsKP password: i65r
Follow the tutorial to download from Baidu without log-in and download client - https://www.youtube.com/watch?v=cigJh9jg4-c
Download modified Gapps and supersu.zip - https://drive.google.com/drive/folde...ElFemQwTTFXcTQ
Credits:
Goes to me @Zauq for figuring out unlocking bootloader, rooting, modifying TWRP for cp8692_I02 etc. Without the unlocked bootloader the above was not possible.
Goes to @cuongvietnam for instructions to modify params and flashing the same and also about the Gapps size issue
Have Fun :good::good::good:
plz share firmware/rom
good effort bro......kindly wants to tell that new kingroot app is now able to root qiku q terra.....and using app2sd i am able to move max of my apps to sd card ....but i also like ur effort to install android 6 rom in indian qiku.....but i hav a request to plz make a video about whole thing(as that would me more reliable to understand).....and plz share ur downloaded firmware/rom......i hav downloaded android6.cpb file shared by zuaq....so any trick to install directly this rom ?
thx in advance
---------- Post added at 05:28 AM ---------- Previous post was at 04:59 AM ----------
and also i think we can use buildprop edit apk to change build name of indiian qiku (I->M) .....anyway i hav very little knowlg of all this...but try to impliment ur process
Rahulraj2012 said:
good effort bro......kindly wants to tell that new kingroot app is now able to root qiku q terra.....and using app2sd i am able to move max of my apps to sd card ....but i also like ur effort to install android 6 rom in indian qiku.....but i hav a request to plz make a video about whole thing(as that would me more reliable to understand).....and plz share ur downloaded firmware/rom......i hav downloaded android6.cpb file shared by zuaq....so any trick to install directly this rom ?
thx in advance
---------- Post added at 05:28 AM ---------- Previous post was at 04:59 AM ----------
and also i think we can use buildprop edit apk to change build name of indiian qiku (I->M) .....anyway i hav very little knowlg of all this...but try to impliment ur process
Click to expand...
Click to collapse
Help me
I was plash rom but now my phone is hardbrick
My computer is see bootloader but flash file cpd no working
mr_thao said:
Help me
I was plash rom but now my phone is hardbrick
My computer is see bootloader but flash file cpd no working
Click to expand...
Click to collapse
You can load bootloader in your manager device? If you can, so it not brick!
Zauq said:
Hello Friends
A little background first !!
QiKU Q Terra (CP8692_I02) which was sold in India and came pre-installed with 360 OS v21, Android 5.1. The OEM went back to China hence there haven not been any software update for our device. I had been trying to boot latest Chinese 360 OS on Indian Qiku Terra to get updates but after flashing the Chinese version the device would not boot at all and would get stuck in fastboot mode. To revive the device, I had to flash back the V21, I had tried several times but no success.
I even got in touch with the 360 OS engineers over mail with the help of an administrator of Qiku Chinese forum but the engineers said it's not possible to flash Chinese 360 OS on Indian Qiku Q Terra.
I had also been trying to root QiKU and I was able to figure it out all recently.
Check out my post -- https://forum.xda-developers.com/an...i02-unlock-t3493636/post69455878#post69455878
This tutorial is also useful for users of CP8692_M02 who had flashed the v21 on their devices and now are not able to go back to CP8692_M02.
Warning !! Try this own your on risk although it's very safe if you follow the instructions without missing any steps. Don't blame me if you still manage to kill your phone and loose your job :laugh::laugh:
Let's begin !!
Just ensure your device bootloader is unlock before you follow the instructions as it's required to boot 360 Chinese OS on the Indian QiKU.
Download the latest firmware and flash the same with YGDP or Qiku Download Assistant tool. When finished, the device won't boot and still be in fastboot mode. Now boot TWRP recovery from your pc, go to the folder where you have the TWRP recovery and press shift and right click and select "open command window here" and type the following
fastboot -i 0x1ebf boot (recovery name).img
This should boot TWRP on your device.
You can also flash TWRP recovery if wish to,
fastboot -i 0x1ebf flash recovery (recovery name).img
Now boot TWRP
fastboot -i 0x1ebf boot (recovery name).img
When in recovery mode you can use cmd to extract params partition which contain your device model name. Open cmd on your pc and type the following command
dd if=/dev/block/mmcblk0p30 of=/sdcard/params.bak
Once done, you'll have a file name params.bak on your phone's internal memory, copy the same to your pc. Download NotePad++ and install it, link - https://notepad-plus-plus.org/
Only use NotePad++ to edit the params, don't use NotePad. Plus make a copy of your params.bak file and keep it somewhere safe in case you mess up with original params file.
Right click on params.bak and open it with NotePad++, now search CP8692. The device model name would be CP8692_I02 just change I to M and save the changes, now it should be CP8692_M02.
The system partition size is not enough to flash Gapps hence you need to use TWRP recovery resize option.
In TWRP recovery and select > Wipe > Advance Wipe > System > click FS Option > click Resize FS now you shall have more free space in system partition
In TWRP now click reboot then click bootloader, in bootloader press volume up for fastboot mode. On pc open cmd in the folder where you have params.bak saved and type the following command:-
fastboot -i 0x1ebf erase params
fastboot -i 0x1ebf flash params params.bak
fastboot -i 0x1ebf reboot
If everything went well your device should boot Chinese 360 OS, Android 6.0.1 normally.
Now flash modified Gapps in TWRP which you have downloaded. The modified Gapps has Gmail & Hangout beside core apps and rest you can download from play store later.
If you flash bigger Gapps, the device will not boot or it shall be in bootloops coz of Gapps size and if you don't flash Gmail and Hangouts with the modified Gapps and download the same from Play store then it would give you connection trouble.
In case you wish to root then flash SuperSU.zip in TWRP.
Back to the booted device:-
To Activate VoLTE, download QuickShortcutMaker app from play store. Open the app and locate MBN test > click on the dropdown menu > click Try > Tick Volte_OpenMkt-Commercial-CMCC > and last click Activate.
Close the app and go to phone setting > Call settings > and enble VoLTE and you're done. You should see HD sign in the status bar of your phone. Now you can enjoy VoLTE calls.
The latest firmware is 360OS 2.0 (12.28) which is beta and gets weekly update. Download the firmware - http://bbs.360.cn/thread-14613403-1-1.html
Follow the tutorial to download from Baidu without log-in and download client - https://www.youtube.com/watch?v=cigJh9jg4-c
Download modified Gapps and supersu.zip - https://drive.google.com/drive/folde...ElFemQwTTFXcTQ
Credits:
Goes to me @Zauq for figuring out unlocking bootloader, rooting, modifying TWRP for cp8692_I02 etc. Without the unlocked bootloader the above was not possible.
Goes to @cuongvietnam for instructions to modify params and flashing the same and also about the Gapps size issue
Have Fun :good::good::good:
Click to expand...
Click to collapse
I wasn't take dd if=/dev/block/mmcblk0p30 of=/sd card/params.bak
C:\adb>dd if=/dev/block/mmcblk0p30 of=/internalsdcard/params.bak
'dd' is not recognized as an internal or external command,
operable program or batch file.
Hlep me
mr_thao said:
I wasn't take dd if=/dev/block/mmcblk0p30 of=/sd card/params.bak
C:\adb>dd if=/dev/block/mmcblk0p30 of=/internalsdcard/params.bak
'dd' is not recognized as an internal or external command,
operable program or batch file.
Hlep me
Click to expand...
Click to collapse
Have you tried the code in custom recovery mode??? If you're using the code when the device is NOT in recovery mode then you have to use the following code:-
adb shell
su
dd if=/dev/block/mmcblk0p30 of=/internalsdcard/params.bak
Just bear in mind that you have to be rooted to use the above mentioned code and in recovery mode you don't need to be rooted.
mr_thao said:
Help me
I was plash rom but now my phone is hardbrick
My computer is see bootloader but flash file cpd no working
Click to expand...
Click to collapse
What was your device model no when you flashed the rom and which rom version did you flash which caused the brick???
Rahulraj2012 said:
good effort bro......kindly wants to tell that new kingroot app is now able to root qiku q terra.....and using app2sd i am able to move max of my apps to sd card ....but i also like ur effort to install android 6 rom in indian qiku.....but i hav a request to plz make a video about whole thing(as that would me more reliable to understand).....and plz share ur downloaded firmware/rom......i hav downloaded android6.cpb file shared by zuaq....so any trick to install directly this rom ?
thx in advance
---------- Post added at 05:28 AM ---------- Previous post was at 04:59 AM ----------
and also i think we can use buildprop edit apk to change build name of indiian qiku (I->M) .....anyway i hav very little knowlg of all this...but try to impliment ur process
Click to expand...
Click to collapse
Flashing the supersu.zip to root Qiku is the easiest way if you ask me. I tried my best to give the instructions in a simplest way possible making video is not on my mind.
Changing the model no in build.prop would not help in booting Android 6.0.1 on Indian Qiku v21. Had this been so easy I would've done the same a long time ago
update file params.bak edited
step 1 : flash rom china and flash TWRP
Step2: flash params.bak
Step 3: reboot
Done
Link : https://tinhte.vn/threads/danh-gia-chi-tiet-qiku-terra-sieu-pham-den-tu-india.2543152/#post-49187102
Rom restore , rooted and playstore,super lite : https://drive.google.com/file/d/0B1JX0MSsEt63Zzd2MzVMb20wNTA/view
Hello bro,i want to downgrade to 5.1 v021 from 6.0 v18 china rom,but i haven't link rom.zip (i have twrp),give me link rom 5.1v021 .zip,please
Thanks for watching!?
volte is not activating even though option came by quickshortcut..app
android 6.0 successfully installed but...volte is not activating even though option came by quickshortcut..app........also need help to change chinese 360safe apk to change language in english
....thx in advance
Rahulraj2012 said:
android 6.0 successfully installed but...volte is not activating even though option came by quickshortcut..app........also need help to change chinese 360safe apk to change language in english
....thx in advance
Click to expand...
Click to collapse
Help me @Zauq. I am not able to download 6.0 update file from baidu as connection to file gets disconnected after 1 GB of data everytime. I have wasted atleast 10 GB of data due to this. Please help me out if you can upload the file to google.
Thank you in advance.
Rahulraj2012 said:
android 6.0 successfully installed but...volte is not activating even though option came by quickshortcut..app........also need help to change chinese 360safe apk to change language in english
....thx in advance
Click to expand...
Click to collapse
Did you also enable VoLTE in system settings?? I would not be able to change Chinese language in 360safe.apk.
imlb said:
Help me @Zauq. I am not able to download 6.0 update file from baidu as connection to file gets disconnected after 1 GB of data everytime. I have wasted atleast 10 GB of data due to this. Please help me out if you can upload the file to google.
Thank you in advance.
Click to expand...
Click to collapse
My google drive is already full hence won't be able to upload it. Trying signing up Baidu and download the file with Baidu client.
Zauq said:
My google drive is already full hence won't be able to upload it. Trying signing up Baidu and download the file with Baidu client.
Click to expand...
Click to collapse
Thanks for your quick reply. I am not able to sign up on baidu. If you have latest file than please upload on any big file sharing site such as pcloud. That will be very helpful. I am bit of noob on development side of Android. I have developed kernel driver for real time linux but android I am learning. Please share if any good tutorials to start developing for Android. Thanks again @Zauq
imlb said:
Thanks for your quick reply. I am not able to sign up on baidu. If you have latest file than please upload on any big file sharing site such as pcloud. That will be very helpful. I am bit of noob on development side of Android. I have developed kernel driver for real time linux but android I am learning. Please share if any good tutorials to start developing for Android. Thanks again @Zauq
Click to expand...
Click to collapse
There you go --- https://drive.google.com/file/d/0Bwy9M10qfmJLVm9MQTU0N1U2Tnc/view?usp=sharing
Have somebody schematic diagram of qiku phones? Please let me know, if find something.
Hello dear all, I have 2 issues
1) not able to get volte , even though hd voice enabled via quick shortcut app
2)updated to android 6 but even though can't make my sd card as internal storage(option is for only as portable storage present....Just like galaxy s7 I also tried abd command, becoz in s7 also even after android 6 update sdcard as internal is not by default present .....But failed)
Plz help .....Thx in advance bro zuak
Rahulraj2012 said:
Hello dear all, I have 2 issues
1) not able to get volte , even though hd voice enabled via quick shortcut app
2)updated to android 6 but even though can't make my sd card as internal storage(option is for only as portable storage present....Just like galaxy s7 I also tried abd command, becoz in s7 also even after android 6 update sdcard as internal is not by default present .....But failed)
Plz help .....Thx in advance bro zuak
Click to expand...
Click to collapse
1) Do you see HD sign in the status bar after enabling VoLTE through QuickShortcurMaker App??
2) Did you follow similar adb shell command for internal storage?? --- https://www.youtube.com/watch?v=PZLV5STiAW8
1) I m able to get on/off volte settings after quick shortcut apk,but as u ask......No hd sign in status bar
2) yes I had applied same adb shell commands but nothing happens, 360 os restarted but no increment in internal memory I need to format my memory card to use it once again
I request to make a small video for this isse resolution and plz upload if possible
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...
Nice work.
Does this stop the phone checking update servers?
loaded2107 said:
Nice work.
Does this stop the phone checking update servers?
Click to expand...
Click to collapse
Yeah It removes all blackphone apps, but you can modify the script
great work although I have encountered a problem in the pixel laucher that gives me error
script not ok
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot
But how is the phone?
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!
carlosinf said:
great work although I have encountered a problem in the pixel laucher that gives me error
Click to expand...
Click to collapse
Hi, I actually move to another phone, I had Lawnchair installed on bp2
Enviado desde mi PRO 5 mediante Tapatalk
notelinos said:
hello. when i flash your script my phone goes on bootloop
i flash it trought TWRP cause my phone cant see any microsd card
i thing the sd slot of my phone have problem
but my phone goes bootloop after flash BP2_Bloatware
can you sent me any sugestion? Thanks a lot
Click to expand...
Click to collapse
Hello, that's a big problem. You must flash files from SD card instead of internal, if you flash from internal storage youll get boot loop and I don't know how to solve that
Enviado desde mi PRO 5 mediante Tapatalk
storkinsj said:
About to spring for a BP2 but ... just out of curiosity:
The reason to own this phone is for the sandboxing and some of the applications that monitor and block application permissions. If you're removing those just to have a fast android phone ... not sure why you bought this one. The camera isn't even any good.
I just want to run basically unmodified. 2 years and many updates have passed since @polartux talked about battery draining Apps and just curious how the latest OS is? Also if I want to install applications I have developed myself (or get a couple off of the google app store) can I assume that's possible? Preciously LITTLE information about those things online. And I have emailed sales multiple times never got a single response. Kind of scary lol.
So :
-can I do ADK dev on this thing?
-has the stock OS gotten better?
-Can I install pandora (or whatever)?
Cheers!
Click to expand...
Click to collapse
Sorry mate but I don't know, I'm not a dev. I only posted this to help.
Enviado desde mi PRO 5 mediante Tapatalk
chape199 said:
IM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE.
Hello there. I own bp2 since last year. So in order to avoid lags and poor battery performance im gonna write this guide.
So thanks to this i achieved a new phone, without battery drain, a very good battery and cpu temp, and almost root access.
These modifications are made on 3.0.14 ROM, I dont know if this works if your blackphone runs another version.
You can install 3.0.14 here
1. First of all you need to flash TWRP. Download and instructions here
2. Once flashed do not reboot system, type
HTML:
fastboot reboot
and press vol+ to enter twrp.
3. Now it will asks you to allow modifications, NEVER do that, always press "Keep Read Only" because you will get bootloop if you mount system as rw.
More info about that here
4. Now flash magisk, then reboot and install magisk apk. Download from here
NOTE: I dont know why but you need a microsd card in order to flash files, because twrp cant mount /data
NOTE 2: At this point you dont have su BUT you can install magisk modules (yes, xposed too).
Now lets give BP2 Pixel's style.
5. Download this script to remove all Google stuff, yes, just do it. I recommend the EXTREME one.
6. Flash it trough recovery and wipe chache/dalvik. do not reboot yet.
7. Now lets flash Gapps again, updated and modular. Just go to this page and select your desired package. I recommend AROMA not only because you install what you need, but you can remove stock apps (calculator, fmradio, stock email, etc). http://opengapps.org/
8. Now, yes, you can boot system.
9. I also made this script to remove all SilentCircle stuff. Just flash it.
NOTE 3: I wrote this script before removing gapps and that things i explained, so let me know wichs apps still get installed and i will add to the script. Also let me know what apps you want to remove.
Screenshots:
Updating...
Click to expand...
Click to collapse
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks
dgc1 said:
I am having a problem, every time I try and install Magisk thro' TWRP I get "failed to verify whole file signature" and "signature verification failed", I can install BP2 9, 10, 11 and 14 zips without any problems. Bloatware zip also throws up the same messages. may need a step by step instruction. As before TWRP is installed and BP2 11 doe's not brick the phone, not sure what 14 will do, thought it would brick the phone. Many thanks
Click to expand...
Click to collapse
Hi, i dont use the bp2 anymore since past year but i remember that you have to flash the zips from external sdcard, never use twrp to flash files trough internal. Maybe thats the problem. Hope ive helped you.
Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF
kenfalco_14 said:
Hi guys when I tried to flash the recovery it told me:
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.556s
[[email protected] Desktop]#
What should I do?
Many thanks
KF
Click to expand...
Click to collapse
To unlock the bootloader I suppose, but how?
kenfalco_14 said:
To unlock the bootloader I suppose, but how?
Click to expand...
Click to collapse
settings
developer options
oem unlocking - on
restart phone
hold volume down (bootloader mode)
connect usb and do command from PC:
fastboot oem unlock-go
## Your DATA will be DELETED ### make backup
I personally have another problem. I can't see TWRP.
Just black screen.
So i'm trying to fight with it using adb shell...
If I have a root and run all scripts mentioned here, I will explain it here later...
BP2 boot to TWRP
Hi All,
I have read several thread and web pages on how to root, install twrp, rom etc and I can not get it to work.
I was able to update the BP2 to 3.0.14 from .9
All I want to do is change to a custom rom.
I did the following:
-enable USB debugging
-enable oem unlock
-installed platform tools on PC
-adb reboot bootloader
-fastboot devices - phone is there
-fastboot oem unlock-go
-reboot - phone appears to be unlocked
-fastboot flash recovery twrp.img
>Sending 'boot.img' (17392 KB) OKAY [ 0.545s]
>Booting OKAY [ 0.040s]
>Finished. Total time: 0.596s
-fastboot reboot
reboots to blank screen
Do over, and when fastboot reboot, I hold down Volume+
still get blank screen
Any ideas?
David_h99 said:
Hi All,
still get blank screen
Any ideas?
Click to expand...
Click to collapse
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.
speed_boy said:
It's because the screen not supported by TWRP.
When you run TWRP you should see all your files in windows by USB cable, right? Hope you put SD card in it.
So you are the same boat like me.
ROOT still doesn't work for me btw, but i have a few commands:
0) run twrp (probably it disappeared for you and stock recovery back, so i'm running it like that in download mode:
fastboot.exe boot twrp-3.4.0-0-bp2.img
1) open shell: adb shell
in the shell:
for install magisk:
twrp install /external_sd/Magisk-v21.1.zip
you have to have this file on sd card okay? =)
To rill bloatware:
twrp install /external_sd/BP2_Bloatware.zip
To kill google stuff will be not so easy because it will ask you questions on the screen.
So i've repacked it to force version without questions (will attach my version here)
twrp install /external_sd/G-Killer_v3_forced.zip
Then you need to install open gapps
twrp install /external_sd/open_gapps-arm-6.0-pico-20201113.zip
If you want to decrypt DATA partition then:
cat /etc/fstab
look for numbers for your DATA partition
then do format:
make_ext4fs /dev/block/mmcblk0p33
your end will be different possibly.
Then disable dm verify:
twrp install /external_sd/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
take it here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
and final reboot:
reboot
Anyway ROOT just simply doesn't work. I was fighting with it a lot of hours
tried super su also without any luck.
Hope it helps you somehow.
Click to expand...
Click to collapse
Thanks for response.
When I do fastboot devices, it shows thone
Once i do the fastboot.exe boot twrp-3.4.0-0-bp2.img command, it reboots and blank screen.
When I do adb shell, i get "adb.exe: no devices/emulators found"
I do adb devices, and it shows no devices attached
I do have installed "Google Nexus ADB interface" device installed
David_h99 said:
I do have installed "Google Nexus ADB interface" device installed
Click to expand...
Click to collapse
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.
speed_boy said:
In win10 I have "adb interface" with ID: VID_18D1&PID_4EE2
In win7 it is "Android composite adb interface"
in both OSes works well.
So try to change driver for example.
Click to expand...
Click to collapse
I am not able to find where to change this to "adb interface"
do you know how I can change this?
The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.
placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed
After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.
Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now
Thread was opened.
mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot
Would this work on Blu Vivo XI since same chipset?
sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer
Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof
mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!
Hi everyone,
I have rooted my last few smartphones and was always happy with it. Now I got new Blackview BV9800 PRO and I want to root it with Magisk. but as the phone is new, there is lack of information on the internet, Anyway, I have found some information, but it is not complete and I believe You, smart guys, can help me to root my smartphone
This is the information I got:
How to root it with Magisk :
Download your rom from : viewtopic.php?f=285&t=532354 (you can alternatively extract it with SP Flash Tool and WWR)
Download and install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/rel ... v7.5.0.apk
Patch the boot image with Magisk Manager
Unlock the bootloader. (Wipe the phone! )
Flash the patched boot image with SP Flash Tool or Fastboot. (ONLY the boot image)
Reinstall Magisk Manager
This is what I did and what happened:
I installed latest Magisk apk from official sources. I opened the app, clicked on "Install Magisk", then via this app I downloaded the zip file, then tried to installed it via Magisk but got an error "Unsupported/Unknown image format".
Any ideas what have I done wrong? Did I have to flash boot image from the ROM, and not the one Magisk downloaded? P.S., the smartphone is new, nothing more then I written above is done to it (no oem unlocking, no usb debugging, etc).
RESERVED
I let Magisk manager patch the original boot.img. After flashing it with fastboot or SP Flash the phone stuck with message that verified boot didn't accept the signature.
Hm... Is there anyone who rooted BV9800 Pro successfuly and could guide us? ?
update fail.
I greet you, I accidentally deleted it when I updated, Nvram. on my phone. BV9800pro. It is possible to provide me with firmware recovered from a similar phone. I also posted on the forum at Blackview but without answer
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
update fail
LGZACRO said:
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
Click to expand...
Click to collapse
Hello
Yesterday during an update, by accident, my equipment, BV9800pro, performed a complete formatting, "Full Format + Dowload", it seems that Nvram has also been rewritten. it is possible to provide us with a solution or file with this data, specific to our equipment. i need a original nvram.bin, and nvram.data, in firmware from Blackview site this its not exist..
if someone wants to help me, I send them a private message with their email address
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
LGZACRO said:
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
Click to expand...
Click to collapse
who guarantees this?
rooting worked for me with that solution given to the PM. I wanted to install AOSP, but I found that the thermal image did not work anymore, there were some problems when previewing the video files from Facebook, and I gave up. from the mistake as I mentioned I format + dowload and delete all important partitions. nvram .bin si nvdata. Nothing works properly, TEE and Google Key are inactive, the thermal image fails, some applications are closed immediately. This is the experience with rooting and installing AOSP on the BV9800Pro
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
make total firmware dump and send the bakup , or nvram.bin nvdata.bin file,
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
i dont now. i dont install twrp.
Ok, pm me your skype or signal or wickr or fb. We will try to do this in few hours
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
I posted in their forum a detailed error report but the moderator deleted my post.
Don't bargain for help by them.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
As I mention there's no TWRP available for this phone yet.
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
I rooted it exactly like You and it worked perfectly! Thanks for auch detailed rooting guide!
By the way guys, I think we Should open the request for TWRP for BV9800Pro. How do You think?
After you unlocked bootloader, it changed to orange state, and it always shows "Your device has been unlocked and can't be trusted..Your device will boot in 5 seconds", it could be resolved by modified LK image.
Refer to
1. https://forum.hovatek.com/thread-31664.html
2. http://bbs.blackview.hk/viewtopic.php?f=286&t=532899 -- included modified LK image
Of course, you could reflash by fastboot, no need to use SP flash tool.
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
james35888 said:
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
Click to expand...
Click to collapse
zlatkomas said:
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
Click to expand...
Click to collapse
Hi, I'm not rooted (yet) and my BV9800 PRO is having some issues with the loudspeaker, any media like YouTube or Spotify, play audio for a second or two and then just go mute, volume can be high but no audio at all, phone calls last longer but also go mute and have to go back to regular "ear-speaker" to keep listen to the other side. Are this the same problems you refer to? I can't remember if this happened after the OTA update tho. Thank you.