Related
Hello
Here's my proplem:
I flashed cyanogenmod nightly build (12.03.2013) and everyting was fine until i updated my HOX by the cmupdater to the next nightly build (13.03.2013). This build is screwed as i can understand ( http://forum.xda-developers.com/showthread.php?t=1786696 ). Ok, then i flashed old working rom (12.03.2013).
USB connection not working since i flash it, however all other works great. In cwm recovery usb storage is not working too. And even in fastboot mode usb is not working.
sorry for my english... hepl me!
Hi,
Did you install HTC Sync Manager to get the HOX drivers ?
Also, if USB doesn't work in CWM... I suggest you to change your ROM, kernel etc....
(On which ROM, kernel etc. are you ? Did you install any addons ?)
o0oMegA said:
Hi,
Did you install HTC Sync Manager to get the HOX drivers ?
Also, if USB doesn't work in CWM... I suggest you to change your ROM, kernel etc....
(On which ROM, kernel etc. are you ? Did you install any addons ?)
Click to expand...
Click to collapse
Yes, htc sync manager and all drivers are reinstalled about five times - no result. I`ve tried three cords, all three are original.
I was on stock ROM, then i flashed cm10.1. And now I'm on stable nightly cm10.1 build. I just can't flash anything, fastboot isn't working...
In cwm I tried to restore old stock backup, but the phone just stops on bootscreen, because i can't flash boot.img i think...
I'm in panic!
I even don't know what else i can try to do to fix it...
'adb devices' returns nothing; same with 'fastboot devices'. I even can't reinstall fastboot mode drivers, cause there's no reaction from windows when i plug the cable in.
Is it kind of "usb brick" or what?
And... is there another method to flash kernel? without fastboot i mean.
what a moron i am...
Full formating of internal memory via CWM was totally bad idea... Now my HOX is totally bricked.
Please help, mates...
What you can't power it on?
Uninstal all drivers and htc syncmanager from the pc. Go into device manager and delete any entry that has something to do with android phones or myHTC (of its there) reboot the pc
Put the phone in the bootloader and connect it to the pc .....
TToivanen said:
What you can't power it on?
Click to expand...
Click to collapse
I can power it on, but there's nothing but the recovery on it.
Mr Hofs said:
Uninstal all drivers and htc syncmanager from the pc. Go into device manager and delete any entry that has something to do with android phones or myHTC (of its there) reboot the pc
Put the phone in the bootloader and connect it to the pc .....
Click to expand...
Click to collapse
Did it all, nothing happened. In fastboot mode when i plug the cable in "fastboot" becomes "fastboot usb", but windows is't reacting...
Fastboot usb is a start.....what if you perform
Fastboot devices from the command prompt
Mr Hofs said:
Fastboot usb is a start.....what if you perform
Fastboot devices from the command prompt
Click to expand...
Click to collapse
Oh, i've tried it so many times... But "fastboot devices" returns nothing, as i said, any other command writes "waiting for device"
Hmmm im running out of ideas here
So you get nothing in the device manager....not a unknown device or APX ?
Mr Hofs said:
Hmmm im running out of ideas here
So you get nothing in the device manager....not a unknown device or APX ?
Click to expand...
Click to collapse
No, nothing...
Mr Hofs said:
Hmmm im running out of ideas here
So you get nothing in the device manager....not a unknown device or APX ?
Click to expand...
Click to collapse
I've found my old HTC Desire, reloaded it into bootloader, then connected to PC and killed all drivers. With Desire it all work great, but HOX is still bricked...
Hmmm then i guess you have some serious usb brick
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Do you know your hboot version and cid....the only possible thing i can think of is a ruu ? If it can read the phone
Mr Hofs said:
Hmmm then i guess you have some serious usb brick
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
Do you know your hboot version and cid....the only possible thing i can think of is a ruu ? If it can read the phone
Click to expand...
Click to collapse
It's no good. It can be fixed in HTC Service center?
hboot 1.36.0000
cid 038 (india as i remember)
It belongs to 3.14.720.** but i can't find one....only lower ones, so thats a no go.
I guess its a repair centre issue
Mr Hofs said:
It belongs to 3.14.720.** but i can't find one....only lower ones, so thats a no go.
I guess its a repair centre issue
Click to expand...
Click to collapse
I think RUU can't help...
To say that it's sad - is to say nothing...
Anyway, thanks a lot for trying to help, mate! :good:
Well i wish you all the best and i really hope you get it sorted ! This goes beyond my knowledge
Ok, my HOX has been bricked too once.
To unbrick it, I downloaded the ROM of my Internet provider (SFR) and installed it on my phone... (I had no waiting for device issue but to put the rom inside my SD card I used the CWM recovery)
Then I installed a custom ROM.
Also, you may try to :
1. Google your " Waiting for device " issue in fastboot usb mode
2. Get a new fastboot kit. I use the "zedomax"'s fastboot kit (it's a Youtuber) You may find the kit in videos descriptions.
I suppose you didn't make any backup of your HOX thanks to the CWM... :l
(I didn't make any backup of my HOX when it's bricked but now it's working fine...)
Good luck !
o0oMegA said:
Ok, my HOX has been bricked too once.
To unbrick it, I downloaded the ROM of my Internet provider (SFR) and installed it on my phone... (I had no waiting for device issue but to put the rom inside my SD card I used the CWM recovery)
Then I installed a custom ROM.
Also, you may try to :
1. Google your " Waiting for device " issue in fastboot usb mode
2. Get a new fastboot kit. I use the "zedomax"'s fastboot kit (it's a Youtuber) You may find the kit in videos descriptions.
I suppose you didn't make any backup of your HOX thanks to the CWM... :l
(I didn't make any backup of my HOX when it's bricked but now it's working fine...)
Good luck !
Click to expand...
Click to collapse
I have few backups: of stock ROM and of cmROM, but it's no connection when i mount mass storage in CWM...
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
myhtconeV said:
Thanks for replying ya
Unfortunately I have TWRP. So my one v is going for repairs :crying::crying:. Still not given up...trying it on my other lappy, lets see if adb picks it up there.
Click to expand...
Click to collapse
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
red de0392 said:
Don't Sweat too Much Mate. It Won't boot into recovery.
Well My Vol Buttons are Dying As well...Will flash CWM Now
We should Learn from other
Click to expand...
Click to collapse
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
myhtconeV said:
:good: what if i try that with mine?
Downloading HTC Sync Manager. Hope the updated drivers work. Called up my IT guy. He is giving me a quote on repairs tomorrow. Come to think of it, my one v was bound to end like this. Screen broken and shattered at 2 places, headphone jack socket gone, volume buttons gone.
Now upgrading to...........................wait for it............................ Nokia 1100.
Click to expand...
Click to collapse
Hahahah...That's a Beast
myhtconeV said:
So by the heading you guys must know I have messed up pretty badly.
Let me tell you first, I have done my research. Tried each and every thing possible (AFAIK) but it just wont boot into recovery.
FLASHBACK: ( I have Sff) (Volume button is broken).
1) Did a clean wipe ( Cache, Dalvik, System),
2) Installed Ignorance V4, ( I thought the kernel must be in the zip, so didnt flash the kernel)
3) Phone booted and stuck in splashscreen. ( Ignorance)
4) Connected it to Laptop via USB. Checked ADB. Device not found.
5) Switched off device, connected to laptop, checked ADB, Device not found.
6) Checked through device manager, and device manager recognizes the phone. All drivers are installed and updated. Windows Vista.
Now, what to do? Is there any way I can get into recovery or even Hboot so that I can flash kernel?.
Need help
Owner of a messed up V.
Vickrant.
Click to expand...
Click to collapse
Recently I have seen one interesting issue that might appear like solution to your problem. According to the description you may try turning off your phone and plugging in a charger. If you will have the same behaviour your phone should start into recovery mode. =)
Edited: Doh! TWRP...
You may try All-In-One-Kit as well. It has high level interface to run adb commands (including Boot into Recovery). Yeah yeah, I've seen your note that adb does not recognize your device, anyway...
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
Stupid answer from me....... Op are both your volume buttons broken?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes.
I have given it for repairs.I have decided not to sell or dispose it.
Its only sometime before I buy a moto g or xperia device. Waiting for my new credit card :fingers-crossed:
which phone would you suggest?
Vickrant.
If you are good with 16gb storage better buy Moto G if not there are a few options like Xperia M , Canvas series and all..
Sorry to be so late to the party, but in case other people get this issue. ADB will often work just after the kernel finishes loading, before it gets shut off. So between the htc boot screen and when the boot anim starts you have a window to commit abd commands. I often use this to save time when flashing kernels etc, notably because my WIP roms rarely make it past bootanim!
red de0392 said:
Which recovery u have ??
If you have Cwm...Let ua battery drain completely and then put in on charge, it will boot into cwm directly. That's the only option.
If you have TWRP, lol..I'd Suggest you torepair your Vol Buttons
Click to expand...
Click to collapse
You sure about this?i am stuck there and i have cwm recovery installed,will it switch itself straight to recovery after the battery is dried up?i am using sony xperia c
Apparently my phone is bricked..
I rooted my phone a long time ago when I first got it, never installed any roms or anything.
I get this message on the LG Screen:
"Secure Booting Error problem
Device UnLock!!, so Boot Success!!"
I've tried multiple ways to fix my phone and I can't get any of them working.
I'd be happy to pay the person in a steam game of your choice!!!!
Thank you
AustinBobDox said:
Apparently my phone is bricked..
I rooted my phone a long time ago when I first got it, never installed any roms or anything.
I get this message on the LG Screen:
"Secure Booting Error problem
Device UnLock!!, so Boot Success!!"
I've tried multiple ways to fix my phone and I can't get any of them working.
I'd be happy to pay the person in a steam game of your choice!!!!
Thank you
Click to expand...
Click to collapse
If you use lg flash tool to go back to stock it should work.
2SHAYNEZ
shayneflashindaily said:
If you use lg flash tool to go back to stock it should work.
2SHAYNEZ
Click to expand...
Click to collapse
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
Uninstall and reinstall drivers ... Try different computer. Lg flash tools should fix your problem . goodluck
2SHAYNEZ
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
That message upon boot is normal if your phone has been modified. Mine says it too and my phone is booting up perfectly fine. In fact, it always has said that from the day I first modified it.
Most likely your software is just bricked. First of all, BE HAPPY YOUR PHONE IS JUST SOFT BRICKED! :laugh:
(I recently hard bricked my phone by accidentally flashing a file for a completely different phone... phone was completely dead!)
You need to provide more info for anyone to help you, whether it's me or someone else:
1) What phone are you using? E980, E988, E986, F240, etc etc.
2) Do you have a custom recovery, like CWM or TWRP? (I'm hoping you are because getting software back will be easier).
2.1) Can you boot into this recovery? (hold volume up and power button at the same time. The boot animation will begin and the screen will then shut off again. Once it does, let go of the power button, but keep holding the volume up key. The phone should reboot into recovery. It's tricky to do, and if any other readers notice that I described it wrong, please correct me!)
3) Do you ever see the LG boot animation? (The animated LG logo)
4) Once you see that message upon boot, do you wait for it to pass and hope the phone boots, or do you panic and force the phone off?
5) To get the drivers to install for using LG FlashTool, have you done the following?
- First download and install the drivers from the LG site (I'd link you to it, but I only know the link to the E980 drivers. I don't know what phone you have).
- Once installed, plug your usb cable into your computer, but not the phone.
- Hold the volume up and volume down buttons at the same time while plugging the usb cable into the phone
- Phone should now boot into Download mode and your computer will start installing more drivers. Let them install.
- Change the Com port of the phone to Com41 (ask if you don't know how to do this)
- Continue using the LG Flash Tool.
I apologize if any of this sounds like I'm insulting your Android phone intelligence. I don't know how much of this stuff you know.
spexwood said:
That message upon boot is normal if your phone has been modified. Mine says it too and my phone is booting up perfectly fine. In fact, it always has said that from the day I first modified it.
Most likely your software is just bricked. First of all, BE HAPPY YOUR PHONE IS JUST SOFT BRICKED! :laugh:
(I recently hard bricked my phone by accidentally flashing a file for a completely different phone... phone was completely dead!)
You need to provide more info for anyone to help you, whether it's me or someone else:
1) What phone are you using? E980, E988, E986, F240, etc etc.
2) Do you have a custom recovery, like CWM or TWRP? (I'm hoping you are because getting software back will be easier).
2.1) Can you boot into this recovery? (hold volume up and power button at the same time. The boot animation will begin and the screen will then shut off again. Once it does, let go of the power button, but keep holding the volume up key. The phone should reboot into recovery. It's tricky to do, and if any other readers notice that I described it wrong, please correct me!)
3) Do you ever see the LG boot animation? (The animated LG logo)
4) Once you see that message upon boot, do you wait for it to pass and hope the phone boots, or do you panic and force the phone off?
5) To get the drivers to install for using LG FlashTool, have you done the following?
- First download and install the drivers from the LG site (I'd link you to it, but I only know the link to the E980 drivers. I don't know what phone you have).
- Once installed, plug your usb cable into your computer, but not the phone.
- Hold the volume up and volume down buttons at the same time while plugging the usb cable into the phone
- Phone should now boot into Download mode and your computer will start installing more drivers. Let them install.
- Change the Com port of the phone to Com41 (ask if you don't know how to do this)
- Continue using the LG Flash Tool.
I apologize if any of this sounds like I'm insulting your Android phone intelligence. I don't know how much of this stuff you know.
Click to expand...
Click to collapse
No, no I understand!
1)E980
2)I have TWRP.
3)I only see the LG Logo, the error message and that's it, it goes right to TWRP after that.
4)I wait for it to pass, and it goes to TWRP.
5)I will try this on a different PC, because when I boot into download mode and plug in the phone, the drivers attempt to install but fail. I have attempted to re-install them multiple times, but I'll give it a shot on my laptop tonight, and let you know if that works.
Thanks for the help, and I may PM you later!
AustinBobDox said:
No, no I understand!
1)E980
2)I have TWRP.
3)I only see the LG Logo, the error message and that's it, it goes right to TWRP after that.
4)I wait for it to pass, and it goes to TWRP.
5)I will try this on a different PC, because when I boot into download mode and plug in the phone, the drivers attempt to install but fail. I have attempted to re-install them multiple times, but I'll give it a shot on my laptop tonight, and let you know if that works.
Thanks for the help, and I may PM you later!
Click to expand...
Click to collapse
Have to tried install cwm through twrp then wiping clean and installing a ROM ...
2SHAYNEZ
Me thinks his botloop is due to a bad rom flash, flash a rom(EZ kat is a good choice if you want the AT&T stock experience). follow shayne's instructions.
@AustinBobDox:
I know EXACTLY what the problem is. You ran into the notorious recovery bootloop, which seems to be happening to many Kitkat users running recoveries incompatible with KK.
I had it a few times myself while using CWM, PhilZ Touch, and TWRP (Yeah, I got them on all 3!)
Unfortunately, the TWRP and CWM recoveries posted in this forum cause this bootloop randomly if you have the stock Kitkat rom installed (whether rooted or not). Personally, I have not been able to get out of it. I ended up flashing a "fix" that was supposed to get me out of it, but... it was for a completely different phone (an HTC) and it hard bricked my phone.
SO DON'T FLASH ANY "FIXES"!!!!!!!!!
Technically, the ROM is perfectly fine. I read that this bootloop is caused by the phone setting a flag that tells it to boot straight into recovery. Basically, when you initiate the recovery boot, it sets this flag, and when you reboot the phone, it's supposed to clear the flag. In the case of this bootloop, it doesn't get cleared for some reason.
Luckily, since you are on TWRP, you can try this:
Open the TWRP command console thing (I think it's under Advanced or something).
Type this command EXACTLY:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
DOUBLE CHECK YOUR SPELLING, SPACES, ETC!!
EDIT: I put a part in bold because it's .1
The decimal could easily have been missed if reading on a smaller screen or something.
Submit the command and try to reboot to system via the TWRP menu.
If this doesn't work, then you have no choice but to use the tot method once you get it working.
EDIT: Oh and before getting the drivers to install by plugging in the phone, install these drivers:
http://www.lg.com/us/support-mobile/lg-E980
(Look under Software Update tab)
Whether the command works or not, once you get the phone up and running again, install this recovery:
http://forum.xda-developers.com/showthread.php?t=2760895
It's the only recovery right now that's definitely working on Kitkat without the bootloop issue. The only downside is that it can't mount the external_SD, so anything you flash must be on the internal storage.
EDIT: Oh and in case you can't tell, don't flash this recovery! You install the APK in Android and then open the app and install recovery from there. You need to root first though.
---------- Post added at 03:48 AM ---------- Previous post was at 03:38 AM ----------
luisoman2000 said:
Me thinks his botloop is due to a bad rom flash, flash a rom(EZ kat is a good choice if you want the AT&T stock experience). follow shayne's instructions.
Click to expand...
Click to collapse
With this recovery bootloop, even if you flash a new rom, the bootloop could remain. I wasn't able to try a whole new flash, but I did try restoring a backup (different things, I know) and I still kept booting into recovery.
Oddly enough, this has happened to me on all cwm versions, flashing the hacked twrp was the only way i could get out of it. I use cwm to flash roms, twrp i only use when in bootloop or to flash mods.
Sent from my LG-E980 using Tapatalk
AustinBobDox said:
I tried but the drivers won't install correctly. They did once, but it just said something along the lines of "Ready", and never did anything even after plugging and unplugging.
Click to expand...
Click to collapse
Did you make sure under, device manager, your port is set to com 41 for your device?
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
jrotert said:
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
Click to expand...
Click to collapse
Since it doesnt show up in device manager, I cant uninstall the driver there.
I also tried it on a new PC that did never get in touch with an android phone - nothing. Not even a sound when I plug it in. The phone is just charging, thats it.
Have you tried using a different cable?
Keksdroid said:
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
Click to expand...
Click to collapse
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
panicbear said:
Have you tried using a different cable?
Click to expand...
Click to collapse
I dont have any other cable, but maybe I should get a new one just to test. The cable I have is just 3 months old and was high quality....
pincher65 said:
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
Click to expand...
Click to collapse
Yeah I always used that tool in the past. But since my PC doesnt recognize the phone at all, not even in fastboot mode, that doesnt help me. I really need a solution that works just with TWRP...
Edit: Just an idea from my side. Would it work if someone, who just cleaned flashed, makes an nandroid backup, which I just restore with TWRP?
what radio at you installed? 7.1.1 02.2017 for TWRP
pincher65 said:
what radio at you installed? 7.1.1 02.2017 for TWRP
Click to expand...
Click to collapse
Radio is m8994f-2.6.36.2.20 - flashed it in December.
For TWRP?? Can I flash the stock zim through TWRP?
Keksdroid said:
For TWRP?? Can I flash the stock zim through TWRP?
Click to expand...
Click to collapse
yes. also PixelROM has full img
pincher65 said:
yes. also PixelROM has full img
Click to expand...
Click to collapse
Okay I will try that. I guess I will loose TWRP when I flash it?!
Keksdroid said:
Okay I will try that. I guess I will loose TWRP when I flash it?!
Click to expand...
Click to collapse
No.
pincher65 said:
No.
Click to expand...
Click to collapse
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Keksdroid said:
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Click to expand...
Click to collapse
disable check md5sum in setting TWRP.
pincher65 said:
disable check md5sum in setting TWRP.
Click to expand...
Click to collapse
Either way I'm blind, or I dont have that setting...
Keksdroid said:
Either way I'm blind, or I dont have that setting...
Click to expand...
Click to collapse
sorry, I have inattentively read the previous post. redownload zip if doesn't help, then your recovery is damaged and it is necessary to look for a way to connect him to PC
Problem solved. Got a new USB cable today, it worked now. Flashed stock image, it finally booted.
But wow, the old cable is already broken after 3 months...well it still charges very fast, but thats it.
Hi, I am new to custom ROMs install , recently got a Poco F3 and When installing I run into a problem, the pc doesnt recognize the device after I run the batch install for the device, when running the console, it gets stuck here (Ill add a picture), its been one hour like this, whta can I do? I am using the lastest version of Pixel Extended.
Also I can no longer get back into normal MIUI so IDK what to do.
Thanks for any help and sorry if this sounds like such a noob mistake but I am really lost right now
Edit:
SOLVED! IDK how, but It was a drivers issue, had to install It and uninstall it multiple times, sometimes the device manager would recognize it but the console script wouldn't, don't know really why it happened but hey I fixed it and managed to install custom ROMs, thanks for the help.
looks like a driver issue when its rebooting fastboot mode,check device manager,might just need to unplug cable and then plug back in to get it working again.
if that doesnt help try a different driver on the pc.
metalspider said:
looks like a driver issue when its rebooting fastboot mode,check device manager,might just need to unplug cable and then plug back in to get it working again.
if that doesnt help try a different driver on the pc.
Click to expand...
Click to collapse
And which kind of driver should I get because in the MIUI unlock app, it says that the latest drivers are installed. Where could I get other drivers?
Bruh124 said:
And which kind of driver should I get because in the MIUI unlock app, it says that the latest drivers are installed. Where could I get other drivers?
Click to expand...
Click to collapse
are u able to boot to recovery? at this step, your phone should boot to recovery, and enter fastboot from there
if able to enter recovery, select advanced > enter fastboot
the installation should continue. dont seem a like a driver issue to me
keyoke87 said:
are u able to boot to recovery? at this step, your phone should boot to recovery, and enter fastboot from there
if able to enter recovery, select advanced > enter fastboot
the installation should continue. dont seem a like a driver issue to me
Click to expand...
Click to collapse
It DID get into recovery mode with the pixel experience logo in it but the script wouldn't move past after waiting for device(one time for like 2 hours)
In the end IDK how, but It was a drivers issue, had to install It and uninstall it multiple times, sometimes the device manager would recognize it but the console script wouldn't even start saying waiting for device , don't know really why it happened but hey I fixed it with that trick and managed to install custom ROMs, thanks for the help!!