Related
Hi guys !
I believe I just bricked my phone, and I'm looking for some help. Here's the story :
I wanted to upgrade my GNex to AOKP kitkat (latest nightly : aokp_maguro_kitkat_nightly_2013-12-25.zip ).
I wanted to wipe it clean, so I first flashed the latest Google factory images : yakju-jwr66y-factory-09207065.tgz, everything went smoothly.
I then flashed the latest TWRP (openrecovery-twrp-2.6.3.2-maguro.img) via fastboot, still no issue.
I used the MTP mount on windows to transfer the new ROM, kernel and Banks Stadard Gapps.
I flashed them through recovery, in that order:
aokp_maguro_kitkat_nightly_2013-12-25.zip
franco.Kernel-nightly-r394.zip
12-14_GApps_Standard_4.4.2_signed.zip
I did a Factory reset prior to that, but no wipe between flashes I believe.
Now I'm stuck into the boot animation, which goes on forever (basically until the battery dies)
NOW : The thing is, I can't simply boot into bootloader; MY HARDWARE VOLUME KEYS ARE BOTH BROKEN !
During the boot process, The device is recognized by the computer (plug in/out sound), I can see the device with adb, but it's marked as "off line" when I try to reboot into recovery or bootloader.
When the phone was switched off but plugged onto the computer, it was detected as "OMAP 4440", and the drivers could not be installed. I then downloaded the latest Samsung drivers from this post : http://forum.xda-developers.com/showthread.php?t=961956 , and the phone doesn't do anything when it's plugged in (but switched off) now...
Does anyone know how to deal with the situation ? The phone seems to not be not quite dead yet, but I can't find a way to reset it.
I can provide any additional information if needed !
Thanks in advance for the help !!
You can try with a USB JTAG (very cheap from ebay) to boot your phone into Download Mode and then flash it with Odin.
Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked
BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!
can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?
Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.
I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?
Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems
Anyone?
does erase work?
yes
can you get into recovery?
oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka
how do you know that erase works, I mean that what you erased has really been erased?
One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.
still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
I have access to the device via usb / fastboot, adb is not registering. If anyone has any suggestions on what I can try, please let me know. I do not have a backup or a version of the OEM ROM. Every effort so far just sends me right back to the Fastboot screen with 3 options. Anything I can run from command prompt using fastboot alone that would help in this situation? Any way to do a factory restore without having an actual OEM image?
Well im stuck at the verizon screen too but for a different reason
JRSwole said:
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
dadrumgod said:
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
Click to expand...
Click to collapse
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Thanks for your response, I have unfortunately tried that too and wipe cache, reset , all back to fastboot. I figured it would be impossible without a pc. Oh yea my stock recovery says modified in the top left corner, but anyway I can get access to a PC But honestly it's been awhile since I even needed to use one and don't know exactly where to start, like navigating around, and how to install what software on the pc. I can't find anyone that will walk me through it locally or online and every tutorial I find is missing some lil step I need. I know Android in detail but after basic root my experience hits a brick wall. I'm capable of more jus got to get broke in on a pc again. Now I only care to root for stuff like freezing apps, gesture control, and really want to use any app in dual window. Ain't screwing with any system tweaks again it was pointless lol I guess I need all the right files and hit up the pc...can't really do worse no??
Sent from my VS986 using Tapatalk
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Oh yea I almost forgot I got side tracked earlier. I know there is already a twrp, I have 2 versions (2.8...something and the next version strait off twrp site. I was the one guy it wouldn't flash through flashify for but others claimed it did. God knows really, but I'm gonna wait till I have a PC of my own before I touch my g4 but man the ability to open any app in dual window is just too damn sweet...if I could only change that one word on build prop to false without all the other hassle
Sent from my VS986 using Tapatalk
JRSwole said:
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
gnomesinrome said:
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
Click to expand...
Click to collapse
If your problem is from an OTA failing due to taking it while modded and you can get to fastboot the following command might fix it:
Code:
fastboot erase cache
That will delete the OTA zip and break the bootloop.
Quick background on situation.
I was running CM13 and I still have TWRP 3.0.2-0. I wanted to try out CM14 or some other variant. I went into TWRP Recovery Mode and Advanced WIPED everything except the Internal Storage and MicroSD (this is probably where I messed up?)
Then went to install and navigate to the new rom and gapps on my microsd card. Well TWRP does not see either. It lists both of them but with 0MB and unselectable. I tried two other card, no go (all FAT32). Tried OTG with 3 different thumb drives, same results. The OS is gone and all I get of course is the white ASUS boot screen loop. ADB doesn't see any devices as well (windows device manager see no new devices when I attached the cable or when I list devices).
The only thing I can boot into is TWRP and I have tried everything to access the SD/OTG without success.
So can I assume I have bricked this thing and must go onto the IntelSOC XFStik procedure? and if so, does having a working TWRP on there force me to deviate from the normal unbrick procedure I have see here and on youtube?
Or is it something really easy that I am missing? I am fairly novice (as noted by my current situation), so maybe it's an easy fix?
Any help is appreciated. Thanks.
@Endosmok
You have LP version twrp recovery? , not the mmbl twrp recovery installed ? which ends in 3.0.2.M1 ??
If you do have 3.0.2.0 for LP bootloader which early versions of CM13 used , then you can fastboot flash stock recovery for 4 20 40 196 in bootloader from here....
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Thanks go to Shakalaca
To get into bootloader -- from Twrp , select reboot , select power off !
Count to ten after switching off.
Press power and vol + , release power when it vibes , release vol+ at asus screen.
Fastboot flash stock recovery for above LP .196 in bootloader , when flashed --- scroll via vol buttons to recovery and hit power. At the dead android , press power and vol+ together for 4 secs , release vol+
You should be in stock recovery now.
Scroll to `update over adb` and select .
adb sideload LP official firmware from asus for LP .196 or .198
If you need help to get thru this step , just ask:good:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Endosmok said:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Click to expand...
Click to collapse
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
timbernot said:
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
Click to expand...
Click to collapse
Ok... let me get this straight.... before I sound too dumb...
You want me to go into the bootloader from TWRP (using Reboot > Power Off), even though I get to TWRP via the bootloader (recovery mode) from a power on?
Also, how do I know if fastboot is enabled? Is it when I see FASTBOOT MODE in the color red on the bootloader screen with 'continue the fastboot process' at the bottom?
I've done step by step what you wrote and I get to the bootloader but fastboot devices shows nothing (I've tried different computers/cables as well). I have the computer connect to the phone w/ bootloader screen on with what i wrote about FASTBOOT MODE in red and contine the fastboot process. If that is not correct, let me know. I did hold down the Volume Up for a bit longer
I'm almost thinking I have a hardware issue with my phone. I did replace the mic with a new module prior. I never checked if the usb storage was functioning after. Though it charges via the usb (even connected to a computer it charges but not recognized as a device). I'll have to double check that as well.... not sure why the sd card is not recognized though either... never touched that area. Could be the reason why TWRP can't access either the micro sd or otg?
I do appreciate the help... and i have been reading other threads... just seem to be at a stand still for now... suggestions are always welcome.
update: tried adjust the cable on the mic module ... no dice... replaced with older mic module, no dice... don't think it's a hardware issue.
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
audit13 said:
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
Click to expand...
Click to collapse
So made some progress here. I think it was a hardware issue now... I put back the new mic module and reconnected the cable and now I can see my SD card and the computer sees it as well in adb and fastboot. That's the good news....
But ran into a new issue when trying to install any ROM from my micro sd card. I get ERROR 7 no matter what ROM I try to install. I have verified that they are the proper roms for my Z00A ZE551ML but still a no go.
What steps should I take next if I can now communicate but get error 7?
Thanks
Which recovery are you using to flash and which file are you trying to flash?
I am using TWRP 3.0.2.-0. Using the install from zip. I select any rom (Nougat Based so far I have tried). RR, Lineage, Octopus, all with the same error.
The phone is running a MM bootloader? What about MM or LP based ROMs?
I believe Timbernot said it was an LP based. I believe I installed about April last year and it was 3.0.2-0
Looks exactly like this
https://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704
You probably need an MM bootloader for custom Nougat ROMs. Did you try any LP-based ROMs?
I have not tried any LP based yet. I will try in a bit and forward the results.
Thanks
Post removed. Let's keep things respectful here folks. :good:
And remember, to each their own.
Cheers,
Darth
Senior Moderator
Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards