So yesterday I installed TWRP alongside CM13.
After that I got some problems with the ROM (rebooting, slow charging) so I decided to return to stock. To flash the stock .kdz I needed to go into download mode, that however did not work my phone just booted normally into CM when I tried to use the method to get into download mode (vol+ & USB). I even tried to force download mode through adb on PC however that also only rebooted the phone.
Then I did a wipe in TWRP (everything except Internal Storage) and shut off the phone.
Now I have the problem that I can not boot (because I obviously have no ROM installed anymore) but I also can't get into recovery anymore.
Also my phone seems to be in "only charge" mode from CM so my PC does not even recognize it correctly. I can't even see it in device manager and neither adb, nor the flash tool nor anything recognizes it.
When I connect my phone to the PC it just shows the CM battery icon that you see when you charge your phone while it's turned off and the LED is glowing yellow.
All of this are things that were new with CM so I guess there is still something left from CM that does prevent my G2 from acting as MTP.
Please tell me there is still hope...
Related
Hi
As many people here i've encountred a problem with fota while being using a rooted ROM (g.lewarne ROM)
Now my phone is bricked. I can't go into recovery nor Download mode. I only have the LG logo for moments with error: secure booting error!
cause: boot certification verify
When i plug my phone it is not recognized in the hardware manager. I've already installed Drivers.
All i have in the hardware manager is a new hard under name QHSUSB_BULK that needs driver.
I have just one hope to get my phone alive, by reconizing it again by my computer, then maybe i can go under download mode.
I've tried everything but nothing could work without download mode.
PS: I've made a hard reset, which was maybe a silly decision.
By the way, after installing the OTA my phone went into CWM Recovery, it was detectable by adb, i used adb to reinstall TWRP, then i used command
"adb reboot download" instead of "adb reboot recovery", then i had never seen the CWM recovery again, only the mentioned above error.
After few seconds my phone screen goes black but the phone is still on since i can see light at the corners of the phone.
and it is not reachable by adb.
It makes me crazy now.
once i plug it to the computer it gives me plenty drives to format and one drive with only one folder inside called image, only readable, with many files inside.
Could you please help me to get my phone alive?:crying:
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
Hello. Few months ago I installed unofficial Cyanogenmod 11 on my E610. After updating baseband it worked perfectly. After some time I decided to restore my phone to the state after installing CM11. It worked no problem. Today I wanted to do the same, and after installing SuperSU and Texdroider DPI I rebooted my cellphone, and it stucks on the cyanogenmod boot logo. If I try to get to recovery mode it stucks on the LG logo instead of CM. Hard reset is not happening at all. I tried to connect my phone via LG User Support Tool and install kdz firmware, but no luck. Although when I connect my phone without the battery to my PC i hear the "ding" windows sound, and phone exists in device manager. It also creates some disc drive in my computer, but unfortunately it's empty. I think textdroider has changed the build.prop file, so the cyanogenmod is not able to start at all. Is there any possibility to get to the build.prop file and change it, so phone will start? Or maybe somehow I can reset my phone or reinstall firmware using my USB cable without entering usb debug or recovery mode? Thanks in advance for any idea :crying:
Put your phone in Emergency Download Mode : switch it off, hold volume down button while plugging USB cable (already connected to the PC).
Then use the Support Tool to go back to LG ROM
mikesrike said:
Hello. Few months ago I installed unofficial Cyanogenmod 11 on my E610. After updating baseband it worked perfectly. After some time I decided to restore my phone to the state after installing CM11. It worked no problem. Today I wanted to do the same, and after installing SuperSU and Texdroider DPI I rebooted my cellphone, and it stucks on the cyanogenmod boot logo. If I try to get to recovery mode it stucks on the LG logo instead of CM. Hard reset is not happening at all. I tried to connect my phone via LG User Support Tool and install kdz firmware, but no luck. Although when I connect my phone without the battery to my PC i hear the "ding" windows sound, and phone exists in device manager. It also creates some disc drive in my computer, but unfortunately it's empty. I think textdroider has changed the build.prop file, so the cyanogenmod is not able to start at all. Is there any possibility to get to the build.prop file and change it, so phone will start? Or maybe somehow I can reset my phone or reinstall firmware using my USB cable without entering usb debug or recovery mode? Thanks in advance for any idea :crying:
Click to expand...
Click to collapse
in these cases emergency mode should work
removing battery sim sd etc... connect your phone to the pc throught us cable pressing vol- it automatically boot into download mode and you can easily use kdz.
make sure you have the last driver from lg websites else kdz wont find your phone, and set emergency option in kdz everything else it similar to a normal flash
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Croshio said:
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Click to expand...
Click to collapse
You must have flashed wrong version of the rom .
After trying the linux method, if you cant get into fastboot mode, recovery or not in download mode, then try this : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
This requires you to open your phone so be cautious .
Thanks I followed that guide. Download mode after. Using the Windows tool instead of Linux then flash tool normally.
Hi,
I have unlocked Xiaomi Mix 3 5g. Phone never been rooted and I've never tried to apply custom ROM. SInce I've got it I'm on original software: at the moment MIUI Global 12.0.3. I've only had TWRP recovery applied but this wiped out ant went back to original recovery after my phone updated itself last time to 12.0.3.
Basically I've had phone ready to apply custom ROM but never done it accualy. I was always on original MIUI and TWRP recovery was applied to my phone.
A the moment after I connect phone to PC using cable, smartphone discovers PC connection but on PC I cannot see internal memory of my phone. And yes I have all needed drivers installed and I've tried using 3 different cables...
I think that may happened after my phone updated itself last time and went back to original recovery...
The worst problem is that now I cannot flash back to TWRP. When phone is connected to PC and I go to CMD, typing ''adb boot fastboot'' command is working and phone reboots itself to FASTBOOT MODE but once I'm in fastboot mode commands are not working and on flash attempt I only see < waiting for any device >
Any solution for this ?
Try using usb 2.0 ports or different computers.
I sometimes get mine to flash by inputting the command first then plugging the phone in afterwards.