Related
'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?
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.
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.
Hey guys!
It's been a while since I've used my Mi A1. I turned it back on after a very long time and it was stuck on the android screen as if there was nothing to boot into so I tried booting into my recovery but there was nothing there either. I figured I probably formatted some stuff a while ago but I don't really remember what happened. Anyways, here's what I did next:
I could only boot into fastboot so I ran the command
Code:
fastboot boot path/to/tissot/twrp.img
but that didn't work.
So I flash the img to boot and tried rebooting to recovery but I was stuck on the android logo and again. I then again had to wait for my battery to run out before I could do anything else (I couldn't enter fastboot again. Only works when the phone is off for some reason)
I then erased the system partition using fastboot and tried booting into the recovery again but no luck. Can someone help me?
I know I messed up... big time. Someone save me
EDIT: Some more details
I tried two recoveries. The Pitch Black on XDA and also the standard "twrp-3.3.1-0-tissot.img" but had the same issue of getting stuck at the splash screen for both.
Also, I remember using Android 10 before all this happened.
EDIT 2: I ran the following commands:
Code:
fastboot set_active a
Code:
fastboot flash boot path/to/tissot/twrp.img
And I can now use the button combination to boot into recovery but I still get stuck on the splash screen
Hi,
have you fixed it? I face the same/similar issue, that I stuck at twrp splash screen after booting in twrp with fastboot
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I have erased/formatted everything (userdata, cache, boot) and also tried to reflash the original rom with mi flash tool, but without success.
Any ideas?
MBR might be creating problem , try clean install with mi flash tool with official ROM .
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
xiaomiA1 said:
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
Click to expand...
Click to collapse
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
MIN313 said:
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
Click to expand...
Click to collapse
If Phone Showing Charging Only and Can't Even Transfer Data , Not Detected on Pc then will have to do EDL flash
My phone is recognized by MiFlash when I enter the fastboot mode
It is also shown with
Code:
fastboot devices
and I can boot into TWRP, but it stucks in splash screen of twrp.
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I also tried older versions of twrp for tissot.
smilar issue, following attempts:
flashed with MiFlash, with or without EDL
flashed installing image with twrp
flashing after wiping dalwik, data, system and so on
flashed several type of ROM: official from xiaomi, crdroid, pixel, lineage
phone only booting with twrp (if installed) or stuck on mi logo
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Brettroth said:
You can try this version. Also try unplugging the USB after it reboots. You aren't getting any crash dump screen? So it should be working.
Click to expand...
Click to collapse
Tried your image and still same result. I am running following command
Code:
fastboot boot TWRP-3.6.1_11-OP6xT.img
The command window outputs the following
Code:
Sending 'boot.img' (34964 KB) OKAY [ 0.747s]
Booting OKAY [ 0.092s]
Finished. Total time: 0.860s
The phone then reboots into Fastboot Mode logo and stays stuck there. I even tried unplugging the USB after it reboots as well.
I even tried using the flash command instead of boot but no success.
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Brettroth said:
How about fastboot boot recovery? Should be able to get into recovery somehow. Doing fastboot flash of twrp will mess up your boot partition but either way you still should be able to get into recovery somehow. There is the msm recovery tool you can use as last resort but it will relock your bootloader
Click to expand...
Click to collapse
I tried doing fastboot boot recovery but i get following error
Code:
fastboot: error: cannot load 'recovery': No such file or directory
Brettroth said:
Actually fastboot doesn't let you use boot recovery command I don't think. Only adb. But once you are in fastboot can't you choose to reboot recovery with volume keys?
Click to expand...
Click to collapse
When I am in fastboot mode, yes I can choose recovery but it takes me to the stock recovery. I do not have a option to flash any zip files there
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Brettroth said:
Maybe you need a twrp for Android 9 since that's what you are on. But fastboot boot twrp should just take you there. Either have to find one that works or go msm route. Maybe windows not reading it correctly also. You using CMD or PowerShell?
Click to expand...
Click to collapse
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
smartinez832 said:
I tried both CMD and PowerShell. I am going to try a A9 version of twrp
EDIT: I am using twrp-3.6.1_9-0-fajita.img (which I assume is for A9) and still get the same result. Even tried a different usb port.. not sure what i could be missing. I also did the instructions as advised straight from twrp's website.
Click to expand...
Click to collapse
I don't know bud. I guess msm tool is the way to go then
Curious did you have the twrp file in same folder as adb and fastboot?
smartinez832 said:
I have been on a journey trying to go back to my T-Mobile OnePlus 6T back as my daily driver but the official updates killed the device for me. I have been successful in flashing it to the international version and now the device is on A9. I am trying to get it updated to A10 but in order do that (does not take OTA updates or can not flash within the updates app) I have to flash in recovery. Right now it is on stock recovery so I am trying to flash TWRP.
The problem is now that everytime I run the command " fastboot boot IMAGENAME.img" the phone restarts (as expected) and boots into fastboot but stays stuck in the Fastboot Mode screen.
I tried different TWRP images (older and the most current version per https://dl.twrp.me/fajita/ ) but I keep getting stuck in the Fastboot Mode screen. The last thing I was able to do without issues was unlock bootloader using fastboot.
I just need to be able to flash TWRP on the phone so I can still the final stock image so I can go back to using it as my DD.
EDIT: Disregard everything I fixed it. mods, please delete thread.
EDITR 2: Disregard that last edit lol Yeah I still need help. I am now tryingto flash twrp on a second 6T and the issue described above still applies.
Click to expand...
Click to collapse
I'm having same issue with fajita (OnePlus 6T) you found any solution if yes then please give some reply