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?
Related
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
I recently installed miui from official website for lg e975. My phone is lg f180 so they both are same.
It was working fine till this morning it asked for update. I allowed. It retarted and now it starts shows google logo. Then goes to recovery.
I flashed my original backup rom. Then even flashed miui rom. Nothing changes. I wiped cache. Data dalvik a lot of times.
It just starts shows google logo. Goes to recovery. Please help
Im sorry if this thread doeant belong here. Mods please move
Thought i should add.
I dont have any other access but cwm recovery
I only have a backup of my original rom through cwm. No kdz files.
I have a miui zip rom on phone as well
awais3344 said:
Thought i should add.
I dont have any other access but cwm recovery
I only have a backup of my original rom through cwm. No kdz files.
I have a miui zip rom on phone as well
Click to expand...
Click to collapse
Flash stock zip kernel from artmod thread.
the problem is. I can't upload any files to mobile phone. if i connect to pc, it turns on, goes to recovery, so I click on mount storage, and other mount option, nothing happens. My computer detects phone as F180L with a exclamation mark.
If i go to download mode, and then try to flash any KDZ file from all the f180 KDzs. It gives me errors.
LG Support Tool on entering serial number and model name says "check out serial number and model"
ADB never detects my phone. So I can't upload anything.
No option to upload files via SD Card.
ok, so I have no clue what happened :crying: phone was in download mode. I did nothing, but only installed LG Support Tool USB driver, while the mobile connected.
Then I installed Microsoft .net framework 4.0. And my phone is now qhs_usbdload. it's officially bricked now. I have no clue what happened. This is all that happened before I restarted and selected "reboot to bootloader" and its dead. So there's nothing left to do but throw it out
WTF OKAY! I have no clue!
But, after seeing that qhs usbdload. (i have seen that before with other phones). I complete lost any hope.
So I for feeling contended, downloaded qpst, and emmc software download, and selected MPRG8064.hex and msimage.bin.
Then like I expected it threw an error "image download failed, cookie if present not received"
so I lost hope disconnected my phone and put it there. After a few minutes thought I should try one last time.
so I connect it my pc and VIOLA it turns ON!?
now I have that same rebooting to recovery problem. I have no explanation for whatever has happened to phone in past 3 hours. I have been with phones for years. This is the weirdest thing to happen ever :angel:
Now someone, please help me?
1. Why is this in Development section?
2. You can't mount internal SD as USB storage. Use adb push or adb sideload instead, that will help you to get the files onto your phone.
awais3344 said:
WTF OKAY! I have no clue!
But, after seeing that qhs usbdload. (i have seen that before with other phones). I complete lost any hope.
So I for feeling contended, downloaded qpst, and emmc software download, and selected MPRG8064.hex and msimage.bin.
Then like I expected it threw an error "image download failed, cookie if present not received"
so I lost hope disconnected my phone and put it there. After a few minutes thought I should try one last time.
so I connect it my pc and VIOLA it turns ON!?
now I have that same rebooting to recovery problem. I have no explanation for whatever has happened to phone in past 3 hours. I have been with phones for years. This is the weirdest thing to happen ever :angel:
Now someone, please help me?
Click to expand...
Click to collapse
Some user got that problem before. I am not sure about how they solve it but I guess that they flash their original KDZ back. If your phone can enter download mode, you should try LG Flash tool 2014 and flash your original kdz to restore incorrect system image.
About adb cannot find your phone, try to remove adb driver from device manager and reinstall LG usb driver.
artit said:
Some user got that problem before. I am not sure about how they solve it but I guess that they flash their original KDZ back. If your phone can enter download mode, you should try LG Flash tool 2014 and flash your original kdz to restore incorrect system image.
About adb cannot find your phone, try to remove adb driver from device manager and reinstall LG usb driver.
Click to expand...
Click to collapse
My phone is acting weird. Sometime it would start. Sometime the red light would blink. Sometimes the red light wouldn't blink at all. Then sometimes, it starts. And then it doesn't.
I have no clue what is going on with it.
But it went to download mode many times again, it would go to fastboot, bootloader, recovery etc. Then sometimes it will not respond to any buttons at all! I know its battery is down, but idk if it's charging or not?
I don't know how to know whether the phone is charging or not. I left it charging for 30 minute, and it didn't even buzz. :crying:
awais3344 said:
I know its battery is down, but idk if it's charging or not?
I don't know how to know whether the phone is charging or not. I left it charging for 30 minute, and it didn't even buzz. :crying:
Click to expand...
Click to collapse
One thing you can do (I've done it in the past a couple of times) is to crack your phone open, disconnect the battery, and charge it with an external charger. That would at least give you a full battery to start with...
Regarding the charging problems, I had that once. I was able to startup the phone by simply using a 2A charger instead of the LG's 1.2A.
When I had this issue it was charging while in recovery. Please look at this post and flash your kdz.
http://forum.xda-developers.com/showthread.php?p=54934779. This one helped me http://forum.xda-developers.com/showthread.php?p=53728658
Sent from my LG-E975 using XDA Free mobile app
kt-Froggy said:
One thing you can do (I've done it in the past a couple of times) is to crack your phone open, disconnect the battery, and charge it with an external charger. That would at least give you a full battery to start with...
Click to expand...
Click to collapse
thanks. but after charging it. I couldn't turn the screen off because it goes in recovery. I turned off the phone after good 30 minute charging. Then went to sleep. And in the morning I connected it to pc. by holding volume buttons for download mode. It didn't go to download mode. Only it's red light is blinking. and no display.
awais3344 said:
thanks. but after charging it. I couldn't turn the screen off because it goes in recovery. I turned off the phone after good 30 minute charging. Then went to sleep. And in the morning I connected it to pc. by holding volume buttons for download mode. It didn't go to download mode. Only it's red light is blinking. and no display.
Click to expand...
Click to collapse
Hey man. I have exaxt same prolem when update miui. Just do this when you got your recovey. Connect your phone to pc, let your pc update driver. Use adb sideload to flash stock zip kitkat e975 lgviet. Goodluck.
huy_gm said:
Hey man. I have exaxt same prolem when update miui. Just do this when you got your recovey. Connect your phone to pc, let your pc update driver. Use adb sideload to flash stock zip kitkat e975 lgviet. Goodluck.
Click to expand...
Click to collapse
Hi, regarding that. I was able to sideload exitrecovery.zip file. It goes to 100% then nothing happens. Nothing happened on phone screen as well.
And can you send me link to that stock zip kitkat? i have a miui.zip and few other roms that I have not tried. thanks
Edit: also what should I do about adb, am i doing correct?
Becuase in adb devices, my device is displayed with deviceID sideload
And i have only pasted adb folder, with a dll and a zip file, there is nothing else, do I need to install SDK?
I tried lg flash tool 2014 again, and it flashed, I swear yesterday I tried to flash it, and after clicking on it, it never showed me country and language selection menu, so it would sit there and do nothing. now I don't know how but it did it :laugh:
thank you so much you'all
I managed to install TWRP and when I tried to flash Furnace Kernel for D803, the phone is stuck on the furnace logo doing nothing. I'd like to come back to the original kernel, but can't push file using ADB sideload cause my ADB don't detect the phone. And, download mode is doing nothing. Helpp !
poudigne said:
I managed to install TWRP and when I tried to flash Furnace Kernel for D803, the phone is stuck on the furnace logo doing nothing. I'd like to come back to the original kernel, but can't push file using ADB sideload cause my ADB don't detect the phone. And, download mode is doing nothing. Helpp !
Click to expand...
Click to collapse
Have you tried this ?
http://forum.xda-developers.com/showthread.php?t=2582142
poudigne said:
I managed to install TWRP and when I tried to flash Furnace Kernel for D803, the phone is stuck on the furnace logo doing nothing. I'd like to come back to the original kernel, but can't push file using ADB sideload cause my ADB don't detect the phone. And, download mode is doing nothing. Helpp !
Click to expand...
Click to collapse
This is not the right forum for this fyi. But you should still be able to get right back into recovery just fine using the button press sequence. Turn off the phone with the power button, now press the power + Volume down button till the screen turns on then once it does, immediately release them both then press them both again til a white recover screen appears. Then just tap the power button two times and it will get you back into TWRP. From here you can flash the old Rom again and it should restore the original kernel. Regardless you should be able to take it from here.
RenderBroken said:
This is not the right forum for this fyi. But you should still be able to get right back into recovery just fine using the button press sequence. Turn off the phone with the power button, now press the power + Volume down button till the screen turns on then once it does, immediately release them both then press them both again til a white recover screen appears. Then just tap the power button two times and it will get you back into TWRP. From here you can flash the old Rom again and it should restore the original kernel. Regardless you should be able to take it from here.
Click to expand...
Click to collapse
I was able to go in recovery, but not transfer file.
Anyway, i managed to transfer file into my phone, and tried to flash another kernel, and it just brick the phone. I went to the service company and they gave a me a new Phone (Galaxy S4) for free since i was still on warranty. So thanks for all your help anyway. I hated that phone, so it's good thing it bricked.
poudigne said:
I was able to go in recovery, but not transfer file.
Anyway, i managed to transfer file into my phone, and tried to flash another kernel, and it just brick the phone. I went to the service company and they gave a me a new Phone (Galaxy S4) for free since i was still on warranty. So thanks for all your help anyway. I hated that phone, so it's good thing it bricked.
Click to expand...
Click to collapse
I'm sorry you had a hard time. The S4 is a decent phone yet not as good as the G2. Hope it gives you less of a head ache.
poudigne said:
I was able to go in recovery, but not transfer file.
Anyway, i managed to transfer file into my phone, and tried to flash another kernel, and it just brick the phone. I went to the service company and they gave a me a new Phone (Galaxy S4) for free since i was still on warranty. So thanks for all your help anyway. I hated that phone, so it's good thing it bricked.
Click to expand...
Click to collapse
- You need OTG cable.
- Copy your ROm in flash disq
- Reboot into Recovery.
- Go to Mount.
- Choose Otg storage.
- Flash your ROM.
:good:
Flashing is not without risks but you can lessen the risks by researching and learning before flashing blindly. If things go badly, 99% of the situations can be salvaged if you don't panick and research the fix before giving up. USB OTG is cheap and provides SD Card flexibility and allows you to back up your phone or rom off-site. Newegg has Kingston microDuo 32gb USB 3.0 right now for $16. http://www.newegg.com/Product/Product.aspx?Item=N82E16820239887
You can also buy a USB OTG cable and use any flashdrive with that cable for about $1 on Epay
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
zedopovo said:
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
Click to expand...
Click to collapse
if you can go to fast boot means your pc must recognize it. install asus usb driver and intel android usb driver. then flash firmware with AFT or with commands
sukhwant717 said:
if you can go to fast boot means your pc must recognize it. install asus usb driver and intel android usb driver. then flash firmware with AFT or with commands
Click to expand...
Click to collapse
He said fastboot doesn't recognize his phone anymore
Sent from my ASUS_Z00A using Tapatalk
zedopovo said:
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
Click to expand...
Click to collapse
There is still hope, this tutorial worked for me so I'll give this link to you:
https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
just follow the instructions and you're good to go, if you need help, I'll try to reply as soon as possible and there are many more experiencedd members here to help you, Hopefully this will work, Goodluck! :good: