yeah, can anyone check this command in bootloader and paste the output here ? I would be very thankful because my phone is stuck in EDL mode and can't be flashed using Qfil. I need to check the output of this command to hopefully be able to figure something out.
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
&(*) said:
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
Click to expand...
Click to collapse
The thing is, I need to check if there is anything like unlock_a & unlock_b partitions. When I flashed the sn.img it could be the A slot only, and now it has switched to B which bootloader might be locked and preventing user from using Qfil.
That's not your issue with switching the current slot, you didn't clone all your slots and now it doesn't have everything it needs to mount properly back into the bootloader. My bet is you have the wrong software and need the more recent QPST and maybe the vc++ redistributables (both 2010 & 2012 x86).
I'm using Qfil 2.0.3.5 from QPST 2.7.496 (the latest one i could find) and have the qualcomm drivers and vc installed, and it's still the same
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
&(*) said:
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
Click to expand...
Click to collapse
Yup, everything is as should be
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
&(*) said:
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
Click to expand...
Click to collapse
I wrote it in another post already, from the moment i started tinkering with it (it was fully functional back then), there always was this Sahara error happening
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
&(*) said:
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
Click to expand...
Click to collapse
Every program's version was the most recent and I had everything installed correctly but I decided to check the drivers details under the HS-USB QDLOADER 9008 device and it turned out, my antivirus had installed a usb driver that was superior to the Qualcomm one and was overriding it. Now Qfil loads some things but still shows the error, which now is ERROR: it took x seconds to open port. Which is longer than 3. This indicates your target is not stable.
A little progress; now try with the device fully powered down, hold both volume buttons and power button, screen should flash for a split second then plug it in and flash the build right away.
Can't do that because this phone is constantly in edl mode and there is no way to turn it off. Holding power off or power off + volume for 15 seconds causes Qfil to blink the port for a split second but there is nothing on the device.
I tried to do it for like 30 mins and every time it reports com port timeout at around 10sec instead of 3
SOOOO
it works !!
Turns out i wasted like 20 hours trying to flash it. The first error was caused by a different driver interfering with the appropriate one. The next one - timeout - solved it by using the _lite elf file instead of _ddr. The _lite one should have flashed the Super.img partition as far as i know. Now it boots .062.
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
&(*) said:
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Click to expand...
Click to collapse
with or without flashing vbmeta and vbmeta_system all it does is boot up, shows the boot animation with chinese SD888 banner and displays the incorrect firmware warning.
Flashing the CN 12.5.535 via Qfil with boot.img already swapped to TWRP boot.img in the root folder also does not work, the phone is stuck in bootloader just like with global rom and modified boot.img.
Malberd said:
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
Click to expand...
Click to collapse
Everything you mention is why QFIL should be used very cautiously and carefully. It's best used for patching or targeting a specific partition. There is a tutorial that has been reported to work for Legion Duels posted here . You might need to request a blank QCN from another Legion Duel 2/Pro 2 owner, or the blank QCN posted within that thread might be modifiable to restore what's missing. The porting from Pro 2 to Duel 2 is turning out to be an unnecessary nightmare and the Lenovo Hong Kong devs need to address it with a solution. The device feels practically abandoned and it shouldn't be.
Related
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
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
lucasdeeiroz said:
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
Click to expand...
Click to collapse
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
adri_sefp said:
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
Click to expand...
Click to collapse
When did you buy this phone?
borksek said:
When did you buy this phone?
Click to expand...
Click to collapse
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
adri_sefp said:
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
Click to expand...
Click to collapse
did you manage to solve this problem?
claudiusuflea said:
did you manage to solve this problem?
Click to expand...
Click to collapse
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
that means there's no work-arround
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
Even if you do that, there's no blankflash for this model... as long as I know, I was looking forward to find it somewhere but there is none available.
claudiusuflea said:
that means there's no work-arround
Click to expand...
Click to collapse
That's correct, now my device shows nothing on screen, it is just black but when I plug the usb cable, fastboot detects it as fastboot mode, all commands are working but nothing else works.
I'm giving up now.
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
works if I have the bootloader still locked?
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
claudiusuflea said:
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
Click to expand...
Click to collapse
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
adri_sefp said:
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
Click to expand...
Click to collapse
Indeed, after flashing an Android 8 firmware my phone went into Qualcomm 908 EDL mode. After blankflashing and flashing the latest firmware had the same issue with "No bootable A/B slot". The same state before hardbricking the phone (AP Fastboot flash mode secure).
adri_sefp said:
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
Click to expand...
Click to collapse
maybe works "lenovo rescue and smart assistant"
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
No, lmsa would recognise the phones after A10 update, but the problem persists. Someone who has repaired this or someone who has managed to take it to the service or managed to revive the phone from this state? With locked bootloader
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
That didn't help either, there's nothing else we can do than replacing the main board.
Hello.
I have a similar problem. I have tried all of the methods listed, unfortunately nothing works. I ended up replacing the motherboard. The old PCB is waiting, maybe someday it can be repaired.
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?
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?