Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.
Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing
Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.
Built-in cd/dvd player is broken, so i can't put Windows 7 on the Mac. That means no tool kits. Tried using terminal command line, but that didn't work either. Is there any other way to unroot this puppy? Thanks for any help.
I'm a bit uncertain what you want to do. Unroot is a lot different whether you still have stock rom, or you use a custom rom.
Before you start, backup all data on the phone, in case it gets deleted.
For stock, use fastboot to flash the newest factory image from Google. I think fastboot is the same on Mac. Afterwards, you can relock the bootloader of you like.
For custom rom, reflash the rom in recovery without any root.
All I want to do is unroot my Nexus 6. Since I can’t put Windows7 on my Mac, I have to rely on using terminal commands. That’s the problem. If I could have gotten the Mac to recognize the Nexus, I would have been done two days ago. I guess that I need a step by step guide on using my terminal.
You'll need to tell more about what you have tried, and what happened exactly.
- can you connect the phone to the Mac with USB and do ordinary file transfer?
- do you know how to put the phone in fastboot mode?
- what happens when you type fastboot devices in the command prompt?
Terminal says" command not found". File transfer works. When i type in "ls", i do get a list of stuff. What i need is the exact commands, one at a time, to get this Nexus 6 unrooted.
Command not found means that you either haven't installed fastboot at all. Or it is in a place where the command prompt doesn't look.
Try this guide to get fastboot ready:
Install and Use ADB and Fastboot on Mac [How to]
If you want to use ADB commands in Mac terminal, you'll have to download and install ADB and Fastboot on Mac or you'll get 'not found' error.
technastic.com
Followed the guide, but it doesn't list my Nexus 6. Anyway, what are the rest of the commands that i need to unroot phone?
So is fastboot now working for you? The Nexus is listed on fastboot devices?
If yes, you can flash the Google factory image:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
There are some instructions there as well.
Of course, if you would rather have a custom rom, you won't want to flash factory.
Note that the data on the phone may be lost in the process.
I will try this later today, but there is one thing that I’m curious about. I do not have my SIM card in the Nexus, it’s in my other phone. Is that the reason why my Nexus serial number isn’t coming up in flash boot?
All i'm getting is "permission denied". WTF is going on??????
I'm done with this. It's taking up too much of my time, and causing me too much aggravation. Thanks for trying guys.
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
buczek0711 said:
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
Click to expand...
Click to collapse
After to flash TWRP you have to flash the vbmeta.img and then boot to TWRP not through commands but manually with hardware buttons, don't allow device to boot to system before to boot to custom recovery otherwise this will be overwritten again.
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
buczek0711 said:
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Click to expand...
Click to collapse
No, this is not the method to boot to recovery from what I pointed out, you don't have to firstly power off device but from fastboot commands you can type either fastboot or fastbootd reboot and inmediately press the volume up till the TWRP logo appears, the fastboot/d command will act same as it be the power button.
The thread explains how to install unsigned drivers in Windows, not to set it on your Redmi but is for your PC. If you succesfully get the drivers installed then you have to reboot your PC entering again in safe mode (not normal mode) and from there the commands through fastbootd are generally the same than those for fastboot.
buczek0711 said:
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
Click to expand...
Click to collapse
Just to be sure you are doing fine and not missing something the adb commands work while device is on and fastboot/d commands work only in fastboot mode.
Can you attach some SS to see what you are typing and the error that brings the cmd?
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
buczek0711 said:
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
Click to expand...
Click to collapse
Yes, fastboot works normally while in cmd, this is intended for that, no problem to enter firstly toi Power Shell but you can switch to cmd from PS just typing cmd and all the commands from here will be for cmd, doesn´t matter at all how many old is, cmd can work inside PS keeping the same aspect.
buczek0711 said:
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
Click to expand...
Click to collapse
You don't need to reinstall nothing, just from the downloaded SDK platform do all that you want to avoid misspelling path and folder directories, I mean place the files you need to use in the same directory and open terminal prompt (PS) in the same folder where adb/fastboot binaries are, pressing right mouse button and shift at same time.
I feel you are missing something simply here, not so hard to do.
The misc.img partition that you mentioned is just to restore something that went wrong in the process.
But if you are happy with this Miui ROM then great. No hurry to answer that, give your time to rest.
I also feel, that there is something simply to overcome, Only the fastbootd is new Stuff to me. However, any time I was doing something with Snap, i was long after finish by the current time (almost a month with It and 3rd day with fastbootd issue).
I don't get it. Now when I've tried to enter fastboot mode...phone entered it (fastboot, not fastbootD). Then I've installed pitch black recovery and sucessfully booted into it by restarting phone and then pressing vol up. Now I'm trying with magisk and another entry to pbrp.
Second try gave me stock recovery again. What is wrong with it XD?
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
buczek0711 said:
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
Click to expand...
Click to collapse
I think you are not following the right direction, if you want consider what I pointed out; you don't have to power off device prior to boot to recovery for first time but you have to type from fastboot (no matter fastbootd) and inmediately from there boot to the custom recovery, when you succesfully booted to custom recovery then flash the recovery zip if there is one (PBR and OFR have one) and if not a zip then flash the image again to the recovery partition, also check if there is some installer apart from the image that can fix it in the ramdisk partition, at this point your issue is solved, next step is to reboot device to system normally, if you don't have any issue on that then OK but if you can´t there some steps more that you should do, but let this for last.
Ok, let's group it.
I do not think that particular matter of how do I restart phone matters here (at least, I do not believe it, that it does anything).
Option to restart to recovery from adb still not working.
Trying to find magisk.zip in main directory of internal storage still fails under pitch black recovery project.
From new stuff - I now got an error message, while opening pbrp, most likely with the issues about system being read-only (not sure though, since I do not remember it now, might look into it once more). I have the options to mount partitions, available from main menu, but since I do not used it at all before, I do not know, how to deal with it.
Also - my system boots normally, it must have overwritten recovery (or at least header of it) sometime during boot, since custom recovery is unavailable to access after first full reboot.
I'll try now to install newer version of twrp from yt that I've posted days back. I would also try with orange fox (however, i cannot find img for it, just source code, don't get it).
Is there someone, who can and will to help me?
Situation looks this - on this 12.0.4 MIUI with android 10 I'm unable to install ANY recovery (either phone do not restart to recovery after proper command from cmd or it boots into it, but after visiting system and then to recovery again it shows stock (even without any operations or updates from ota).
I cannot force to work either twrp 3.4.2b, twrp 3.5.2, pitch black recovery 3.0.0 beta.
After trying to install magisk 21.4 zip from twrp 3.4.2b phone entered bootloop, because f**k you, user, I cannot even get it to fastboot mode now (btw, fastboot now works, fastbootD is luckily a long-gone crap).
All cmd's have been run with admin rights. There are NO SUCH THING, as misspelling (cmd and adb would not execute command ,if it is misspelled, either command or filename). I've installed drivers once again and used cmd from dedicated folder with adb fastboot portable version (runned as admin, of course).
Now I'm downloading older version of rom for fastboot (miui 11.0.9) with android 10. Something has to finally work on this piece of junk.
Writting each time is success (cmd says "OKAY" nad displays time, it took to do so), downloading recovery image to start from it also works, there aren't any errors in cmd, yet phone still isn't working.
Where's the issue with it? Apart from being mediatek, which seems to somehow enormously hardened any flashing? I did not encounter anything like this with qualcomm, yet mediatek still manages to pisses me off with their really weird implementations and working (???) of their stuff.
another update from battlefield. Managed to finally get mediatek verify bypass in smart phone flashing tool, however it ended with forcing me to format anything in the phone (if not, program would not let me install anything).
Second problem is forcing me to disable verify, yet command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img put in fastboot mode (yes, it works now) does not work, because adb says, that "--disable-verity" is not a recognised command.
SPFT cannot properly download images from phone and welcomes me with error about download exception, happening either in recovery part or in boot part. SInce I do have access to fastboot now, I can overcome it (I think).
Old miflash tool to install roms via fastboot says it cannot flash rom in locked stage (I might have lost unlocked status, but I'm not sure about it). Do you know ways to overcome it?
It is me again (inb4 use edit). Had to unlock phone again by using miphone unlocker (it went ok). Still cannot flash using SPFT, miflash started showing idiotic errors like "no file in directory" or "cannot access to directory" (it could before, I did not changed name of it). Will continue reporting of progress (or the so-called "progress").
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.