Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?
Related
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.
carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:
the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.
Already tried that ... Also impossible.
Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.
You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.
I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
tnsmani said:
Most likely the connector has become loose (since you have not said anything about the screen being broken) and you can try to reconnect it by yourself.
Another alternative is to see if adb is working and your PC is authorised. If so, you can use the 'adb pull /sdcard' command to copy your data to the PC.
Alternately, search with Google since I remember reading about a method to mirror your screen and then using the mouse to enable whatever you want.
Click to expand...
Click to collapse
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
manto02 said:
I'll check the connector but the screen has some cracks (tho i've seen screens in worse condition then mine work).
And i can't use the mouse because OTG is not on, on other phones you don't need to give permission to use OTG but on mine you have to,
Click to expand...
Click to collapse
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
tnsmani said:
What about adb? That is the easiest.
I am not talking about connecting the mouse to the phone through OTG. I am talking about using the PC's mouse to manipulate the cursor to the point where you want it on your PC's screen where your mobile screen is mirrored.
Click to expand...
Click to collapse
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
manto02 said:
I think you are referring to Vysor, but i can't use it with debugg off again. Edit: I see that there are other apps like that but for most of them you have to install them on the phone, i'll search a bit more tho.
As for ADB i tried before with another phone with debug off and adb doesn't see the phone, i'll try with my broken phone but i don't think it will be different.
Click to expand...
Click to collapse
Just now, I switched off USB debugging in my OP3 and connected it to the Laptop. While the command 'adb devices' does not find the phone, as soon as it is connected, it shows up as a storage device and I can open it and copy data. I think that for this to work, you should have enabled MTP option for file transfer.
Check this on your phone.
EDIT: Check THIS as there seems to be a way though I am not sure that it works on current Android versions since the file locations may be different. Read till the end.
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
manto02 said:
My phone goes in charging mode when connected to pc, and pc doesn't see it.
Did you do that through recovery mode?
Click to expand...
Click to collapse
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
tnsmani said:
No. Tried it while booted.
Now I tried on recovery mode. Still I get it as a storage device and I can copy data.
So most probably your phone is stuck on charging and not on MTP.
Click to expand...
Click to collapse
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
manto02 said:
I believe so, every time I connected it to pc i had to switch manually from charging to recovery.
I guess my best solution is to buy a screen replacement and repair it myself
Click to expand...
Click to collapse
Have you tried fastboot flash twrp recovery and then fastboot reboot to recovery
You can try usb c to hdmi adapter , connect to a monitor or tv.
I am not sure but worth trying!!!
manto02 said:
Hi all!
I recently dropped my OP3 and now i have a black screen and touch screen doesn't work. The phone is still on and operating (i tried calling it from another phone and it works). I want to recover data but apparently i have usb debug off and i tried connecting a keyboard with an OTG but apparently i had to activate OTG from phone, otherwise it doesn't recognizes it.
Do you know any method to recover data?
My last chances are repairing the screen myself to avoid the assistence erase all the data, or transfer my motherboard to another OP3, but do you know any other method before these two above?
Thank you
Click to expand...
Click to collapse
From what i can remember, the recovery mode, accessible from the fastboot menu, has a usb access mode.
If worst comes to worst though, i personally have replaced the screen on my OP3, and its not as difficult as it seems or is made out to be. Took me max 4 hrs.
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate
chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.
Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..
After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!
Ok, my Nexus 7 2013 wifi (flo) is totally dead, almost. I thought I was smart enough to play around with the partition table with "parted" (trying to make room for gapps) ... NOT! By the time I finished messing around my tablet was totally dark. When I plug it in via USB to my PC, the PC recognizes that something just plugged in but it does not recognize the device. I can no longer use ADB FASTBOOT to do anything and of course TWRP is out of the question since I have no image on my tablet screen.
Is there anything for me to try short of buying another motherboard? Before the demise I tried sysrepart.zip, sysrepartundo.zip, Miflash, stock ROMs, kernels, etc.
I fear I have no way in since I have no display and the PC will not recognize the tablet.
UPDATE: For some unknown reason my bootloader came back, but that is all I have. The bootloader is just a display, it is useless ... it does not work.
gusw
Guswhite3 said:
...UPDATE: For some unknown reason my bootloader came back, but that is all I have. The bootloader is just a display, it is useless ... it does not work
Click to expand...
Click to collapse
So the bootloader came back, fastboot mode is displayed, but you can not use the navigation buttons and, when connected to a PC, the "fastboot devices" command is not listing your unit, right?
In this case go here to explore diagnostic and repair options.
If something else happens, either do RESTOCK or UNBRICKING.
:fingers-crossed:
k23m said:
So the bootloader came back, fastboot mode is displayed, but you can not use the navigation buttons and, when connected to a PC, the "fastboot devices" command is not listing your unit, right?
In this case go here to explore diagnostic and repair options.
If something else happens, either do RESTOCK or UNBRICKING.
:fingers-crossed:
Click to expand...
Click to collapse
Thank you. I used both UNBRICKING then RESTOCK and my tablet came back to life! Thanks again for pointing me to these two scripts.
guswhite3
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Sorry for a new thread. My device went into brick state . Cannot even use power and volume button. Followed almost majority of youtube and xda. The process of Ant flash or flash was not working older versions also. It gets stuck with authorisation as I am using EDL mode . Is there a way to skip Auth. Kindly help.
No you can't skip auth, you have to get it on your Xiaomi account which will take 30-60 days or in some cases more. Or they can just ignore/deny it.
You can use test-point method, but do it on your own risk. If you mess something in your motherboard then you can kiss your phone goodbye.
Alternatively you can just send your device to a service center and they will fix it for you.
However if your phone is detected in fastboot mode. Then you can fix it yourself.
Try downloading this driver then check if your device is detected in fastboot.
XDHx86 said:
No you can't skip auth, you have to get it on your Xiaomi account which will take 30-60 days or in some cases more. Or they can just ignore/deny it.
You can use test-point method, but do it on your own risk. If you mess something in your motherboard then you can kiss your phone goodbye.
Alternatively you can just send your device to a service center and they will fix it for you.
However if your phone is detected in fastboot mode. Then you can fix it yourself.
Try downloading this driver then check if your device is detected in fastboot.
Click to expand...
Click to collapse
Thank you . ADB ( have a warning kind of symbol) when I connect phone I get a refresh kind of stuff happening in Device manager but ADB continue to have that code (10)). How to resolve this or if this normal then I am unable to access the phone .
Secondly Test-Point Method (I am yet to get to it) is this EDL mode then I did try couple of time as there are many threads but I think everyone showed Video but continued to state no Auth is required so I tried more times now but no luck .. I will google more on Test Point method if that is different. Appreciate your answer
Who should we approach to get an Authorization (Will give a try ) as service center states mother board replacement. All threads related this were in 2018.. Just saw one thread but that was kind of not leading to closure .
Teddy126 said:
Thank you . ADB ( have a warning kind of symbol) when I connect phone I get a refresh kind of stuff happening in Device manager but ADB continue to have that code (10)). How to resolve this or if this normal then I am unable to access the phone .
Secondly Test-Point Method (I am yet to get to it) is this EDL mode then I did try couple of time as there are many threads but I think everyone showed Video but continued to state no Auth is required so I tried more times now but no luck .. I will google more on Test Point method if that is different. Appreciate your answer
Who should we approach to get an Authorization (Will give a try ) as service center states mother board replacement. All threads related this were in 2018.. Just saw one thread but that was kind of not leading to closure .
Click to expand...
Click to collapse
Your reply is all over the place, I didn't get a single thing of what you said.
Just boot your device to fastboot then type in cmd fastboot devices if you get a response with your device id then your device is detected in fastboot.
Test-point is exactly EDL mode just that you access it directly from the chipset instead of the normal way so it skips auth.
You have to connect two points in the motherboard with your usb then connect it to the PC with the correct driver (Qualcomm 9008)
If you don't know what you're doing then get it to a professional or some friend of yours, don't break it more.
XDHx86 said:
Your reply is all over the place, I didn't get a single thing of what you said.
Just boot your device to fastboot then type in cmd fastboot devices if you get a response with your device id then your device is detected in fastboot.
Test-point is exactly EDL mode just that you access it directly from the chipset instead of the normal way so it skips auth.
You have to connect two points in the motherboard with your usb then connect it to the PC with the correct driver (Qualcomm 9008)
If you don't know what you're doing then get it to a professional or some friend of yours, don't break it more.
Click to expand...
Click to collapse
Thank and sorry for the confusion.
Please note cannot get to Fastboot mode as power+Vol Down does not respond. What i tried to explain is when I installed ADB drives I get a warning symbol in device management
Tried EDL mode with tweezers by simultaneous connecting so that I try flashing. There were some video's. But I could not flash as it was asking Auth.
Teddy126 said:
Thank and sorry for the confusion.
Please note cannot get to Fastboot mode as power+Vol Down does not respond. What i tried to explain is when I installed ADB drives I get a warning symbol in device management
Tried EDL mode with tweezers by simultaneous connecting so that I try flashing. There were some video's. But I could not flash as it was asking Auth.
Click to expand...
Click to collapse
Well then you have no options but to it give to a professional since you can't do a test-point boot.
XDHx86 said:
Well then you have no options but to it give to a professional since you can't do a test-point boot.
Click to expand...
Click to collapse
Thank you will follow this advise. Just tried by seeing EDL videos which I realize is not true and everyone might have had auth code. Thank you for resp[onding