Related
My friend has the clone of the DNA, but tried to flash CM. but is now stuck in a bootloop, but we tried to do a backup. But the backup file won't even show anymore, I can't find a rom to restore it. would anyone on here have a back up or rom that would work?
wewooo said:
My friend has the clone of the DNA, but tried to flash CM. but is now stuck in a bootloop, but we tried to do a backup. But the backup file won't even show anymore, I can't find a rom to restore it. would anyone on here have a back up or rom that would work?
Click to expand...
Click to collapse
Is the device fully S-off, otherwise you will need to manually install the boot.img in fastboot mode.
I've used the M6-7 snapshots on the LRA version without many issues.
http://download.cyanogenmod.com/?device=dlx&type=snapshot
durgis said:
Is the device fully S-off, otherwise you will need to manually install the boot.img in fastboot mode.
I've used the M6-7 snapshots on the LRA version without many issues.
http://download.cyanogenmod.com/?device=dlx&type=snapshot
Click to expand...
Click to collapse
I think we missed the step of S-Off, what would be your recommended way to do it manually. Does Moonshine for the DNA work?
wewooo said:
I think we missed the step of S-Off, what would be your recommended way to do it manually.
Click to expand...
Click to collapse
Extract boot.img from the ROM zip file and reboot the phone into fastboot.
Code:
adb reboot-bootloader
Then flash the boot.img
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
durgis said:
Extract boot.img from the ROM zip file and reboot the phone into fastboot.
Code:
adb reboot-bootloader
Then flash the boot.img
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Then flash the rom?
wewooo said:
Then flash the rom?
Click to expand...
Click to collapse
Either order should be fine, but I usually do the ROM first.
durgis said:
Either order should be fine, but I usually do the ROM first.
Click to expand...
Click to collapse
thanks so much it worked great, but do the sense roms for the DNA work on the deluxe?
wewooo said:
thanks so much it worked great, but do the sense roms for the DNA work on the deluxe?
Click to expand...
Click to collapse
Any of the DNA roms should work pretty well on the LRA model. I haven't tried any of the sense ones myself though.
EDIT: I encountered numerous problems in installing CM13 on Z5C, but a solution is already written here, and it's better than what I could write (because me no good english
Also the problem as explained below is determined only by a wrong environment, in which I blindly flashed uncompatible SW.
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
C:\adb>fastboot flash recovery TWRP-3.0.0.0-suzuran-v2.img
sending 'recovery' (21760 KB)...
OKAY [ 0.756s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.943s
Click to expand...
Click to collapse
Despite the lack of errors the phone is completely unaffected, there's no way I can enter recovery but flashing with "fastboot flash boot", which is improper and so OS loading is broken (it boots only the recovery).
EDIT: I then discovered that's normal behaviour, and that I wasn't able to boot in recovery normally because I flashed Marshmallow SW on Lollipop
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
davidbevi said:
Hello, as in title I cannot get "fastboot flash recovery recovery.img" command to work.
This is what terminal gives me:
I wasn't able to find a solution on the internet, I hope someone can help me.
Z5C E5823, Win7, adb and fastboot are OK
Click to expand...
Click to collapse
There's nothing wrong here? Looks successful to me.
civicsr2cool said:
There's nothing wrong here? Looks successful to me.
Click to expand...
Click to collapse
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
You might want to re-download the TWRP and flash it again. You might be that one in a million person who have a corrupted downloaded file.
davidbevi said:
My bad, I'll explain better; terminal is OK, but phone is unaffected by the command. I found that the only way to enter the recovery was flashing it in boot (found by error), in this way the phone finds it, but it can't boot properly anymore.
Click to expand...
Click to collapse
Download twrp 3.0.2, you're using the wrong one. Also if you use flash tool you can hotboot the recovery to get into it if you don't have a custom kernel that will allow you to get into recovery.
firdyRAY said:
[...] corrupted downloaded file.
Click to expand...
Click to collapse
I doubt because I tried 3 different packages, and every single one works, just I have to flash it unproperly. I would follow your advice anyway if it wasn't for:
civicsr2cool said:
Download twrp 3.0.2 [...]
Click to expand...
Click to collapse
This is the only thing I found googling, can you please give me a link or more info?
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
davidbevi said:
I managed to get TWRP v2.8.7.0 on my phone.
I'd like to write a solution on the original post, so those who have my problem also have my solution, but I have to know better:
1) the TWRP I installed comes from a zip containing boot.img and recovery.img
2) flashing both ("fastboot flash boot boot.img" & "fastboot flash recovery recovery.img") did the job
My guess is that you need a piece of code that IS the recovery and a piece of code that MAKES the recovery ACCESSIBLE. If this is the case I don't get how I was able to boot into recovery when flashed on boot. I am confused!
Click to expand...
Click to collapse
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
civicsr2cool said:
twrp 3.0.2
https://www.androidfilehost.com/?fid=24499762636001943
twrp 3.0 and up is for marshmallow, anything below is lollipop. the boot.img is your kernel, like i said before you need to have a custom kernel to access twrp or hotboot it every time you need it. if you're running marshmallow with a lollipop kernel idk how well that will work out for you in the long run. to understand why you need the boot.img kernel i suggest looking up sony ric.
Click to expand...
Click to collapse
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
davidbevi said:
Thanks a lot, I was able to determine that my problem was caused by a ROM that is too old for what I was trying.
I was trying to install CM13 following CTXz's guide, but I had no idea I had to start from Marshmallow (and it's not written).
Click to expand...
Click to collapse
its in the thread somewhere towards the middle because i tested lollipop to cm13 and got nowhere fast as well.
edit:it says in op that required firmware is 6.0 fwiw
Hi, I used fastboot to boot TWRP without flashing it (using fastboot boot twrp.img). Foolishly of me when exit TWRP I was asked to disabled Stock Recovery wich I swiped yes. Now my stock recovery is gone. How do I enable it via TWRP again without having to flash it? or what are my options? phone functionlity was not afected, just the stock recovery.
thanks.
imho you either use twrp OR stock recovery. so in my opinion youve done all right.
Download fastboot image.. extract boot.img from it. Boot in TWRP using fastboot .. then install->install image->boot.img(file you extracted)->flash->choose recovery, not boot when where to flash->done.
If it doesn't work then flash the whole fastboot image with mitool.
h0LLe said:
imho you either use twrp OR stock recovery. so in my opinion youve done all right.
Click to expand...
Click to collapse
dragneelfps said:
Download fastboot image.. extract boot.img from it. Boot in TWRP using fastboot .. then install->install image->boot.img(file you extracted)->flash->choose recovery, not boot when where to flash->done.
If it doesn't work then flash the whole fastboot image with mitool.
Click to expand...
Click to collapse
I ended up flashing the whole image beacuse it bricked when using the command "fastboot oem lock".
any idea why it bricked? i did flash a stock recovery before in order to lock it again.
After rooting it im interested in locking the bootloader again. Maybe I skipped a procedure in order to lock the bootloader again??
Right now im rooted, phone working, stock recovery (since I flashed a fastboot image with SP tools) and unlocked bootloader but I want to lock it without bricking it again.
thanks.
pach33 said:
I ended up flashing the whole image beacuse it bricked when using the command "fastboot oem lock".
any idea why it bricked? i did flash a stock recovery before in order to lock it again.
After rooting it im interested in locking the bootloader again. Maybe I skipped a procedure in order to lock the bootloader again??
Right now im rooted, phone working, stock recovery (since I flashed a fastboot image with SP tools) and unlocked bootloader but I want to lock it without bricking it again. (i lock bootloader for my friend which has redmi 3s)
thanks.
Click to expand...
Click to collapse
To lock bootloader again you must flash stock image via fastboot with "lock bootloader" bat file (it is in stock image flashtool zip). But why U need to lock bootloader? i dont see sense to do it.
dromaczek said:
To lock bootloader again you must flash stock image via fastboot with "lock bootloader" bat file (it is in stock image flashtool zip). But why U need to lock bootloader? i dont see sense to do it.
Click to expand...
Click to collapse
Hi, thanks for the answer, I want to lock it because some features got disabled when unlocking the bootloader, like xiaomis "Find mi Device". I also read that having the bootloader unlocked may compromise your data security.
pach33 said:
Hi, thanks for the answer, I want to lock it because some features got disabled when unlocking the bootloader, like xiaomis "Find mi Device". I also read that having the bootloader unlocked may compromise your data security.
Click to expand...
Click to collapse
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
chandradeepdey01 said:
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
Click to expand...
Click to collapse
He write only true! He could "read that having the bootloader unlocked may compromise your data security" :laugh::laugh::laugh::laugh::laugh:
chandradeepdey01 said:
:laugh::laugh::laugh::laugh: funniest thing i read on the internet today
Click to expand...
Click to collapse
dromaczek said:
He write only true! He could "read that having the bootloader unlocked may compromise your data security" :laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Glad I made you guys laugh. :good: Next time I will better use the noob friendly Q&A.
pach33 said:
Glad I made you guys laugh. :good: Next time I will better use the noob friendly Q&A.
Click to expand...
Click to collapse
Woah, didn't mean to offend you bro. It was sarcasm.
It is replaced not disabled...
Hello,
I've been looking through this forum for quite a while, but I have yet to stumble upon a guide that can fix me up for taking the next step after the bootloader unlocking process. Yet, there's been lots of custom roms made for rmx2001. So here I'm with my unlocked rmx2001 or realme 6, wondering if I am missing out on something crucial for the next step because this is my first time doing something like this on a mediatek based phone. Kindly help me out pweese.. thank you;
Update:
I've dwelled deep into the forest, fought clones of sundar pichai, then finally.. successfully flashed my phone with custom recovery.
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
cristianwcw said:
zero help, good for nothing advices. Search on other forums ,you Will get at least real help
Click to expand...
Click to collapse
lmao
ignoll said:
From what I've had read around this forum and other places, before flashing any custom recovery, the vbmeta.img must be flashed with a patched one, which as usual, there are rules one must follow to modify this certain android component.
This is the first for me, as per Android 8 (or Android 7 with its super confusing arb system took in place), any changes inside the recovery, system, etc are being handled by this vbmeta module.
It seems that vbmeta.img changes for every android or system update and to patch this vbmeta.img, the android version must be the same as what the patch corresponds to... (correct me if I'm wrong; this is my understanding based solely from what I have read, please take this with a big chunk of salt).
I currently have the b.57 update installed on my device, and I only found b.55 here on the next forum's page... the point is I have to wait for the latest patch of vbmeta b.57. Am I understanding this correctly, or am I just talking in elven language to myself? Anyway thank you for reading.
Click to expand...
Click to collapse
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Lyco. said:
Hi fellow weeb I'm curious of how did you manage to flash custom recovery?
Click to expand...
Click to collapse
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Lyco. said:
Do you a vbmeta.img for the latest patches b.59 or any guide to extract vbmeta, Just like you said the vbmeta corresponds with the patch.
Click to expand...
Click to collapse
We can just use the vbmeta.img from stock ROM .ozip
Thanks
HemanthJabalpuri said:
We can just use the vbmeta.img from stock ROM .ozip
Thanks
Click to expand...
Click to collapse
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right?
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
ignoll said:
g'day to you sire *tip*, sorry for the late response. Before flashing any custom recovery;
make sure your phone is unlocked,
- boot to bootloader,
- flash vbmeta.img (this assuming you will not be using realme UI or stock ROM in that case, because chances are you can't go back once you've flashed this image [although not entirely sure])
code here:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- finally, flash your custom recovery
code here:
Code:
fastboot flash recovery <name of the file>.img
Now, I tried flashing twrp, but for some reason, it didn't work. I personally got recommended to use Pitch Black Recovery Project, basically a fork from twrp. It couldn't read my sdcard, but it has better ui compared to twrp. That said, you still can flash custom rom by adb shell through pbrp.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Is this the stock vbmeta? Or do anyone have any?
Lyco. said:
I thought it depends on the patch. i just want to be careful i don't want to brick my device again btw the stock ozip is b.23 am i right? Or do you have a stock vbmeta?
Click to expand...
Click to collapse
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
HemanthJabalpuri said:
No, we don't need to modify anything to it.
--disable-verity and --disable-verification options to fastboot will patch it and flash automatically for you.
Also you can use vbmeta.img from any version of stock .ozip.
I am a Realme C12 user.
Thanks
Click to expand...
Click to collapse
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Lyco. said:
Ok so what would I do if pbrp didn't showed up? And goes to bootloop, Do i just need to flash ofp and use realme flash tool?
I'm a new at flashing firmware so sorry about that
Click to expand...
Click to collapse
Then flash stock recovery.
HemanthJabalpuri said:
Then flash stock recovery.
Click to expand...
Click to collapse
So after i flash the stock recovery should I flash the ozip there? And thanks for all the information.
Hi guys,
i unlocked the bootloader of my p20lite with PotatoNV and i installed TWRP recovery.
Then i wiped alla data including internal storage. I tried to flashing some ROM (with zip file and with img file), but they don't work(it seems they aren't installed), at every reboot system smartphone shows me TWRP recovery.
I don't know what to do. Do you have any tips please?
Thank you
After attached image i show only TWRP
freddie993 said:
Hi guys,
i unlocked the bootloader of my p20lite with PotatoNV and i installed TWRP recovery.
Then i wiped alla data including internal storage. I tried to flashing some ROM (with zip file and with img file), but they don't work(it seems they aren't installed), at every reboot system smartphone shows me TWRP recovery.
I don't know what to do. Do you have any tips please?
Thank you
After attached image i show only TWRP
Click to expand...
Click to collapse
Look here
https://forum.xda-developers.com/t/i-bricked-my-p20-lite.4449545/#post-86936013
Hi tried to follow those instructions . When i hold both volume button i receive attached screen. i tried to install ROM with sideload method but nothing to do.
freddie993 said:
Hi tried to follow those instructions . When i hold both volume button i receive attached screen. i tried to install ROM with sideload method but nothing to do.
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
i can't access in fastboot mode neither from TWRP
i did it @-Alf-
freddie993 said:
i did it @-Alf-
Click to expand...
Click to collapse
does this mean problem solved?
-Alf- said:
does this mean problem solved?
Click to expand...
Click to collapse
unfortunately no , i tried to install system via fastboot but at the reboot i show TWRP....
freddie993 said:
unfortunately no , i tried to install system via fastboot but at the reboot i show TWRP....
Click to expand...
Click to collapse
In fastboot mode flash stock recovery_ramdisk, download Here
Use command fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img, then run command
fastboot erase userdata, and reboot.
-Alf- said:
In fastboot mode flash stock recovery_ramdisk, download Here
Use command fastboot flash recovery_ramdisk RECOVERY_RAMDISK-9.1.img, then run command
fastboot erase userdata, and reboot.
Click to expand...
Click to collapse
with this command i resolved, the ROM has been installed Thank you , but now i must install again twrp?
freddie993 said:
now i must install again twrp?
Click to expand...
Click to collapse
if you need it ...
My little advice - install TWRP instead of eRecovery, it makes things easier... And please use RECOMMENDED TWRP , not this sh... 3.5.2 and above.
-Alf- said:
if you need it ...
My little advice - install TWRP instead of eRecovery, it makes things easier... And please use RECOMMENDED TWRP , not this sh... 3.5.2 and above.
Click to expand...
Click to collapse
i'd installed
twrp-3.6.1_9-0-anne is this wrong for you??
freddie993 said:
i'd installed
twrp-3.6.1_9-0-anne is this wrong for you??
Click to expand...
Click to collapse
this TWRP has caused you problems, but I will not force my opinion on you.
Happy flashing!
-Alf- said:
this TWRP has caused you problems, but I will not force my opinion on you.
Happy flashing!
Click to expand...
Click to collapse
don't worry. thank you very much for your tips
freddie993 said:
don't worry. thank you very much for your tips
Click to expand...
Click to collapse
hey hi id like to know which version of twrp you ended up installing? if any.
had the same issue as you and solved it the same way but id like to keep twrp as my main recovery
James1807 said:
hey hi id like to know which version of twrp you ended up installing? if any.
had the same issue as you and solved it the same way but id like to keep twrp as my main recovery
Click to expand...
Click to collapse
hi, sorry for waiting, i have 3.5.1 version
freddie993 said:
hi, sorry for waiting, i have 3.5.1 version
Click to expand...
Click to collapse
ok and uh any special procedure to keep twrp as your main? or you just flashed it to the recovery like that and thats it?
James1807 said:
ok and uh any special procedure to keep twrp as your main? or you just flashed it to the recovery like that and thats it?
Click to expand...
Click to collapse
just flashed to the main recovery, but they both remained and for enter in the twrp i must push vol up+down togheter.