hello all
i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or downgrade from newer version for any reason.
This will erase all user data.
1. do it on your own risk, I'm not responsible for any damage to your devise.
2. Unlco your bootloader here is the steps by earthCallingAngela ----->>> Here
3. if you having issue to connect your drive to your computer while on bootloader you can install Intel driver, its worked for me, ----> Here
4. now install Intel Phone Flash Tool, i think it will install drivers as well, download it from here
5. Download Yoga book YB1-X90F Stock Rom Uploaded by Flippy498 from here
6. open Intel Phone Flash Tool and boot your phone on bootloader by Vol Up + Power, you should see the tool detect your Tablet.
7. on intel tool click on brows and located the Rom, wait for the tool to unzip it,
8. do not change anything just click on Flush and wait for it, on the middle of the process the tablet will ask you if its ok to wipe user data choose yes
after that the tablet will reboot and finish the installations and power off itself, power it on and wait for it, its will take long time for first boot so do not power it off.
Halo keyboard will not work until you do these steps By vimalbhimani on here
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) a list of country codes will po up, browser the country code list, then chose country code US and click OK
e) Then device will reboot and update, you should be able to use halo Keyboard after that.
note: i have issue with TouchPl keep stopping, had to chose google instead of Lenovo to get it to work without error
if you want to update the system to latest version (7.0.1) you can just go to update and update it.
if you have something to add please do
Thank you all.
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Flippy498 said:
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Click to expand...
Click to collapse
Thanks Flippy for sharing the steps with us.
can i downgrade from Nougat to Marshmallow？
microbai said:
can i downgrade from Nougat to Marshmallow？
Click to expand...
Click to collapse
sorry for the delay, yes you can, just follow the steps.
ayad said:
hello all
i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or downgrade from newer version for any reason.
This will erase all user data.
1. do it on your own risk, I'm not responsible for any damage to your devise.
2. Unlco your bootloader here is the steps by earthCallingAngela ----->>> Here
3. if you having issue to connect your drive to your computer while on bootloader you can install Intel driver, its worked for me, ----> Here
4. now install Intel Phone Flash Tool, i think it will install drivers as well, download it from here
5. Download Yoga book YB1-X90F Stock Rom Uploaded by Flippy498 from here
6. open Intel Phone Flash Tool and boot your phone on bootloader by Vol Up + Power, you should see the tool detect your Tablet.
7. on intel tool click on brows and located the Rom, wait for the tool to unzip it,
8. do not change anything just click on Flush and wait for it, on the middle of the process the tablet will ask you if its ok to wipe user data choose yes
after that the tablet will reboot and finish the installations and power off itself, power it on and wait for it, its will take long time for first boot so do not power it off.
Halo keyboard will not work until you do these steps By vimalbhimani on here
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) a list of country codes will po up, browser the country code list, then chose country code US and click OK
e) Then device will reboot and update, you should be able to use halo Keyboard after that.
note: i have issue with TouchPl keep stopping, had to chose google instead of Lenovo to get it to work without error
if you want to update the system to latest version (7.0.1) you can just go to update and update it.
if you have something to add please do
Thank you all.
Click to expand...
Click to collapse
I followed all of the steps and it says "Flash Failed (Fastboot) PLEASE HELP
Edit: I fixed the problem by simply rebooting it. I didn't think it would be that easy.
SameSame, but L-Version ... cannot find Stock ROM ...
Hi there,
I would like to downgrade 2 Tablets YB1-X90L (not F), this thread is onderful BUT I cannot find the STOCK ROM version for the L-Model (the one with LTE) ... can someone point me out as where to get it ? The background is that Nougat screwes up the playstore ... as discussed in many other threads and there is no -permanent- solution... Thank you!
pwallenb said:
Hi there,
I would like to downgrade 2 Tablets YB1-X90L (not F), this thread is onderful BUT I cannot find the STOCK ROM version for the L-Model (the one with LTE) ... can someone point me out as where to get it ? The background is that Nougat screwes up the playstore ... as discussed in many other threads and there is no -permanent- solution... Thank you!
Click to expand...
Click to collapse
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Could someone please help me with downgrading my YB1-X90L, it just refuses to boot at all after my nephews messed with it, I found the stock rom but I can't get some of the needed programs and drivers,
Flippy498 said:
Here's an alternative method for those who don't trust flashing tools due to bad experiences and prefer flashing files manually via Fastboot (like me):
Follow steps 1. to 3. and 5. of the opening post.
Unzip the stock rom (archive) into your ADB/Fastboot folder.
Boot the tablet to the bootloader (c.f. step 6. of the opening post).
Use the following commands:
Code:
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot flashing lock
fastboot continue
Execute each of them with Enter and wait till a command got executed completely before you try to use the next one.
It might happen that you face an error while flashing that oemvars bootloader_policy-oemvars.txt. I couldn't find out why that happened and ignoring it seems to be harmless.
Follow steps a) to e) of the opening post.
Click to expand...
Click to collapse
Hello
I made this all and my Yoga-Book runs on Android 6.0.1 . But is there a possibility to get an Android Build 7.1.1? Because I can't restore my Backup it seams it is corrupt and if I try to update im configuration-app its does anything but at the end its allways on 6.0.1.
It would be great if someone can helb me.
Best regards
Peter
borisattva said:
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Click to expand...
Click to collapse
sorry for replying to such an old post.
could you or anyone else please reupload a 6.x stock rom for the yb1 x90L? i just cant find any working link and am currently stuck with a device without properly working wlan. wlan keeps turning itself off after a few seconds after reboot and only restarting the whole device can turn it back on again... i hope a rollback can solve the issue...
phsma said:
sorry for replying to such an old post.
could you or anyone else please reupload a 6.x stock rom for the yb1 x90L? i just cant find any working link and am currently stuck with a device without properly working wlan. wlan keeps turning itself off after a few seconds after reboot and only restarting the whole device can turn it back on again... i hope a rollback can solve the issue...
Click to expand...
Click to collapse
looks like the original link is down, so i searched for the file name YB1-X90L_USR_S110085_1710170829_WW08_EP_ROW_otafull.zip and this came up:
YB1-X90L_USR_S110085_1710170829_WW08_EP_ROW_otafull.zip | Easy Firmware
easy-firmware.com
ive no idea if this is working or safe to use but its a start.
good luck
So my Android YB1-X90F was locking up when trying to boot, just stuck showing the Lenovo logo. Thinking I'm clever I stubbled across the boot menu if you start the device with the Volume Up held. From there I tried the Recovery Mode and did a Factory Reset. Then the tablet started up and shows the Green Andriod Bin Man, saysi Encrypting and promptly reboots. So one starts Googling and ends up here. Some very help information, thanks for that.
So I've got as far as installing all the drivers/Intel Phone tool/Android Suite etc. but I'm still stuck. The flash is locked. Is there another way to unlock this as I can't get into Android to allow the developer options as suggested in Step 2 of the opening post?
Trying the fastbook commands in post 2 also fail
Code:
FAILED (remote: Prohibited command in locked state.)
finished. total time: 0.170s
TIA
LOL @ me, of course the manual fastboot commands fail as that's precisely what the Phone Tool App trying when doing its magic.
galumph said:
So my Android YB1-X90F was locking up when trying to boot, just stuck showing the Lenovo logo. Thinking I'm clever I stubbled across the boot menu if you start the device with the Volume Up held. From there I tried the Recovery Mode and did a Factory Reset. Then the tablet started up and shows the Green Andriod Bin Man, saysi Encrypting and promptly reboots. So one starts Googling and ends up here. Some very help information, thanks for that.
So I've got as far as installing all the drivers/Intel Phone tool/Android Suite etc. but I'm still stuck. The flash is locked. Is there another way to unlock this as I can't get into Android to allow the developer options as suggested in Step 2 of the opening post?
Trying the fastbook commands in post 2 also fail
Code:
FAILED (remote: Prohibited command in locked state.)
finished. total time: 0.170s
TIA
LOL @ me, of course the manual fastboot commands fail as that's precisely what the Phone Tool App trying when doing its magic.
Click to expand...
Click to collapse
I'm in the same boat. I acquired a YB1-X90F but all it does is show the orange Lenovo splash screen, then a black screen.
So here I am reading threads. But I'm already at my first hurdle...since I can't boot into the OS and go into Developer Options to start the boot loader unlock process.
YB1-X90F No OS(?) - Flashing Help
TL;DR: Noob needs to stock flash a device that won't boot into OS. Here's how the recovery looks (without and interaction): Boot loader: Splash screen: I have acquired a YB1-X90F that just shows the orange Lenovo splash screen and or a...
forum.xda-developers.com
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing
Edit: The Android N update bricks the device for some reason.
Brent.M said:
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing
Edit: The Android N update bricks the device for some reason.
Click to expand...
Click to collapse
any ideea why my yoga book is not visible in fastboot?
i installed drivers and platform lite indicated in drive location.
currently my yoga sbows bootloader error 05 during booting
Thank you @Brent.M I have a booting Yoga Book again
borisattva said:
found myself in the same boat and eventually came across this:
https://cloud.kolyandex.su/index.php/s/npeVhVlnJw8BFIy
hopefully it sticks around long enough for others to grab.
note that the steps are slightly different in that you have to manually select the .json in the extracted folder.
Click to expand...
Click to collapse
The link is not work anymore, could you please share you firmware for x90L model ? thanks
Related
Hello everyone,
This is my first post on xda and I've read some of the posts etc and I thought it's time to begin to start questions related to my problem. This will be kinda long post and I'll try to give as much as information from my device specs to what I did to my device up to this point so you guys can understand my problem maybe help me or simply you can say its bricked and I can done with it. And last, I'm kind of newbie with android environment.
As you can see from the title my device is 'Reeder a8i Quad tablet' which is currently in Turkey. Device specs are following:
Uses Intel atom bay trail, Android 4.4.4, TF card (similar to sd)
bootloader title says 'droidboot' and for the recovery there is no install from sdcard or something like that.
There is almost little knowledge with the device and official site is not helping ( I guess they don't care at all )
Some Turkish forums actually got some idea about rooting and flashing stock rom. ( Later in 2015-2016 they released 5.1 for the device and that's all ). Forums actually use old how-to's from reeder support with images how the process done for upgrading android system.
First I try to find some ways to root the device but unfortunately my lack of knowledge and almost no guide for root get me stuck in the first time. I had 4.4.4 android and I was looking at ways to root it. My friend used King Root to root an old samsung phone but later he deleted it and suggested me to use it since I couldn't find any other way. I give it a try and use king root and followed instructions and voila! I had root access on my tablet and quickly installed greenify, root browser, uninstall ( for stock applications and especially google apps ) and later I installed superSU with terminal. Now for the fun part. I did give all these apps root access and deleted stock apps including google apps and 1-2 apps that king root installed while rooting. After deleting google apps I screwed up and keep getting crash reports for some of the services. I didn't know what I did to that point for google so I simply wipe data and wishing reverting all the things. After boot, there is king root app, google services again crushing and tablet looked unstable. I installed root checker which gives me that no 'root access' so I opened king root app and it couldn't root with error messages. I installed gapps for 4.4.4 and google services returned normal. Connected my tablet to pc and use king root again to root. Again device is rooted. Installed same apps, deleted king root apps and entire google apps, services, etc from tablet. Now I got no problems with google, successful root and happy face.
After closing my tablet and opened some day I saw that I don't have root access and king root app again no help at all. Again connected pc, app seems unstable with says my device is rooted and sometimes says not rooted. There was something wrong for sure and again wipe data etc. But now I found reeder tablet stock rom from the internet ( website is closed just today! ) including tons of tools and drivers and roms for other devices including mine. It's not actually site just index so you just go in a folder click and download etc. Installed my drivers, I already had android studio so adb fastboot etc but I did download some quick tools for just for this. I remember my device couldn't open so I just did some things from adb and fastboot and after 1 day work it's opened with 4.4.4. But google kept crashing so I understand that I didn't flash a stock rom entirely. Again root with all the apps and I simply use the device for some apps.
Up to this point I want to call part 1 because after this may be 3-4 months passed and about 2 days ago I started to play with tablet again. Now I installed some network tools to play with. Trying to use some MITM or cookie stealing etc. I used tons of apps including kali linux's nethunter tools which I get from their zip file. Obviously some of them not work and some other are. Still my root is unstable one time it says rooted one time says not. So It kept bothered me but now I don't want to use king root tried to search other ways to replace it with supersu. There is a guide here to use a shell script but it didn't worked so I found an app to replace it. It says done but king root app kept crashing and this point is where I called point of no return ( at least for me ) I downloaded king root app to my pc and tried to root it. It says rooted and now reboot etc. After that nothing changed and still the same. Btw, before tried root I used fastboot to try to open bootloader with boot.img from stock rom but I don't know what it actually does so. Again app is crashing there is no root access so I wanted to install stock rom. There is a guideline for 4.4.4-5.1 for my tablet and there is a tool named 'Manufacturing flash tool v6+' from intel. But I need an OTG for that since I don't have one. Flashing tool uses an xml file. Since I have that from stock rom's folder. I thought give it a try but nothing happened and tool supposed to detect my device but it didn't. At that time I could use fastboot and adb without a problem so I assumed tool got some sort of bug and installed again but result were same. I tried to wipe data and reboot but I got recovery screen with '3E' error. I tried to get into recovery screen to use adb and do something. I desperately used fastboot flash boot boot.img, fastboot flash recovery recovery.img and system system.img from 4.4.4 but not only it failed with the error 'end of footer from /tmp/update.zip not 0xFFFF file exists' but somehow corrupt the device rom and now I was stuck with reeder logo with infinite loop. After that I wanted to give that manufacturing flash tool a try again and same result. I did buy an otg cable for tablet and for my phone which screen destroyed couldn't unlock since touch screen almost not working and usb debug is closed to open that phone as well. There are files from reeder help desk to upgrade it to 5.1. I copied those files to tf card and used otg cable on my keyboard. Guide says press ESC key until bot manager is coming up. There is a screen with bot manager including bios settings. Guideline and tools says it's for upgrading bios so I did those steps and now again recovery mode. Opened manufacturing flash tool with my 5.1 xml but no result so I found something under menu to 'Print flash file cmds' used it and it simply bunch of fastboot commands. I opened fastboot and executed all those commands one by one for myself. Eventually some of them are failed with 'fastboot oem unlock' etc. Since it's changed into flashing unlock which both commands give error from tablet 'unknown command' I followed steps. ( At the end of the post I will give the xml commands from manufacturing flash tool ) After that at I used 'fastboot flash esp_update' provided with esp.zip file successfully. After that 'fastboot flash fastboot droid.img' failed. Following with 'fastboot flash boot boot.img' 'fastboot flash recovery recovery.img' 'fastboot -S 200M flash system system.img' all those commands failed and couldn't install the 5.1 manually.
At this point if I wanted to open my device it simply tries to update bios with the same file ( if tf card inserted ) other than that still at recovery with 3E and adb sideload not working with the error I got above 'end of footer from /tmp/update.zip not 0xFFFF file exists'
I know that my post is long and tried to give as much as information as I can. I just hope device is not completely bricked and there is a way to solve this. Any questions about information about device etc you can shoot I try my best to answer. Thank you for people who are reading this to spare their time.
Manufacturing flash tool xml file commands and success or fail after I executed them in DNX mode ( volume up + down + power at the same time )
fastboot flash osloader "I861B1C_1601001_64_20160115\efilinux-userdebug.efi" - success
fastboot boot "I861B1C_1601001_64_20160115\droidboot.img" - success
sleep - failed
fastboot oem enable_oem_unlock - failed
fastboot oem unlock - failed
fastboot oem wipe ESP - success
fastboot oem wipe reserved - success
fastboot oem start_partitioning - can't remember
fastboot flash gpt "I861B1C_1601001_64_20160115\partition.tbl" - success
fastboot oem enable_oem_unlock - failed
fastboot erase system - success
fastboot format cache - success
fastboot format config - success
fastboot format logs - success
fastboot format factory - can't remember
fastboot oem stop_partitioning - failed
fastboot flash ESP "I861B1C_1601001_64_20160115\esp.img" - success ( After this point I assume device is rebooted and opened a screen which is kinda new with big green 'NORMAL BOOT' text )
fastboot erase keystore - success
fastboot oem verified - success
fastboot format data - success
fastboot flash esp_update "I861B1C_1601001_64_20160115\esp.zip" - success
fastboot flash fastboot "I861B1C_1601001_64_20160115\droidboot.img" - failed
fastboot flash boot "I861B1C_1601001_64_20160115\boot.img" - failed
fastboot flash recovery "I861B1C_1601001_64_20160115\recovery.img" - failed
fastboot -S 200M flash system "861B1C_1601001_64_20160115\system.img" - failed
fastboot continue - failed ( it says success but reboot never happened )
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 all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Jonsonrocky said:
Hi all, i have a problem that i can't solve, is the oem unlocking on my blu life one x2. I downloaded adb and fastboot (windows user), phone and adb drivers, and when i put the phone on bootloader mode, i run the "fastboot oem unlock" command, and the command prompt say: "need user wipe data, do fastboot oem unlock-go", so i put these command, and the oem is not unlocked yet, so I repeat those steps and the command prompt keeps showing me the same message (need user wipe data, do fastboot oem unlock-go). At this point, I have no idea what I'm doing wrong, I made the factory format many times, and I cannot unlock the OEM.
Can help me pls? I want to root my device, but because of this problem, I can not go to other steps :crying: :crying:
Thanks
Click to expand...
Click to collapse
any here? ...
Jonsonrocky said:
any here? ...
Click to expand...
Click to collapse
Hi there, I have THE VERY SAME PROBLEM. Done the same, with same lame results... BOOTLOADER STILL UNLOCKED!!
It is really frustrating... been through many posts and guides but can't finish them... fastboot OEM unlock with the user data eraser switch didn't work out well in any case.
IS THERE ANYBODY OUT THERE WITH A COMPLETE WORKING GUIDE WILLING TO SHARE IT?
Thanks in advance.
J.
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
pvkid said:
I have the same problem also, I have posted on another thread but no responses. here is my error:
"FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.003s"
Has anyone figured out how to onlock the NEW BOOTLOADER?
I have a new life one x2 that BLU sent me.
Click to expand...
Click to collapse
I guess no one knows the answer to this problem. This phone used to be rootable but I guess Blu changed something in their latest release of the Life One X2
How to root a Blu life one X2
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Thank you for this. I just left on vacation and will not be able to try this till next week, hope you are around then as I am sure I will have questions.
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
TWRP: https://drive.google.com/file/d/0B6_iuhJQH7aGM0JkOXJkUHdlRHM
MAGISK: https://www.apkmirror.com/apk/topjohnwu/magisk-manager/
STOCK: https://drive.google.com/file/d/0B6_iuhJQH7aGUFdVVkkzUk8yYWs
DRIVER: https://drive.google.com/file/d/0B6_iuhJQH7aGa3Q1cmN3eHI3QUE
DOWNLOAD: https://drive.google.com/file/d/0B6_iuhJQH7aGR05CSnlhWm1HWWc
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Any luck?
We have ROOT in BLU Life One X2
dougo007 said:
Any luck?
Click to expand...
Click to collapse
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Links aren't working
dougo007 said:
I actually still use this device and should be able to get you through this.
I'm not sure where are you on the device i.e. partly unlocked ect.
I'll start you from the top and I'll let you pickup wherever you like.
First, let's get our links ready (because I had these ready to go for myself).
I just checked it now, the device specific links still work.
ADB: Link works
TWRP: Link does not work
MAGISK: Link works
STOCK: Link does not work
DRIVER: Link does not work
DOWNLOAD: Link does not work
1) Download The driver, download program, and stock ROM.
2) Install the first two files.
3) Go to: C:\Program Files (x86)\Qualcomm\QPST\bin
4) When your device is off; Hold down the vol up AND down while turning on the device and wait until the text disappears
5) Plug in the phone to the PC and a red light should start blinking
5) Unzip the stock rom (when done, it can take a while).
6) Open QFIL.exe
7) You should see "(COM8)" on the top for the connection
8) Click on the first Browse button and select the mbn file from the extracted stock ROM folder
9) Click on LOAD XML and click rawprogram_unsparse_upgrade and then patch0
10) Click download until the phone reboots into test mode; click reboot to start the 'new' phone
-----------------------------------------------------------------------------------------------------------------------
1) Do the generic phone stuff to unlock the bootloader by enabling dev options and then enable BOTH OEM unlocking AND USB debugging
2) Download and install magisk from the link above and then download the zip file it gives you to flash
3) Download the TWRP image and ADB files listed above and do whatever you need/want to do (boot, flash, or both)
4) Flash the magisk zip file and your done
-----------------------------------------------------------------------------------------------------------------------
Delete the folders fota, fota-updater, and fire from the system partition in TWRP as these are the spyware/adware that BLU added
If you want to disable and other apps that BLU added, you can just rename the file from *.apk to *.ap
I'll try to be around if you have any questions
Click to expand...
Click to collapse
Hello dougo007,
Some of the links are dead and I am stuck and cannot figure out how to get passed the failed error on OEM unlock. It just keeps saying try unlock go.
Could you please provide new links or point me to someplace that I can use to oem unlock my BLU Life ONE X2. I searched and can't seem to find anything.
Having the same issue as you were and the links don't work
pvkid said:
Sorry it has taken so long for me to get back to you but I have been traveling out of the county and have not had time to try this.
I have been successful in rooting 2 Life One X2 phones with this prosses. One was new out of the box and the second one was an older one about 2 years old.
Thank you for all your help when no one ele knew the answer.
My next project is to root an Oukitel OK6000, there does not seem to be much information on this phone. If you hear of anything please let me know.
Click to expand...
Click to collapse
Hi pvkid, do you happen to have the files from the link? or new places I can find them I am stuck in the same place you were and can't for the life of me find anything anywhere else that helps.
Hi everyone,
first of all, I guess there should be a section dedicated to the Z5 to keep the forum clean!
Other than that, I'm really having trouble with my Z5. I can't find a way to move on from fastboot mode! Can't boot to edl, tried to flash recovery but they won't boot and so on...
Do someone has some idea? I can provide every information you need to troubleshoot that!
Thank you in advance,
Lorenzo Benevento.
Hi , inside stock firmware which .img files you have ?
Hello guys,
Could any of you create a brick troubleshooting thread in this model?
I need help with unbricking my Z5. I think I messed up with the recovery partition.
I can't turn it on at all after I press all the button combinations.
I tried the suggestions on the Sahara error that they did on the Lenovo Zuk Z2 with no success.
Does anyone have a workaround for this kind of thing?
edsmanco said:
Hello guys,
Could any of you create a brick troubleshooting thread in this model?
I need help with unbricking my Z5. I think I messed up with the recovery partition.
I can't turn it on at all after I press all the button combinations.
I tried the suggestions on the Sahara error that they did on the Lenovo Zuk Z2 with no success.
Does anyone have a workaround for this kind of thing?
Click to expand...
Click to collapse
Look here for steps that you can try ...
https://blogthetech.com/flash-file-lenovo-z5-l78011-firmware-download-stock-rom/
Good luck : )
Teddy Lo said:
Look here for steps that you can try ...
https://blogthetech.com/flash-file-lenovo-z5-l78011-firmware-download-stock-rom/
Good luck : )
Click to expand...
Click to collapse
Hello Teddy,
Thanks for taking the time to reply! Fortunately Rendroid15 helped me to fix it.
help
how do u fix it? i have the same problem here, please help
edsmanco said:
Hello Teddy,
Thanks for taking the time to reply! Fortunately Rendroid15 helped me to fix it.
Click to expand...
Click to collapse
Yes, how do u fix it? Share withy us.
xplozia said:
Yes, how do u fix it? Share withy us.
Click to expand...
Click to collapse
Join the telegram group: Lenovo Z5 Brasil, the guys there can help.
I used qfil to restore it.
I also used the video by rendroid. Send him a PM and he'll reply.
Hi there!
I've been trying out a few things and was wondering how on Earth you got it into fastboot mode in the first place? I can't find a way.
xplozia said:
Hello,
I bricked my Lenovo Z5. I need your help, please!
I installed from fastboot, Pixel Dust ROM and after that, the phone not starting. When I connect the phone to PC, I have message with Unlocking Bootloader (was unlocked initialy, on old rom) then Lenovo logo and after a black screen.
I downloaded ZUI_3.9.075_ST for Lenovo, I installed Qualcomm drivers, I installed Qfill but when connect the phone I don't have 9008 Port, to me is 900E. I read few forums about this error (https://zukfans.eu/community/threads...e-easily.3504/ and https://club.lenovo.com.cn/thread-3021991-1-1.html), I makeed a USB cable for DEEP Flash,I peeled the usb-c cable and touched Green and Black wires, but without success.
I installed a new Lenovo USB driver and with USB cable for DEEP Flash, I put the phone in the 9008 port, and Installed with successful, many ROMs 3.9.075, 3.9.200, 4.0.390 but every time after the first reboot appear message with opened bootloader then Lenovo logo and restarting to infinite.
When the phone is connected to PC I have on the phone a menu with "First Boot Mode" and the phone is accesible from PC:
"C:\Users\user>fastboot devices
bb806aa3 fastboot"
I will apreciate yours help. Thank you!
Click to expand...
Click to collapse
Did you follow this guide? https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/guide-how-to-flash-android-8-1-9-0-t3840839
Yes I see your post and I solved my phone
greetings,
im rookie here but once my MEDIATEK phone got stuck in fastboot mode and i fixed it with connecting to pc and type " fastboot reboot " in adb
edsmanco said:
Hello Teddy,
Thanks for taking the time to reply! Fortunately Rendroid15 helped me to fix it.
Click to expand...
Click to collapse
share the fix
Please refer to the replies above
Lenovo z5s stuck in fastboot
It's been a very long time since this thread was created, but maybe, with some hope i could get some answers, i have the same problem with the z5s, and i can't do anything, all because i mess with the recovery and i can't get out of the same, when i turn off my cellphone and connect a charger, my cellphone boot automatically into fastboot, i need some help, i don't even know if the telegram thing still exists
Thelostman said:
It's been a very long time since this thread was created, but maybe, with some hope i could get some answers, i have the same problem with the z5s, and i can't do anything, all because i mess with the recovery and i can't get out of the same, when i turn off my cellphone and connect a charger, my cellphone boot automatically into fastboot, i need some help, i don't even know if the telegram thing still exists
Click to expand...
Click to collapse
Before, you installed a new qfil rom? If yes, folow the instruction from https://forum.xda-developers.com/showpost.php?p=77583961&postcount=2 and install Pixel Experience:
2. fastboot flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
xplozia said:
Before, you installed a new qfil rom? If yes, folow the instruction from https://forum.xda-developers.com/showpost.php?p=77583961&postcount=2 and install Pixel Experience:
2. fastboot flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
Click to expand...
Click to collapse
Don't worry i've already solved with some CHINESE PIROMANCY!!!!!!! Even with effective IMEI restoration (I couldn't restore the 2nd IMEI because I didn't know how to set up this one manually with the method I've used with my lenovo)
Hello,
I have a Lenovo Z5s. I wanted to install new android rom like Pixel Experience
I managed to unlock the bootloader with adb fastboot.
I succeeded in flashing TWRP recovery 3.3.1-0529 for my device.
I've downloaded Pixe Experience GSI rom available here https://forum.xda-developers.com/z5...evelopment/lenovo-z5s-pro-twrp-3-3-1-t3953346
I have copied and pasted the Pixel Experience rom (.img file) on my SD Card.
With TWRP, I have wiped necessary files for a clean install.
I have launched the installation of the rom, installation was complete, the phone has reboot, I show Pixel Experience boot sequence with Google logo. The process asked me a password (Encrypted?) . I decided to reboot the phone.
Now, the phone is blocked with a bootloop in recovery mode. I can't access anymore to TWRP recovery. (Erased?)
To explain clearly the situation: I have the menu showing these options: Restart bootloader > Recovery mode > Power Off > Boot to FFBM > Boot to QMM I> Start
FastBoot Mode
PRODUCT_NAME - sdm710
VARIANT - SDM EMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - yes
DEVICES STATE - unlocked
No Bootloader, no Baseband.
All of the options return the phone back to the same menu.
The situation seems to be critical (phone bricked) and I can't do anything and I don't know what to do. Is there a chance to save my phone?
Your help will be precious to make my phone work.
Thanks in davance . Best regards.
Hey guys i am also in bootloop with unlocked bootloader ,can you please help us to save our phone !!!???
Hello. I Factory reset my Mi A3 while in my Google account not through recovery. Now when I boot the phone I get an error saying unable to connect to wifi when phone is connected to wifi and the when I try to add my Google account I get a message the The Google servers are unavailable and try again later. I did some looking and tried a few suggestions on line, about deleting Google app caches and delete account and add account. I deleted the phone in my Google account in my desktop and can't add it again, I turned off two step verification...it's seems like the phone isn't behaving at all right. I can get into the phone and a message will tell me to finish setting up and when I tap the message I go to the start up page. The phone isn't currently rooted but the bootloader is unlocked.
Thank you in advance for reading this far, please any help is appreciated.
I haven't experienced that problem myself, but if you have already factory reset your phone, then why not download the stock rom and flash it? That would reinstall your OS and may solve the problem. Do it from Android SDK platform-tools. You will need to boot your phone into fastboot mode.
Download the stock MIUI firmware fastboot image from: https://xiaomifirmwareupdater.com/miui/laurel/
Then follow the guide here: https://www.thecustomdroid.com/xiaomi-mi-a3-stock-firmware-guide/
Thank you for your reply. I was thinking about that and wasn't sure if it would help. I will try that and let you know how it goes.
bjlabuk said:
I haven't experienced that problem myself, but if you have already factory reset your phone, then why not download the stock rom and flash it? That would reinstall your OS and may solve the problem. Do it from Android SDK platform-tools. You will need to boot your phone into fastboot mode.
Download the stock MIUI firmware fastboot image from: https://xiaomifirmwareupdater.com/miui/laurel/
Then follow the guide here: https://www.thecustomdroid.com/xiaomi-mi-a3-stock-firmware-guide/
Click to expand...
Click to collapse
I was able to download files and flash however its ion a boot loop stuck on android one screen and ther fix at the end of the directions say to execute command to get a active however my computer return with fastboot is not a internal or external command or file. Please advise. I will look on here for fix too. Thank you
bjlabuk said:
I haven't experienced that problem myself, but if you have already factory reset your phone, then why not download the stock rom and flash it? That would reinstall your OS and may solve the problem. Do it from Android SDK platform-tools. You will need to boot your phone into fastboot mode.
Download the stock MIUI firmware fastboot image from: https://xiaomifirmwareupdater.com/miui/laurel/
Then follow the guide here: https://www.thecustomdroid.com/xiaomi-mi-a3-stock-firmware-guide/
Click to expand...
Click to collapse
Well I have gone from bad to worse. Now stuck on fastboot screen and bootloader locked. Ugh!
If you google "mi a3 stuck on fastboot screen etc" you should get a couple of suggestions. Can you boot into recovery? Press the power key and the vol. up key at the same time. Keep holding until phone restarts, then release the power key and wait for the Recovery menu screen to appear.
Also did you read the Important Note at the bottom of the instructions?
If the device fails to boot into the OS and keeps bootlooping, connect it to the PC while in fastboot mode, and execute the following command:
.\fastboot set_active a
bjlabuk said:
If you google "mi a3 stuck on fastboot screen etc" you should get a couple of suggestions. Can you boot into recovery? Press the power key and the vol. up key at the same time. Keep holding until phone restarts, then release the power key and wait for the Recovery menu screen to appear.
Also did you read the Important Note at the bottom of the instructions?
If the device fails to boot into the OS and keeps bootlooping, connect it to the PC while in fastboot mode, and execute the following command:
.\fastboot set_active a
Click to expand...
Click to collapse
Thank you for you reply. I did see the instructions and tried the script while connected in fastboot mode. I tried the miui tool and relocked my device while and now I am in fastboot with locked bootloader. I was reading about EDL mode help however the first attempt came back unable to enter EDL because bootloader locked. I decided to step away for a few days to take a beat before going further.