Hey everyone.
All the links for downloading 10F appear to be broken. I need to downgrade from 10V to 10F so I can root, but can't file the firmware anywhere.
Anyone any ideas where I can find a working link?
Ta!
Sent from my LG-H930 using Tapatalk
Why would you need to downgrade to V10f for root ?
Im running V10v and have no problem at all.
flash TWRP in fastboot (fastboot flash recovery twrp.img), then boot that image (fastboot boot twrp.img)
Now youre in TWRP, enable modifications, reboot into recovery again (so you boot the one thats actually flashed)
then flash lg-rctd, no-verity-opt-encrypt-6.0, completly wipe data (factory reset, includes internal memory to get rid of encryption, optional) and flash Magisk
Now you have a rooted stock rom. Optionally with disabled encrpytion (only if you completly wiped /data ), so you can actually take a backup of that partition too and twrp is able to mount it
Some ppl had problems with V10v installing TWRP like me. Tried 1000 times to no avail, downgraded to V10f and TWRP worked the very first time w/o any problems on the lower FW vers.
SGCMarkus said:
Why would you need to downgrade to V10f for root ?
Im running V10v and have no problem at all.
flash TWRP in fastboot (fastboot flash recovery twrp.img), then boot that image (fastboot boot twrp.img)
Now youre in TWRP, enable modifications, reboot into recovery again (so you boot the one thats actually flashed)
then flash lg-rctd, no-verity-opt-encrypt-6.0, completly wipe data (factory reset, includes internal memory to get rid of encryption, optional) and flash Magisk
Now you have a rooted stock rom. Optionally with disabled encrpytion (only if you completly wiped /data ), so you can actually take a backup of that partition too and twrp is able to mount it
Click to expand...
Click to collapse
Hey, ta for the reply.
Like the guy said below, I've tried a few times and never been able to get TWRP to stick.
No harm me trying again though, I'll give it another spin just to make sure.
Sent from my LG-H930 using Tapatalk
Thats what the fastboot boot twrp.img and then reboot recovery (inside that twrp) commands are for
To actually make it stick and not get it overriden again.
Edit: had todo that twice actually, because i ****ed up the system one time, and went back to completly stock to find out what i did wrong (result, a magisk module was causing some error)
SGCMarkus said:
Thats what the fastboot boot twrp.img and then reboot recovery (inside that twrp) commands are for
To actually make it stick and not get it overriden again.
Edit: had todo that twice actually, because i ****ed up the system one time, and went back to completly stock to find out what i did wrong (result, a magisk module was causing some error)
Click to expand...
Click to collapse
Well fair play, followed your instructions and it worked first time! Not sure why it didn't before but I'm all rooted now.
Just need some custom ROMs to be developed now
Sent from my LG-H930 using Tapatalk
SGCMarkus said:
Why would you need to downgrade to V10f for root ?
Im running V10v and have no problem at all.
flash TWRP in fastboot (fastboot flash recovery twrp.img), then boot that image (fastboot boot twrp.img)
Now youre in TWRP, enable modifications, reboot into recovery again (so you boot the one thats actually flashed)
then flash lg-rctd, no-verity-opt-encrypt-6.0, completly wipe data (factory reset, includes internal memory to get rid of encryption, optional) and flash Magisk
Now you have a rooted stock rom. Optionally with disabled encrpytion (only if you completly wiped /data ), so you can actually take a backup of that partition too and twrp is able to mount it
Click to expand...
Click to collapse
it doesnt work on v11m tried 5 times every time when I try to boot twrp (fastboot boot twrp.img)
it starts
shows me the V30 logo
stays for 3-4 seconds
shuts down
restarts normally....
I think i will try it with v10v again tomorrow
Edit: also didnt work with v10v after i flash twrp and try to boot into twrp(fastboot boot twrp.img) the phone restarts normally
Related
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!
So it's my second attempt to flash lineage os (unofficial) on my Realme XT. First time I was a little careless and bricked my device (had to go to the service center for that). Second time I took all the precautions still I'm having almost same problem, but this time its not yet bricked.
I unlocked the bootloader. It went fine.
Flashed unofficial TWRP and booted back to stock os.
When I tried booting to TWRP again I realized it was reset back to stock recovery. So I flashed it again and made backup of all the partitions (stupidly on internal storage). Booted back to system to check that backup is showing on internal storage. Again booted to TWRP and wiped everything except internal storage, flashed lineage and gapps. Wiped dalvik/cache rebooted to system. I was greeted with system partition destroyed error screen.
I flashed vbmeta.img via fastboot, the error was gone but still i was not able to boot to lineage. (I directly flashed vbmeta.img via fastboot. Didn't use the "fastboot --disable-verity --disable-verification" command.)
Now I'm having a different kind of problem.
I can boot into TWRP but I can not boot to system (lineage os). Can't go back to stock as well because the internal storage is encrypted i think (all the folders have random names). After flashing vbmeta.img (via fastboot) now I am not able to connect my phone via fastboot.
Without fastboot TWRP backup is the only option for me to get it back in a working state. If anyone reading this has stock color os with TWRP, It would be great help if you could give me a TWRP backup of system.
Also, I would ilke to know where I messed up while unlocking/flashing, so that I can avoid this in the future.
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
There is a flashable twrp stock rom.. in guides section. Flash it in twrp.
Thanks I'll try that!
naushad.016 said:
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
Click to expand...
Click to collapse
How you managed to get fastboot ?
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
You cannot flash the StockRomXYZ.ozip file directly via TWRP or OrangeFox recovery but if you want to flash COLOR OS then use this link - https://forum.xda-developers.com/realme-xt/how-to/official-ota-update-rmx1921ex11-11-26-t3993041 to download and flash directly otherwise convert the .ozip file into .zip file before flashing. Try the steps mentioned in the link to convert - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277 . After conversion, copy the .zip into storage and always use the Clean Flash method to flash the firmware.
Hope you got it.
Hi, I'm having some issues trying to install the newest update of A10.
I was on A9 with unlocked bootloader, root and twrp of recovery.
I first tried to install the .rar image via recovery but I couldn't find in the memory, but I already wiped system vendor and data.
So when I rebooted to try if the file was there or not, there was no recovery anymore.
Now I'm trying to flash the newest rom via fastboot but through the flash_all.bat it gives me fastboot tz_a error, so I'm trying to install a recovery through fastboot using this guide https://forum.xda-developers.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603 but of course it doesn't work and when I reboot it doesn't enter the recovery but always in fastboot (even tho I press the + button).
What should I do now? Is there anyway to erase everything and install a clean OS from 0 just from fastboot? (Without the flash_all or miflash because it doesn't work)
P.S. I don't care about the data, I've done a backup of all my important files before
Thanks for the help
Sapper Morton said:
First, you have to understand what you did. You wiped your system and vendor image, and didn't installed a newer one afterwards, you didn't wiped your recovery (it's inside boot partition).
Further, .rar files will not be flashed through TWRP, .zip must be used instead, with proper format, there must be a compatible flash script inside.
You can't access your recovery, just because you wiped system; inside your bootloader there's a component responsible to manage the slots, bootctl and by default if it detects a corrupted or invalid system partition, it will always boot onto bootloader mode.
As for the tz_a error, you must unlock critical partitions flashing, just because, tz is a critical partition, thus, run in Fastboot:
Code:
fastboot flashing unlock_critical
If you want to know your current state, use:
Code:
fastboot oem device-info
Your current slot is blocked by bootctl, but this doesn't mean your inactive is too, so, use:
Code:
fastboot set_active other
And reboot into TWRP again, that is, if you do have it installed in your inactive slot.
Fastboot/ADB and other tools, you will find it in here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
If you want to restore using recovery firmware, please do the favor, and read the post below:
https://forum.xda-developers.com/showpost.php?p=82595733&postcount=379
Click to expand...
Click to collapse
Thanks for the help but I managed to get into the recovery and install the rom via fastboot, the thing I was missing was a recovery working for Android10 (even though I remember recovery doesn't have nothing to do witg the installed OS), so I managed to install the recovery and root, and everything went fine after a few tries between various guides. Probably my partitions now are all messed up, but if I boot normally it goes into system (slot A), if I boot into recovery it goes into twrp and also works fastboot. Probably I also installed the OS on slot b, but I don't care as long the first partition works well
Hi there,
Trying to root (magisk) my V30, I flashed TWRP as boot (fastboot flash boot twrp.img) instead recovery... (I did fastboot flash recovery twrp.img) after that...
I guess, because I flashed twrp as boot img, im having a bootloop to twrp I cannot fix..
from TWRP I tried wiping everything, installing magisk, etc... but always boot into TWRP..
Any idea how can I fix? Can I flash the stock boot.img from LG V30? Thanks!
PD: Also, on twrp reboot screen, I see: "No OS Installed!" ... I did a system wipe, did I break it? :S
thanks!
I would try reflashing a ROM, but I expect that probably won't work. The alternative is to start over with a KDZ (which includes a boot partition).
You may be able to flash only the boot partition with the KDZ as well... you could try that first.
Either way, I would make sure you flash TWRP again afterwards, just in case, so that the stock recovery isn't put there by mistake.
schwinn8 said:
I would try reflashing a ROM, but I expect that probably won't work. The alternative is to start over with a KDZ (which includes a boot partition).
You may be able to flash only the boot partition with the KDZ as well... you could try that first.
Either way, I would make sure you flash TWRP again afterwards, just in case, so that the stock recovery isn't put there by mistake.
Click to expand...
Click to collapse
Yeah, re-flash KDZ to restore boot partition. Use Partition DL mode and do NOT choose all partitions. Choose boot partition.
If that doesn't work, then reflash all of KDZ. Bootloader will still be unlocked, but phone will be back on pure stock. Then go through the WTF Section 6 to reinstall TWRP, reformat internal memory, install Magisk, etc.
I made a mess, I really did. Was on Paranoid Q5 and wanted to try the CrDroid 7, so flashed DFE to decrypt the phone. However this made the phone stuck in fastboot. Don't really know if I misunderstood some instruction, or got hold of wrong file...
But here's the real problem - I cant install TWRP through the fastboot!
The Shell does report "sending, OKAY, writing, OKAY", but it wont reboot to TWRP either through ADB or manually.
Is this a common problem? Any help would be appreciated...
When I experienced something like that in the past, I used fastboot to directly boot to recovery, and then permanently flash twrp from inside this temporarily booted twrp. After flashing, reboot again to recovery and you are now ready to flash a new rom of your choice.
So you flashed dfe then rebooted but phone stuck in fastboot? Which dfe zip did you use?
It appears that DFE wiped all the partitions that's why even the recovery is not being flashed because partitions are not getting detected.
The easiest way to boot your phone is to flash stock ROM using flash tool to recreate the partitions. After that anything else can be done.