Based on Huawei's EMUI3.0 B009 ROM for X1, contains bunch of enhancements / mods (e.g. split screen multi-tasking; real time network speed display etc).
For both 3G and 4G versions of X1 sold in China (503L and 501u; if yours is a 501L and you have already cross-flashed 503L's ROM, I believe you can flash this mod too.)
Can be flashed without wiping data over and above B008 (with or without KangVIP mod installed) or B009 ROM.
Rooted (via Kinguser).
Your X1 must have an unlocked bootloader to flash this mod.
If you get android.phone FCs after flashing, activate Airplane Mode to temporarily overcome the problem, then proceed to install and initiate Xposed framework (2.5.1) to solve it. (There is NO need to wipe data or clear cache etc etc; problem is unrelated.)
For full details (pics, explanations, downloads etc), pls visit original thread at:
http://cn.club.vmall.com/thread-2646028-1-1.html
For those who cannot successfully download from Baidu's servers, alternate untouched link below:
https://www.mediafire.com/?nwi1mbcfkvroqoo
All credits to Team HRT_KangVIP
potatohead said:
Based on Huawei's EMUI3.0 B009 ROM for X1, contains bunch of enhancements / mods (e.g. split screen multi-tasking; real time network speed etc).
For both 3G and 4G versions of X1 sold in China (503L and 501u; if yours is a 501L and you have already cross-flashed 503L's ROM, I believe you can flash this mod too.)
Can be flashed without wiping data over and above B008 (with or without KangVIP mod installed) or B009 ROM.
Rooted (via Kinguser).
Your X1 must have an unlocked bootloader to flash this mod.
If you get android.phone FCs after flashing, activate Airplane Mode to temporarily overcome the problem, then proceed to install and initiate Xposed framework (2.5.1) to solve it. (There is NO need to wipe data or clear cache etc etc; problem is unrelated.)
For full details (pics, explanations, downloads etc), pls visit original thread at:
http://cn.club.vmall.com/thread-2646028-1-1.html
For those who cannot successfully download from Baidu's servers, alternate untouched link below:
https://www.mediafire.com/?nwi1mbcfkvroqoo
All credits to Team HRT_KangVIP
Click to expand...
Click to collapse
Does it have issues of app 400 dpi compatiblity
And I'm on b001 320 dpi 4.4.2 version should i download b009 and flash it before flashing that one and what about unlocking bootloader i didnt do it before
Thanks
Ahmed.ragab said:
Does it have issues of app 400 dpi compatiblity
And I'm on b001 320 dpi 4.4.2 version should i download b009 and flash it before flashing that one and what about unlocking bootloader i didnt do it before
Thanks
Click to expand...
Click to collapse
320dpi roms are emui2.3 based, so u cant flash this mod directly over, you will first need to be on emui3.0 b008 or b009 full rom.
This mod will check for bootloader status, the flash will only proceed if the bootloader is unlocked.
As for 400dpi compatibility, I have not encountered any apps (that i use) that refused to install; user experience wise of apps at 400dpi, I actually prefer some apps to appear larger on screen for easier touch input and reading.
For apps that you want to run at 320dpi, you can install xposed and do per app dpi setting, best of both worlds.
potatohead said:
320dpi roms are emui2.3 based, so u cant flash this mod directly over, you will first need to be on emui3.0 b008 or b009 full rom.
This mod will check for bootloader status, the flash will only proceed if the bootloader is unlocked.
As for 400dpi compatibility, I have not encountered any apps (that i use) that refused to install; user experience wise of apps at 400dpi, I actually prefer some apps to appear larger on screen for easier touch input and reading.
For apps that you want to run at 320dpi, you can install xposed and do per app dpi setting, best of both worlds.
Click to expand...
Click to collapse
thanks potatohead I will download b009 first then the mod u share and I will search about how to unlock bootloader
thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:15 PM ----------
while I'm searching I found lollipop Rpm for mediapad x1 did u know anything about it ?
http://www.unlock-bootloader.info/mp3-0/huawei-mediapad-x1-6129.html
Thanks
Ahmed.ragab said:
thanks potatohead I will download b009 first then the mod u share and I will search about how to unlock bootloader
thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:15 PM ----------
while I'm searching I found lollipop Rpm for mediapad x1 did u know anything about it ?
http://www.unlock-bootloader.info/mp3-0/huawei-mediapad-x1-6129.html
Thanks
Click to expand...
Click to collapse
there are users who feedback-ed that no special steps need to be taken for bootloader to become unlocked - once you flashed a full ROM it will become unlocked - i can more or less vouch for that personally as the bootloader on my X1 just unlocked itself one fine day, i don't even know how or when exactly did it happen till today! Your mileage may vary.
As for lollipop, whatever you saw on the net is 101% fake no such ROM for X1 yet as we speak.
What is "real time network speed" ?
omniphil said:
What is "real time network speed" ?
Click to expand...
Click to collapse
sorry, omitted the word display after speed, already edited OP.
shd be - real time network speed display
potatohead said:
there are users who feedback-ed that no special steps need to be taken for bootloader to become unlocked - once you flashed a full ROM it will become unlocked - i can more or less vouch for that personally as the bootloader on my X1 just unlocked itself one fine day, i don't even know how or when exactly did it happen till today! Your mileage may vary.
As for lollipop, whatever you saw on the net is 101% fake no such ROM for X1 yet as we speak.
Click to expand...
Click to collapse
so If flashed the total package of b009 from chiness forum and flashed that one u shared . is enough ?
Ahmed.ragab said:
so If flashed the total package of b009 from chiness forum and flashed that one u shared . is enough ?
Click to expand...
Click to collapse
yes, after flashing the full rom followed by the mod, nothing else to flash maybe install xposed if u dun mind losing the ability to change themes in xchg of having per app dpi setting ..
potatohead said:
yes, after flashing the full rom followed by the mod, nothing else to flash maybe install xposed if u dun mind losing the ability to change themes in xchg of having per app dpi setting ..
Click to expand...
Click to collapse
I flashed Rom but when i try to flash the mod u share it won/t see the screenshot any idea ?
Ahmed.ragab said:
I flashed Rom but when i try to flash the mod u share it won/t see the screenshot any idea ?
Click to expand...
Click to collapse
have you installed Hisuite? You need to install Hisuite for Windows to correctly detect and load the correct drivers for your X1.
http://download-c.huawei.com/downlo...loadId=16205&version=60297&siteCode=worldwide
if you have installed Hisuite and still getting error msg, check that you have activated USB debugging on your X1 (click the build number in About Phone to turn on Dev Mode, then enable USB debugging from within).
hope the above helps
I tried run.bat but it never works for me.
The the method I use is fastboot command:
- enter in fastboot mode (vol down + power)
- fastboot flash boot boot.img
- reboot in fastboot mode
- fastboot flash cust cust.img
- reboot in fastboot mode
- fastboot flash system system.img
- reboot
I hope it will help.
potatohead said:
have you installed Hisuite? You need to install Hisuite for Windows to correctly detect and load the correct drivers for your X1.
http://download-c.huawei.com/downlo...loadId=16205&version=60297&siteCode=worldwide
if you have installed Hisuite and still getting error msg, check that you have activated USB debugging on your X1 (click the build number in About Phone to turn on Dev Mode, then enable USB debugging from within).
hope the above helps
Click to expand...
Click to collapse
hi suit was installed and I was already enabled usb debugging .. I ran run.bat file as administrator and it gave me that should I enter recovery mood or what i have to do ? see screenshot
super_sonic said:
I tried run.bat but it never works for me.
The the method I use is fastboot command:
- enter in fastboot mode (vol down + power)
- fastboot flash boot boot.img
- reboot in fastboot mode
- fastboot flash cust cust.img
- reboot in fastboot mode
- fastboot flash system system.img
- reboot
I hope it will help.
Click to expand...
Click to collapse
when I try go to fast mod it write me this
Ahmed.ragab said:
View attachment 3138122
hi suit was installed and I was already enabled usb debugging .. I ran run.bat file as administrator and it gave me that should I enter recovery mood or what i have to do ? see screenshot
Click to expand...
Click to collapse
if you got to the screen in your screenshot, you have already successfully flashed the mod, you do not need to wipe data first, simply press Enter key on your keyboard, the screen will disappear and the phone should reboot normally.
the first boot after flash will take slightly longer and after a slight while you should see the 'Android is upgrading' apps dialog box, if u did not encounter any error after booting, you need not wipe data; if u do (other than the FCs mentioned in the OP), you can then proceed to wipe data / factory reset via the instructions provided in the earlier screenshot or from the System menu.
i m not too sure abt using fastboot mode directly to flash though, never have the need to.
after flashing the full rom, did u set it up first before flashing the mod? i m not sure whether will it make a difference, but u may want to try setting up the full rom first, then try to flash the mod.
anyway, my personal experience is the 'Advise to enter recovery mode' screen appears only after the mod has been successfully flashed, so if u see that screen, you have flashed the mod.
if u can boot up after that, go to About Phone to check if the software version ends with KangVIP, if yes, you have definitely succeeded.
potatohead said:
if you got to the screen in your screenshot, you have already successfully flashed the mod, you do not need to wipe data first, simply press Enter key on your keyboard, the screen will disappear and the phone should reboot and boot normally.
the first boot will take slightly longer and after a slight while you shd see the 'Android is upgrading' apps dialog box, if u did not encounter any error after booting, you need not wipe data; if u do (other than the FCs mentioned in the OP), you can then proceed to wipe data / factory reset via the instructions provided in the earlier screenshot.
i m not too sure abt using fastboot mode directly though, never have the need to.
Click to expand...
Click to collapse
my mob boot normALLY WITHOUT ANY ANDROID UPGRADING WINDOW WHAT IS THAT LINE FASTBOOT NOT RECOGNIZED AS INTERNAL OR EXTERNAL.. ?
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
I can't see any change in my mob ?
---------- Post added at 05:43 PM ---------- Previous post was at 05:38 PM ----------
potatohead said:
if you got to the screen in your screenshot, you have already successfully flashed the mod, you do not need to wipe data first, simply press Enter key on your keyboard, the screen will disappear and the phone should reboot normally.
the first boot after flash will take slightly longer and after a slight while you should see the 'Android is upgrading' apps dialog box, if u did not encounter any error after booting, you need not wipe data; if u do (other than the FCs mentioned in the OP), you can then proceed to wipe data / factory reset via the instructions provided in the earlier screenshot or from the System menu.
i m not too sure abt using fastboot mode directly to flash though, never have the need to.
after flashing the full rom, did u set it up first before flashing the mod? i m not sure whether will it make a difference, but u may want to try setting up the full rom first, then try to flash the mod.
anyway, my personal experience is the 'Advise to enter recovery mode' screen appears only after the mod has been successfully flashed, so if u see that screen, you have flashed the mod.
if u can boot up after that, go to About Phone to check if the software version ends with KangVIP, if yes, you have definitely succeeded.
Click to expand...
Click to collapse
not it isn't end with kangvip and I already flashed fully b009 but when I tried to flash ur mod without any sucess I rooted b009 and removed some system apps .. maybe this cause the problem ?
Ahmed.ragab said:
my mob boot normALLY WITHOUT ANY ANDROID UPGRADING WINDOW WHAT IS THAT LINE FASTBOOT NOT RECOGNIZED AS INTERNAL OR EXTERNAL.. ?
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
I can't see any change in my mob ?
---------- Post added at 05:43 PM ---------- Previous post was at 05:38 PM ----------
not it isn't end with kangvip and I already flashed fully b009 but when I tried to flash ur mod without any sucess I rooted b009 and removed some system apps .. maybe this cause the problem ?
Click to expand...
Click to collapse
maybe, try flashing the full rom again, set it up normally, dont root or remove anything, then flash the mod (the mod will root it for u).
when flashing the mod, use the choice (in sequence) as below:
a) connect the phone (switched on normally with USB debugging on) to computer via USB (i usually choose MTP mode but shouldnt matter) - make sure all drivers installed properly, no error msg or uninstalled device in Control Panel, Hardware and Sound, Device Manager
b) 1, Enter
c) Press any key to continue
d) Phone will reboot into fastboot mode, if you see the wordings 'Bootloader Unlocked', you will be presented with 2 choices again
e) 1, Enter
f) Flashing procedures will continue, after it has finished, the enter into recovery mode page will appear - this does NOT mean you phone is now in recovery, this is merely an instruction page advising u to wipe data - OPTIONAL - not needed for now actually, especially if you come from a newly set up B009 rom
g) Press any key, phone will reboot normally - wait patiently for 'Android is upgrading' dialog box to appear - sign that the mod has been successfully flashed
h) Press any key again to close the green flashing dialog box on your PC
potatohead said:
maybe, try flashing the full rom again, set it up normally, dont root or remove anything, then flash the mod (the mod will root it for u).
when flashing the mod, use the choice (in sequence) as below:
a) connect the phone (switched on normally with USB debugging on) to computer via USB (i usually choose MTP mode but shouldnt matter) - make sure all drivers installed properly, no error msg or uninstalled device in Control Panel, Hardware and Sound, Device Manager
b) 1, Enter
c) Press any key to continue
d) Phone will reboot into fastboot mode, if you see the wordings 'Bootloader Unlocked', you will be presented with 2 choices again
e) 1, Enter
f) Flashing procedures will continue, after it has finished, the enter into recovery mode page will appear - this does NOT mean you phone is now in recovery, this is merely an instruction page advising u to wipe data - OPTIONAL - not needed for now actually, especially if you come from a newly set up B009 rom
g) Press any key, phone will reboot normally - wait patiently for 'Android is upgrading' dialog box to appear - sign that the mod has been successfully flashed
h) Press any key again to close the green flashing dialog box on your PC
Click to expand...
Click to collapse
when I pass step c my phone not rebooted to fastboot mode it do nothing .. I tried to go to fastboot manually it write me with green color (phone unlocked then I press enter no flashing procedure occurred it give me the screenshot I shared with u directly after I press enter and nothing happen with mob or pc ( what is the line (fast boot not recognized as internal or external ....
Ahmed.ragab said:
when I pass step c my phone not rebooted to fastboot mode it do nothing .. I tried to go to fastboot manually it write me with green color (phone unlocked then I press enter no flashing procedure occurred it give me the screenshot I shared with u directly after I press enter and nothing happen with mob or pc ( what is the line (fast boot not recognized as internal or external ....
Click to expand...
Click to collapse
sounds like your driver not properly installed or corrupted as adb could not reboot your phone into fastboot mode properly, subsequently, not able to fastboot flash your phone.
uninstall and reinstall hisuite, if problem persists, change a cable, change usb port or change to another computer to flash.
potatohead said:
sounds like your driver not properly installed or corrupted as adb could not reboot your phone into fastboot mode properly, subsequently, not able to fastboot flash your phone.
uninstall and reinstall hisuite, if problem persists, change a cable, change usb port or change to another computer to flash.
Click to expand...
Click to collapse
I flashed it finally I ran run.bat file normally .. phone not rebooted itself to fastboot mode .. I did it manually device detected again and it begin installing thx for ur help @potatohead
Related
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh:
hi folks,
tomorow should be getting my hands on the Ulephone power 2.
its the 5.5 screen 4gb ram 64gb rom.
all looks good until i have seen that the normal duel sim is one is hybrid for sdcard which is the norm right,
ant
but............
usually its sim 1 is for 4g cards and the hybrid is for 2g/3g/sdcard. yeah?
well the power 2 looks like its sim slot 1 is a 2g/3g slot and the hybrid is 4g or sdcard??????????
so will have to choose 4g or sdcard??? that cant be right?
I don't try this device with sim.
I know you can use the older power (1) have a sim 4g and SD card
So i believe the power 2 have the same method.
My first steps: How to root this device? i don't find a twrp.
I try to root with kingroot kingoroot, no results
Please?
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Hello my friends. I just bought the ulefone power 2 and i try to root it. Can anyone help me pls ???
mmidders said:
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Click to expand...
Click to collapse
I'm sure it's not working the twrp from the power (1).
If you have troubles with bootloops you can flash again the facatory rom and SP flash tools.
Press the power volume + and - and SP flash tools gonna flash.
The only way is to made a twrp from the k6000 http://fvknl.pro/k6000-plus-root-guide/
I don't know how, that device is almost the same...
There has been 2 ulefone Updates since launch
Android 8.0 is scheduled for end of the year.
Updates are fine, who can create a TWRP? So we can finally root the device
geheimke said:
Updates are fine, who can create a TWRP? So we can finally root the device
Click to expand...
Click to collapse
up
TWRP please!
Not so easy to do it. It will take very long time to port or build twrp
It sucks that power 2 still doesn't have root or twrp. I refuse to touch unrooted phones. I just received it as gift. I will keep it in a drawer and check next month or so.
I find that it lacks optimisation, kinda laggy in 3D/games ..
On Antutu, scores is 44000. I tested a galaxy S5 of a friend, it was 72000. For a phone that is several years older than Power 2.
I understand that it comes not with high end cpu/gpu but still..
I will copy my post from needrom website.
I have successfully rooted my two Power 2 phones. I had to port the TWRP recovery from Oukitel k6000 plus using Carliv Image Kitchen and following some online tutorials.
The only issue is, TWRP is semi functional, that is, touch doesn't work. I had to connect a mouse to my phone via OTG usb port and using some dongle to make USB smaller to fit the port. Also it comes with Russian language as default, but can be changed to English or any other as the original TWRP from Oukitel k6000+ (3rd button from second column, then click on Globe tab at the top right then choose English and the only button at the bottom to accept the change).
I am trying to fix this with no luck so far. But at least I am rooted and I was able to flash "SR1-SuperSU-v2.82-SR1-20170608224931.zip" which is the latest as of writing this. SuperSu functions properly and I am able to use AdAway.
If anyone is interested in the recovery image, I will post it. I flashed it using fastboot though after unlocking the bootloader using "fastboot oem unlock"
Click to expand...
Click to collapse
Rebel_X said:
I will copy my post from needrom website.
Click to expand...
Click to collapse
I would very much like to give this a go with my ulefone power 2!
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
alpsayin said:
I would very much like to give this a go with my ulefone power 2!
Click to expand...
Click to collapse
Check the post above :good:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
Check the post above :good:
Click to expand...
Click to collapse
mbs.yaswanth said:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Click to expand...
Click to collapse
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
alpsayin said:
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Click to expand...
Click to collapse
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
This:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
Click to expand...
Click to collapse
And this combined:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
Click to expand...
Click to collapse
Apparently if you dont flash the supersu first time you go into TWRP then it gets messy. Got the root working now. Thank you for the help and of course for the TWRP build!
Also if anyone's wondering it's possible to restore the system via fastboot. Extract the rom zip (can be downloaded from http:/ulefone.com/download/power2.html ) and flash boot, recovery and system;
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
link for sp flash tool u used.
Rebel_X said:
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
Click to expand...
Click to collapse
ok what should i select there? formal all+download or download only or firmware upgarade???
So i wanted to flash a new firmware on my MTK Device (UleFone Power 2), but i ran into some Errors while doing so, thus , my phone died in the process.
Following Errors occurred, depending on which (SP Flash Tool;SPMultidownloadflashtool;etc) you use:
Errors:
Internal Buffer
STATUS_SEC_IMGHDR_TYPE_MISMATCH
Through digging and asking on the web, two wonderful and very very helpful people: alterogi and finally Sunray888
This solution popped up. Thank you so much to both of them!!
Solution:
But first: You are now warned, try this at your own risk.
Quoted from Sunray888, alterogi. Credits to them.
My German Guide (more detailed with Pictures): Outside of XDA
Side Note: For the UP2 Rom you use SPMultiPortFlashDownloadProject , for the UK6P ROm you use SPFlashTool.
(Links & Attachments below!) (Adb-Fastboot.zip & Checksum.zip)
Part1:
1. Download all the files. (Below are the links and attached files.
2. Extract each zip to its own folder. Then Put the files of the Checksum.zip into the ROM Folder of the Ulefone Power 2.
3. Run the Checksum.exe and wait until it is done. It will show up in the black CMD when it's finished. A new Checksum.ini should be in the folder now.
Part2:
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Get the Oukitel K6000 Plus ROm Version 2.0 Ready. Extract it to its own folder somewhere on your desktop.
3. Open the SPFlashtool and select the android scatter file of the Oukitel Rom.
4. Connect your phone, hold Volume down and press on "Download" in the SPFlashTool. Now you wait for the process to end, WHILE still holding the button down.
5. After it is done flashing your new Firmware unto your phone, start it like you would normally do. Disconnect your phone now. You can now also skip the Setup Details, since we still have to flash the original Firmware.
6. Go to Device Infos on the bottom of your phone settings, tap a few times on Build Number until the Developer Options activate. Go back and tap on Developer Options.
7. In here you activate OEM Unlock and USB Debugging. Back to the pc: Now you open a CMD Windows and navigate to your extracted ADB-Fastboot Folder. (Some Pictures of this are on my German Tutorial Thread, Link above).
8.Connect your phone, tick the avaible spot of the upcoming new popup notification. Shutdown your phone now. Hold Volume Up and Power Button at the SAME Time until the Fastboot Menu pops up.
Make sure your phone is still connected to the pc.
9. In the cmd window you will now have to type the following thing: fastboot oem unlock
9.5 Another Method to get into fastboot mode: (OR enabled usb debug, accept connection between your PC and Ulephone and send command fastboot reboot bootloader after that "fastboot oem unlock")
10. After the process is done. You are still in fastboot mode.
And let the phone connected to the Pc.
11. Now you have to flash the original ROM/Firmware. In this case only Version 17 will work.
On this step i had a lot issues with "insufficient buffer"-Errors under SP Flash tool, but there is a solution for this.
Be careful :
Try to use #SPMultiPortFlashDownloadProject Version 3.1620 - only this software worked for me,earlier Versions i tried ( v.3.1636 ) always showed an Error.
Current Status: Phone is still connected to pc, fastboot mode, oem has just been unlocked by yourself.
What to do now:
12 Open the SPMultiPortFlashDownloadProject, load scatter file of the Ulefone Power 2 Firmware, then press scan. Nothing will happen now, so be quick: Don't disconnect your phone.
Press Volume Up + Power Button at the same time to simulate a new connection to the pc. While the phone is still connected via cable! We have to do this. You will now hear a sound which you normally would here when connecting a new device to your Pc. Now you just have to keep holding the Volume Up Key.
IMPORTANT:
Don't let go of the button until the Programm shows up a Green Tick which signals the end of the Process. Now you can let go of the button.
13. After the scan has finished, press start and flash firmware. But how? It's easy. Just do the same again. ->>
13.1 Press Start in the Flash Programm.
13.2 We have to simulate a new connection. Hold Vol+ and Power Button. Until you hear the sound again, now only keep holding the Vol+ Button.
14. Wait for the green Tick Notification. Until then: Don't you dare let go of the Vol+ Button. When it shows up, you're pretty much done. Congrats!
15. Restore NVRAM and NVDATA.[/I] through mtk engineering mode: open dialer and call *#*#3646633#*#* , scroll down to GRPS and type in your IMEI (can be found in the box, in which your phone came shipped with). If it says something like that it's successfully written.-> Activate Airplanemode, wait a few seconds, deactivate it, activate Mobile Data Connection and wait. It should show a mobile data active.
Download Links: (I didn't upload those files,i simply shared the links, all credits to their respective owners. Use at your own risk.!)
UP2 Rom: Google Drive
Flashtool for UP2 Rom: One Drive
UK6P 2.0 + Flashtool: Click me
Checksum Gen Zip: --Below--
ADB Components: --Below--
UPDATING:
After flashing V15 Ulefone Firmware, use the SP FLASH TOOL to flash the newest firmware via "Firmware Upgrade" mode. remember to keep pushing vol up before connecting phone!
How to:
Press Download in Tool
Push and hold vol up
Connect cable to pc.
wait until green tick shows up.
Profit.
Same situation here. I've tried flashing with and without battery, no success. I can confirm that I did NOT lock the bootloader. Not that it helps me much.
I've tried using different versions of SPFT in addition to the multiport tool, but they either don't work with Power 2 scatter file, or show the same error.
This can potentially be a driver / USB issue, so I will probably try that next (different computer, fiddle with the drivers). I've also seen claims that SPFT v3 can happily flash over this, and then newer versions start working too, so try that if you can. It did not work for me - the download never starts on my computer with v3.
I can also add that I can flash preloader as well, although I try and leave that off when possible. The modem and lk* partitions show the same error you have, though, and the phone is dead.
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
7. Restore NVRAM and NVDATA.
Hope this helps somebody.
Thanks for your reply!! I will try that and report back ! I'm so glad there are people out here who help !
EDIT: OMG, You are my hero!!! The Flash Process went just fine, no errors. It boots up. Thank you so much! Now i can flash like a devil again, haha
EDIT2: So i could use the phone with the oukitel rom but i want the original rom, firmware.
So here is the other Problem. I can't flash them. I either get insufficient buffer error or the imghdr error.
Could you link me what you are using? I really need the phone. Thanks for your help in advance.! :S
Hi sm00th4f3
I add some advices to Vivanyok instruction by red letters --->
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
OR enabled usb debug, accept connection between your PC and Ulephone and send command
fastboot reboot bootloader
after that
fastboot oem unlock
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
on this step i had a lot issue with insuffitient buffer under SP Flash tool, but yesterday i win too.
be careful :
after oem unlocking you should NOT reboot ulephone to Android,let phone stay connected to PC
try use #SPMultiPortFlashDownloadProject version 3.1620 - only this soft help me,earlier i tried v.3.1636 but always error appear.
and when i started flashing i stayed ulephone connected to usb (i dont disconnect phone after oem unlocking) and i simulated connection by long press volume UP + Power buttons. You can control connection by default PC sound.
due in SPMultiPortFlashDownloadProject other interface i did not change flashing type, it was firware update by default.
After that my ulefone become alive.
7. Restore NVRAM and NVDATA.
good luck, if any questions ask me on 4pda.ru
So, i tried your nice guide, and it finally worked!! Side Note is: After fastboot oem unlock you have to scan with the #SPMultiPortFlashDownloadProject version 3.1620 your phone first, and then like you have already said, use the volume up+power button combo to simulate a connection. and then it will be flashed. Holy crap. Thank you so much!!.
You are welcome, last three day i also tried flash my up2
Still same problem
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
bletru said:
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
Click to expand...
Click to collapse
Look in your inbox, i wrote you a private message.
bletru said:
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
Click to expand...
Click to collapse
That will help many others like me.please post the ule stock rom you flashed and the flash tool.
SUNRAY888 said:
Hi sm00th4f3
I add some advices to Vivanyok instruction by red letters --->
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
OR enabled usb debug, accept connection between your PC and Ulephone and send command
fastboot reboot bootloader
after that
fastboot oem unlock
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
on this step i had a lot issue with insuffitient buffer under SP Flash tool, but yesterday i win too.
be careful :
after oem unlocking you should NOT reboot ulephone to Android,let phone stay connected to PC
try use #SPMultiPortFlashDownloadProject version 3.1620 - only this soft help me,earlier i tried v.3.1636 but always error appear.
and when i started flashing i stayed ulephone connected to usb (i dont disconnect phone after oem unlocking) and i simulated connection by long press volume UP + Power buttons. You can control connection by default PC sound.
due in SPMultiPortFlashDownloadProject other interface i did not change flashing type, it was firware update by default.
After that my ulefone become alive.
7. Restore NVRAM and NVDATA.
good luck, if any questions ask me on 4pda.ru
Click to expand...
Click to collapse
cannot find the up2 rom which can be flashed after flashing Oukitel K6000 Plus ROM. Please help...
Download Links added. There shouldn't be any problems using my method as long as you think as well.
Be aware that you have to use the Flashtool i linked, the exact same Flashtool Version as mentioned. Otherwise go to my german thread outside of xda to get more detailed pics.
solved my problem
this was the solution for me, thanks a lot....
recovered!
Hello guys! Thanks for the instructions, it worked great! Only thing, the fastboot you supplied has an password, so I used another I found online.
I finally got time to take care of my bricked Power 2 phone, and I got it back to life using the Oukitel method.
The phone works great, I only had to input IMEI numbers manualy.
Is there a need to lock back the bootloader, because now my device says "orange state", your device cannot be trusted?
hm hm.... fastboot allows me to lock the bootloader, but then the phone would reset itself to factory state for security reasons, so I will leave my bootloader unlocked, as I don't want to go trough the phone app installation and getting the settings to my taste
i just updated the zip..there shouldn't be a password anymore. ^^
For us, there isn't really a need to lock the bootloader. Since we can simply install every ota update by downloading the new rom from external sites. Just a reminder: don't use the ota update app since it will brick or just not work, since your bootloader is unlocked.
Ulefon power 2
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
brumen1 said:
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
Click to expand...
Click to collapse
don't forget to enable oem unlock (bootloader isn't unlocked yet after you do this)
then fast boot the phone with oukitel rom, unlock the bootloader with adb fast boot unlock
don't let go of the vol button while flashing the phone with multiport flash tools
don't use ulepfhone original cable, mine was not working ok although there was no visual damage to the cable. I used another one that fit the usb port on the phone more firmly
bad_ri said:
don't forget to enable oem unlock (bootloader isn't unlocked yet after you do this)
then fast boot the phone with oukitel rom, unlock the bootloader with adb fast boot unlock
don't let go of the vol button while flashing the phone with multiport flash tools
don't use ulepfhone original cable, mine was not working ok although there was no visual damage to the cable. I used another one that fit the usb port on the phone more firmly
Click to expand...
Click to collapse
The Original Cable is fine...the problem might only be with yours.
brumen1 said:
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
Click to expand...
Click to collapse
Read the thread, it's not that difficult.
sm00th4f3 said:
The Original Cable is fine...the problem might only be with yours.
Click to expand...
Click to collapse
maybe, just told what happened in my case, the original cable was bad from the first day
good luck with the flash
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?