Here is some background.
I ordered an LG G7 ULM off of ebay a few days ago. When I got it, I noticed that it was an LG G7 Sprint that was converted to ULM. (Which is typical of eBay). I decided to flash the latest ULM firmware to the device by downloading the latest kdz and flashing with LGup. What I didn't realize until later is that I flashed the "Brightpoint" ULM version. Knowing this, I wanted to flash the non Brightpoint version, but when I try getting into download mode, it doesn't work. It only shows the G7 logo, then shows the battery charging symbol.
Additionally, I am in USB debugging mode and have OEM unlock on in developer options.
Things I have tried:
Holding volume up and then plugging USB
Holding volume down and plugging in USB
Holding volume up and power button
Holding volume down and power button
Reboot fastboot via adb
Also, when i try using LGup without download mode it gives and error "spc code does not match"
Does anyone know how to fix this?
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
sampal said:
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
Click to expand...
Click to collapse
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
onenite said:
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
Click to expand...
Click to collapse
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
TWiiTCH said:
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
Click to expand...
Click to collapse
Thanks for the reply.
I was reading into flashing the laf.img file which would fix the download mode not working, but I'm unable to gain root, so that isn't really an option.
I guess for now, I'm stuck with this firmware version. But, at least I'm on the latest pie version... Hopefully there will be a fix for it, or maybe someone will know how to fix this.
I have heard that you can buy for a service to fix this for around $30. But I don't think I would trust someone doing changes to my phone without a guarantee.
Help me
I have the same problem too, my phone is Verizon variant and I can't get to download mode
babykut said:
I have the same problem too, my phone is Verizon variant and I can't get to download mode
Click to expand...
Click to collapse
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
onenite said:
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
Click to expand...
Click to collapse
You are welcome
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Thank you bro
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
When exactly do you hit the volume up button?
it doesnt seem to work for me
landonloco said:
When exactly do you hit the volume up button?
it doesnt seem to work for me
Click to expand...
Click to collapse
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
Wuh. It could work, but my question is, HOW THE HELL DID YOU GET YOUR LAPTOP/PC TO DETECT THE CELL PHONE!!!!!!
PD: I Have the same problem, plis help me
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
it shows no command screen
Related
I know there is a script to get into recovery mode, anyone know if there is one for download mode, or can someone make one, for the phones not able to use 3 button combination. ?
12.My phone cannot enter download mode or recovery mode using the buttons combos. What can I do?
Some batches in various countries seem to not have this feature. Whether this is an intentional change made by Samsung or simply a software error is not completely clear. While some Samsung offices see it as a softwarebug and are claiming that they will release a software fix, others do not acknowledge the issue and so not replace phones without the fuction. If you are one of the unfortunate group who cannot use the button combos (VolumeUp+Home+Power for recovery and VolumeDown+Home+Power for download mode), you can use the commands "adb reboot recovery" and "adb reboot download" to get into the respective modes (See Post#3 for a step-by-step tutorial on using ADB). However, if you cannot enter download mode by using the button combo, you will NOT be able to recover from a failed flash! Since this is a rather common occurance, I strongly advise you NOT to flash your phone using the adb reboot download command!
Click to expand...
Click to collapse
Read the big faq
Ahh ok, ty.
I will try that.
Ok i have a small script for you to use! but read the WARNING below!
IF the flash fails... you won't be able to restore or reflash your phone and it WILL be bricked. Because your not able to go into download mode anymore.
So use it at your own risk (generally flashing is pretty ok and safe with odin and it has never failed for me!) But thats just my experience. If your pc crashes or you get unlucky any other way.
Anyway script is in this post! Download it but don't spread without a warning it because it is very dangerous and similar to Russian roulette.
Instructions:
1) Put phone in USB Debugging
2) Connect Phone
3) Download script and unzip it somewhere
4) open Reboot recovery.bat
also you could just use adb. i guess this is what BackfireNL's script does, so just to give you all the information:
Code:
adb reboot recovery
or
Code:
adb reboot download
is what you want
And it must be said, since you dont have access to the 3 button combo, you have only ONE shot of getting this right.
Thx, this is just what I was looking for.
I have flashed my own sgs tons of times, never had any problems, this is to be able to flash a friends phone(lacks 3 button comb.)
I have the same problem and i tried adb reboot download, but not working.
It worked with rooted firm, but without the 3 button i cannot root the new firm, so this command not works.
Any useable advice?
krisz222 said:
I have the same problem and i tried adb reboot download, but not working.
It worked with rooted firm, but without the 3 button i cannot root the new firm, so this command not works.
Any useable advice?
Click to expand...
Click to collapse
I am quite certain that I went into recovery mode using ADB without root. Then of course I rooted.
sorry for my last message
i was able to flash the new firm because i used this command
but now adb refuse it, i thought its because its not rooted...
but now i have "no way out"....cannot flash recover or root...
a new kernel can fix this? or what should i do?
USB-Debugging enabled?
Settings -> Applications -> Development -> USB-Debugging
Hello i am having problem with my samsung galaxy nexus I9250
i just factory reset the Slimbean Rom and now got stuck on Slimbean boot logo
i cant even go to the recovery mode, i cant even enter to the download mode,
but on the Slimbean boot logo when i attached the USB on my computer the Galaxy Nexus was detected and i can access the internal storage
but my phone is still stuck on Slimbean Logo
NEED HELP!
THANKS!
a small reward will be sent to anyone that can help me fix this out :good:
You tried accessing recovery by pressing vol up+vol down+power, then scrolling down to recovery with volume key and press power?
ntybrav infpire
t1.8matt said:
You tried accessing recovery by pressing vol up+vol down+power, then scrolling down to recovery with volume key and press power?
Click to expand...
Click to collapse
yes i tried that but slimbean wont let me
What happens when you press the button combo? Does it do anything at all like go to fastboot mode or it just tries to boot the ROM?
t1.8matt said:
What happens when you press the button combo? Does it do anything at all like go to fastboot mode or it just tries to boot the ROM?
Click to expand...
Click to collapse
no luck, its just proceeding to the ROM, i cant enter fastboot or flashboot or download mode even if i combine any keys
Weird, I don't know how you would lose fast boot. I'm not sure if this will work but can you plug into your computer and boot the phone up and try to use adb to boot into fast boot. I think its adb reboot-fastboot or adb reboot fastboot. Or try adb reboot-recovery or adb reboot recovery. I can never remember if you need the hyphen in adb.
t1.8matt said:
Weird, I don't know how you would lose fast boot. I'm not sure if this will work but can you plug into your computer and boot the phone up and try to use adb to boot into fast boot. I think its adb reboot-fastboot or adb reboot fastboot. Or try adb reboot-recovery or adb reboot recovery. I can never remember if you need the hyphen in adb.
Click to expand...
Click to collapse
maybe i guess it was bricked im stuck on the Slimbean logo like forever, sorry but what tool can i use to enter the adb fastboot ? noob here thanks for the response anyway
Follow Step A and Step C #1-2 from here to get adb and fast boot setup on your computer. http://forum.xda-developers.com/showthread.php?t=1626895 After you get it setup, you go into the platform tools folder which you will download as part of Step C and right click and click command prompt, then enter those commands I gave you. How did you root and install a recovery the first time?
t1.8matt said:
Follow Step A and Step C #1-2 from here to get adb and fast boot setup on your computer. http://forum.xda-developers.com/showthread.php?t=1626895 After you get it setup, you go into the platform tools folder which you will download as part of Step C and right click and click command prompt, then enter those commands I gave you. How did you root and install a recovery the first time?
Click to expand...
Click to collapse
Here's what just happened
my brother gave me this phone,
it has a slimbean rom which is my first time seeing that rom
i just go to settings
and click the factory reset
when the phone boots up i can only access the settings no other thing after that
i managed to get into the recovery mode of that rom on the settings
and install the rom again which is still on the sd card
then after the installation is completed when it boots up its now stuck on boot screen
and im screwed
i tried the universal naked driver but no luck device is still not recognized
I see. You're not supposed to use factory reset from the settings. You should only be doing that from recovery. I'm really not sure what else to do, my knowledge is limited on this. Hopefully someone else with more experience can chime in. I'm sorry I'm not able to help you on this. You tried using the platform tools to open a command prompt?
t1.8matt said:
I see. You're not supposed to use factory reset from the settings. You should only be doing that from recovery. I'm really not sure what else to do, my knowledge is limited on this. Hopefully someone else with more experience can chime in. I'm sorry I'm not able to help you on this. You tried using the platform tools to open a command prompt?
Click to expand...
Click to collapse
yep maybe thats my last luck hope it works, you think usb jig might work on this ? well thank you so much for your time and for trying to help me may god bless you always
No, theres no reason to use a USB jig. It's driver issues or something else simple, I'm just not site what. Not trying to get on you but it helps to know what your doing before you mess with things. If someone else is able to help you figure it out, do a lot of research in the general stickies before you do anything else. I hope you are able to get it going again and sorry I couldn't help you further.
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse
Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.
Hello All,
I would like to start by saying that I am a novice when it comes to rooting phones so ANY help received here will be greatly appreciated. I have come across a few people within the various forums who have a very similar issue to the one I am having, but nothing exact. Now to the point.
Phone: Zenfone 2 (Model: ZE551ML-23-4G64GN-BK) came unlocked from amazon.com
Carrier: Metro PCS.
PC used to root: Win 7 64 bit / AV: Avast Free.
Issue: About 1 month ago I rooted my phone. Last night I received a prompt to do an OTA update, and selected install. I realized after that I shouldn't have done that, but it was too late. My phone would not load past the black and white ASUS loading screen.
I then proceeded to do some research online, and try to "unbrick" my phone myself. I figured out how to hold the power button + volume up key, select Recovery Mode with the power key, and press power + volume up again to get into the Recovery Mode. I was following some instructions online that didn't really make sense, which led me to choosing Wipe Cache Partition. This didn't work, so I had to manually reboot the phone (Hold the power key, and turn it back on). From that point forward I have been unable to get back into the Recovery Mode. Once I get to the sleeping android with the red triange I have tried holding power + volume up (which got me into recovery mode the first time), power + volume down, power + both volume up and down, I've rebooted my phone several times to make sure I was doing this as soon as the little android appeared and nothing happens. The android just pulses in and out and nothing happens. This is the first of my many problems as I have never flashed a ROM before, and I am a novice. Also my PC does not recognize my phone at all at this point. I'm using the same cable and port that I always use when transferring files. The port has been tested with a tablet and iPhone, which works. My questions are as follows:
1. Am I screwed? lol.
2. Is there a way/trick to getting into recovery mode again?
3. Can I still unbrick my phone without getting into recovery mode? Is there something I can do with my phone connected to the PC perhaps?
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
For anyone who may have found this thread I think I found a fix here. I will let you know after I test this if it works:
http:
//valuestuffz.blogspot.com
/2015/10/fix-zenfone-2
-stuck-in-recovery-wipe-cache-partition.html?m=1
Sorry. I had to break up the link in order to post it.
Clavin0089 said:
I would also like to mention the following:
1. I've downloaded firmware Version V2.20.40.160 from asus website. Is this the right "image" or 4 files I should be using to flash onto my phone?
2. I've also downloaded ADB, but it doesn't look like the 15 second one, and it does not detect my phone. What tools do I download in order to fix the issues I am having?
Thank you in advance!
Best regards,
Clavin0089
Click to expand...
Click to collapse
i was in same sit with a brick of sorts and used this guid to help me:
> http://www.asus-zenfone.com/2015/12/how-to-downgrade-asus-zenfone-2-firmware.html *** I used this to go from the 168/174 ( 174 didnt fix issue that 168 caused ) back to 160
> http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html *** How to enter recovery if you dont know how
make sure the phone is plugged into a usb2 port and not a 3.0
what got me is when i installed adb, it put adb files in a default directory on my hdd, so i just copied the files to the folder where where i had all files at See below
i used the .160 file to restore my phone and it worked..
now if phone isnt detected yet, you may still need files. have you tried iSocUSB-Driver ?
I followed the steps outlined in the link:
http
://valuestuffz.blogspot.com/2015/10/fix-zenfone-2-stuck-in-recovery-wipe-cache-partition.html?m=1
And everything appeared to have gone smoothly, however, now my phone just loads, and will not enter the home screen. I just have that ASUS IN SEARCH OF INCREDIBLE screen now. I was able to get into the recovery mode, but it doesn't appear to have worked. I also received the "Permission denied" errors mentioned in the link. Any suggestions?
My phone is now detected by the PC for the record.
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
I did push over 3 files, but when I downloaded the .160, it only had droidboot.img,and boot.img. I tried both .168 (Which may have been totally wrong, but had all 3 files) and .160 from the asus website where you can select firmware. I did the .160 most recently. I put the recovery.img, droidboot.img, and boot.img into the adb folder, and ran the following CMDs:
Fastboot erase cache
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
I then used adb sideload CMD to load the .160, and it reached 100% and said successful. I attached a screenshot of what the "permission denied" CMD looks like.
Pu$$nBooT$ said:
didn't know of that but it has same steps but one I linkd easier to read and doesn't have wall of text.....
did you push the 3 required files via adb on bootloader screen ?
if so did you push the rom file in recovery once you selected adb sideload from the list ?
remember you have to follow the instruct exactly and be on correct screen when you push the files....
first boot takes some time
Click to expand...
Click to collapse
Tonight after work I will try the links you suggested to me once more, and let you know the results. I sincerely appreciate all of your help here! Thank you very much!
anytime...
i never seen/encountered that error message before... try adb kill-server command if you run into any issues. when you start again it will load automaticaly... have you tried different usb ports? stay on usb2.0 when connected and try original oem cable that came with the phone. if you dont have it, try different micro-usb cables ( i had issues when i had my lg g3 being on a usb3 port, so i made sure mine was plugged in a 2.0 port )
Currently i am on beanstalk, and want to go back to stock.
I flashed the stock recovery via fastboot, but when i enter into Stock Recovery mode, it gives me Error icon.
The whole process is to flash the stock zip via sideload, but i am not able to enter the stock recovery.
The stock version i am trying to flash is 2.20.40.160.
I flashed all three files, Droidboot.img, recovery.img, boot.img.
And then turned the phone off, and now it is stuck on Asus screen. Urgent Help!!
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Pu$$nBooT$ said:
btw when u see that error icon, nothing is actually wrong.... you have to hit 2 buttons simultaniously to enter recovery.
see > http://www.asus-zenfone.com/2015/03/zenfone-2-how-to-enter-recovery-wipe.html on step 6, this is normnal.. once u do button dance, you will enter step 7 and select flash via adb.. then you flash the rom file
Click to expand...
Click to collapse
Yeah, i looked it up, power + volume up. That did it. Thanks!
np...
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit.
Vol down + power buttons does not work. Neither does volum up + power. But when I press vol up+vol down+power my PC emits sound of connected device. I think that it is a problem of A/B partition, but I need to get to fastboot to fix it.
Any solution? I have already tried battery running out.
marcos_rgn said:
... my PC emits sound of connected device.
Click to expand...
Click to collapse
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
.
Renate said:
Yes, but what's it seeing?
You can poke around in Device Manager (View Devices by Connection can be helpful) and find which "device instance" is there.
You can also simply adb devices and fastboot devices to see if anything is there.
You could also try UsbLog.exe. Just run it and plug/unplug things.
Click to expand...
Click to collapse
This is with usblog.exe.
I have checked and adb devices and fastboot devices are empty even while device is connected (in that 3 seconds window). I have runned some commands with "wait-for-device" and they didnt work.
So you have the MediaTek ROM bootloader there.
I've played with some of the MediaTek stuff (and even started to write a native Windows MTK client), but I'm no expert.
There are two modes, 0e8d/0003 (ROM) and 0e8d/2000 (preloader).
You might look here: https://github.com/bkerler/mtkclient
Try holding the VolUp while rebooting to try to get 2000.
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
you can flash with this spflash tool to take back your phone.
SP Flash Tool v5.2044 Edited By Kurdish Gsm Team (Free Downlowd)
SP Flash Tool v5.2044 Modefiad Version With Auth Bypass Button
www.firmware4mobile.com
here is the video tutorial
Renate said:
I hope that you have a copy of your original boot? You can flash it back and see if things work.
It's always good to have a good recovery before you get deep in modification.
Click to expand...
Click to collapse
I have stopped boot loop by flashing boot.img and vbmeta.img with MTK client, thank you!
Generally speaking, if I want to return to default ROM, what files should I flash? What are the "software pieces" that Magisk touches and modify?
marcos_rgn said:
What are the "software pieces" that Magisk touches and modify?
Click to expand...
Click to collapse
Normally, Magisk only needs to have the boot image replaced.
The instructions tell you to optionally make the vbmeta inactive, but Magisk ignores all that verification anyway.