Hey guys.
I'm having trouble to come forward booting my device with TWRP on my Sony Xperia XZ1 Compact (G8441) using a MacOSX.
Additional info to the phone:
version-baseband:1307-7511_47.2.A.11.228
version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
Steps I did:
Unlocking the bootloader (worked)
Flashing with TWRP from Androidfilehost (here) with:
Code:
./fastboot flash recovery TWRP.img
I've used Android 9.0 twrp-3.3.1-0-lilac-pie-5.img as TWRP.img
It gives me:
Code:
./fastboot flash recovery TWRP.imgSending 'recovery' (34548 KB) OKAY [ 0.750s]
Writing 'recovery' OKAY [ 0.262s]
Finished. Total time: 1.016s
Booting with TWRP:
Code:
./fastboot boot TWRP.img
Sending 'boot.img' (34548 KB) OKAY [ 0.749s]
Booting OKAY [ 5.742s]
After step #3 the phone gets stuck on the Splash screen showing "SONY" (blue LED light on)
Rebooting into normal mode using Volume-Up + Power also gives me a similar outcome leaving the phone stuck on the "XPERIA" screen.
I've read somewhere in this forum that a possible solution could be to format the cache and user data which gives me:
Code:
./fastboot format cache
/Applications/Android/./mke2fs failed with status 1
fastboot: error: Cannot generate image for cache
And a similar one for user data.
Does anyone of you have a clue what I did wrong and what I need to do next to solve it? Every constructive comment is much appreciated.
Best
EDIT:
I could get it running and were able to install lineage-17.1-20201217-UNOFFICIAL-v1.7-lilac from here (androidfilehost.com - modpunk).
It was working to get into TWRP through unplugging the USB cable. Restarting the phone and directly after it restarts pressing volume up and plugging in the USB again.
Wondering why you try to boot into TWRP when it has already been successfully installed?
Code:
fastboot boot <TWRP.IMG>
is used if TWRP isn't already installed yet.
You should run
Code:
adb devices
adb reboot recovery
instead.
Related
HI,
When press power on phone shows "HTC " logo than goes to black screen,
I can go to hboot menu but whenever I press recovery option, black screen comes again and no recovery menu. I also try to install recovery via adb but result is same.
Code:
C:\Android\android-sdk\platfo
sending 'recovery' (3182 KB).
OKAY [ 2.391s]
writing 'recovery'...
OKAY [ 2.844s]
finished. total time: 5.234s
This phone is unlock bootloader with htcdev and have hboot version 1.10.0000
Any tips or suggestion will be highly appreciated.
thanks
br
Seniors, need your help urgent ....
I would download adlx's recovery again and flash it via fastboot with this command:
fastboot flash recovery recovery.img
Maybe you used wrong recovery, size looks a bit small to me...
Hi Guys,
Yesterday I installed the new TWRP 2.7.1.0. and that is when the problems started. Everytime when i loaded TWRP my screen got messed up and i got a split screen (At that time my ROM worked). So I tried to get back to a older TWRP, after a couple of tries i finally installed 2.4.4.0. But then I couldn't acces my internal memory nor my sdcard through TWRP(The ROM still worked fine). So i tried CWM, other TWRP's, still the same issue. To keep the story short, I eventually pressed on the WIPE button in Recovery ... And now I am stuck in TWRP. I can't load any zip files.. Is there any hope?
Tab: TF300T
A small update. After some trial and error i got my rom running again and i can also get in to recovery (Power button + volume down). Now I have erased the old TWRP with "fastboot erase recovery". But now I can't install a new recovery? I tried flashing a recovery and I am getting the messages "sending recovery ok", "writin recovery ok". But i don't see the loading bar on the tab...
I feel lonely here hehe.:laugh:
I resolved the issue and got my tablet running again, with the following steps:
Download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
http://support.asus.com/download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T&os=8
Install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
If the PC doesn't recognize your tab, then try installing the universal naked drivers:
http://forum.xda-developers.com/showthread.php?t=2263822
Guide: http://forum.xda-developers.com/showthread.php?t=2139767
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
All credits to - Buster http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
hashims said:
Got desire HD which has a faulty firmware and most of the process gets killed and im unable to do anything like installing new app, Bluetooth connection or accessing memory through PC.
However, it does lets me connect to the PC
Details of DHD:
2.3.3
S-OFF
Stock recovery
Background:
Since I’m unable to install any app in it, I got hold of iRoot software and it says rooted successfully
now I got few recoveries
Problem:
adb reboot bootloader .. Goes to fastmode usb
fastboot flash recovery recovery.img … CMD says everything went successful
sending 'recovery' (4002 KB)... OKAY [ 0.777s]
writing 'recovery'... OKAY [ 1.372s]
finished. total time: 2.150s
fastboot reboot
Now it reboots and starts again in android. When I go back to bootloader screen it is still the same no custom recovery installed?
I also have tried going to 'recovery' option in bootloader after flashing recovery the phones gets stuck on HTC green logo and white background
Click to expand...
Click to collapse
I think when you flash a recovery and you boot into android, android overwrites the custom recovery with the stock one. Try to boot to recovery without booting in android.
I decided to reflash TWRP using Fastboot (Yes, it did show up in Fastboot), and I was able to flash it using:
fastboot flash recovery twrp.img
But when I tried to boot from it using: fastboot boot twrp.img
I get the following error:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (14698 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.274s]
finished. total time: 0.790s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.529s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
plzzzhelp
Hmmmm...i don't think you can't reboot into recovery using fastboot command...you need to use power button + volume down to reboot into recovery manually....
iPusak Gaoq™ said:
Hmmmm...i don't think you can't reboot into recovery using fastboot command...you need to use power button + volume down to reboot into recovery manually....
Click to expand...
Click to collapse
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
battery low!!!!! said:
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
Click to expand...
Click to collapse
re-flash the recovery and don't forget to use this command after flashing recovery....
Code:
fastboot format cache
then reboot to recovery manually....
I have exactly the same problem except I still have a working OS.
After I couldn't boot into recovery I tried to flash a new recovery by using the TWRP app ("flashed successfully"), reboot to the recovery... same thing, it's stuck at the logo. I tried the flashify app as well (flashed successfully)... reboot... same thing.
I also tried to format the cache in fastboot after flashing the recovery which didn't help.
So either I am stuck with this ROM for the rest of my OPOs live or someone can help me.
I am by no means new to flashing. I flash new ROMs since my HTC Desire, I flashed my SGS3 on a weekly basis and I own my OPO since it came out and I never had any problems.
battery low!!!!! said:
i tried all things..none of them worked..still stucked at oneplus logo..
and i don't have any rom installed..i can only boot into fastboot
Click to expand...
Click to collapse
if you don't have ROM installed you can manually flash a a rom from fastboot.
Return your OPO to Stock via fastboot
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
and reinitialize the rooting process, flash Twrp and supersu
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
DarthLuch said:
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
Click to expand...
Click to collapse
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
adm1jtg said:
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
Click to expand...
Click to collapse
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
DarthLuch said:
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
Click to expand...
Click to collapse
If 21 worked but 22 didn't... Going from my faltering memory that means your not on March security, your on feb or earlier. 22 only worked on March, i am running it myself.
I got stuck here, too... I used the flash tool (flash.android.com) and it put me back to stock after about a 20 minute progress bar crawl
I have the same problem can someone help me?
YYa solucionaste ?