[Solved] - Full Wipe - Newsflasher -> no usb device vid:0x0fce pid:0xb00b - Sony Xperia XZ1 Compact Questions & Answers

Hello,
Device is rooted and BL is unlocked and on FW v47.2.A.10.45
Performed a wipe incl system and internal storage. (Dalvik/ART is included)
Wanted to start over, and perform a full backup after this...
I shouldn't have checked ''internal storage'' in TWRP is my fault here i believe.. NO OS.
Now NEWSFLASHER can't flash the device cause of error:
No usb device with vid:0x0fce pid:0xb00b
Click to expand...
Click to collapse
Grabbed a other laptop.
Disabled driver signing.
Reinstalled GordonGate flash driver.
Also this laptop gives the same error.
Can i throw away this device ?
I still can get into flash and ''adb'' mode.
Things should be possible you should say.
Thanks in advance..
Fingers crossed, still busy ruling things out.

Does it show up correctly in device manager?

It did yes. (SOMC FLASH DEVICE)
Issue solved in the meantime.. but how ..
I've flashed this unit 3 times before now in flash-mode while the led was BLUE. (flash mode, as it should be right)
Apparently it can be flashed as well while it's in recovery mode.. (or bootloader mode?)
Connected the phone through USB (on pc) while holding volume DOWN when led went GREEN.
In NewsFlasher i pressed N twice, and it flashed instead of giving the above mentioned error.
Luckily i got quite fast in the meantime of repeating all the steps (flashing twrp, magisk, removing bloatware etc)
Issue solved.
Now full nandroid backup time to get this over with.
Thanks for your time anyway!
Saw different solutions for this everywhere, but not flashing a device while it was NOT in flash mode, lol.
Curious if somebody has an explanation for this.

I got EXACKTLY the same problem....
Worked fine last summer. :s

Hi! I have the same problem.
Please, can you explain to me exactly all the steps to fix it?
Thank you so much

This appears to occur if there is a problem with the "android-sdk-platform-tools" package..?

Related

[Q] How to unbrick my 4X - a question of life and death!

