Related
I did this: http://forum.xda-developers.com/showthread.php?t=2046439 then attempted to put CM10(http://forum.xda-developers.com/showthread.php?t=1840414) on the phone. I downloaded the stable version for Verizon wireless and made sure it was correct etc. I went to TWRP and put install then went to the .zip and continued after doing that the phone resets saying "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.". I am not entirely sure what I did wrong but it will no longer let me enter twrp but it does let me go to the download screen. Did I brick it or what? Thanks.
ryan7654321 said:
I did this: http://forum.xda-developers.com/showthread.php?t=2046439 then attempted to put CM10(http://forum.xda-developers.com/showthread.php?t=1840414) on the phone. I downloaded the stable version for Verizon wireless and made sure it was correct etc. I went to TWRP and put install then went to the .zip and continued after doing that the phone resets saying "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.". I am not entirely sure what I did wrong but it will no longer let me enter twrp but it does let me go to the download screen. Did I brick it or what? Thanks.
Click to expand...
Click to collapse
That method did that too me as well. use this instead
http://forum.xda-developers.com/showthread.php?t=2332825
You didn't brick it I had that pop up my first flash as well
Pretty sure It was because it didn't unlock the bootloader correctly.
http://forum.xda-developers.com/showthread.php?t=2199042
spitfire143 said:
That method did that too me as well. use this instead
http://forum.xda-developers.com/showthread.php?t=2332825
You didn't brick it I had that pop up my first flash as well
Pretty sure It was because it didn't unlock the bootloader correctly.
http://forum.xda-developers.com/showthread.php?t=2199042
Click to expand...
Click to collapse
How do I use odin to put the bootloader file on my phone since it's not an .md5 file etc.? Sorry, just don't understand.
" I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!"
Boot normal. use tool in first link to unlock the bootloader and CM should be up and running
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
also you should be able to get into recovery just let go of the volume, power, home as soon as you see the samsung logo pop up
spitfire143 said:
" I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!"
Boot normal. use tool in first link to unlock the bootloader and CM should be up and running
---------- Post added at 02:00 AM ---------- Previous post was at 01:58 AM ----------
also you should be able to get into recovery just let go of the volume, power, home as soon as you see the samsung logo pop up
Click to expand...
Click to collapse
I did the hold the volume button down/home at same time then press power but that sends me to the normal do I want to download press up to continue or down to cancel. I pressed down and it still gave me the warning. I try going to recovery but it prevents me by telling me the same message. I think it's the bootloader like you said but I don't understand how to get the file on the phone through oden. I downloaded that first link but it won't go through oden because it's not the .md5 etc and the computer isn't showing me the phone data through my files.
I am going to odin flash a stock image then re-boot.
I reflashed the phone using odin. I went through and used the "casual" rooting process which appeared to work. I went into twerp then pressed install then pressed the .zip for the CM mod. It re-loaded and now it's stuck on the CyanogenMod screen with a circle. I don't understand if it's installing or what?
I understand now why it wasn't working. Answer in here: http://forum.xda-developers.com/showthread.php?p=36341274 Anyways, now that I got CM to work. GAPPS refuses to work, it sends an error message saying that the Setup Wizard has failed. I don't understand that.
Checked to make sure the GAPPS version I downloaded was the one compatibale with the CM version, it was not so I re-downloaded the correct version now everything is working great. Thanks spitfire143 for all the help and getting me on the right track!
I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!
I suggest that a mod moves this to the General section
pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon
timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??
Thank god for this thread omg, saved my life
Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!
Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers
hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it
I have Huawei Mate 7 L09, and I have problem because my phone doesn't charge. I can't turn it on and I can't enter to update mod or to hard reset but only on fastboot and rescue mod. Anyone can help to solve this problem, please????
when I try to charge the phone only show me a battery with red and the light pulse 5 time to red. how does it mean?
my phone is not rooted or unlocked.
:crying:
have you tried it longer to load over night or so?
yes, when I charge for a long time the battery show me 100% and when I try to turn it on it's the same.
I have the same problem, I can’t enter on Recovery or force update through the three buttons method, my bootloader is unlocked.
Anyone can help!
Regards
MM or LP on it?
I attempted to upgrade from LP to MM the phone ended to bootlop, I then unlock the bootloader and trait the bat method given in a Spanish website in order to wake up the device.
I can’t not install recovery or force install through the three boot method, my device can only enter in fastboot safe mode.
Please answer.
BR
---------- Post added at 12:27 PM ---------- Previous post was at 11:52 AM ----------
Genti007 said:
I attempted to upgrade from LP to MM the phone ended to bootlop, I then unlock the bootloader and trait the bat method given in a Spanish website in order to wake up the device.
I can’t not install recovery or force install through the three boot method, my device can only enter in fastboot safe mode.
Please answer.
BR
Click to expand...
Click to collapse
One more explanation of my problem.
I attempted to upgrade from LP to MM the phone ended to bootlop, I then unlock the bootloader and used the bat method given in a Spanish website in order to wake up the device at this address http://forum.frandroid.com/topic/215484-unbrick-mate-7-mt7-l09/.
Now I can’t install or enter recovery or force install through the three buttons method, my device can only enter in fastboot safe mode.
Please answer.
If is this the brain forum than there should be an answer.
BR
Time ago happened to me with a MTK phone. Flashed the wrong ROM and, therefore, the wrong recovery. I trust you must succede in installing back stock recovery. Not easy I understand.
does it work with fastboot locked, because i cant unlock my phone.
I want to put my phone back to factory, as it was out of the box. I have done a few things but when it starts up, the keyboard is missing and all the stock Apps are missing.
Can someone provide me with a step by step guide on how to put it back to stock Android 7.0
Cheers
what i did was reboot to recovery (twrp) if you can somehow, and plug in to computer and use adb to reboot to bootloader. adb reboot bootloader
from there i hold down power and volume up (keep plugged in to computer). It should boot to stock recovery and you can connect the phone to wifi and download stock.
I was on Lineage and it was working great I just wanted to go back to stock 5.0 emui. This worked for me after I screwed around for a day trying to figure out how to get back and I sort of stumbled into it.
It was stuck on the blue Honor Screen immediately after for the first boot forever so i actually held down power + Volume down I think until it rebooted then immediatley Power Button + volume up and factory reset it again. This did it and booted it up back to 5.0.
the only thing is my bootloader is still unlocked. Back on emui 4 this sort of method would lock it up as well as unroot and put everything back to stock but it doesnt lock the bootloader back up at least on mine. hope this helps sorry if my directions suck this is my first time posting.
For me, when I try to download from the recovery screen it comes up with an error and won't download.
jasonst165 said:
For me, when I try to download from the recovery screen it comes up with an error and won't download.
Click to expand...
Click to collapse
That is my problem, too. Didn't find any workaround for it yet and would also be interested!
I am on the US l04 version maybe yours is a different model and uses a different method?
Really difficult to find 100% sure fire answers at least for me with this particular device so I just started to be my own guinea pig and test out things on my own. I also was able to lock my bootloader back by using this command
fastboot oem relock [unlock code i received from honor site]
cfda.008 said:
I am on the US l04 version maybe yours is a different model and uses a different method?
Really difficult to find 100% sure fire answers at least for me with this particular device so I just started to be my own guinea pig and test out things on my own. I also was able to lock my bootloader back by using this command
fastboot oem relock [unlock code i received from honor site]
Click to expand...
Click to collapse
I am on the FRD-L09 Version. I also have another problem, that my PC won't recognize my Honor8 in Fastboot Mode (both: google's .exe files and the amazing Huawei MultiTool by Team MT).
every ADB Command works fine so far.
Since all downloadlinks for Huawei Firmware from here didn't work for me so far, too, i am trying the original Firmware from hihonor.com. The last time i checked it wasn't offered there until recently.
I am trying to make a SoftwareUpgrade via the Service Menu (*#*# 2846579#*#* tipped into the calling interface). This will execute the Update.app i copied to my sdcard/dload/ folder.
I hope i am not forgetting any procedures before i try to update. Right now my device is rooted and the bootloader is unlocked, while TWRP3.1 is installed.
I'm new to this so I don't know how to share links or files yet or even if thats possible but I used the "Huawei Android USB Driver" I found on one of the posts on this site. I cant remember exactly which one I'm not the most organized person with my files. look around on xda there are links to it somewhere. I'll try to dig around for you here in a few minutes see if i can find the link.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
Oh one more thing
in emui 5.0 i found USB debugging always shuts itself off for some reason. So when your phone is plugged in go back into your developer settings and switch usb debugging back on.
I dont know why they changed this it wont stay on for me at least automatically
cfda.008 said:
I'm new to this so I don't know how to share links or files yet or even if thats possible but I used the "Huawei Android USB Driver" I found on one of the posts on this site. I cant remember exactly which one I'm not the most organized person with my files. look around on xda there are links to it somewhere. I'll try to dig around for you here in a few minutes see if i can find the link.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
Oh one more thing
in emui 5.0 i found USB debugging always shuts itself off for some reason. So when your phone is plugged in go back into your developer settings and switch usb debugging back on.
I dont know why they changed this it wont stay on for me at least automatically
Click to expand...
Click to collapse
The USB Driver you mentioned are the ones which can be installed via the Huawei Multitool by Team MT. In the unzipped folder from there, there is a Huawei_Multi-Tool.bat which can be run. It can be used for multiple purposes, even installing all drivers. (except the ones for my fastboot connection obviously, but it also could be a hardware problem. so i didn't report this problem to them).
perhaps it can already help you guys.
I resolved my issue. I followed the downgrade instructions and it worked a treat. It then auto updated back to Nougat.
I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
use another Android phone download huaweifirmware finder on the google play ，select mha-l29c567，than select dns update，change your router dns，you can do erecovery after setup dns！
sweetjuice said:
use another Android phone download huaweifirmware finder on the google play ，select mha-l29c567，than select dns update，change your router dns，you can do erecovery after setup dns！
Click to expand...
Click to collapse
Thank you for your response. However, I tried it and it didn't work for me. I downloaded the app, checked the firmware was available, registered the update, changed my router DNS, and then attempted the eRecovery. It downloaded the package then installed it, but the same problem continues.
audioralf said:
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
you can install a full firmware with hwota method.
audioralf said:
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
Is this the information you're asking for?
Huawei Mate 9
Version: MHA-L29C567B910
I don't know how to get any other information (other than the IMEI and SN which are on the box), since I can't make it past the boot logo screen.
mavera said:
you can install a full firmware with hwota method.
Click to expand...
Click to collapse
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
cr33p3r1n1134 said:
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
mavera said:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
Click to expand...
Click to collapse
Rebranding is not really necessary.
@OP
For MHA-L29C567B190 (you wrote B910 which I assume is incorrect), use:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v84935/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...35/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/.../v84935/f2/full/hw/usa/update_full_hw_usa.zip
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
cr33p3r1n1134 said:
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
Click to expand...
Click to collapse
Unlocking bootloader does a factory reset so that might be why it's working again
cr33p3r1n1134 said:
I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Click to expand...
Click to collapse
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
ji_mestone said:
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
Click to expand...
Click to collapse
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
cr33p3r1n1134 said:
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
Click to expand...
Click to collapse
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
ji_mestone said:
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Yeah, the ADB sideload problem also happened to me. Eventually gave up on that.
I hope I'm allow to post links.
But here is a link to something I remember using.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Using those tools mentioned in that post helped me out. I had to do a lot of experimenting with that as well. Every time I connected and disconnected my phone from my computer, I checked which were the references that needed deleting, then deleted them. It was tedious, but I'm not expert, so maybe I took the long way.
Maybe try using those tools?