Related
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?
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Czechball said:
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Click to expand...
Click to collapse
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
dirlan2001 said:
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
Click to expand...
Click to collapse
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Czechball said:
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Click to expand...
Click to collapse
If you can get into download, you could connect to a PC and start the LG-tools.Use that to restore to the original ROM and start allover again with latedt software (TWRP, ROM, SU)
Cheers
I tried to unroot my phone with SuperSU.
My phone reset and all I get is a google logo screen and another screen that says "Your device is corrupt, it can't be trusted and may not work properly."
I can get into TWRP through recovery mode. Can anyone walk me through the steps to get my phone working again. I don't care if everything gets deleted and it's unrooted. I was trying to factory reset and unroot anyway.
Thanks for reading and any help or knowledge you can pass down.
poptrunks said:
I tried to unroot my phone with SuperSU.
My phone reset and all I get is a google logo screen and another screen that says "Your device is corrupt, it can't be trusted and may not work properly."
I can get into TWRP through recovery mode. Can anyone walk me through the steps to get my phone working again. I don't care if everything gets deleted and it's unrooted. I was trying to factory reset and unroot anyway.
Thanks for reading and any help or knowledge you can pass down.
Click to expand...
Click to collapse
Download the factory image that matches your OS. Use fastboot to flash the system and boot images. Follow section 9 of my guide:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
Thanks for the quick reply. Working on it, I'll check back in when I'm finished or if I have any problems.
I entered in the commands into my command promp listed in your guide #9.
It responds with "waiting for any device". I don't know if my path system is wrong or what. My computer does recognize my phone when it's plugged into the USB port but I cannot access any files to it directly from my PC.
Also, I do have an old back up on my PC I could restore. I just don't know how to transfer it from my computer onto my phone via TWRP.
Update. I flashed the factory image and fixed my phone. Just took some troubleshooting on moving some files around and using the command prompt.
Thanks SlimSnoopOS!
So I've had a read through other threads on different sites and youtube videos etc.
Basically I was trying to root my phone using magisk following the video where TK roots a oneplus 5, but was switching out the software for the oneplus 3 version of twrp.
All was going well, connected phone to pc, unlocked it, copied the files across, flashed and installed twrp then when it rebooted after installing twrp it came up with an error saying that "dm-verirty" is not started in enforcing mode, and the phone wouldn't boot past that.
I relocked the OEM, as I couldn't get it to recovery mode (stock) so tried that and now I can get it into recovery mode.
It will happily go into fastboot mode, have tried reflashing stock recovery and trying to update the os via adb.
Have been looking at the Mega Unbrick Guide - but can't get my phone to show up on my pc to even begin there.
Would appreciate any and all help, plus tips for what to do after I get it back to stock as I'm still keen to root my phone but don't want to screw it up again and have to go through all of this again.
The Mega Unbrick guide is your best hope. Did you install all the drivers on your PC? Specially the Qualcomm ones? Also, make sure to press the volume up button like it says in the instructions for 40 seconds. Otherwise it doesn't show up. If all fails, try using a different PC.
Hi,
I was running LineageOS on my Galaxy Tab S tablet (SM-T800). I tried to update LineageOS. I went into the settings and downloaded the lastest version. However, the installation didn't go through. The download was successful, but an error message told me to try and manually install the update. I tried to go into TWRP mode to install manually the update. Instead of going in the recovery mode, I saw a TWRP app on the Google Play store. I tried and install that app. It went ok, however, I needed to reboot my tablet to finish. I did so, but after that, I got stuck in booting mode, between the TWRP logo and the Samsung logo. So the tablet was trying to boot in TWRP mode, but after about 5 seconds on the splash screen of TWRP, the spalsh screen disapear and then the tablet tries to boot in normal mode. It doesn't work, and the tablet reboots in TWRP mode, but, again, unsuccessful. It's a loop, alterning between the two splash screens.
I tryed to go into download mode and flashed the stock ROM (found on Updato) while using Odin on my computer. It worked. However, after the process, my tablet got stucked on the Samsung logo only. Now, it doesn't go in recovery mode (TWRP). I can only go in download mode or regular mode (but not working). Only the download mode works.
I don't really know waht to do. I tryed to redo the process with Odin and the custon ROM, but it didn't work better.
What can I do?
Thank you very much for your help!
Blaccko said:
Hi,
I was running LineageOS on my Galaxy Tab S tablet (SM-T800). I tried to update LineageOS. I went into the settings and downloaded the lastest version. However, the installation didn't go through. The download was successful, but an error message told me to try and manually install the update. I tried to go into TWRP mode to install manually the update. Instead of going in the recovery mode, I saw a TWRP app on the Google Play store. I tried and install that app. It went ok, however, I needed to reboot my tablet to finish. I did so, but after that, I got stuck in booting mode, between the TWRP logo and the Samsung logo. So the tablet was trying to boot in TWRP mode, but after about 5 seconds on the splash screen of TWRP, the spalsh screen disapear and then the tablet tries to boot in normal mode. It doesn't work, and the tablet reboots in TWRP mode, but, again, unsuccessful. It's a loop, alterning between the two splash screens.
I tryed to go into download mode and flashed the stock ROM (found on Updato) while using Odin on my computer. It worked. However, after the process, my tablet got stucked on the Samsung logo only. Now, it doesn't go in recovery mode (TWRP). I can only go in download mode or regular mode (but not working). Only the download mode works.
I don't really know waht to do. I tryed to redo the process with Odin and the custon ROM, but it didn't work better.
What can I do?
Thank you very much for your help!
Click to expand...
Click to collapse
Have you tried to reflash twrp via odin ? If that works go into twrp reformat your partitions, then flash a custom rom.
Hi,
Thanks for your answer. I tried to reinstall TWRP with Odin on my computer. The process went well, but the reboot of my tablet that occurs at the end of the process got stuck again on the Samsung logo. It didn't get to TWRP mode. I tried to go manually into recovery mode by holding power+vol up+home, but it didn't work.
What else can I try? Thank you,
Blaccko said:
Hi,
Thanks for your answer. I tried to reinstall TWRP with Odin on my computer. The process went well, but the reboot of my tablet that occurs at the end of the process got stuck again on the Samsung logo. It didn't get to TWRP mode. I tried to go manually into recovery mode by holding power+vol up+home, but it didn't work.
What else can I try? Thank you,
Click to expand...
Click to collapse
Are you trying to get to twrp from powered off state ? If not , get to power off state, then use key combo again to try to get into twrp.
Also when you flash twrp, in odi , there is a setting to prevent auto reboot, use that and try to get to twrp via key combo from download. Mode., finally tripple chech the key combo you are using is correct
Hi,
Thanks for the help. I tried to get to TWRP from power off state. The TWRP splash screen appears, and stays on for about 5-10 sec. After that, the splash screen disappear and the tablet reboot to get stuck on the Samsung logo again. It's like if the TWRP booting process doesn't go through...
Thanks again for your help,
Ouch !!
Looks like you got a real problem , and getting into territory I'm not expert in, Ashyx is the real authority with twrp for this device, you can try to pm him and hope he takes pity on you ( he has been helping guys on this qa thread tirelessly for over a year, and is prob taking a well deserved break ).
Otherwise a few more suggestions,
Maybe your PIT is messed up , ( but you prob would not make it to twrp splash screen in that case )
Twrp may still be trying to execute the script from the original linage update and not finding something bails ( total guess ).
Try flashing a stock ( downloaded from sammobile or somwhere you trust ) rom via odin, and see if you can get into the stock recovery. From there do a factory reset and see if you can get stock running.
Try getting into twrp with device connected to pc ( helped in some wierd cases, you never know lol ).
When TWRP splash screen comes up, try some key combos , maybe twrp checks for a script abbort key combo ?
Checkout the TWRP github issues page, see if your bug is there and a solution, create a bug report or mail a dev directly.
Have a look at the TWRP code, maybe some clues ??
Hi,
So not much development here...
I tried to download the stock ROM for my device from Sammobile and tried flashing it with Odin (JOdin actually, I'm on Mac), but it says it need a PIT file. I let Casual fin the PIT file and it finds it. Only, after that my device does not reconnect to Odin even though it's still plugged in my computer. I tried to unplug it then plug it back, but then Odin says the PIT file is corrupted. I tried to restart my device, but still not connecting to Odin...
I tried getting into TWRP with my device connected to my computer. Still the same problem of rebooting while TWRP is booting (while it's on splash page).
No combo key seems to work to keep TWRP open and loading...
Didn't find anything on TWRP github and I'm not saavy enough to look into TWRP code.
So, I'm still stuck with my initial problem. Do any of ou have some advices/suggestions or can help me with my problem please? At this point, I've been without my tablet for more than a month and it S**KS!!
Thanks in advance everyone,
Blaccko said:
Hi,
So not much development here...
I tried to download the stock ROM for my device from Sammobile and tried flashing it with Odin (JOdin actually, I'm on Mac), but it says it need a PIT file. I let Casual fin the PIT file and it finds it. Only, after that my device does not reconnect to Odin even though it's still plugged in my computer. I tried to unplug it then plug it back, but then Odin says the PIT file is corrupted. I tried to restart my device, but still not connecting to Odin...
I tried getting into TWRP with my device connected to my computer. Still the same problem of rebooting while TWRP is booting (while it's on splash page).
No combo key seems to work to keep TWRP open and loading...
Didn't find anything on TWRP github and I'm not saavy enough to look into TWRP code.
So, I'm still stuck with my initial problem. Do any of ou have some advices/suggestions or can help me with my problem please? At this point, I've been without my tablet for more than a month and it S**KS!!
Thanks in advance everyone,
Click to expand...
Click to collapse
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Hi, thanks a lot for your time.
I will try that at work tomorrow as I don't have Windows at home. However, I did try to flash stock ROM with Windows initially (see first post for more info) and it didn't solve my problem. I wasn't able to access recovery mode after the stock ROM was flashed. Hope it's gonna work now and I'll be able to factory reset.
I'll let you know tomorrow afternoon.
Thanks,
ashyx said:
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Click to expand...
Click to collapse
WOW!!! Thank you so much Ashyx. I can now finally use my Tab S. I'm so grateful!!! Thousand time thank you! I deeply appreciate your help for resolving my problem.
ashyx said:
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Click to expand...
Click to collapse