I have half-bricked P880. Bought just a week ago.
My ROM is stock V10C. I’m trying to get rid of that crap ROM, but so far without success.
I have rooted the phone but flashify is the only app saing that the phone is not rooted. Every other app which requires root is normally working. I can’t unlock the bootloader because phone can’t be recognized by any computer, using different Windows, USB cables etc. It just shows charging but PC doesn’t see any connected device. Nor the phone shows any connection option when I connect it to PC by USB.
I’ve tried to install TWRP (without success) and CWM (successfully) but the phone can’t be load into bootloader. Just an LG logo will appear and this error message:
[LGE_SECURITY ERROR] boot image signature
Critical failure: Unable to start kernel
Unrecoverable bootloader error (0x00000002)
I think it’s still locked.
This method hasn’t help either…
http://forum.xda-developers.com/showthread.php?t=2251407
What’s more, the error message appears almost every time I try to turn on the phone. Sometimes it takes 10 attempts until the phone will finally boot into Android.
Yes I’ve tried basic things like playing with USB debug mode, LG PC suite option/USB tethering… please don’t respond to my question by that kind of suggestions, I’m no rookie in flashing roms and Android problems.
Only hope for me is to flash kdz file via PC (when the phone is off and battery out). BUT I’m unable to do that, due to problem that the phone is again NOT RECOGNIZED by PC. Of course I've tried every kind of LG driver but the problem is in the phone, because the PC won’t even notify by sound that a phone has been connected to it. So I need to change the corrupted bootloader… somehow.
I’ve already searched everything to this issue on XDA and elsewhere - without any solution. So I’m 95% the phone is half-bricked without any chance to flash new ROM.
If none of those things that you said doesnt work, as last resort you should try this
http://forum.xda-developers.com/optimus-4x-hd/general/s-stuck-rescue-ultimate-rescue-guide-t3012444
Thank you for a quick reply! However the autor of the method says:
i mean when you get stucked with S/W screen, and you can't flash the device in any way
Click to expand...
Click to collapse
In my case I can't say that I'm stuck with S/W screen. Because I don't even get in there. Any PC in my home (XP/Windows 7) don't even recognize that a mobile has been connected to it. So there is no S/W screen. The only way I can get in S/W screen is to keep the battery in, but it doesn't solve anything. Because the phone remains unrecognized to PC. Therefore I'm unable to flash anything. A simple explanation in here arose: the USB port in my phone is faulty. BUT, how that can be, when the USB charging works fine and even S/W screen appears while the battery is in?
Either way I'll keep your suggestion as the final solution(since I'm very skeptical of it and also dont have screwdriver small enought to take out those tine srews) if there will be no other responce to my problem.
I'm not very experienced in things like this, but when I was flashing kdz to my phone, my computer wasn't able to recognize the phone with battery out, so I did whole process with battery in (and it worked)
anyway if you want to unlock the bootloader you have to update to official JB (just flash JB kdz and then wipe data in LG recovery to prevent bootloop)
so first you have to connect somehow your phone in sw mode to computer
then flash JB kdz and wipe data in LG recovery (it should be back even if you've flashed twrp)
and finally root JB and unlock bootloader (for example this way I found by two clicks here at xda, just browse Optimus 4x general category: http://forum.xda-developers.com/showthread.php?t=2251407 )
I hope I helped you a bit
I agree with you SuperLamic. Especially with this:
so first you have to connect somehow your phone in sw mode to computer
Click to expand...
Click to collapse
My only hope is to flash kdz file using fastboot mode. However after days of searching on XDA, installing all kinds of drivers, trying different methods etc., I'm still unable to connect my phone to PC.
Any PC I tryied so far haven't even made a sound while pluging my LG to it. Nor it's vissible in the list of connected USB devices.
So now I'm sure that a USB port on my phone is faulty There is no other possible explanation. But thank you all for your suggestions anyway.
P.S.
There is maybe a tiny chance for workaround by unlocking the bootloader without PC. But this method doesn't work. http://forum.xda-developers.com/showthread.php?t=2251407 With unlocked bootloader I woud be able to solve the problem without PC. Right now I can't install TWRP nor CWM because they require bootloader to be unlocked. CWM in ROM Manager always says that installation was successful but actualy, it wasn't. Since there is always this error when I try to load recowery mod...
[LGE_SECURITY ERROR] boot image signature
Critical failure: Unable to start kernel
Unrecoverable bootloader error (0x00000002)
EDIT:
So I find out that only JB ROMs can be unlocked. It's not possible with my stock ICS. So there is really only one solution: repair my USB port on LG to flash kdz. But I'm afraid that these days a repair will cost more than the phone itself :[

After Nougat 4.0 - onePlus 3t dead

Hi there,
perhaps you guys can help me
I use a onePlus 3T 128GB and directly after delivery I update the OS, install twrp, make a clean backup and then personalized the phone.
Runs quite good but yesterday I wanted to update the system to 4.0 Nougat...
So I downloaded the full installer, backuped the full current system via twrp and then flash and install the 4.0 version.
Yeah... doesn't work really good...
After the Pin and the code for the sim card, the OS ask for a third pin code but none of both works. And I never have another pin code since years...
Then I wipe the cache and system with twrp and restore the last backup. Doesn't work. It only boots to the onePlus Logo and then nothing happens.
Same for the first clean backup without any personalisation...
For now I have an great smartphone that doesn't work... yayy...
Anyone of you has an idea how can I get my running phone back – with all my data and apps?
Edit1: adb sideload doesn't work
Edit2: Full Installer installed >> reboot >> no OS installed
Thanks for all guys.
Oliver
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
You said you wiped your system..
what did you expect?
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
raj7749 said:
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
No, it doesn't work
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Jo_Jo_2000 said:
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
When wiping system before installing a full roms zip (not only an incremental update), I would expect a working, os containing partition - like on the oneplus one (did that many times on bacon). But I can confirm, it's not working on opt3; at least not with oos4. In this case I need to restore working systemmpartition (from twrp-3.0.3-0), and flash then the rom zip.
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
GammarursPulex said:
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
Click to expand...
Click to collapse
Would you try the following: From twrp restore your very first backup (firmware, system and boot), don't leave twrp and wipe (reformat with f2fs) data (I'm talking of the entire userdata partition, not only "wiping data without wiping media"); flash the full oos4 zip (the one with 1.4GB); don't leave twrp, go to Advanced->copy logfile. Try to boot system.
If the system stiil refuses to boot up completly, get the logfile with adb via twrp and show us.
DO NOT try this, without usb-c otg cable and usb stick, because you are reformating your data partition. That's the reason I have not tried this: need to get an usb-c otg cable (BTW: recommendations on usb-c otg cables welcome, but OT: so PM).
GammarursPulex said:
No, it doesn't work
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
mcdachpappe said:
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
Click to expand...
Click to collapse
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
GammarursPulex said:
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
rms4067 said:
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
Click to expand...
Click to collapse
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
GammarursPulex said:
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
Click to expand...
Click to collapse
When you say load the backup, you mean a backup that you made in TWRP recovery, prior to bricking your phone?
My experience with the unbricking guide was that it in essence did a full wipe and reset (including the recovery partition). That would eliminate TWRP from your phone as well as any stored backups you had.
When I unbricked, I opted to just leave it stock as nougat was around the corner.
I also re-read your original post. I wouldn't have considered your phone "bricked" at that point.
I would bet that you could have booted the phone into TWRP.
You'll want to keep these things in mind too for future TWRP encryption issues (it's a known issue that most likely won't be fixed).
1) before you make a twrp backup, remove any figerprints/pins/passwords from your device, sometimes prevents issues for me
2)if you existing pins/passwords don't work try "default_password" that may work
3)if all else fails, boot into twrp, navigate to /data/system/ and down the list will be a few files to delete
- password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
4) the last step is always the first step for me, too many issues with twrp and encryption
GammarursPulex said:
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
Click to expand...
Click to collapse
u r doing something wrong.. please follow guide correctly
It works 100℅
Just out of curiosity, did you unlock the bootloader before you did everything? Also did you go into settings -->developer mode and turn on OEM unlock and USB debugging?
From my experience, try wiping everything through twrp --> install the firmware/backup --> and then try doing another wipe and reboot. Now I understand you might lose your root/SU after wiping, but perhaps this will at least boot into the system for you.
If all else fails, try using ODIN and flash your stock firmware http://downloads.oneplus.net/devices/oneplus-3t/
EDIT:
If you're having driver issues try this.
1. Go into device manager (as admin)
2. Double click the device that you're having trouble with
3. Click on "Details" tab
4. Under "Property" dropdown, choose "Hardware Ids"
5. When you select that you should see a bunch of values under there. Right click the first one and copy it.
Ex:\ I have an S7 phone so mine looks like "USB\VID_04E8&PID_6860&REV_0400&ADB"
6. Now the value you copied, try searching it in google. Or paste it on here for us to help you find drivers compatible with it. Usually you can find compatible drivers in google. Once you find them and download them, if you go back to that device and click "Update Driver" you can manually point to the extracted drivers. It will find the compatible *.inf file and install it for that device.
Hope this helps!
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
this works for me, every time i kill my 3T.
you must be doing something wrong.
Follow everyline

