Related
Hi guys i need some help with my phone, as there's lots of problems. First of all, this phone was given to me by a friend and im not sure what he did to it, and neither is he.Also, i am VERY confident it is NOT bricked.
So the first problem is that when i turn the phone on, i see the G! screen then it goes black (except for the backlight) and it will just stay there forever. Next, it does boot up into fastboot mode (with the 3 android skaters) when i hold power+camera, but i cant get it to work properly with my computer. The last problem is, i cant get into recovery, it just shows the g1 screen and then goes black forever. Also, when i hold the trackball and the power, the blue LED DOES turn on, i read somewhere that that means its not bricked so..
What i am trying to do is install the latest radio, ClockWorkRecovery, and HTX MUI X by Hintay
Any help you could give would be great. Thanks guys!
Info from fastboot screen:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005
CPLD-4
RADIO-2.22.19.26I
APR 20 2009, 15:30:43
blue light mode doesnt inherently mean its not a brick it just means you can force new firmware and software with jtag, problem is not many do this and it requires special equipment.
Not sure what happened to it either but the good thing is you have bootloader access, so what i would do is get your computer to recognize your phone, cant attest to why it isnt, did you install the proper drivers? did you install adb.exe and fastboot.exe from the android sdk? did you add a path in environmental variables or at least open the command prompt in the same directory as fastboot.exe?
i assume you have windows but if youre running a linux distro its even simpler to get fastboot working, i cant attest to mac being im not an apple guy
other issues may be a faulty usb port or bad usb cable
really you just need to get fastboot working on pc and then almost for surely what you describe can be fixed that way
Black screen
demkantor said:
blue light mode doesnt inherently mean its not a brick it just means you can force new firmware and software with jtag, problem is not many do this and it requires special equipment.
Not sure what happened to it either but the good thing is you have bootloader access, so what i would do is get your computer to recognize your phone, cant attest to why it isnt, did you install the proper drivers? did you install adb.exe and fastboot.exe from the android sdk? did you add a path in environmental variables or at least open the command prompt in the same directory as fastboot.exe?
i assume you have windows but if youre running a linux distro its even simpler to get fastboot working, i cant attest to mac being im not an apple guy
other issues may be a faulty usb port or bad usb cable
really you just need to get fastboot working on pc and then almost for surely what you describe can be fixed that way
Click to expand...
Click to collapse
I'm not sure what driver to install as there are 3 to choose from nad yes installed the adb.exe and the fastboot.exe and i did add the enviroment variable. Also, yes I am on windows. Also, when i plug the phone into the computer in fastboot mode, the phone changes from "fastboot" to "fastboot USB" which is good, right? and i am confident the usb wire works since i use it with other devices to charge and transfer files.
There's a good chance you don't have a brick but even with having bootloader access you still could. If you have a sim with data plan you can easily flash the dreaimg.nbh within bootloader. That an all upgrades including radio/recovery/SPL/ROM can be done without adb or fastboot. This may be more work then just finding out why it isn't working but its an option
Sent from my Nexus 7 using xda premium
Forgot bout dat
demkantor said:
There's a good chance you don't have a brick but even with having bootloader access you still could. If you have a sim with data plan you can easily flash the dreaimg.nbh within bootloader. That an all upgrades including radio/recovery/SPL/ROM can be done without adb or fastboot. This may be more work then just finding out why it isn't working but its an option
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I guess i forgot to mention this. When i try to flash the dream.nbh, one of two things happens. Either it doesn't detect the file at all, or it attempts to flash it but it will just sit there for hours never finishing. I'm hoping this doesn't mean its bricked.
Also, i dont have a data plan, i was waiting to add it until i got this phone working. Is it necessary to have a data plan to flash the dream.nbh?
Well it is leaning more likely that is a brick, if the SD card is good and is properly formatted that is. Also a good idea to check the md5sum of the .nbh you are flashing, needs to be named properly and on the root of sdcard (no folders)
If all the above is verified could easily be a brick but don't give up hope, double check everything, try again to get the proper drivers, and if all else fails sell it as parts
Sent from my Nexus 7 using xda premium
First of all, that's an old bootloader that does not have fastboot.
Format your SD card and then try to flash the DREAIMG.nbh
If it still does not work, and does not show any errors, I am afraid it sounds like you have a bad NAND chip.
Because if the file was corrupt, it would show an error. If you needed a gold card, it would show an error.
the 1.33.2005 spl does have fastboot flash capabilities as far as i know, so i would still keep trying that out (fix drivers etc) a fastboot erase system -w may cure some issues but if bootloader is corrupt then either jtag or try to flash a new one through fastboot.
but like nerdyguitarist said if its a fried nand then youre sol
Thanks Guys
demkantor said:
the 1.33.2005 spl does have fastboot flash capabilities as far as i know, so i would still keep trying that out (fix drivers etc) a fastboot erase system -w may cure some issues but if bootloader is corrupt then either jtag or try to flash a new one through fastboot.
but like nerdyguitarist said if its a fried nand then youre sol
Click to expand...
Click to collapse
im very confident im using the right driver, as i checked lots of threads to be sure, and I dont feel its worth the money to get such an old phone jtagged so im just going to let it be ;(Thanks for all your help and advice guys!
After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215
jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
i suggest you contact with HTC customservices to repair this problem.
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.
cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.
On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app
thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.
Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
PsyClip-R said:
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
Click to expand...
Click to collapse
Well, fastboot don't want to work neither so that answer didn't help at all
Tenderenden said:
How can I fix this?
Click to expand...
Click to collapse
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
doppelhelix said:
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
Click to expand...
Click to collapse
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot? Because I think that flashing stock ROM will erase any personal data, but I really need to get it.
Tenderenden said:
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot?
Click to expand...
Click to collapse
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Okay, I got it. Now, have you got any suggestions how to get contacts and (hopefully) SMS back?
Tenderenden said:
how to get contacts and (hopefully) SMS back?
Click to expand...
Click to collapse
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
Click to expand...
Click to collapse
Does this work with locked bootloader? That would be really messed up.
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
Click to expand...
Click to collapse
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
doppelhelix said:
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
Click to expand...
Click to collapse
Unfortunately in this case contacts weren't synchronised.
LuK1337 said:
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
Click to expand...
Click to collapse
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Tenderenden said:
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
Unfortunately in this case contacts weren't synchronised.
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Click to expand...
Click to collapse
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
LuK1337 said:
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
Click to expand...
Click to collapse
I will try it as fast as I can. Thanks
I am new to the forums and I need your help. The display on my LGWR went black after update even on cradle. It cannot even connect to my mobile via BT. The only thing it does is vibrate when the button is pushed and the heart sensor blinks a single time (when it turns on I guess.) as the vibration is a small one. When connected to PC running Windows 7, it is detected as Android Bootloader Interface, but ADB does not show any attached devices. Fastboot does show some alphanumerical device when (fastboot devices command is run). I have disassembled to remove the battery and tried to run it without the battery on cradle to no avail. Your help is needed as to what to do.
So it seems to hang in fastboot mode?
Try some fastboot commands then:
Code:
fastboot getvar all
fastboot reboot
Dear Ranf.
Many thanks for your reply. I ran fastboot getvar all and this is what I got. Screenshot is attached. Please guide me further.
Thanks.
Looks like you already downloaded the firmware? Right?
If so start with wiping cache and userdata:
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
I have downloaded the M1D63X boot, recovery and system (Disc Image Files) saved in my PC. They are not present in the SD card of LGWR. Shall I execute the commands or can I use fastboot and install this M1D63X on the LGWR. Thanks for your support.
The 2 format commands are basically the same as a factory reset. Please try them and then reboot.
Where did you download the file (URL please)?
Boot and recovery usually aren't trouble makers. system.img will if it's not a sparse image file.
The download like is as under Ranf:
http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Dear Ranf,
I tried to run Fastboot flash cache, and this is what the result was. Please guide.
Oh I see: you first need to unlock the bootloader with:
Code:
fastboot oem unlock
How can I dod that, as the screen is blank on the watch. I have tried it, fastboot says OKAY on my PC screen, but the watch does not reboot on its own and I have to manually restart it to get recognized in PC at Android ABD Interface. What can I do.
After running "fastboot oem unlock" you somehow need to acknowledge your decision (I'm a Sony SW3 user)
Either swipe the screen from tp left to bottom right or
press the power button.
Do you see anything on the watch screen when in fastboot mode?
Dear Ranf,
I finally able to unlock bootloader and formatted cache and userdata and then rebooted it, but the problem still exists i.e. black screen and only vibration.
Is there any way I can install stock Rom via fastboot and if so please guide me how and from which url should I download the files.
Thanks.
Screenshot of the fastboot format cache and userdata is attached for your perusal.
At 1st look the download you have is fine.
You need to flash 3 partitions:
Code:
fastboot flash boot M1D63X_boot.img
fastboot flash recovery M1D63X_recovery.img
fastboot flash system M1D63X_system.img
When you see errors at any of these steps post them here.
Thankfully all things well without any errors, but the watch is still the same, no display whatsoever. I am really devastated now. If there is anything else that can be done, please guide.
Screenshot of the processes is attached.
Sorry I must admit I'm a bit lost now. Best you ask @vt0r in the thread where you got the firmware from.
Thanks a lot Ranf. God Bless You.
You have done all steps that you can do, probably your display is broken...
I'm sorry...
When your watch starts, you see the lg logo?
Is there a way to check if the display is broken as when I disassembled the watch everything looked fine with no signs of wear or moisture. The battery also is not holding charge as when you put the watch on cradle it vibrates but off of it, vibration stops. How can I charge the battery manually.
Hey,
my watch had exactly the same problem.
I had to repair it. They had to replace the mainboard.
Luckily the warranty paid for this.
Lucas
Lucky for you that you had warranty left. For me there are two problems. First no warranty left and secondly replacement parts are not available here in Pakistan, so if there is any online store from I can manage the parts, do let me know Lucas.
Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards
I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.
UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?
Have you read THIS thread? Try to follow exactly those instructions...
jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help