Related
Hi all,
I've been playing around lately with this Dual Core Dual Sim device, named Intki E91, with Android 4.0.4, rooted it, then replaced the iPhone iOS style launcher with Samsung's TouchWiz launcher, all fine so far, but then proceeded to wipe all non-useful built-in apps with the help of Uninstall Master 3.2.0, then deleted all Chinese related stuff from the internal memory, at which point the phone resets, no longer boots and I am now stuck in the Android System Recovery 3e with no chance of ever restarting it. Power button + Volume Down takes me to a screen where it says "Enter factory mode" and it just hangs there so one has to remove the battery and then reboot only to get to the stock recovery again.
Now there is no ClockworkMod for this phone and the manufacturer here http://www.intkimobile.com/ did not reply to me when I mailed him about the problem, asking for the factory ROM.
I could only find a find a custom ROM (（E91动力）软件z19b-intki-e91-01_R01_user) on a Chinese website with a "MT6575_Android_scatter" file, but when attempting to flash it with SP Flash Tool 3.1304.0.119 it says Sp Flash Tool Error : 8200, "the load and target are inconsistent", "the load to be downloaded is for MT6575", "the target platform is MT6577_S00".
Afterwards, I looked for a different scatter file for 6577 processors and I found "MT6577_Android_scatter_emmc" file all over the web, then attempted to flash using that, but got the BROM ERROR : S_DA_EMMC_FLASH_NOT_FOUND (3144)
At this point I really do not know what else to attempt to revive this phone, I would really appreciate if someone extracted their stock ROM for this device and post it here as an "update.zip", or give instructions on how to bypass the SP Flash Tool errors, or made a custom recovery for this device so i could flash the above mentioned ROM with no errors, or even develop a custom ROM altogether.
Thanks for your time.
Edit: I flashed a custom recovery using the tutorial here: http://www.labandroid.com/china/2013/02/flash-cwm-recovery-to-mtk-phones-without-sp-flash-tool/ but it doesn't work, so now I no longer have a recovery.
My only hope is a solution through Smart Phone Flash Tool.
If only someone could make the errors go away...
The only thing left to do now is to try and format the Flash using SP Flash Tool, an see if that can enable a error-free flashing.
But it's a lot of hassle writing the imei's back afterwards. And if it doesn't work I will have a total brick...
Before proceeding, can someone confirm if formatting the flash fixes the SP Flash Tool errors (especially given its internal memory is a mere 512mb ? - could that be the cause of errors?)
Please advise...
Thanks
im in the same boat as u - struggling to find a working alps iphone 5 rom
hiphone5 MT6573
ushir said:
im in the same boat as u - struggling to find a working alps iphone 5 rom
Click to expand...
Click to collapse
Hello i have a clone hiphone 5 mt6573 and need some help please
can i install any custom roms please help. here's
my phones info
board: Unknown
bootloader: Unknown
brand: Aple
cpu_abi: Armeabi
cpu abi: Unknown
device: konka73_gb
display: alps.gb.fdd2.mp.v2.14
hardward: mt6573
manufacturer: Unknown
model: phone5
product: konka73_gb
Hello.
I have a problem, namely Quantum Goclever have 400 Lite, which has android 4.4.2 (kitkat).
The problem is that I can not do root, tried programs:
-Towelroot
-Android Kingo ROOT
-iRoot
-Framaroot
-SRSRoot
-root Genius
-Zhuodashi
and no I do not work
in Kingo can not find your phone when you turn on the phone
in Root Genius at 86% Root falied
in Towelroot change the code as it is hangs apk
in iRoot Root falied after restarting the phone to
in general it's Framaroot inaction
in SRSRoot Root falied
in Zhuodashi nor gives advice
some Chinese apps best hehe phone from China
sorry for my bad english
Goclever Quantum 400 Lite based on MTK6572
refresh
@refresh
refresh
@refresh
You need usb tether drivers on goclever site kingo worked for me
Sent from my QUANTUM_400 PLUS
If something goes wrong it's only your responsibility! This will void the warranty! For information purpose only!
There are two versions of this mobile. One is recognized by Mtk Droit Tool and other not. I'm going to write about the problematic one.
to get:
SP Flash Tool
Preloader VCOM drivers
PhilZ recovery.img ported by "tomcofik" (md5sum: 60ca70def40e00ee2406b8ced4fddc4b size: 5.04MB)
UPDATE-SuperSU-v2.40.zip file
Proper scatter file from stock rom (MT6572_Android_scatter.txt size: 6,72KB)
to do:
Install drivers
Copy UPDATE-SuperSU-v2.40.zip to your phones build in storage memory in directory "0\clockworkmod"
Switch phone off
If something goes wrong it's only your responsibility! This will void the warranty! For information purpose only!
Lunch SP Flash Tool, load scatter file and recovery.img
Click on Download (Download only) and plug in your phone
When done hold vol+ and power button to boot into recovery
Install zip from sd card
Reboot
Done!
If something goes wrong it's only your responsibility! This will void the warranty! For information purpose only!
Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-J710F, SM-J710FN, SM-J710GN, SM-J710MN, SM-J710K models only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxyj72016exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/jcadduono/android_device_samsung_j7xelte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
@jcadduono ,
Thanks for official TWRP.
Hello guy !
@jcadduono , thank you very much for great work ! It's fully working for my SM-J710FN
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Not sure if both are related but I had flashed this TWRP 4-5 days back. Last night after reboot (wasn't the 1st one after flashing certainly), phone didn't boot because of custom binary FRP lock. Had to reflash firmware.
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Amit.A said:
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Click to expand...
Click to collapse
jhampzkidoodle said:
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Click to expand...
Click to collapse
Normally on the newer Samsung devices we can flash https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/ and then go to the wipe page and use [Format Data] to turn off encryption.
It seems there is a bug with the Exynos 7870 devices that causes vold to encrypt the device regardless of whether or not boot image fstab actually calls for encryption, and I've tried removing all hints of encryption support from the boot image and yet still the system will start encrypting on the next boot.
TWRP does not support Samsung's closed off encryption as it relies on the Android OS frameworks.
I've tried submitting this issue to Samsung's Mobile Security team but they just shrugged it off and said you can't turn it off on purpose.
So pretty much you're SOL for data partition (internal storage is inside that) reading in TWRP until someone comes along with system modifications to disable encryption or a custom ROM.
Hi bro... @jcadduono
Thanks for making Official TWRP Recovery for our J7 2016. Really its great work Thanks again. :good:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
@jcadduono with the custom kernel http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736 encryption can be turned off.
thewinelover said:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Click to expand...
Click to collapse
I doubt it, it has different exynos processer
artssa said:
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
Click to expand...
Click to collapse
Offtopic post you have. Shouldn't be a problem for flashing a firmware for your device via Odin, whichever ROM you are using.
Join us Samsung Galaxy J7 2016 users Samsung Galaxy J7 ? Official Group in Telegram
Here you can chat with anyone.
Here many xda developers are present.
Here you can share any kind of data and files in any size.
And the biggest thing is that here you will get instant solution to any problem. :good:
Telegram Group Link : https://telegram.me/joinchat/Cmh8LUAs6AFEJUfawPCiWg
Regard by @KeMii :good:
I Root the Device but After root there were many issues..... I Keep on getting an notification that unauthorized action ...
and also my device keeps lagging it lags just for a second but this games every 2-3 mins
I also freezed KNOX with lucky patcher but the problem still persists any meathod to solve the problem Thanks
Installed Xposed... Few Modules and Partition Crushed... It was my Brand NEW Phone :'(
Hello, TWRP backup not properly block set. The size of EFS equal to 4 MB in size, inside the reserve of zeros.
No IMEI as all zeros!
Need to fix, or put my. In my TWRP you can flash system.img from firmware.
Good luck to everyone! TWRP is correctly bekapit EFS.
Extract postcode to flash the IMG.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone. Please forgive me for my English :laugh:
The Lord does not forget to thank! And then I see the downloading is not weak and thanks to zero.
ermakovermakov7878 said:
Hello,your TWRP backup is not correct unit is specified. The efs size is equal to 4MB, inside backup zeros.
I took apart and tell it like it is. That's correct TWRP backup efs + setting backup System.img
Unpack the zip to flash the img.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone.
Please excuse me for my English :laugh:
Click to expand...
Click to collapse
But it is all in russian :/
Will this work with J7-2016 with Snapdragon 617 ?
Skylinestar said:
Will this work with J7-2016 with Snapdragon 617 ?
Click to expand...
Click to collapse
No
will it work on Galaxy J7 prime ? it has same exynos 7870..
jcadduono said:
Team Win Recovery Project 3.0.2-0
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Click to expand...
Click to collapse
i have SM-J710FN. if I only follow below 3 steps, then will i b able to root my device ??
1. allow usb debugging and OEM unlock
2. flash official TWRP via Odin ... then re insert battery & reboot into TWRP
3. wipe data in TWRP and then falsh SuperSU via TWRP
is it enough.. Do I need to flash kernels first ??
Test twrp build for this mediatek device (SM-C7100). Post logs etc so I can help solve issues when I am available to do so.
TWRP download: https://www.androidfilehost.com/?fid=673956719939834043
SM-C7100_C7100ZHU1ARB1.zip: https://www.androidfilehost.com/?fid=673956719939834050
Kernel download: https://www.androidfilehost.com/?fid=746010030569970527 April, 23rd, 2018
Sources
Kernel source: https://github.com/travismills82/android_kernel_samsung_mt6757
TWRP device tree: https://github.com/travismills82/twrp_android_device_samsung_jadeltechn
Kernel Features
Knox Disabled
DM-Verity Disabled
Tima Disabled
More TCP congestion control algorithms
Remove verifiedbootstate flag from /proc/cmdline (for safety net)
Conservative gov enabled
Always enforce selinux disabled
Fsync on/off Toggle
Ninendo Wiimote support
+ More not listed check git changes for a full list
Regards,
Travis82
Hi it didn't work... I think this is for J7 plus only and please Help after flashing the custom recovery my boot logo of C8 is gone.... Please help
I have tried to install using odin and it says on the phone a chinese message,which i translated with google, that read your phone needs to be unlocked to install a custom operating system, even though i enabled oem unlock and usb debugging. I used viper4android on my old phone and its annoying that im not able to install it on my new one.
Please help me when you get time:good:
the twrp cannot mount data partition unless format it first. and my device is sm c7100.
I can't install twrp in the first place.
How did you guys install it.
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
How to use the TWRP with Android Oreo?
Gautam488 said:
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
Click to expand...
Click to collapse
Brother how do you manged to unlock bootloader...? Please share with us
google play gives an error, the installation screen is not constantly installing
Hi everyone,
For those who have tried, could you please confirm whether the files are working or not.
Since there is no steps and instructions, can someone post the the procedure/code used for flashing kernel and TWRP?
Thanks
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
toto4c19 said:
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
Click to expand...
Click to collapse
Libsecure storage cannot be downloaded from anywhere could you please provide me link for the module
toto4c19 said:
For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
Hello, thx for all your hard work.
Click to expand...
Click to collapse
My C8 is 8.1 tried resetting back to factory, still 8.1
Noted your comment re ODIN, but I use Linux, Odin seems Win only.
Have successful rooted and installed Lineage on an old Note 3, but I didn't have to downgrade that!
Can you give me please, some guidance how I can return this wretched thing back to 7.1?
Actually, I am suspecting return is the wrong word as it may have come with 8.1 installed.
I'm a bit lost at this point.
Cheers
p
EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.