Related
EDIT:
In my humble opinion, there's a new blade around, since all the sources for recoveries on english websites don't work with my 256mb "new" blade (jan 2012), while many people using older chinese blades from china unicom can use all the software found online.
flashing re regular cw with rom manager, adb won't work and give errors later shown in this post.
the only recovery i found that will actually work and let me install another rom is a recovery i found on a chinese forum.
downolad this recovery: http://dl.dbank.com/c0sw12amzu
chinese forum: http://bbs.anzhi.com/forum.php?mod=v...fromuid=423904
in that forum u can't see the download link because you have to log in and write a message in that topic in order to see the link.
to flash this recovery go to this thread, page 3 first post and follow the instructions from matt4321.
I am waiting for someone to try with "new blades" with the same problem as mine.
ORIGINAL POST:
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
thanks to anybody that can help me.
Flash cwm using rom manager again
i tried but nothing... :/
thanks by the way.
Does anyone knows how to install CW via adb? i found how to do it here http://forum.xda-developers.com/showthread.php?t=852905 but i have no idea how to download the latest cw for my china uni blade.
thanks if anyone has some hints!
Are you sure you installed the right version of CWM according to your phone's GEN?
Sent from my Blade using XDA app
well, i guess so, my phone is gen2. i installed cw from rom manager, i just selected zte blade. i tried to reinstall cw, to reinstall rom manager, tried to dowload cw with wifi or data internet connection, same result as 1st post, or either like phone stuck on start screen when booting into cw (but the phone was working).
btw, i am using the latest cw.
i wonder what's wrong with my zte :/
Do not use CWM's latest verson
tetora said:
well, i guess so, my phone is gen2. i installed cw from rom manager, i just selected zte blade. i tried to reinstall cw, to reinstall rom manager, tried to dowload cw with wifi or data internet connection, same result as 1st post, or either like phone stuck on start screen when booting into cw (but the phone was working).
btw, i am using the latest cw.
i wonder what's wrong with my zte :/
Click to expand...
Click to collapse
I guess that there's nothing wrong with your device. My Blade is similar to yours (256MB RAM) and the last version of CWM does not work: I even can't enter recovery mod with it. The solution is to use CWM version before the last one (5.0.1.0 I think).
You can easily install it via ROM Manager: Just go to the last option (CWM all versions and select the desired one).
[]'s
Ah, the Best rom so far to our stripped Blade in my opinion is Squadzone's CM7.2.0 RC 5.6
5.0.1.0 isn't working... could you please check which one you have on your blade?
btw thanks, i didn't see that option in ROM Manager!
i am trying with the 5.0.0.8, just in case... i hope it will work...
edit: no, it doesn't work... :/ i'll try with the previous one. with 5.0.0.8 i can't even boot in cw.
Anyone has a tip? it really doesn't work. i really have no idea how to do it via adb, if this could fix the problem.
tetora said:
Anyone has a tip? it really doesn't work. i really have no idea how to do it via adb, if this could fix the problem.
Click to expand...
Click to collapse
I guess the only option for you is to try Amon RA recovery. I don't even know if it still exists. Check out the CM wiki regarding flashing. It might be there.
Sent from my Blade using XDA app
---------- Post added at 06:30 PM ---------- Previous post was at 06:18 PM ----------
You can follow this if you want but the versions of recoveries are old.
http://forum.xda-developers.com/showthread.php?t=915143
Sent from my Blade using XDA app
the problem is that i can't enter recovery mode (i can, but i can't use it) and i can't get the "green android" screen.
to my extent, i have no way to write anything via usb onto the phone. am i right?
i tried all of the cw versions, but all of them give me the same error i posted in the 1st post...
I think CWM can't find your root. Very weird issue. Will check and get back.
Sent from my ZTE Blade using XDA app
Try rooting the phone again! I had problems with my sisters blade when Z4root wouldn't perm root, only temp root (even if i pressed the perm root button).
Use zergRush to root again (or something similar) then flash CWM again through fastboot or adb
z4root actually works, apps that need SU enabled work also when i restart the phone.
zergrush doesn't work. everything seems fine but in the end the phone is not rooted.
plus, i can't use fastboot or adb since the recovery mode does not work, so i have to reinstall it from rom manager.
and yes, i tried to root it again, but with z4root, but nothing.
You should be able use adb with the phone on. Make sure USB debugging is enabled. Install drivers, use adb to reboot into bootloader, then flash cwm through there. Maybe there is a problem with the way rom manager is trying to flash cwm.
Sent from my ZTE-BLADE using Tapatalk 2
tetora said:
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
thanks to anybody that can help me.
Click to expand...
Click to collapse
it could come from root access or you have made a bad manipulation, I have got a similar problem, my recovery has been deleted after have tried to flash one .
thanks matt, but I still can't do anything. adb command works from command line, but fastboot is not working.
the device is recognised when i type "adb devices" when rebooting in recovery, but any commands starting with fastboot give back an error "fastboot is not recognised as a command ..."
maybe it's the way i added fastboot. i found the fastboot.exe and put in the android-sdk\tools folder. even if i restart the pc it's still not recognised.
but if i go in the folder where fastboot.exe is it works, well, kinda, because "fastboot devices" gives me nothing. "fastboot \?" gives me the list of every option i can use, but i can't use them.
i guess it is like this because when i reboot the pc says there are no drivers for the phone. i actually tried to give him the drivers that come with the android sdk and the ones from zte, but both of them do not work. I guess that with the right drivers it will work, but i have no idea where to get them. am i right?
thanks for the patience.
i almost forgot, usb debug is enabled.
i found some drivers here: http://android.modaco.com/topic/319156-winxp7-zte-blade-drivers-and-adb/ and now it's recognised from the pc as "android bootloader interface", but fastboot is not working, it doesn't see the device. :/
tetora said:
thanks matt, but I still can't do anything. adb command works from command line, but fastboot is not working.
the device is recognised when i type "adb devices" when rebooting in recovery, but any commands starting with fastboot give back an error "fastboot is not recognised as a command ..."
maybe it's the way i added fastboot. i found the fastboot.exe and put in the android-sdk\tools folder. even if i restart the pc it's still not recognised.
but if i go in the folder where fastboot.exe is it works, well, kinda, because "fastboot devices" gives me nothing. "fastboot \?" gives me the list of every option i can use, but i can't use them.
i guess it is like this because when i reboot the pc says there are no drivers for the phone. i actually tried to give him the drivers that come with the android sdk and the ones from zte, but both of them do not work. I guess that with the right drivers it will work, but i have no idea where to get them. am i right?
thanks for the patience.
i almost forgot, usb debug is enabled.
Click to expand...
Click to collapse
Okay so it seems the issue is that fastboot won't work and there's some drivers issue!? I remember a while back when i had issues with getting fastboot to work with my ZTE blade, I can't remember where i got the drivers from but recently got my Xoom and the drivers installed from the device wouldn't work, so used koushs drivers for his tether app which worked, give those drivers a go but for ZTE of course, http://www.clockworkmod.com/tether/drivers
you could also try flashing CWM via adb which is what I used to do when I had issues with fastboot, i've got the instructions and commands saved on my computer if you want me to upload them? but then again a google search would probably produce the same results but i've used these before and know they work.
EDIT: also after rereading what you said and saying fastboot isn't recognized as a command (sorry if this is a dumb point) put when in the command prompt you are changing the directory to where the fastboot file is located right?!
as I understand, adb can't flash the recovery, only fastboot.
the drivers are working, windows xp recognise the phone both in recovery and in bootloader mode.
yes, i am running fastboot from the path fastboot.exe is located.
with google the only thing i get is rebooting via adb into bootloader and use fastboot...
so far no luck...
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
amartinss said:
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
Click to expand...
Click to collapse
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
yasin0005 said:
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
Click to expand...
Click to collapse
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
amartinss said:
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
Click to expand...
Click to collapse
Ok...take u r time
yasin0005 said:
Ok...take u r time
Click to expand...
Click to collapse
I can not upload files yet .. I am new to XDA have less than 10 places .. sorry but I can not post the image of the error message. But this is the message that appears on the device ...
Error picture this link amartinss.com.br/sing/IMG_20160101_123536.jpg
OR described below
"Now send the package you want to apply to the device with 'adb sideload <fillenme>'...
Finding update package...
Opening update package...
Verifying update package...
Installing update package...
assert failed: !less_than_int(28686307, getprop("ro.build.date.utc")) || greate_than_int(getprop("ro.build.date.utc"), 1392739200)
return code 8E: Error in /sideload/package.zip
(Status 8)
Installation aborted."
This happens when I try to downgrade the sideload...
To fix your issue, you need to:
1) Update your Recovery to the Latest STOCK version
2) Reinstall your ROM downloading full firmware from ASUS site
The issue is that your ROM/Recovery is not up-to-date to run the update package.
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
patrick.bitencourts said:
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
Click to expand...
Click to collapse
have you found a solution to your problem ???
I am also facing same issue while updating with adb sideload..
if you have got a solution please post it..
Have you tried to acces fastboot with the adb command: adb reboot fastboot ?
Then you could try again to flash your updated recovery.
There is a CWM modified recovery you should try.
Hi, i have a huge problem (probably for me ), my recovery can't mount /data, it goes like this "Failed to mount "/data" invalid argument". Im using TWRP 3.0.0-1
So ROM cant boot it stuck's (before that i have played with many experimental ROM's..)
And kdz updt doesn't work because when i trying to get in e/d mode it turns in fastboot..
What can i do to solve this? I tried something with adb but when i typing commands like adb usb, adb shell it comes with "Error: Closed"
So, friends, please help me, because im fcked out brains with that problem..
LG-E610 user
Ja_Ch said:
Hi, i have a huge problem (probably for me ), my recovery can't mount /data, it goes like this "Failed to mount "/data" invalid argument". Im using TWRP 3.0.0-1
So ROM cant boot it stuck's (before that i have played with many experimental ROM's..)
And kdz updt doesn't work because when i trying to get in e/d mode it turns in fastboot..
What can i do to solve this? I tried something with adb but when i typing commands like adb usb, adb shell it comes with "Error: Closed"
So, friends, please help me, because im fcked out brains with that problem..
LG-E610 user
Click to expand...
Click to collapse
Use format data in recovery and reboot
Jonas Cardoso said:
Use format data in recovery and reboot
Click to expand...
Click to collapse
Thanks a lot man, this helped me out )
The error continues
Jonas cardoso, do you hava nother solution?
askelam said:
Jonas cardoso, do you hava nother solution?
Click to expand...
Click to collapse
Try reflash Stock or format data in twrp
Format /data in Twrp worked
Jonas Cardoso said:
Try reflash Stock or format data in twrp
Click to expand...
Click to collapse
Thanks for it man
askelam said:
Thanks for it man
Click to expand...
Click to collapse
Nice
I flashed the new*B336 update for EMUI 5 and when i got into it i saw that there were not any system apps, i checked why and it appeared i had to install another*full_data file or smth, is there any way i can do it now ???
Btw when i try to boot into TWRP it says Your device is booting now... and does nothing
The situation is now even worst, why can`t nobody help?
Please someone help. i really need my phone back and i can`t take it for repairs.
When i try to install stock rom of EMUI 4 the install says error code - 7
failed to mount /vendor (invalid argument)
failed to mount /product (invalid argument)
I have no OS installed and i cant use HiSuite to recover using fastboot.
dload mode says the app update package does not exist when there is a corrent update.app in the dload folder on my SD card
and*i also am sure i*used the right OEMinfo file ;(
please respond someone.
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Abdulla7 said:
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Click to expand...
Click to collapse
Okay, i will try and see what happens and report back to you. Thanks for the response
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
theAuxify said:
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
Click to expand...
Click to collapse
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Schlengge said:
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Click to expand...
Click to collapse
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
theAuxify said:
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
Click to expand...
Click to collapse
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Schlengge said:
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Click to expand...
Click to collapse
Yea, says :
Phone unlocked
FRP Unlock
And if i use the command adb devices in fastboot mode no devices appear at all*D:
EDIT : I managed to flash boot.img and recovery.img without errors with the device not showing on the list of devices.
Says everything is okay
But when i try to flash system.img it shows this
C:\Users\Auxify\Desktop\Huawei\Huawei-P9-Lite>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445202 KB)...
OKAY [ 14.775s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 14.828s
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Schlengge said:
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Click to expand...
Click to collapse
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Schlengge said:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Click to expand...
Click to collapse
Yeah.*I can boot into recovery N B9 but when i try to flash/wipe/do anything it says cant mount /vendor /product /version
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Schlengge said:
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Click to expand...
Click to collapse
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
theAuxify said:
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
Click to expand...
Click to collapse
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Schlengge said:
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Click to expand...
Click to collapse
Yea, but thats not for /vendor /product /version*xD
P.s : Happy 2017 ;P
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Schlengge said:
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Click to expand...
Click to collapse
Meh, i guess ill just drive out and get it fixed xD Its a loooong way though DD
Thanks for all your help brother ;p
theAuxify said:
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
Click to expand...
Click to collapse
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
jkmaziku said:
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
Click to expand...
Click to collapse
The best, is to try to install twrpmeticulus, wipe all except external storage property, install oeminfo.zip badwolf, go back to reboot, shut down.
Restarts Dload bxxx.
I only see her.
Hi,
My ZE550KL was locked in boot with this message: "Security Error: This phone has been flashed with an unauthorized software & is locked", so i followed some tutorials and was able to install TWRP recovery (i had bootloader already unlocked). Then when trying to reinstall stock rom, i realized i had to reinstall the stock recovery. I did it and installed the stock rom with version matching with the stock recovery i installed(UL-Z00L-WW-1.17.40.1531-user). Everything was going ok, but when my newly installed stock rom was popping multiple apps stopped working an i was unable to basically do anything. So i tried reinstalling stock rom again, but this is when things collapsed. As i entered recovery to reinstall the rom, it has lots of errors from partition cache
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
. This same errors happens when i try to wipe it from the recovery, but when i erase the cache partition on fastboot it says "OK". I also tried to reinstall twrp, but apparently my bootloader was blocked again, and it says it is flashed when i try, but when rebooting it boots again on stock recovery.
So i tried just booting twrp, but then it says my bootloader is blocked and can't boot twrp. Also tried sideloading stock rom from adb, but it gets the same cache partition errors. I tried
Code:
fastboot -w
and it says OK but the cache partition errors are still there. I also tried
Code:
fastboot erase ASDF
and i get some errors.
TLDR; I'm stuck at a cycle where i have to remount cache and all other partitions via TWRP, but i can't install TWRP because my bootloader got locked again and i can't unlock it because i need to install some rom to do it, but since my cache partition is destroyed i can't install anything, neither via fastboot on pc nor from recovery on the phone.
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
TheImpulson said:
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
Click to expand...
Click to collapse
I didn't. Can you please explain how to do it? Thanks
VMokaccino said:
I didn't. Can you please explain how to do it? Thanks
Click to expand...
Click to collapse
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
TheImpulson said:
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
Click to expand...
Click to collapse
Well, i tried all these format commands, but nothing has changed
VMokaccino said:
Well, i tried all these format commands, but nothing has changed
Click to expand...
Click to collapse
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
VMokaccino said:
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
Click to expand...
Click to collapse
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
TheImpulson said:
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
Click to expand...
Click to collapse
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
VMokaccino said:
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
Click to expand...
Click to collapse
Take your phone to service center I guess.