So everything has been fine up until my device started hemoraging storage randomly, So i thought I would just reboot into recovery and wipe everything and just restart with CM13. I attempted to reboot into TWRP 3.0.2.0 and TWRP just looped over and over. I can still boot into the OS, DD'ing /dev/zero and then the recovery image doesn't seem to fix this issue though. and since we don't have fastboot mode I can't just boot the recovery image manually. Anyone have any solutions other than using ODIN since I use Linux on all my computers?
I have access to fastboot / bootloader / download mode, but I cannot boot into system OR recovery, not with stock, or modified bootloop fix twrp or regular twrp, stock or bootloop fix boot image.
Is it possible to mount the user partition via fastboot? Or am I out of luck here?
I'm looking for a way to move an application to system without rooting the phone, because some apps ban rooted users and because I don't want to lose data on my only phone.
I found out that you could do that by loading twrp on fastboot, but I can't seem to find fastboot on this specific phone, just download mode (odir, I think) and recovery mode.
Typing fastboot devices won't show any device and that's why I can't use fastboot boot twrp.img
Now I guess I could try to load twrp with an recovery partition but I have no idea how to do that, if you have any solution it'd be very appreciated.
mateusvmv said:
I'm looking for a way to move an application to system without rooting the phone, because some apps ban rooted users and because I don't want to lose data on my only phone.
I found out that you could do that by loading twrp on fastboot, but I can't seem to find fastboot on this specific phone, just download mode (odir, I think) and recovery mode.
Typing fastboot devices won't show any device and that's why I can't use fastboot boot twrp.img
Now I guess I could try to load twrp with an recovery partition but I have no idea how to do that, if you have any solution it'd be very appreciated.
Click to expand...
Click to collapse
Samsung devices don't support fast boot.
Install twrp and follow the relevant instructions. It's all there in the thread.
Hey, my G5 suddenly stopped booting. It's running the Pixel Experience and teamwin 3.2.1-0 Recovery.
System boot stops and motorola logo. Recovery boot stops at teamwin logo.
Fastboot does not work, adb works at teamwin logo. Adb recognizes the device in recovery mode.
Any Ideas what's wrong or where to start? Would love to access my data...
sdcard and external_sd foders seem to empty...
thanks
Floscher said:
Hey, my G5 suddenly stopped booting. It's running the Pixel Experience and teamwin 3.2.1-0 Recovery.
System boot stops and motorola logo. Recovery boot stops at teamwin logo.
Fastboot does not work,
Click to expand...
Click to collapse
fastboot commands don't work or it will not boot to bootloader/fastboot mode?
Floscher said:
adb works at teamwin logo. Adb recognizes the device in recovery mode.
Any Ideas what's wrong or where to start? Would love to access my data...
sdcard and external_sd foders seem to empty...
thanks
Click to expand...
Click to collapse
Try connecting to wall charger.
problem: fastboot loop.
defails:
i see a quick (0.5s) poco boot logo, then it goes to fastboot mode. this happened after i flashed a custom TWRP image of an poco 3 image (alioth).
commands i ran that bricked everything:
fastboot flash boot twrp-3.7.0_12-0-alioth.img
fastboot flash boot_b twrp-3.7.0_12-0-alioth.img
Click to expand...
Click to collapse
what i tried:
- flashing official firmware with miFlash tool. i get a timeout error, nothing chages.
- flashing offical firmware via script:
F:\androidROOT\POCO-f3\alioth_eea_global_images_V13.0.8.0.SKHEUXM_20220823.0000.00_12.0_eea>fastboot erase boot_ab ||
Erasing 'boot_ab' FAILED (remote: 'unknown command')
fastboot: error: Command failed
"Erase boot_ab error"
Click to expand...
Click to collapse
pls help
you're not supposed to flash twrp to the boot partition you need a boot partition image.
the recovery is a ram disk image stored inside the boot partition.
once you fix the boot partition you can boot the img of twrp and once in twrp theres an option to flash it to the recovery ram disk.
@metalspider thanks! where can i find such an boot image? in the firmware images i found a boot.img file, is that right? i flashed it with
fastboot flash boot boot.img
Click to expand...
Click to collapse
infinite fastboot loop is fixed now. booting to twrp does not work tho.
it boots to a loading state now, but it loads infinitly.
i wiped all data in recovery mode.
so i did boot to TWRP, which does work now.
what to do now? transfere a rom via adb and custom recovery it via TWRP boot?
depends what rom you want to flash
a lot of custom roms will have you flash their boot which includes there recovery and adb sideload the rom zip from there.
some will require a specific firmware version and some even need custom vendor images etc
follow the rom you choose install instructions
mafima said:
@metalspider thanks! where can i find such an boot image? in the firmware images i found a boot.img file, is that right? i flashed it with
infinite fastboot loop is fixed now. booting to twrp does not work tho.
it boots to a loading state now, but it loads infinitly.
i wiped all data in recovery mode.
so i did boot to TWRP, which does work now.
what to do now? transfere a rom via adb and custom recovery it via TWRP boot?
Click to expand...
Click to collapse
How are you booting into TWRP?
"fastboot boot twrp.img" is the recommended way.
This will simply boot TWRP (only load it into RAM), and from inside TWRP, if you want to install it, go to Settings-page > Advanced > "Install RamDisk".
You can also use OrangeFox Recovery, it's slightly more modern and my preference.
The reason why we do it this way nowadays, is because the Boot-partition and the Recovery-partition got merged, now we only have Boot-partition. This is also why your phone stopped being able to boot. You replaced the Boot-code with just TWRP-code. However TWRP-code needs to be *patched* into the Boot-partition, meaning *added* to the Boot-code. Fastboot can only replace partitions entirely, however Recovery *CAN* modify partitions.
Hope this clears things up.
mafima said:
@metalspider thanks! where can i find such an boot image? in the firmware images i found a boot.img file, is that right? i flashed it with
infinite fastboot loop is fixed now. booting to twrp does not work tho.
it boots to a loading state now, but it loads infinitly.
i wiped all data in recovery mode.
so i did boot to TWRP, which does work now.
what to do now? transfere a rom via adb and custom recovery it via TWRP boot?
Click to expand...
Click to collapse
Fastboot is your unbricking friend, well is better than stuck in 9008 edl mode,
you could try my post,
[A13]Evolution X for POCO F3/Mi 11x[alioth][OFFICIAL]
Evolution X 7.0 for the POCO F3 [alioth] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
Using parts 1,1a,1b & 2.
I hope it helps
fixed now. back to MIUI 13! oem still unlocked. but i am scared trying to root it now xD
solution:
download the firmware from official miui. extract the 4gb zip. i used alioth_eea_global_images_V13.0.8.0.SKHEUXM_20220823.0000.00_12.0_eea
copy the boot.img to ur platform tools
fastboot flash boot boot.img
use miflash tool to flash. select the folder u downloaded (alioth_eea_global_images...)
try it multiple times
mafima said:
fixed now. back to MIUI 13! oem still unlocked. but i am scared trying to root it now xD
solution:
download the firmware from official miui. extract the 4gb zip. i used alioth_eea_global_images_V13.0.8.0.SKHEUXM_20220823.0000.00_12.0_eea
copy the boot.img to ur platform tools
fastboot flash boot boot.img
use miflash tool to flash. select the folder u downloaded (alioth_eea_global_images...)
try it multiple times
Click to expand...
Click to collapse
I have rooted many phones over the years,
I follow my instructions as before, using Part 2, Part 5 & Part 6,
when rooting new roms that don`t have a useable recovery.
If i make a complete mess of my F3 then i use parts 1, 1a & 1b in fastboot mode,
Its a nice easy way to return almost to original stock with minimal effort,
I`m glad you got it sorted.