Related
Hello everyone, need a little help if possible .
The say curiosity killed the cat, well… it killed my phone. To be more precise I wanted to know if my 550ml (with unlocked bootloader and running cm12.1) could run a 551ml firmware so… I did install thru TWRP the superzen firmware and after that the screen turned black. Can’t see anything . Not even in fastbootmode, no logo, no nothing. If I turn it on and plug it to the pc it shows, I see the internal memory and the sdcard. It’s gotta be from the different resolution that 550 and 551 have but how do I change it since I can’t see anything?
I did a userdata reset thru fastboot, wiped cache , reinstalled stock recovery ,boot recovery, tried to install stock firmware, still no change. I even managed to enter stock recovery and did an adb sideload of the latest firmware from the asus site.
As for now the phone boots, the capacitive buttons respond, the led indicates that it charges, the pc sees it but no matter what I do the screen remains black. Most likely I’m on the setup wizard but like I said I don’t see anything.
So… What can I do now? To the Asus service with it or …?
I'm not much of a forum user so go easy on me. Thank you.
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
fastmix said:
Not sure if it's going to make a difference but here is an idea, try sideloading a cm recovery and flash a cm rom and see what it does...
Click to expand...
Click to collapse
Unfortunately it does not work, when i try to sideload a rom with twrp it gives this: error closed. Probably because usb debugging is not enabled... and in cwm different error: Device unauthorized...
Are you sure bootloader is unlocked?
It has to be unlocked cause i can flash permanent TWRP and when I enter TWRP recovery i can touch the buttons, even tried to do a restore in the dark... But nothing... Still the black screen persists... Thank you anyways.
PS: Well it looks like I've managed to resolve my problem. Thanx to user helroz i have found in his google drive a Raw firmware and I was able to flash it via fastboot with Asus Flash tool and now the phone booted, no more black screen for me. Lesson learned.
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
hello everyone, i am having a small problem with my htc one m8
whenever i open my phone it says systemui has stopped working, No navigation buttons no notification bar and the background becomes black and comes back again and becomes black, flashing forever
so when i searched about this on google i found someone that says you need to install systemui apk and you must have stock recovery, i cant install apks because my phone wont go past lock screen and i cant see anything on it, and i have Twrp recovery
and this problem happened to me after i downloaded and installed xposed, i downloaded it many times but this time for some reason i am having some problems with it
Recovery: Twrp
Android version: 6.0 ( Marshmallow, official not a custom rom )
---------------------------------------------------------------------------------
i tried flashing xposed uninstaller zip but it didnt work, tried wiping cache and dalvik cache, but no luck
i entered twrp recovery and plugged my phone on my pc and i managed to get my pictures and files etc, but some files are missing
can i solve this problem without having to format the phone ? sry i am a big newb :/
Thanks for your time..
Bump
aa1429 said:
hello everyone, i am having a small problem with my htc one m8
whenever i open my phone it says systemui has stopped working, No navigation buttons no notification bar and the background becomes black and comes back again and becomes black, flashing forever
so when i searched about this on google i found someone that says you need to install systemui apk and you must have stock recovery, i cant install apks because my phone wont go past lock screen and i cant see anything on it, and i have Twrp recovery
and this problem happened to me after i downloaded and installed xposed, i downloaded it many times but this time for some reason i am having some problems with it
Recovery: Twrp
Android version: 6.0 ( Marshmallow, official not a custom rom )
---------------------------------------------------------------------------------
i tried flashing xposed uninstaller zip but it didnt work, tried wiping cache and dalvik cache, but no luck
i entered twrp recovery and plugged my phone on my pc and i managed to get my pictures and files etc, but some files are missing
can i solve this problem without having to format the phone ? sry i am a big newb :/
Thanks for your time..
Click to expand...
Click to collapse
Turn your phone off, then boot it by holding power + vol down. That'll take you to bootloader.
Hook up to your PC and open CMD in ADB. Issue the command fastboot getvar all and post the readout here after deleting you IMEI and serial# (and MEID if you have one).
With that information, I or someone else here will be able to direct you on the proper RUU to run to get you out of this issue.
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Search for the Hard Bricked thread by Naman Bhalla and use it. The links in it may point to older versions, so find out if any later versions are available.
Namanpuri80 said:
Hi guys, my OnePlus 3 will not turn on at all. It does not boot into recovery mode, fast boot mode or regular booting up. No matter what button I press/press and hold, it does not turn on. I can also confirm that the screen is working and it doesn't have that display issue, it's literally off and won't turn on under any circumstances. What do I do? I've plugged it into my Windows PC and it detected my phone but it won't show anything about the phone at all. Please help me, I've been at this for over a week. How did this happen? It started with my flashing CM13 with GAPPS (Google Apps) and that worked successfully. I then tried to flash CM14 without GAPPS because I was too excited (stupid me) and now if I try to boot into recovery mode it won't boot up into anything at all. Please help me, it would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If pc detects phone try /adb devices ,if it detects phone, go like this: /adb reboot bootloader then it should reboot into fastboot. If so try fastboot flash recovery "yourrecovery.img" (I suggest stock recovery of oos you had before brick). The next step, if you boot into recovery is to adb sideload stock oos. Command for that is /adb sideload "youroosfile.zip"
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
ach3fck said:
You need to use Msmdownloadtool to go back to stock because you are stuck in EDL(qualcomm emergency download mode), check Mega unbrick guide and use method 2 to go back to stock, and i guarantee it will work 100%.
Click to expand...
Click to collapse
That's right I even recover a CB8 dead OP3
toolkit
try oneplus 3 toolkit
Try the Unbrick tool, everything that is bricked can be solved...
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
Try flashing miui via batch scripts is what I would do...
When you extract firmware there should be flash_all.bat file inside, run it via cmd - just type the name of it with cmd directed at the folder where the firmware is unpacked. ( For this you need adb tools installed properly so that the whole system has access to it , if you don't know how then download platform tools from google , unpack it and copy everything inside platform tools folder then paste into firmware folder , then you should be able to run the scripts inside firmware folder )
It will start regular process that mi flash does but if it fails then I guess you can see where it fails exactly and update here .
Idk...
You know, this would've been much easier to read if you put some effort into your grammar.
What error did you get in Mi Flash? Did you download the correct Fastboot Stock ROM for your specific region?
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
try to download again the firmware, maybe the file you have been trying to flash is corrupted.
Most and foremost, try to be specific what it was you encountered. Feels like I was reading in a wattpad.
How did you do it?
Please share with how you solve it
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.
Click to expand...
Click to collapse
Please share with us how you solve it
miku1024 said:
Please share with how you solve it
Please share with us how you solve it
Click to expand...
Click to collapse
Basically , I managed to flash it successfully after many attempts. I was getting different errors every time when I was trying to flash the EU version in my PC , so I thought of switching to my laptop and trying with the GLOBAL version this time. I succeed the 2nd time . I also used a different usb cable. So it was just miflash being miflash... nothing to worry about.