This is VERY unstable its impossible to use most things touch is off by tons but you can still boot and you have to select the system boot in FFF to boot into the main system
but it works
In a zip form
Related
Just a heads up that even performing a boot into a custom recovery through fastboot with MRA58N will now fail Verified Boot. I wanted to use android pay so I stayed completely stock in flash with MRA58K. I was able to boot through fastboot TWRP and update my host file. This worked like a charm and everything including android pay seemed to work. I just upgraded to MRA58N, let it optimize with no verified boot failure then through the bootloader booted TWRP, and performed no action but reboot/power off.
I am now getting the Verified Boot message that my device is corrupt. I am continuing to run this way and will test android pay again. If it doesn't work I will need to decide between pay and ads.
For clarity, did you flash a custom recovery, or boot a custom recovery with fastboot? I thought the ability to use the boot option in fastboot was long gone.
artiemon said:
For clarity, did you flash a custom recovery, or boot a custom recovery with fastboot? I thought the ability to use the boot option in fastboot was long gone.
Click to expand...
Click to collapse
Booted through fastboot. fastboot boot openrecovery-twrp-2.8.7.1-shamu.img
1- Clean flash stock rom
2- Go to recovery
3- Wipe data and wipe cache
and clean boot, no failure message.
My English is so bad.
MRA58R is released.
https://dl.google.com/dl/android/aosp/shamu-mra58r-factory-1b87b77e.tgz
I was flashing TWRP
I couldn't boot into system after flashing..
This is what I did:
1. fastboot boot recovery.img
2. Swipe to allow modifications in twrp
3. Flash TWRP installer zip
4. Reboot into partition B
5. Reboot bootloader
6. fastboot boot recovery.img
7. Swipe to allow modifications in twrp
8. Flash TWRP installer zip
9. Then I rebooted into recovery to check if recovery boots and it did.
But afterwards couldn't boot back into system. It was again booting into recovery.
I booted into recovery using fastboot boot, that's why it might won't boot into system. Is there a command to boot into system after above procedure?
Files used: https://m.youtube.com/watch?v=tRcYUMBgvaI
? How to Root Mi A1! Unlock Bootloader, TWRP Recovery ... - YouTube
By Dhananjay Bhosale
Kindly also suggest source of files you used, if you know another working method.
I have the same problem. Meanwhile, flash the stock fastboot images.
Why do you want to have TWRP installed? I am following these steps each month (fastboot ROM was always out sooner than my OTA) without any issues.
1. flash stock ROM via fastboot
2. fastboot boot twrp-3.1.1.img and don't allow system modifications or you won't be able to apply OTA
3. install magisk 15.1
4. reboot to system
If first boot takes more than 2-3 minutes, hold power off button until phones restarts, second start will take the usual time.
I also don't allow any modifications from TWRP, and just boot to TWRP when I need to. I do not install TWRP.
Sounds like you'll have to do a miflash of the rom, then try not installing TWRP and not allowing any modifications in TWRP to system. Just use TWRP to flash Magisk.
Is there a way to determine if I have stable oos
.13 is on both A and B?
Thanks
fastboot getvar current-slot
will return with either A / B AS active slot
fastboot --set_active=(Whatever slot your not on)
YOu just need to go to settings, check sys ver. should say OS VERSION somewhere, reboot back to fastboot mode and type above commands. You can also
fast boot boot twrp.img
with this updated official (rename to twrp.img) : https://eu.dl.twrp.me/fajita/twrp-3.3.1-0-fajita.img
permanent twrp installer zip https://eu.dl.twrp.me/fajita/twrp-installer-3.3.1-0-fajita.zip
it will boot then you can copy this zip file to internal and have twrp installed via zip on both slots, you will need to reinstall magisk after on both slots, just make sure to boot into system after you flash magisk the first time before changing slots and then flashing magisk again to inactive slot by fastboot --set_active=(desired slot) and booting twrp img and flash magisk that way..IF U INSTALL THE INSTALLER ZIP(PERM TWRP) ONLY CHANGE SLOTS IN TWRP BY CHOOSING SLOT AND THEN YOU MUST REBOOT BACK TO RECOVERY(OR SYSTEM IF YOU STILL NEED TO VERIFY OOS VER) UNLESS YOU ARE PERFORMING A CLEAN FLASH OF A NEW ROM FROM SAME OOS BASE ON BOTH SLOTS. Then you would have found under settings if you are indeed on same oos on both slots. SO BOTH SLOT A AND B HAVE desired base, you would then boot the img via fastboot boot twrp.img (RENAME TWRP-3.3.0.1-fajita.img to twrp.img) then afterbooting mount all partitions and you would wipe dalvik/cache /system and /data only, (i like to wipe internal sometimes aswell when doing clean flash to make sure device is gutless) then you can remount /system and mount usb storage and copy rom zip to internal and then flash, it will complete and you want to reboot system, it will say no os installed/areyou sure. just say yes and reboot, will boot into custom rom. then you must reboot to bootloader after booting rom once, then fastboot boot twrp.img choose opposite slot (this is the only time i choose to make another slot active while not actually doing a reboot back to recovery because i dont flash the twrp perm-installer untill after i successfully get custom on both slits to avoid recovery issues /i have had many issues before with twrp regarding slot changing and how it flashed to a/b systems with custom roms built in recoverys. so i always do it this way) mount all partitions if not already, again, wipe /system /data /dalvik. you will need to go back and remount all partitions in twrp and then recopy the rom to internal from pc with mount usb storage and then flash rom reboot. then fastboot boot twrp, and install the installer zip to retain twrp forever. if you say ever need to update rom just dirty flash on the slot your on/ reboot system after/ go back to recovery(fastboot boot twrp.img from pc because you may lose twrp-perm after flashing rom depending on rom) choose other slot via twrp in reboot section, then choose reboot system. (recovery--(only works if twrp-perm is installed, or else if you dont perfer having twrp permanently just choose reboot system, then reboot to fastboot after, and reboot twrp.img) then dirty flash on the slot we have just changes to and then rom is updated on both slots, then you may reflash twrp perm(installer).zip and then you need to flash magisk and reboot and then reboot back to recovery and change slots reboot back to recovery and flash magisk once more... YOU MUST FLASH MAGISK AFTER TWRP EVERY TIME THEN REBOOT BEFORE GOING FURTHER INTO STUFF AS ALWAYS OR YOU WILL NOT BOOT . if you want to update to open beta base if still on stock .13 on both slots use above steps instead of /custom rom/ you can be flashing the /beta rom/full ota zips/ on both slots then you will have new base of beta(whatever beta you choose) then you can flsh custom rom on top of that. if you flashed a custom rom over the .13 and wish to update to beta base instead of .13 you will need to reformst the device and lose all data unless you perform a back-up prior
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
shikaji said:
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
Click to expand...
Click to collapse
I had a very difficult time rooting my Xperia X Compact (F5321) using the method you describe above. I had exactly the same problem with bootloop and sticking on the Sony screen. My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
So I opened up ADB and flashed the renamed boot.img file, followed by Twrp. Then I booted into TWRP recovery (power button + volume down) and installed the supersu (or magisk if you prefer) and drmfix.
Then I rebooted to system and after a few minutes it booted normally into the Xperia homescreen.
Regards,
Dave
funkoot said:
My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
Click to expand...
Click to collapse
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
shikaji said:
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
Click to expand...
Click to collapse
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
shikaji said:
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
Click to expand...
Click to collapse
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Bluestar01 said:
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Click to expand...
Click to collapse
unfortunately i've tried that as well already. same thing - stuck at sony screen or bootloop.
Hello, any updates ? I have the same problem, after flashing my F5321 with Flashtool to update from android 6 to 8...
Hello This a thread to show you how to prevent the stock rom from flashing the stock recovery every time you boot up. There is a script likely located in the boot.img file of the stock rom that flashes the stock recovery every time you boot up. what you have to do is overwrite that boot.img which would disable that script from running. one easy way to do this is to flash twrp and flash magisk.zip, this will overwrite the boot.img
magisk
Magisk-v21-4.zip - BytesTransfer
bytestransfer.com
"
McNoob
Senior Member
Google really is a friend. All I had to do was install Magisk before booting to System.
Below are my exact steps, if that helps someone.
Preliminary:
Download Magisk 17.1 zip, place it on a USB flashdrive.
Install latest magiskmanager apk from Play store (or sideload it if not on the store)
1- In Fastboot:
fastboot flash recovery twrp.img
fastboot boot twrp.img (If all goes well, this boots to TWRP; if prompted for a code, hit cancel)
2- Disconnect the cable.
Reboot to recovery once more (just to make sure, this is probably redundant; hit cancel if prompted for a code)
3- Mount USB-OTG, connect your flashdrive.
Install Magisk.
During the installation, you'll see some red fail lines, but Magisk seems to work around the encryption, just be patient.
4-Reboot System. You're done! Launch MagiskManager. Device is rooted in the process, too. (Verify with a root checker app).
Power Off. Hit Power + volume Up - You should boot to TWRP.
"