Good evening could somebody throw a backup system or TWRP native firmware Fastboot.
Related
hi everyone,
i downloaded OFFICIAL 6.0.1 CyanogenMod 13.0,i worked on it whole weekend,now i have fully working android but not working recovery,if i would tried flash recovery through fastboot then will work only recovery and system would be gone,work just system or recovery,some way how to get both?
sorry for bad english im czech
sindymichal said:
hi everyone,
i downloaded OFFICIAL 6.0.1 CyanogenMod 13.0,i worked on it whole weekend,now i have fully working android but not working recovery,if i would tried flash recovery through fastboot then will work only recovery and system would be gone,work just system or recovery,some way how to get both?
sorry for bad english im czech
Click to expand...
Click to collapse
Download the latest TWRP.zip from here and flash it via Cyanogen Recovery.
And if that doesn't work, you can flash the TWRP.img via fastboot,
then reboot,
it will directly boot into TWRP,
then from TWRP flash the ROM.zip and TWRP.zip without wiping anything.
Hi guys, I'm completely newbie in Adroid stuff, and need help to get back my phone.
My software:
ROM Versio: V100R001C00B133SP01
EMUI: 2.3
KitKat[/INDENT]
So, what I did before:
Unlock boot loader
Installed TWRP 2.8
Installed Kingo Root
Got rooted
Installed Super SU
My issue:
Following the article, posted on this thread link, I got some some errors, then I tried by myself extract boot, cust, system and recovery from Huawei Extractor for ROM: Sophia-L10_V100R001C00B621_Firmware_West%20European%20Region_Others_Android%204-2 and ran the following commands using ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this, my phone got in boot loop, I did some search here, and found a force recovery method (putting B133 ROM on SD root directory DLOAD folder and tried force update without sucess.
Does anyone any suggestion to get my phone back?
By the way, my final gola is got Lollipop or Marshmallow working on this phone if it can be alive again
Thank you,
Ivan
Hey guys!
My P10 is stuck in a bootloop between two recovery modes (the wiping one and the flashing one), I can't access TWRP anymore even if I flash it through fastboot with the recovery_ramdisk command.
Can someone tell me how can I flash the boot image of the latest oreo update through fastboot? Which file is it when I have extracted the UPDATE.APP file?
Thank you!
Hi guys, I have to flash a recovery stock to update via OTA. Should I use a recovery related to my serial number (as explained here) or can I use a generic recovery for EMUI 5.0? On my p9 Plus now I have EMUI 5.0.3
Briefly, I saved an EMUI 5.0 recovery on my PC, can I always use this or after every new update the recovery changes and I have to flash a new one looking at my build number?
Sorry for my noob question, thanx in advance
Guys, nobody can help me?
1st, if you have rooted your phone you must do a full update (download the full update package)
2nd for the recovery flash the image of your current version, and next time never flash moded recovery img on recovery partition, you must flash it in recovery2 partition (cmd : fastboot flash recovery2 recovery_image.img)
xzanium said:
1st, if you have rooted your phone you must do a full update (download the full update package)
2nd for the recovery flash the image of your current version, and next time never flash moded recovery img on recovery partition, you must flash it in recovery2 partition (cmd : fastboot flash recovery2 recovery_image.img)
Click to expand...
Click to collapse
Thanx for your answer, really interesting! So if I flash TWRP on recovery2 partition I will be able to update directly via OTA from the update menu on my phone without connect it to pc even if I'm rooted because I maintain my stock recovery on recovery partition?
And after update I have to re-root my phone or this method keep it safe?
yes, you can update directly.
and after the update you have to re-flash TWRP on recovery2 and re-root your phone, and mabye you need to re-unlock your phone first
xzanium said:
yes, you can update directly.
and after the update you have to re-flash TWRP on recovery2 and re-root your phone, and mabye you need to re-unlock your phone first
Click to expand...
Click to collapse
Ok I understand, thanx a lot! :good:
While I was in a hurry, I made a serious mistake and did this :
fastboot flash boot filename.img
( I wrote the TWRP recovery image, into the boot partition ! )
Now, I need to reverse this, and getting stuck.
My Note 11 [SPES] (without NFC) has this current image :
• V13.0.15.0.RGCMIXM
I have re-downloaded this Xiaomi ROM as a Fastboot image and a Recovery image as well.
So, I'm looking for advice on how to get the original boot img
back into my phone, eg. with Fastboot method or Recovery method (if possible)
PS:
I'm using a Windows PC (and not a Mac)
Thank You.
metaxda said:
While I was in a hurry, I made a serious mistake and did this :
fastboot flash boot filename.img
( I wrote the TWRP recovery image, into the boot partition ! )
Now, I need to reverse this, and getting stuck.
My Note 11 [SPES] (without NFC) has this current image :
• V13.0.15.0.RGCMIXM
I have re-downloaded this Xiaomi ROM as a Fastboot image and a Recovery image as well.
So, I'm looking for advice on how to get the original boot img
back into my phone, eg. with Fastboot method or Recovery method (if possible)
PS:
I'm using a Windows PC (and not a Mac)
Thank You.
Click to expand...
Click to collapse
Just flash the boot image that is inside the fastboot ROM, and then, if you want back TWRP, boot to it, through fastboot, and then, through TWRP, flash it to the ramdisk partition.
SubwayChamp said:
Just flash the boot image that is inside the fastboot ROM, and then, if you want back TWRP, boot to it, through fastboot, and then, through TWRP, flash it to the ramdisk partition.
Click to expand...
Click to collapse
@SubwayChamp ,
Thank You for that advice.
It saved me.
( The work PC I was using, had some 'security restrictions' set by the company,
where I could not open the Fastboot image at first, but I managed to work it all out
and grab the boot.img file , and then proceeded as your suggestion )