Hi everyone. First of all, excuse me for my not well English. Today I've tried to reset my Motorola Moto G XT1032: it's a GPE converted by me some months ago. I've not succeded to reset it using Android settings. So, I've tried using the flashboot menu (Volume down + power, Recovery, Volume up + power, delete all), but all data has remained on the phone.
So I tried to re-flash GPE firmware, as I did some months ago, but after the process the phone does not boot and stucks on Google boot logo with an the opened lock. I've tried many guides but I've not succeded to repair. Please, help me! Thanks.
P.S. I'm using Linux for fastboot and other tools.
I'm trying again by re-flashing. Now I'm seeing that there is an error on flashing partition.gpt. Why?
u can change a rom
Hi !
I have the same problem, beside all that my phone is in bootloop i cannot install any custom recovery, what ever custom recovery i flash i get hab check failed or partition mismatch and then i end up with the stuck recovery (i know i should not reboot right after the flash and i go to recovery mode but the moment i boot up i see the old recovery)
I am not sure what is wrong but i guess there should be something wrong with my partitions. the only rom that gets flashed with no errors (but still gets stuck in the bootloop) is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC
I managed to see my files via the command fastboot boot recovery recovery.img but then i only have read access, If only i had write access i could upload some files to my phone and get it working with updating from SD card .
any help is appreciated
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
alexandrino said:
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. Is nt that exactly what i did ? i mean i looked at the files . there ate generally two types of files. some are XML which i need to use fast boot. the other one is a zip file with several folders in it which i dont know how to flash. do you mean there is my answer?
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
alexandrino said:
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
Click to expand...
Click to collapse
I have followed the guide but maybe here is actually my problem
there are two kinds of ROMS to my knowledge. one has several files in it boot.img recovery.img chucnks etc... and there are no folders in the ROM file it is usually called XML
second type is a zip file like this one http://forum.xda-developers.com/devdb/project/dl/?id=14940 if you exract it there is a file named boot.img and two folders META-INF and System.
in the system there are numerous files but there is nothing to flash. the only way i know is flashing via fastboot. i dont know how flash these zip files.
one more point is that i dont have a custom recovery ( and i cannot install one since it does not show up after each reboot for an unknown reason)
from what i read people upload these second type zip files to their phone and then install it with their custom recovery software, but i dont have that luxury!
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
alexandrino said:
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
Click to expand...
Click to collapse
yes i guess. we can continue here, and thanks.
For anyfirmware i get hab check failed and partition mismatched errors
for recoveries i get mismatched partition error
they said you should ignore them but i am not sure if i should!
the only firmware which flashes flawlessly is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml by works i mean it just does not come up with any errors and it flashes but still the bootloader loops.
by the way, is there anyway i could upload some images to the device ? i cannot side load adb cause it comes with verification error in the middle of upload for anything i tried.
Thank you everyone for the replies. Some months ago I converted my Moto G to GPE as reported in this guide. When I tried to do it again (with the purpose of resetting the device) I got the issue descripted in my first post. But I was doing the all procedure using Ubuntu: I opened the batch file, written in Windows Batch Language, and I executed all the commands through the bash. Maybe, that's the thing that has made the phone not starting anymore. In my last try I've followed the procedure using Windows and now everything is ok.
Related
When my brother first got his Moto G, I helped him root it and set up Xposed Framework with a security module, per his request. When he got the notification to update to Android 5.0, he accepted it and thereby screwed everything up.
Now when he tries to boot the phone, it shows the Google logo with the unlocked bootloader icon underneath for a while before showing the boot error symbol (android guy lying on his back with a red triangle). I've noticed that during this boot animation, the screen flickers, which is something I've never seen before. When the error symbol shows up, I can hold volume up + power to get the recovery menu. I can also boot into the bootloader by holding volume down + power while the phone is off.
I've tried wiping the phone via recovery, flashing a factory image, anything I could think of, with no success. What should I do? Thanks in advance!
You probably have to flash full factory image including the bootloader in fastboot mode. Are you familiar with that?
tetakpatalked from Nexus 7 flo
tetakpatak said:
You probably have to flash full factory image including the bootloader in fastboot mode. Are you familiar with that?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Yeah, I'm sure I won't have any trouble with that. I couldn't find a link to a factory image though, do you have any idea where to look?
Muniosi said:
Yeah, I'm sure I won't have any trouble with that. I couldn't find a link to a factory image though, do you have any idea where to look?
Click to expand...
Click to collapse
On Motorola's website, same one where you can get bootloader unlock code. You just have to create login.
Did you see this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
tetakpatalked from N7100
tetakpatak said:
On Motorola's website, same one where you can get bootloader unlock code. You just have to create login.
Did you see this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
tetakpatalked from N7100
Click to expand...
Click to collapse
I think I found the page you're talking about, but as you can see there is no option for any model of Moto G, only Moto X. I've looked in other places for a Moto G factory image, but with no success. The page in the thread you linked, which hosts the factory images, seems to be down.
Muniosi said:
I think I found the page you're talking about, but as you can see there is no option for any model of Moto G, only Moto X. I've looked in other places for a Moto G factory image, but with no success. The page in the thread you linked, which hosts the factory images, seems to be down.
Click to expand...
Click to collapse
Ouch? I will check when I have my PC again, now I'm on road only with my phone.
tetakpatalked from N7100
Moto G Firmware
http://motofirmware.com/files/category/26-falcon/
ATTACK said:
Moto G Firmware
http://motofirmware.com/files/category/26-falcon/
Click to expand...
Click to collapse
That looks very useful, thank you so much! I'm not sure which file to download though. The device is a US-bought Google Play Edition phone, so would it be GPE_XT1032_KOT49H.M004_CFC.xml.zip?
Muniosi said:
I think I found the page you're talking about, but as you can see there is no option for any model of Moto G, only Moto X. I've looked in other places for a Moto G factory image, but with no success. The page in the thread you linked, which hosts the factory images, seems to be down.
Click to expand...
Click to collapse
Hello mate, here are the firmwares:
http://www.firmware-team.com/forumdisplay.php?f=14
:fingers-crossed:
tetakpatak said:
Hello mate, here are the firmwares:
http://www.firmware-team.com/forumdisplay.php?f=14
:fingers-crossed:
Click to expand...
Click to collapse
Thanks a lot! I really appreciate it. I'll let you know if I have any troubles (but I should be fine). Thanks again!
I followed your advice and as far as I can see it should have worked, but I ran into an issue. Everything was going fine until I got this string of messages on the phone:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Muniosi said:
I followed your advice and as far as I can see it should have worked, but I ran into an issue. Everything was going fine until I got this string of messages on the phone:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I didn't check how the firmware gets installed. Is it a flashable zip?
If you are sure to have downloaded right firmware (for your device) and if you should flash zip in a custom recovery, just disable signature veriication in your recovery in such case.
But if the firmware consists img files that have to be flashed in bootloader mode with fastboot, maybe the firmware really doesn't match you device! Be sure to use proper factory image or recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
I didn't check how the firmware gets installed. Is it a flashable zip?
If you are sure to have downloaded right firmware (for your device) and if you should flash zip in a custom recovery, just disable signature veriication in your recovery in such case.
But if the firmware consists img files that have to be flashed in bootloader mode with fastboot, maybe the firmware really doesn't match you device! Be sure to use proper factory image or recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I just downloaded the GPE_XT1032_KTU84P.M003_CFC.xml.zip file, booted into recovery, selected the sideload option, and used adb to push the .zip file to the phone. Did I do something wrong?
Muniosi said:
I just downloaded the GPE_XT1032_KTU84P.M003_CFC.xml.zip file, booted into recovery, selected the sideload option, and used adb to push the .zip file to the phone. Did I do something wrong?
Click to expand...
Click to collapse
IDK, as I wrote you before, you have to check the zip contents, and also to read in another threads how people are flashing factory image to Moto G.
Maybe the zip contains img files or also bootloader that need to be extracted and flashed in bootloader mode with fastboot (like on all Nexus devices)
I wasn't yet dealing woth flashing factory image on Moto G, on this phone I was so far only erasing it to install custom ROMs.
tetakpatalked from Nexus 7 flo
tetakpatak said:
IDK, as I wrote you before, you have to check the zip contents, and also to read in another threads how people are flashing factory image to Moto G.
Maybe the zip contains img files or also bootloader that need to be extracted and flashed in bootloader mode with fastboot (like on all Nexus devices)
I wasn't yet dealing woth flashing factory image on Moto G, on this phone I was so far only erasing it to install custom ROMs.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
I'm not sure, but I unzipped the file and this is what it contained:
Code:
boot.img
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
motoboot.img
NON-HLOS.bin
recovery.img
servicefile.xml
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
Hi all,
I'm after some help with a 1st gen Moto G. It belonged to my mother, and was happily running CM for years before dying on her one day. She posted it back to me months ago...I failed to fix it then, and I'm not having much luck this time either.
It sits on the bootloader ok, and I can fastboot interact with it, but although attempts to revert to stock, or update TWRP etc look like they've worked, nothing ever changes. It's as if its storage has gone read-only.
CM is still there, but bootloops 9 times out of 10. Occasionally it'll start properly, before rebooting seconds later, probably because it can't write anything and it crashes out.
I can however, boot (not flash) the latest TWRP and play around with that, but even simple file operations like trying to delete anything fails ("process ended with ERROR 1"). I've tried clearing, factory resetting, reformatting, etc, but nothing has an effect. CM and the old files are all still there.
I don't need this phone, nor the files on it - it'll go in the trash if it can't be fixed - so not worried about damaging it any way in an attempt to revive it
Thanks
Everything you describe suggests Emmc corruption. Threads are created about it regularly. It's an issue that can effect any android phone, and while age could be the key factor - my launch-day Falcon has never had an issue. There is no cure.
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Everything you describe suggests Emmc corruption.
Click to expand...
Click to collapse
Ah, interesting. It's not something I've come across before, so it's good to at least know what's (probably) wrong with it.
lost101 said:
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
fastboot transfered about 26% of the file before exiting.
TWRP reported:
Code:
installing zip file '/sideload/pacakge.zip'
>>> XT1032 Retail Europe 5.1 (Untouched) <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
Updater process ended with ERROR: 7
imilne said:
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
Click to expand...
Click to collapse
Do as I instructed to remove all doubt of Emmc corruption.
Hey,
what a day, searching whole night how to get my phone back to life but nothing is happening. Somehow i did managed to birck my mi4c. I tried to install custom ROM with TWRP I think 'miui_MI4c_7.1.20_e887ff73d2_7.0' it finished like in 2minutes and asked me about rebbot or wipe data. Choosed reboot and only mi logo appeared.
Since then I cannot go back to recovery TWRP i had 0.3.1.0.0 version(did update today previous one was old like 0.2.8.3.0).
My phone previously was running on cyanogenmoed 12.1**with anroid 5.1.1.
The only options i have now i to go in fastboot.
Somehow ADB dont find any device now, tried all kind of versions and still the same.
I have no luck with xiaomiflash/miflash either, the program finds my device but dont flash it.
Tried too with many versions (old and new ones) but no luck....
Error:
The system cannot find the file specified .(0x800700002: flash_all_except_storage.bat)
Tried with all three options (flash all, flash all except storage, flash all except data and storage) but is giving me the same error..
I did download a few images .tgz
libra_images_7.1.4_20170104.0000.00_7.0_cn_a4e850e718
libra_images_6.1.7_20151221.0000.11_5.1_cn
libra_images_V8.2.3.0.NXKCNEC_20170407.0000.00_7.0_cn
Check for space extracted with winrar, renamed too...still same old problem.
Tried to solve with the QFIL (Qualcomm_Flash_Image_Loader), but I cant see my device there...
Drivers I think are correct one (I think)
I think i did something stupid**(
Or I dont understand what i am exactly doing...
I would really appriciated any kind of help, thanks!!!!
4Cvetko4 said:
The only options i have now i to go in fastboot.
Somehow ADB dont find any device now
Click to expand...
Click to collapse
But in fastboot mode you DO NOT use the ADB command, only "fastboot.exe" (on Windows). Do the following:
get fastboot
extract "fastboot.exe" and the DLL files to the folder with flash_all_except_storage.bat
run flash_all_except_storage.bat
:good:
SOLVED!!
with this en . miui . com /thread-255776-1-1 . html and Minimal ADB and Fastboot
then i flashed it.
Now that i installed this ROM 8.2.3, it contains half english chinese apps and ofc no google apps which for me is useful.
I did unlock it via miflash_unlock(asked for unlock some days ago), and then uploaded twrp recovery.
But when I go in recovery mode there is some chinese words and three options (screen is blue-black), you can select via up and down volume and confirm with power button.
No idea why there isnt a twrp recovery.
thanks!!
Congratulations!
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.
There's no recovery partition on A/B phones remember.
RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.
pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file
noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Try to manual flash using fastboot
Fastboot flash system system.img
Fastboot flash recovery recovery.img
Then flash EU rom
LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
The same thing happened to me when I tried to install and use TWRP.
To fix this, I used the MiFlash tool and flashed the fastboot ROM which you can download from here.
LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
try unlock bootloader via internet
format data once via twrp