The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1
Related
I would like to know if someone could make a custom recovery and a stock version of android that I could put on my Blu Pure XR. I don't care if get rid of the 3d Touch on the phone. I just would like to have the stock android interface again and probably also the ram management will be better on the stock version.
I have the same request, would love to see TWRP. I'd like to install pixel launcher as system app and remove the adsup fota spyware.
The Pure XR is otherwise a great phone. Power management on stock is fantastic, i can get 6-7 hours of screen on time.
The Pure XR is essentially a Gionee S8 but sadly I dont see any custom recovery or development interest for that either.
Include me as well. Thanks
So the Pure XR is similar/same to the Symphony Helio S20...
There's a thread here that has a working twrp: https://forum.xda-developers.com/android/general/how-to-root-symphony-helio-s20-t3491123
I tested the recovery.img by loading it with fastboot without flashing and it worked!
You'll need adb/fastboot and the drivers first. Then boot the phone into fastboot mode by holding power + Up keys.
Select fastboot. After that, run: fasboot devices to make sure your phone is detected. Once detected:
fastboot oem unlock
reboot the phone, it'll do a force wipe
hold power+up keys again and boot to fastboot mode
Now, run this on your PC: fastboot boot recovery.img
Once the image is transferred, the screen goes blank...wait a min or two and TWRP will show up.
rom/firmware blu pure xr?
Anyone found a good stock ROM/Firmware for the Blu Pure XR?
if you finde one just tell us
ishman27 said:
Anyone found a good stock ROM/Firmware for the Blu Pure XR?
Click to expand...
Click to collapse
if you finde one just tell us
exciter0 said:
So the Pure XR is similar/same to the Symphony Helio S20...
There's a thread here that has a working twrp: https://forum.xda-developers.com/android/general/how-to-root-symphony-helio-s20-t3491123
I tested the recovery.img by loading it with fastboot without flashing and it worked!
You'll need adb/fastboot and the drivers first. Then boot the phone into fastboot mode by holding power + Up keys.
Select fastboot. After that, run: fasboot devices to make sure your phone is detected. Once detected:
fastboot oem unlock
reboot the phone, it'll do a force wipe
hold power+up keys again and boot to fastboot mode
Now, run this on your PC: fastboot boot recovery.img
Once the image is transferred, the screen goes blank...wait a min or two and TWRP will show up.
Click to expand...
Click to collapse
When I connect the phone through Fastboot and enter the command "fastboot devices," the phone is never recognized. I'm using Windows 10. Any help would be appreciated.
I used Linux instead. Have you installed the mtk and adb windows drivers?
exciter0 said:
I used Linux instead. Have you installed the mtk and adb windows drivers?
Click to expand...
Click to collapse
Yes, I installed the mtk and adb drivers however while adb works and detects my phone, fastboot does not.
Ok, I attempted using the SP Flash Tool on Windows 10 and successfully installed TWRP and rooted the phone. The only flaws are that the phone takes a few minutes to load into TWRP and unfortunately, there are still no custom roms on the device. It is a good start however.
Galaxxus_Rosarrius said:
Ok, I attempted using the SP Flash Tool on Windows 10 and successfully installed TWRP and rooted the phone. The only flaws are that the phone takes a few minutes to load into TWRP and unfortunately, there are still no custom roms on the device. It is a good start however.
Click to expand...
Click to collapse
Hey bud, big favor, would you describe step by step the rooting process, I used SP Flash Tool on windows 7 to install TWRP and it gave the ok check marK, then I tried to boot into recovery and I found out that TWRP was not installed. Do you have to unlock the bootloader to be able to install TWRP using SP Flash Tool? Thanks in advance.
Sent from my SM-G935T using XDA-Developers Legacy app
Hello everyone, I need your help, I've been trying to unlock my bootloader to root my phone, under setings I have developer options-OEM UNLOCK, but I only get as far as FASTBOOT MODE using my laptop as well as my pc, I tried this process with Windows 10, Windows 7 and latest Ubuntu. I tried different data cables, different usb ports 2.0 and 3.0 and nothing seems to work, I can put the phone on FASTBOOT MODE with my pc or lap, but then after that it looks to me that there is no comunication between my pc and phone. I installed all drivers several times and under DEVICE MANAGER everything looks good, as far as data cables I'm using 2 blu original data cables as well as aftermarket ones. Any help will be appreciated. Thanks in advance and have a good day.
Sent from my SM-G900T using XDA-Developers Legacy app
oscarmaldonado said:
Hey bud, big favor, would you describe step by step the rooting process, I used SP Flash Tool on windows 7 to install TWRP and it gave the ok check marK, then I tried to boot into recovery and I found out that TWRP was not installed. Do you have to unlock the bootloader to be able to install TWRP using SP Flash Tool? Thanks in advance.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I remember something similar to this happening to me when I used a different version of SP Flash tool. Try SP Flash Tool v5.1624.00.000. After this make sure you have the scatter file for the MT6755 as well as the recovery file for the phone. Make sure that you have selected the scatter file for the phone and that the recovery.img is in the same directory as the scatter file.
Once this is done, make sure that you have installed the preloader or VCOM driver for the phone. This is tricky as the opportunity to apply the correct driver comes when you are powering on the phone and in this time you must click on the device that pops up in this time, right click it, and click properties.
Once this is done, go back to SP Flash Tool and click download, your phone must be off and unplugged before doing this. Then after this step, plug in your phone and the download process should begin (this might take a while). After this, boot into recovery mode which also will take around 3-5 minutes maybe more. After this you will have TWRP installed and from there you can install various apps including SU.
Galaxxus_Rosarrius said:
I remember something similar to this happening to me when I used a different version of SP Flash tool. Try SP Flash Tool v5.1624.00.000. After this make sure you have the scatter file for the MT6755 as well as the recovery file for the phone. Make sure that you have selected the scatter file for the phone and that the recovery.img is in the same directory as the scatter file.
Once this is done, make sure that you have installed the preloader or VCOM driver for the phone. This is tricky as the opportunity to apply the correct driver comes when you are powering on the phone and in this time you must click on the device that pops up in this time, right click it, and click properties.
Once this is done, go back to SP Flash Tool and click download, your phone must be off and unplugged before doing this. Then after this step, plug in your phone and the download process should begin (this might take a while). After this, boot into recovery mode which also will take around 3-5 minutes maybe more. After this you will have TWRP installed and from there you can install various apps including SU.
Click to expand...
Click to collapse
Thank you very much, I'm gonna give it a try as soon as I get a chance, I'll report back. Thanks again.
Sent from my SM-N910T3 using XDA-Developers Legacy app
Hi everyone, TWRP has been released by lopestom here https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
Since the Pure XR threads are very slim here I thought I'd post this here.
Seems my XR's data has got very slow, signal strength weak, etc.
Trying to figure out if this is Cricket or something up with the phone. My wife has a Blu Life one X3 and the same Cricket and her signal and data speeds are always better than mine.
What are some things to check/look for? I've tried a few like manually choosing the Network, changing the APN settings, etc.
Any further advice would be greatly appreciated.
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:
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
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
EFAYSAL said:
Hi...
I try to root my FL02 (ALCATEL FLASH PLUS 2) every thing goes perfect and i get ORANGE STATUS but at the last step when trying to flash the rom with TWRP it could not read the SD card and system folder isn't abel to wipe so i try to repeat steps again.
first flasing in the video done and mobile restarting. no logo on screen and it doesnt boot and cannt go in boot mode or fastboot mode.
it connect and disconnect with PC but i still can connect it to flashing programme and i can send flash from PC but it doesnt boot and nothing appear on the screen.
any help....
Phone : FLASH PLUS 2
N D1M N7KE 03 TJZ
ANDROID 6.0
I follow this video to root
youtube.com/watch?v=d8zPGPJ_uZY
Click to expand...
Click to collapse
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
SubwayChamp said:
Ok, tell me to can help you;
Do you have TWRP installed?
Do you unlock bootloader succesfully?
In which modes you can enter? fastboot, recovery, download (do detects SPFlash Tool?)
Click to expand...
Click to collapse
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
EFAYSAL said:
Thank you SubwayChamp for help.
No , TWRP is not installed now .
Yes, I think bootloader has been unlocked. It is done with Orange status.
I think it is in download mode. it detects SPFlash.
Click to expand...
Click to collapse
Ok, I guess that your device is actually in bootloop and don´t booting.
Tutorial that you followed has many steps and don´t need to do all this to just root device and it contains some files like lk.bin that you can´t be sure that should be for your device.
Some users use this file (lk.bin) of an unlocked device and think that flashng in other device then get unlock it but no need, your device can be unlock it just follow some commands in fastboot mode.
Now you can do the next;
Try to flash again your rom stock (I guess that you don´t have a backup), if for some reason your official tool doesn´t work then use only some images like boot, system and userdata with the scatter.txt to flash them through SP Flash Tool.
Here a link to TWRP https://youtu.be/6vj_BY6xJdA, you can root it with supersu v2.78 0r v2.82 and here some files that can be usefull too https://drive.google.com/uc?id=0BwJgeCYTpnEHNlg2VUlieHFTYVU&export=download
Update steps that you are following to can assist. What extension has your rom and if it is recogniced for SP Flash Tool. I didn´t ask you if you can enter to fastboot mode and if you can then you can know if your bootloader is unlocked typing fastboot oem info
Most info that you give and some screenie will help to understand better
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
EFAYSAL said:
Unfortunatly, it can not enter to fastboot or recovery mode. Those files in replay didn't work and i dont have a backup. I try to flash recovery.img, system.img and preloader_shine_plus.bin . All done but it still black screen and does not boot. But now it connect to Pc without disconect .
I cant add link or images to my post.
Click to expand...
Click to collapse
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
SubwayChamp said:
Gmail didn´t warn myself about your post. Did you solve it?
You said that flashed recovery, system and preloader but how, through SPFlashTool?, if yes, are you sure that this tool recogniced your device?
You forgot to flash boot.img too.
Other way to try; flash only preloader.bin and then try flashing boot, system and userdata that are the three most important partitions to can boot.
Like last resort you can do a Format all + flash but only like last.
Click to expand...
Click to collapse
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
EFAYSAL said:
first of all thank you for your help. I was busy last week .
Yes it was with SPFlash and it is show MT6775 when mobile connect . but if i try flashing boot it gives an erorr and cant flashing.
I think i have a wrong boot file.
I miss userdata file.
Do you know where can i download necessary files for this model?
I apologize for delaying. It is time for school examin
Click to expand...
Click to collapse
I´m not sure if you are connecting correctly your device at right time and form to can flash it properly. Every device has more or less a specific way to do it. My last alcatel it was connected just with device power off and after to tap on download, but in other device Blu Dash was connected pressing just vol_up and my last mt6757 Bluboo had to press both vol up and down at time to connect to pc and after to tap on download option. To have sure that is well done increase volume in your pc, you will hear a first sound that is cause pc is recognicing but then you have to hear a second sound that is when SPFlashTool is recognicing device and you will see a red line in down side of the tool window, release button inmediately and let tool to work.
This is a good rom for your device according the author is optimized https://droid1311.blogspot.com/2017/08/alcatel-fl02-aka-flash-plus-2-via.html and this is the link directly if you have troubles with pop-up-adds https://drive.google.com/file/d/0BwAGh1drb91SeDZwV1VXbXpjQWM/view
Also you can try with other versions of SP Flash Tool, most stable maybe should be v5,1628 https://androidmtk.com/smart-phone-flash-tool leth me know how you go
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
SPFlashTool 5.1628:
I try all the way with and without pressing any button but no luck . And when it work finishing with error.
SPFlashTool 5.1628:
I try all the way to get that mode but nothing works. So I try to click download button then conect the phone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
EFAYSAL said:
If I understant, the status bar has to be red then I will release the mobile button and click download in SPFlashTool.
I try all the way to get that mode but nothing works. So I try to click download button then conect the pkone by random buttons and every time i get red color , yellow , green ,purple , yellow (for many times 100%)
then i get this error:
ERR: STATUS-SEC-IMG-TYPE-MISMATCH (0xC002002A)
Click to expand...
Click to collapse
There is a part that is not variable in the way to use this tool, ever you have to tap on download before to connect device and is recommendable too connect cable usb to pc (not yet to device); from here is when the button that you have to press can vary but like I said you before in my last mt6757 (a very similar to yours) works pressing both vol at same time to connect terminal cable to device and now you will see a red line (could be violet-ish)
Try before just flashing only preloader file to recreate some partitions and then do other flash for the other files.
Of course you have to be sure that all drivers are installed correctly cause this tool needs to put your device in download mode (a special level) and also keep it in this state so find VCOM drivers for Alcatel and adb/fastboot installer and try to uninstalling some older drivers that you don´t use and many times we keep in our pcs and for a short data transmission can helo that all the rom move it in same folder where SPFlashTool is allocated.
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
EFAYSAL said:
After updating drivers and trying all the possibilities buttons the red line doesnt appear.
Click to expand...
Click to collapse
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
- In what android version are you, 6.0?
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
- Did you try to flash just preloader, only this file?
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
SubwayChamp said:
Ok, here there are somethings that we need to know
- First of all don´t forget to charge your battery, after many attempts could consume a lot.
- Your device is recogniced in fastboot mode? mtk has two variables ways to enter to, pressing both vol + pwr till an options menu appear, then you have to select, and the other method most known is vol down+ pwr to go diirectly
Click to expand...
Click to collapse
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
SubwayChamp said:
- In what android version are you, 6.0?
Click to expand...
Click to collapse
Yes, last time it was 6.0 before the root
SubwayChamp said:
- What is the exact variant of your device, you can know maybe seeing in the box, this rom is for 5095K version 6.0 MM
Click to expand...
Click to collapse
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
SubwayChamp said:
- Did you try to flash just preloader, only this file?
Click to expand...
Click to collapse
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
SubwayChamp said:
If SPFlashTool don´t give signals of recognicing device is probably that your device is not now totally power off, try pressing pwr by 7 seconds, then try to flash again combining both vol with pwr button
Upload some screenshot about the process
Click to expand...
Click to collapse
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
EFAYSAL said:
Which option mode should appear? Screen is always black (off) all that i have on the phone is the LED.
I try more than 4 different drivers for Alcatel Flash Plus 2 (vcom & cdc) but no sound from SPFlash to prove that it recognise the phone. Sounds just release and keep relrease from Windows 10.
Yes, last time it was 6.0 before the root
Unfortunatly, I dont know . There is nothing on the box or manuel.
that is what i found on the box :
FL02
Venus gold H-B
FL02-2HLCEU2
- PWR+VOL(+) : reset the phone
It is done. all that i have to do is to tab on Download and then connect the phone and I dont need to press any button.
I did that but it is same.
Note:
Success fash always done without pressing any button on the phone. and I try it with and without buttons sometimes it is fail when I press a button and otherwise it work.
I have formated whole fash.
Click to expand...
Click to collapse
You need to try two different ways to flash files and restore your device.
First method: fastboot mode
You need to get device enter to fastboot in order to flash some files like system, boot and userdata, then there are two main methods to do it:
- Pressing pwr + vol down
- And I mentioned that sometimes work pressing both volume button + pwr and a menu have to appear to can select an option to enter to (fastboot mode), in some devices this method is not working but you have to try several times attempting to.
Second method: SPFlashTool
You have to ever press first of all Download box and connect terminal cable to pc and the buttons thhat you need to press at time to connec cable usb to your device may vary, sometimes vol down, sometimes both vol but never pwr button; if pc recognice then you have to release all buttone an let it pc continue the flash process.
If SPFlashTool recognice device first flash only preloader file and select now lk.bin too. Flash only these two files and after do again a new flash with the rest of the files, Why you need to do this? your partitions are corrupted and you need to restore them with these files in order to can flash all another files.
Before all of this charge your battery, if you have a cover removable then extract it some minutes and put it again.
Also I read that for this model it´s used this tool instead of SPFlash Tool https://androidmtk.com/download-sugar-mtk-sp-flash-tool (inside the zip you will find a password to start the tool) but I´m not sure what kind of rom it needs, you have to connect your device to begin the process, you will find in product models section in the tool this variant for your device "FL02"
Try first the other tool and then this and let me know how you go, mtk devices are almost unbrickeable so it´s just to find the appropriate way to return it to the life.
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
EFAYSAL said:
Hi again!
It was along time,I know . But I tried to know why I can’t return my phone back to life.
I have searched all possible websites for rom of this model and I have formatted my pc and installed win7 with all necessary drivers.
I can’t found any rom for it but now I can flash all the necessary files for boot they flashing and running smoothly but the mobile can’t boot up.
I try to use that app in your replay. It recognizes the device but stuck after that and keep looking for rom without any chance to download it.
I think I have a wrong rom files. I can’t find any other reason but this.
I will write again all information about my phone:
It is called Alcatel Flash Plus 2
I bought it from AliExpress and it came from Indonesia as I remember (not sure)
On battery wrote:
FL02
TCL communication Ltd
FL02-2HLCEU2
Click to expand...
Click to collapse
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
I understand that you tried with Sugar tool with no lucky.
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Is there some custom development, recovery, roms for your device?
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
SubwayChamp said:
Yes, so many time
When device is booting, it stays in bootlogo or goes atleast to bootanimation?
Click to expand...
Click to collapse
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
SubwayChamp said:
I understand that you tried with Sugar tool with no lucky.
Click to expand...
Click to collapse
Yes. After recognizing it keeps trying to download data but no luck.
SubwayChamp said:
Did you try again through SP Flash tool? trying to flash in a first attempt only preloader file and in a second attempt the other files? (try with 2 or 3 versions and see the differences).
Click to expand...
Click to collapse
I know it is disappointing!. I try this but no luck.
SubwayChamp said:
Is there some custom development, recovery, roms for your device?
Click to expand...
Click to collapse
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
SubwayChamp said:
I think that now you are flashing correct rom through fastboot but like you did before bad/wrong flashings your bootloader is refusing to boot to system. Flash through fastboot all the partitions that you can follow the syntax for every one of them by i.e. typing fastboot flash cache cache.img and so on one by one (some of them are unflashable through this method)
Click to expand...
Click to collapse
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
EFAYSAL said:
Unfortunately, nothing happens. The screen is black no bootlogo appears or anything that shows that device is booting. It is looking like nothing has happened.
Yes. After recognizing it keeps trying to download data but no luck.
I know it is disappointing!. I try this but no luck.
Unfortunately no, all that I found are TWRP recovery Roms. I don’t know if I can use them with SPFLASH Tool.
I began lose hope that the mobile could work again. I live in Sweden and no technicians kan help me to fix this issue. I should do it by myself.
If you kan help me to do that step by step. Please write to me what I have to do from the beginning step by step until I reach the end. To be sure I'm doing it by the right way.
Thanks
Click to expand...
Click to collapse
I´ll tell you some ideas with no any specific order that you can try or see if works.
Really very strange that display stays in black, you told me that flashing files through fastboot is working but doesn´t appear not even bootlogo, connect to pc as it is and see how pc recognices in devices manager and my pc if appears like a determined drive d/e/f so it looks that some bad flashing burn your kernel and this case is similar to when a Samsung device need to use jtag method to revive, if in your country no-one knows about Alcatel devices this could be a similar case to what I´m saying then it could be a clue for a technician. I tell you this cause many time ago when I flashed by error a Samsung s4 and only this method revived my device.
Try this, flash your stock recovery only through SPFlash tool and flash after through Alcatel Download tool your stock rom cause some firmwares need to detect stock recovery first to can flash other partitions.
At this stage don´t you have stock recovery, no? so you can try to format data cause sometimes when bootloader is altered then avoid to boot and formatting data can solve this.
If this recovery twrp is for your device you can try flashing through SPFlash tool, you have to put recovery.img and scatter-txt in a same folder. then if succesfull format data, system, wipe cache and dalvik and maybe later try to port some custom rom would be a way to solve this.
To flash any partition through fastboot this is the syntax, just follow one by one any of the files that are in your rom folder so just follow these, if some of then can´t be flashed don´t worry then it´s not flashable:
fastboot flash boot bot.img
fastboot flash cache cache.img
fastboot flash lk lk.bin
and so on till the end
...But after try this if you didn´t get boot to recovery and obviously you can´t delete data nor system then delete first the next partitions trough fastboot typing:
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase boot
Try all this and let us see how it goes
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
EFAYSAL said:
I have flashed TWRP Rom but it is same , no luck.
On sugar tool I got this message after success flashing via SPFLASH tool.
View attachment 4518365
I tried all possible buttons to connect device to PC on Fastboot mode but the PC cannot send data to my device.
To be in Fastboot mode , the device has to boot while pressing on (PWR & VOL+) but my device can’t boot.
Click to expand...
Click to collapse
I see that Sugar tool detects your device like rooted and refuses to flash anything, compare imei number which is in the box, I hope that it couldn´t be changed.
Don´t tell me simply no luck, what it says in SPFlash tool when you tried to flash TWRP and I guess that you put scatter-txt and twrp renamed recovery.img simply in the same folder. Just to be clear, to can flash with this tool your device it has to be off not needed fastboot for this. (provide some screenie)
Other combination of keys to enter to fastboot to flash some partitions when something is missing is, try these three ways:
- Pressing only vol down and at same time connecting to charger (connect first one terminal of cable to your device and then to the charger)
- Pressing the three buttons till a menu appears (you must to release inmediately all)
- Pressing vol up + pwr till a menu appears (you must to release pwr button inmediately) then choose fastboot
In the post 4 I provided a link from Google Drive, in this zip there are 8 items;
- From the item 2 use this version of SP Flash tool, put the four files in a folder and flash them
- In the item 3 you will find some scripts for fastboot, maybe they´re working better and also you have here a subfolder with twrp image.
- And if you get sucessfully install twrp in the item 7 there is a backup with some files to restore from this recovery.
Try one by one and update the info, I hope that your motherboard is not damaged.
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?