even though my phone is s-on, i flashed liquid smooth rom via twrp, forgot to flash boot.img via fastboot command, and rebooted the system, but the phone booted, and kernel was flashed, how is that possible?
Because this isn't the One X, it doesn't need flashing separately, TWRP can do it, so it did.
Related
Hi,
I have been on CoreDroid and I am trying to install the RD-Miui Rom, I have extracted the boot.img flashed it via fastboot and installed the rom, but all I get is the boot screen, the one thing that happens when I flash the boot.img is the phone reboots immediately after(not sure this should happen) I've also tryed using the boot.img flasher provided by the developer but I still get stuck on the boot screen. Can anyone help?
I simply reformatted the system and it worked
I successfully flashed cyanogenmod 11x last night. I followed the steps and everything works great! The phone boots fine, all features work ok. I had a slight issue of it hanging on the CM logo, but I powered down, booted to hboot > factory reset, and it booted up fine the second time.
Strangely, I don't seem to be able to get into recovery any more? if I go into hboot > recovery it just boots CM. I tried flashing the recovery again using fastboot, as I did when first installing CM, but it still doesn't work. Next I installed Rom Manager, installed the latest CWM, and rebooting into it from there - Still doesn't work.
Any suggestions?
I had the same problem i was flashing the boot.img in the recovery partition. Fastboot flash recovery [recovery.img]
Fastboot flash boot [boot.img]
Angelo37 said:
I had the same problem i was flashing the boot.img in the recovery partition. Fastboot flash recovery [recovery.img]
Fastboot flash boot [boot.img]
Click to expand...
Click to collapse
Lol once I had opposite problem. Flashed a recovery as a kernel lol just kept bootlooping recovery..
Sent from my alarm clock.
Thanks! flash recovery did it!
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Update:
I ran the "flash-all.bat" on both slots and booted up twrp using fastboot and installed the magisk zip (not the img) before installing the manager, I then installed the manager once I booted up the rom. So I guess it's stock with root for now...
hapse said:
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Click to expand...
Click to collapse
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Lughnasadh said:
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Click to expand...
Click to collapse
Ah I see, thank you
I have the Oneplus 7t. Been using the global fastboot zips to bring the phone back to stock after experimenting with custom ROMS/kernels.
This time, after flashing the msm xr rom I went back to stock using 10.0.6 global fastboot rom. everything looks good while the flash all script is running and then it reboot and sits at the bootloader screen. I cannot get past the bootloader screen. Someone please help.
I can access recovery mode and fastboot. When in fastboot I run fastboot devices and everything checks out. I run the flash all script and everything runs fine. I reboot and its stuck at the bootloader screen. What gives?
EDIT: Figured it out. I used the wrong flash script for the wrong ROM. So the incorrect rom was only flashed to one slot. I used the Resurrection Remix ROM and used the flash script for it and the ROM flash to both slots. Then I downloaded the global 10.0.6 fastboot stock rom and when I start the flash all script, it identified my filesystem instead of saying "Unknown File system type, RAW".
Now I am successfully booted back into stock ROM.