Database Users

Yoga Tab 2 (830,1050,1380) - TWRP 2.8.7.0(6)

'what? lol'

1050F - All Good!
Thanks!

YamYam

ionioni said:
you tried to flash a partition from dnx mode
Click to expand...
Click to collapse
Doh... Been so confused lately....

workdowg said:
Doh...
Click to expand...
Click to collapse
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.

ionioni said:
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.
Click to expand...
Click to collapse
Probably... I had 3 or 4 more people interested... I posted the working MicroSD install files... But I do feel lonely...

Thanks brother, I will test in upcoming Saturday and will revert back.

a beginner's guide....tnx[emoji1] [emoji1]

@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update

pug1 said:
@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update
Click to expand...
Click to collapse
Since the bootloader is unlocked you may do what you wish. Permanent TWRP will make the job easier. Have at it!
As far as the current ROM from Lenovo.... It is really stable for me. I froze the usual suspects and I get about 3-4 days with 8-9hrs SOT. I don't game on this tablet and keep the brightness down to about 1/3.

updated: added compilation from 6.0 sources - TWRP 2.8.7.0(6)

ionioni said:
updated: added compilation from 6.0 sources - TWRP 2.8.7.6
Click to expand...
Click to collapse
Pretty... all good on the 1050F.

1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??

dtrail1 said:
1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??
Click to expand...
Click to collapse
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
what is the OTA you're on?

ionioni said:
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
Click to expand...
Click to collapse
Already figured it, but thx!! I forgot to FIRST boot it from DNX mode once, and then flash it permanently from fb mode. thx

I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you

QuazIqbal said:
I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you
Click to expand...
Click to collapse
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img

ionioni said:
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img
Click to expand...
Click to collapse
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.

any 830 owner can confirm if it is working or not on his device?

QuazIqbal said:
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.
Click to expand...
Click to collapse
1. when you are entering the above two commands are you in DNX mode? ('fastboot starting' on screen)
2. when you upgraded to Lollipop did you used the OTA update process or you just flashed a stock Lollipop rom?
3. boot to your normal Android OS and open Contacts and in the search contacts box enter ####0000# it will open a VersionInfo window, tell me what it says under BIOS version line
by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
Click to expand...
Click to collapse
4. right after you entered the commands it rebooted (ie you heard the tab buzzing as if you power on from off state) or just continued and booted t Android?

My lenovo a6000 is hard bricked. PC not detecting it.

Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?

arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method

JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc

arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.

I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected

sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.

arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.

sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference

One update. I can get into the fastboot mode. But the bootloader is locked. What to do?

arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.

sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"

arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.

sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight

sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".

arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?

sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed

arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.

sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.

arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock

arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?

forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?

videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.

WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work

sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?

zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.

Stuck twrp says no os installed . But i did learn how to push files.

just trying to get back to stock now 

videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .

Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.

thanks everyone.

videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.

I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help

This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much

avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical

videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks

avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.

Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks

avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Fastboot mode issue in MiA1

Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??

Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.

I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.

MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.

oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started

MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.

oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?

MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.

oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.

MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.

oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.

MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.

oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?

wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.

Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!

MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html

I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.

Phone stuck in Sony boot logo (not even charging), please help!

Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!

Nobody will help?

jayeffpee said:
Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Click to expand...
Click to collapse
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...

levone1 said:
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
Click to expand...
Click to collapse
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?

jayeffpee said:
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
Click to expand...
Click to collapse
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?

levone1 said:
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
Click to expand...
Click to collapse
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)

jayeffpee said:
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
Click to expand...
Click to collapse
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...

levone1 said:
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
Click to expand...
Click to collapse
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?

jayeffpee said:
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
Click to expand...
Click to collapse
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?

levone1 said:
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
Click to expand...
Click to collapse
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.

jayeffpee said:
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
Click to expand...
Click to collapse
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...

PHP:
levone1 said:
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
Click to expand...
Click to collapse
Thanks for the link! I have downloaded and flashed all the IMG files inside with fastboot, everything OK. But the phone is still not rebooting to system nor to recovery mode. same behaviour. Stuck in sony logo.