OP3T Bootloop - no way to flash new firmware?

Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
If you can flash/boot into TWRP, then probably nothing is lost. While in TWRP, if you connect your phone with PC, what happens? Do you hear the usual USB connection sound? If yes, what appears in the device manager?
Even if it doesn't appear in device manager, don't worry.
Boot into TWRP, go to storage, DISABLE MTP and enable it again. I know it sounds dumb, but just try it. It will be recognized as long as you have the proper drivers installed.
After that copy the zip of an OxygenOS based ROM like FreedomOS and flash it. Don't wipe anything. It will boot fine. I've done that a few times, never had a problem.
Thanks for the advice guys - no, no sound, nothing - as I said, I only get the charging (+) icon in twpr next to the battery percentage.
I did disable and enable MTP before - although not plugged in a pc during the process - will try if I have the chance.
One more thing that might ring a bell for someone - I tried the key combo for hard reset today(power + vol down) for a couple second and moments later I got a fuzzy (random colored pixels) screen and a red led. Weird, if you ask me.
P.S.: Today I tried to chat with OP a bit - 230 Eur for a new MB (64GB) and 255 Eur for my 128GB version - I just wanted to know, I'm still not admitting failure though. But as a student, these numbers from the support literally hurt me when reading...
grello said:
Hello!
I am a happy owner of a OP3T 128GB version, but I've currently ran into an interesting issue . I am familiar with rooting android, fastboot, adb and stuff and I have limited experience (a begginer, but a quick learner ) with some other android phones. I hope I'm not creating a duplicit question - I am really sorry if I am, but I haven't found a solution to my problem even after hours spend behind the desk.
Long story short - accidentaly did an Advanced wiped in TWRP (3.1.1-0) and wiped my system (OS) and everything in the phone. I don't really care about the data, but checking the Sysem box in Advanced wipe menu has brought me into serious trouble it seems. Of course, I got a bootloop - my bad, right , nothing I can't fix I thought... But when I approached to try to flash a zip or .img of a system file/stock ROM respectively, I found literally no way to do so. My phone isn't recognized by my PC(s) (Windows and Mac) and I tried everything I could. The device isn't even a Qualcomm or sth. in the device manager - simply nothing, I can only get the device to charge sometimes when connected to the PC (seen in TWRP). I cannot connect an USB key to it via OTG either in TWRP to flash from there - TWRP just does not seem to know I even plugged a USB into the phone. I tried OP drivers, adb naked drivers, the phone and the PC just don't seem to be communicating at all.
The device can boot into fastboot, recovery (TWRP) and if proceeded TWRP prompts with "No OS installed" and I get a bootloop as expected. Is there any way I could try to flash the device with proper firmware? I do have the firmware and everything, I just can't seem to find a way how to flash it . I am a young student who just likes to play with tech stuff and devices and messed up and cannot help myself and I am really hopeless at this point . Any advice is greatly appriciated.
Thank you so much.
Matus
Click to expand...
Click to collapse
1) try to update the twrp to the official 3.1.1.0. Then flash the latest modem firmware for your device and try to flash a custom rom like lineage os (a 7.x rom)
If you connect the phone to PC in TWRP and your phone is not recognized, chances are good that either your phone's USB or the cable (or the USB port on the computer) is not working. You can try to download the adb driver installer from here, just to check if your phone is listed by the installer: http://adbdriver.com/downloads/
Update - tried the MTP Enable/disable option in TWRP (in the Mount menu) while plugged into the PC, with no luck
IvanPrince - have you actually read the description of my problem? I have the 3.1.1-0 and even if not, how should I actually flash another version of twrp? The problem here is I cannot seem to find a WAY how to flash ANYTHING on the device.
I'll see about the adb drivers and update.
Thanks all,
Does the phone show up as anything on the PC when you boot to fastboot? I re-read but didn't see anything about it.
Nope - nothing. By now, I believe it is a hardware problem as the phone indeed got wet before my mistake with the advanced wipe. It appears to work just fine though, apart from the connectivity issue, so I believe the MB should be ok as everything else, including the screen is.
I just have one, perhaps a little courageous thing I'd like to ask from someone kind enough. Anyone with a Oneplus 3 or 3T who's not afraid to open the phone for a couplne minutes and has a multimeter alongside with a USB cable should be able to help me. :angel:
Could you, my awesome stranger, check where the 4 USB pins (on the side where you plug them into the PC) lead (make contact/'BEEP' on the multimeter) with the actual phone motherboard? It would REALLY help me in troubleshooting and perhaps saving 250 Eur. So far, I have this: (same color means contact) at that point. See picture.
BLACK - GND (all the heatsinks are connected to GROUND as well)
GREEN - DATA +
YELLOW - DATA -
RED - VCC
If anyone decides to open up their phone and help out a fellow xda guy, it will be greatly appriciated. :angel:
Hey Bro I was curious to know if you tried this method of recovering from a hard brick... When I first got my 3t something similar happened to me. I can't remember all the details of my hard brick but I thought I was f***ed. Please try this if you have not already.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Might be a dumb question, but you did remember to mount the USB when you connected the otg right?
If the bootloader is unlocked, you can save it.
I would flash the stock recovery and the latest factory image (4.1.7)
Download them both from here:
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/
After flashing the stock recovery using fastboot, boot to stock recovery and sideload through ADB the stock factory image.
Reboot and after checking that everything is working fine, feel free to relock the bootloader if you wish to stay 100% stock.
If the computer doesn't recognize it at all then it's a driver problem, not the phone... at least that's what I think.
try to use the program to fix my oneplus 3t it said download complete. try to restart
try to use the program to fix my oneplus 3t it said download complete. try to restart it and can press the screen and it keep rebooting it like the screen is frozen
please help me out

Can't boot into flash mode after making stupid moves

Hey!
I used the SLiMM rom for quite some time. The phone got really really slow, so I reflashed it. Restored apps, some time it was okay, and then again. So I decided to try a different rom.
The phone was previously done after this tutorial - https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
So, to the issue now. Long story short, I flashed the CarbonROM through TWRP (didn't hassle to search how to install it correctly, my bad). Anyway, I bricked the phone. Red blinking led. I got it saved with Xperia Companion. Now I'd like to do all the stuff again, but I can't access flash mode anymore. With the same computer I used to do it before (Windows 8). Unfortunately, I don't have a Windows 7 computer here anymore, but I've tried it on one Windows 10 computer, same issue. I can access fastboot. If I try to repair it again with the Xperia Companion, it also needs flash mode, which it can't access.
Can you please help me?
I've tried different ports and cables, siganture verification is turned off, reinstalled drivers, tried with different Flashtools. Did the factory reset, and the hard reset.
Please please.. :angel:
EDIT: fastboot is actually not working, only the blue LED lights up.
EDIT2: with about the 8th time, suddenly it started working. USB2, Windows 10.

Alcatel Idol 4 6055K problem with firmware

Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.
I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers

Categories

Resources