I have a blu dash 3.5
im trying to flash the cwm for my model and when i try to flash a recovery it says:
sending 'system' <size of file>...
OKAY [time]
writing 'recovery'...
FAILED <remote: partition 'recovery' not support flash>
so do you know the problem? and how tro fix it
do you need the getvar all info??(its odd because when i do getvar on the partition types
it shows like:
partition-size:recovery: 600000
partition-type:recovery: raw data)
every one of the partition its like that
CAN YOU HELP ME?
timedude said:
I have a blu dash 3.5
im trying to flash the cwm for my model and when i try to flash a recovery it says:
sending 'system' <size of file>...
OKAY [time]
writing 'recovery'...
FAILED <remote: partition 'recovery' not support flash>
so do you know the problem? and how tro fix it
do you need the getvar all info??(its odd because when i do getvar on the partition types
it shows like:
partition-size:recovery: 600000
partition-type:recovery: raw data)
every one of the partition its like that
CAN YOU HELP ME?
Click to expand...
Click to collapse
i think that, recovery yoy are trying is not for your phone or it may be currupted
Vaibhav Chauhan said:
i think that, recovery yoy are trying is not for your phone or it may be currupted
Click to expand...
Click to collapse
so where can i find the right one for my fone?? my fone its the updated version it has the android 4.1.2 and i found the version for the older blu dash with the 2.3 android
you think its because of that??
timedude said:
so where can i find the right one for my fone?? my fone its the updated version it has the android 4.1.2 and i found the version for the older blu dash with the 2.3 android
you think its because of that??
Click to expand...
Click to collapse
you can google it or serch on xda all forum for your device
one device's recovery can not work on another
Vaibhav Chauhan said:
you can google it or serch on xda all forum for your device
one device's recovery can not work on another
Click to expand...
Click to collapse
the problem is i didn't find anything for my device, don't you think i can find the right android so i can put the 4.1.2 back in the cell phone??
timedude said:
the problem is i didn't find anything for my device, don't you think i can find the right android so i can put the 4.1.2 back in the cell phone??
Click to expand...
Click to collapse
try this link here you will find cwm recovery for your device
http://forum.xda-developers.com/showthread.php?t=2321264
Vaibhav Chauhan said:
try this link here you will find cwm recovery for your device
http://forum.xda-developers.com/showthread.php?t=2321264
Click to expand...
Click to collapse
actually i alrealdy tried that one, but i can erase the recovery, when i do that step, it gets stuck on the erasing forever
and that version is for the 170i my device is for the 171i.
why that happen? why it gets stuck?
timedude said:
actually i alrealdy tried that one, but i can erase the recovery, when i do that step, it gets stuck on the erasing forever
and that version is for the 170i my device is for the 171i.
why that happen? why it gets stuck?
Click to expand...
Click to collapse
i don't think your device have ported cwm
Vaibhav Chauhan said:
i don't think your device have ported cwm
Click to expand...
Click to collapse
so what should i do?? its on a infinite loop, i can go in to the android.
do you think there's a solution for it?
can i re-install the android on him?
timedude said:
so what should i do?? its on a infinite loop, i can go in to the android.
do you think there's a solution for it?
can i re-install the android on him?
Click to expand...
Click to collapse
try to flash stock rom of your device
Vaibhav Chauhan said:
try to flash stock rom of your device
Click to expand...
Click to collapse
ok but where can i find it, i dont know where to seach, the only thing i find is for the 170i version that comes with the 2.3 android, mine is the new verrsion
so what do i do?
timedude said:
ok but where can i find it, i dont know where to seach, the only thing i find is for the 170i version that comes with the 2.3 android, mine is the new verrsion
so what do i do?
Click to expand...
Click to collapse
i have also search for your device but i think there no work done for your device on xda
Vaibhav Chauhan said:
i have also search for your device but i think there no work done for your device on xda
Click to expand...
Click to collapse
so i cant re-install the android on my device? i got to throw it in the garbage and buy another one?
timedude said:
so i cant re-install the android on my device? i got to throw it in the garbage and buy another one?
Click to expand...
Click to collapse
always take nandroid backup before taking any risk
try to find your stock firmware and flash it
I have the same problem..
I have a Blu Dash 3.5 D161a with android 4.2.2. This cellphone has been bought from the network provider, it starts with the network provider's logo instead of the blu's logo. I can enter in fastboot mode and I'm able to see my device from adb, but when I type fastboot erase recovery or fastboot erase system it gets stuck on erasing.
Is the booloader locked or something like that?
Same problem - D161a
HernanMorel said:
I have a Blu Dash 3.5 D161a with android 4.2.2. This cellphone has been bought from the network provider, it starts with the network provider's logo instead of the blu's logo. I can enter in fastboot mode and I'm able to see my device from adb, but when I type fastboot erase recovery or fastboot erase system it gets stuck on erasing.
Is the booloader locked or something like that?
Click to expand...
Click to collapse
I also tried to install CWM
(using info from http://forum.xda-developers.com/showthread.php?t=2321264)
but fastboot erase recovery never completes and fastboot flash recovery cwm-5.0.2.8-d170i.img fails with "partition 'recovery' not support flash"
Perhaps there is another way to install CWM recovery?
Related
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Marcusprit said:
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Click to expand...
Click to collapse
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
es0tericcha0s said:
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
Click to expand...
Click to collapse
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Marcusprit said:
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Click to expand...
Click to collapse
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
es0tericcha0s said:
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
Click to expand...
Click to collapse
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Marcusprit said:
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Click to expand...
Click to collapse
Your device boots and is already rooted, right? If so, try to flash the updated img files with : https://play.google.com/store/apps/details?id=com.cgollner.flashify
recovery
Thank you I now have recovery
Marcusprit said:
Thank you I now have recovery
Click to expand...
Click to collapse
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
Hello,
1.Ive rooted my phone emui 4.1 with kingroot
2. I've flashed Official twrp 3.0.2
3. After booting in twrp I tried to clear cache but it unable to clear cache.
4. Then I've force rebooted to recovery then all partitions got unmounted (shocked)
5. So I flashed mm kang ROM then phone bricked so I thought that stock recovery may mount all partitions so I flashed stock recovery (back up)
6. Finally I'm unable to boot in stock recovery and ROM
7. What do u think guys? How to solve this issue ??
Any one faced same problem?
***Main thing is what ever I try to push a file from adb to phone in fastboot mode (ex- recovery,boot.IMG) it says "writing recovery failed:command not allowed". why I'm getting this error ?? I've unlocked bootloader too ***
Thank you!
.
Martin213 said:
Restore backup of stock rom if you able to boot in twrp.Did you try flash with huawei multitool?
Sent from Paris with love ?
Click to expand...
Click to collapse
I tried but partitions are unmounted so its not booting up,struck at Honor logo
How to solve this???
Pranav Kumar said:
How to solve this???
Click to expand...
Click to collapse
if bootloader works: download official image, use fastboot flash commands to flash all parts
otherwise
download official image from huawai, (update.app) copy to sd, boot phone with all 3 buttons pressed. it shold boot into some recovery.
endrancer said:
if bootloader works: download official image, use adb flash commands to flash all parts
otherwise
download official image from huawai, (update.app) copy to sd, boot phone with all 3 buttons pressed. it shold boot into some recovery.
Click to expand...
Click to collapse
I tired pushing recovery image to device but command says "writing recovery,failed (command not allowed)"
And I tried update.app in SD card in a folder dload tried 3button method also, but it is not booting in recovery right how it can take update?
Pranav Kumar said:
I tired pushing recovery image to device but command says "writing recovery,failed (command not allowed)"
And I tried update.app in SD card in a folder dload tried 3button method also, but it is not booting in recovery right how it can take update?
Click to expand...
Click to collapse
are you able to boot into bootloader? is "fastboot devices" command showing anything?
eddor1614 said:
are you able to boot into bootloader? is "fastboot devices" command showing anything?
Click to expand...
Click to collapse
Yes its showing
Pranav Kumar said:
Yes its showing
Click to expand...
Click to collapse
have you extracted BOOT, RECOVERY, SYSTEM and CUSTOM from huawei package?
eddor1614 said:
have you extracted BOOT, RECOVERY, SYSTEM and CUSTOM from huawei package?
Click to expand...
Click to collapse
Yes I tried but when file is being pushed to phone it says failed (command not allowed) repeats
Can you see "phone unlocked" on screen?
Yeah, sounds like locked bootloader.
Gsavas said:
Yeah, sounds like locked bootloader.
Click to expand...
Click to collapse
No bro I've unlocked bootloader
And I can see *phone unlocked" in fastboot mode
Gsavas said:
Yeah, sounds like locked bootloader.
Click to expand...
Click to collapse
have you tried flashing BOOT or SYSTEM partitions?
Pranav Kumar said:
No bro I've unlocked bootloader
And I can see *phone unlocked" in fastboot mode
Click to expand...
Click to collapse
You could try to reinstall drivers then or try a different pc.
Gsavas said:
You could try to reinstall drivers then or try a different pc.
Click to expand...
Click to collapse
Tried and I got same error(failed(command not allowed))
Do you have hisuite? If not try uninstalling drivers then install hisuite and try flashing with fastboot then. By the way does your device get recognised when you type "fastboot devices" command?
that's strange.
have you tried booting into second recovery?
eddor1614 said:
that's strange.
have you tried booting into second recovery?
Click to expand...
Click to collapse
Yes in eRecovery I can see "update recovery" after connecting to wifi it says "failed to get device info"
I ran out of options.
You might want to try all the same, using different UPDATE.APP version, like B180 or B200, using a different cable, different computer, etc.
Then next step will be Huawei support, it might be a memory/hardware problem.
Sorry man.
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
rominail said:
then I executed :
fastboot format:ext4 boot
Click to expand...
Click to collapse
You completely destroyed phone's boot-loader, what is comparable to a computer's BIOS.
What do you expect? IMO phone is case for the e-waste.
rominail said:
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
Click to expand...
Click to collapse
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Thanks
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
rominail said:
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
Click to expand...
Click to collapse
That's okay! Please so make sure you do some research if your new to the custom OS scene.. it's always good to learn new things
maybe you can flash again like from the factory by using the default flashing and ROM tools.
BryanHafidz said:
maybe you can flash again like from the factory by using the default flashing and ROM tools.
Click to expand...
Click to collapse
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
TheExploitedOne said:
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Click to expand...
Click to collapse
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
mahirab23 said:
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
Click to expand...
Click to collapse
What seems to be going on after the flash?
TheExploitedOne said:
What seems to be going on after the flash?
Click to expand...
Click to collapse
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
mahirab23 said:
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
Click to expand...
Click to collapse
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
TheExploitedOne said:
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
Click to expand...
Click to collapse
I can't get into fastboot.
another solution?????
mahirab23 said:
I can't get into fastboot.
another solution?????
Click to expand...
Click to collapse
Can you access EDL mode?
TheExploitedOne said:
Can you access EDL mode?
Click to expand...
Click to collapse
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
mahirab23 said:
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
Click to expand...
Click to collapse
MiracleBox and QPST yes
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
mahirab23 said:
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
Click to expand...
Click to collapse
I have the tools needed in my cloud I can make into a zip file. You'll need to also do some research on your part but I can also write a readme file too so you have a basic understanding. Just give me a few to get the link
EDIT:
Here you go this has all you'll need for flashing your device in EDL as well as create the firmware if needed
https://mega.nz/file/rc8CVIiB#qnM3_ZzrvCJtp_M7Y9ZftZqDtGgWeN0tqFrLlT30pws
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
mahirab23 said:
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
Click to expand...
Click to collapse
Absolutely good sir! I'm glad that I can help
TheExploitedOne said:
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
Click to expand...
Click to collapse
Thank you for your help, unfortunately it's a mediatek
Hey, my situation no is:
BootLoader unlocked
TWRP installed
No ROM
And now my phone is empty, no old ROM, no new one. It makes situation much harder cuz i dont have SD card or OTG cable.
Any idea how i could get custom or stock ROM installed?
LycanRS said:
Hey, my situation no is:
BootLoader unlocked
TWRP installed
No ROM
And now my phone is empty, no old ROM, no new one. It makes situation much harder cuz i dont have SD card or OTG cable.
Any idea how i could get custom or stock ROM installed?
Click to expand...
Click to collapse
Reboot into eRecovery and try to update your phone using option "Download latest version etc...." . It requires good wifi connection.
-Alf- said:
Reboot into eRecovery and try to update your phone using option "Download latest version etc...." . It requires good wifi connection.
Click to expand...
Click to collapse
Tried it, fails.
Have you tried install custom ROM , e.g. caos, losq-224 , alpha-ROM from fastboot? It should work. Make sure to have the stock recovery flash , before booting up the ROM, you will need to perform a factory reset in stock recovery.
-Alf- said:
Have you tried install custom ROM , e.g. caos, losq-224 , alpha-ROM from fastboot? It should work. Make sure to have the stock recovery flash , before booting up the ROM, you will need to perform a factory reset in stock recovery.
Click to expand...
Click to collapse
I tried caos, losq, lineage 16 through fastboot. Always fails. Error 7, error 9..
How do i get stock recovery back?
Btw thanks for your time Alf
LycanRS said:
Always fails. Error 7, error 9..
Click to expand...
Click to collapse
Error 7 in fastboot ? , never seen...in TWRP only, due to incompatible script in META-INF.
LycanRS said:
How do i get stock recovery back?
Click to expand...
Click to collapse
Without SD card or OTG ? I'm out of ideas bro.
Try fastboot flash stock recovery and stock erecovery
Then boot into erecovery and download?
Erecovery restore can fail with twrp installed as recovery
Videophile said:
Try fastboot flash stock recovery and stock erecovery
Then boot into erecovery and download?
Erecovery restore can fail with twrp installed as recovery
Click to expand...
Click to collapse
I could try that, but where do i get the files?
Videophile said:
Then boot into erecovery and download?
Click to expand...
Click to collapse
LycanRS said:
Tried it, fails.
Click to expand...
Click to collapse
@LycanRS , what's your region? C...?
IMO you can try to flash stock system.img from fastboot.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
and post the results.
Stock recovery EMUI 9.1 download
Just bought a MicroSD card. What do i do?
LycanRS said:
What do i do?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/need-your-help-stuck-with-no-rom.4233327/post-84677259
Videophile said:
Try fastboot flash stock recovery
Click to expand...
Click to collapse
Got stock erecovery, downloading stock image over wifi now
LycanRS said:
VNS-L21
Click to expand...
Click to collapse
Wrong section bro...
Okay, got back to stock rom
EMUI 9.1.0.132(C432E5R1P7)
-Alf- said:
Wrong section bro...
Click to expand...
Click to collapse
What GSI would you recommend?