Hey!
I wanted to flash a custom rom because my stock rom was very very slow (after 3 years of permanent usage). I installed TWRP and wipe the phone. Then I wanted to use adb to push the desired rom to my Gnex. But my Gnex is not recognized by the computer. So there is no adb possible. Am I lost? Do I need to recycle my Gnex or is there any change to bring a rom onto the phone? TWRP is working but without usb connection it is worthless, is it?
I fear that the usb port of my Gnex is not working properly (maybe broken). It's charging but no computer recognize it (I tried 2 Windows machines and two Mac Books).
I'm happy for every tip or hint. Maybe you could help me find a way to get my Gnex working again. I'm not very optimistic but the android community amazed me before and so I hope you guys do again
Bye
Tschoartschi
Odin Mode??
is ur phone totally bricked?? can't u go to the odin mode ( by pressing power button and volume down button) ????
drivers?
Are the drivers installed so the phone and cpu can communicate?
Is the device recognized by the windows device manager when its plugged in? If not you could try to copy the rom zip on a usb flash drive and then connect it over usb otg (to see if it's mountable in the twrp mount section).
Phone works normally except it's undetected by pc. It boots itself, boots to twpr (3.0.2.-3) or fastboot. I flashed various roms, after some time detected that couldn't access storage, but didn't actually care - thought it's something with those beta stage roms.
Decided to flash original rom, but neither adb or fastbot are working. Actually, windows even won't detect device. At all. No signal that i connected cable. The phone meanwhile keeps charging. Tried to connect at manjaro linux with same luck - adb devices or fastboot devices won't detect anything.
Formated data in TWRP (thought, that it was encryption i used fault), but no luck. Now i could load to TWRP, bootloader. Is there any possible ways to get phone back to reality before me trying LGUP scary thing?
updated. could that be somehow damaged cable fault?? i checked with my wife's phone (same model) and it's not detected either. it's a nilkin cable, worked perfectly before. could that be possible somehow to damage a cable that it would only charge phone? or i bricked both nexuses?
updated 2. oh my, LGUP also detects nothing. this seems like a bricked phone.
updated. faulty cable.
I am flashing wrong ROM on my redmi 1s .my phone was not able to switch on ,not charging, no bootloader,no fastboot mode totally crashed. I pressed volup+power,voldown+power not going to any mode.When I connected to PC,it recognized Qualcomm qdloader driver. I am flash to ROM with mi flash tool it recognised COM10 PORT When I flash official stock ROM I got error not flashing.is there any way to flash ROM on my device.I am searched on google I found Qualcomm flash tool,how to flash ROM with Qualcomm flash tool pls help me
naveen3186 said:
I am flashing wrong ROM on my redmi 1s .my phone was not able to switch on ,not charging, no bootloader,no fastboot mode totally crashed. I pressed volup+power,voldown+power not going to any mode.When I connected to PC,it recognized Qualcomm qdloader driver. I am flash to ROM with mi flash tool it recognised COM10 PORT When I flash official stock ROM I got error not flashing.is there any way to flash ROM on my device.I am searched on google I found Qualcomm flash tool,how to flash ROM with Qualcomm flash tool pls help me
Click to expand...
Click to collapse
Man, you are not the only one in this situation, I accidentally erased the f*cking 'tz' partition. If you are on linux, connect the phone to USB, the preloader will find that the whole of the data is messed up and put the phone into bulk mode. In bulk mode, the partitions of the phone is exposed as such so you can copy files into it. DONT DO IT WITHOUT RESEARCH. BUT I AM NOT SURE HOW TO RESTORE IT. If I get tz.img instead of tz.mbn, I will be able to 'dd' it. I dont think I can 'dd' a mbn file.
..
generex144 said:
Man, you are not the only one in this situation, I accidentally erased the f*cking 'tz' partition. If you are on linux, connect the phone to USB, the preloader will find that the whole of the data is messed up and put the phone into bulk mode. In bulk mode, the partitions of the phone is exposed as such so you can copy files into it. DONT DO IT WITHOUT RESEARCH. BUT I AM NOT SURE HOW TO RESTORE IT. If I get tz.img instead of tz.mbn, I will be able to 'dd' it. I dont think I can 'dd' a mbn file.
Click to expand...
Click to collapse
MIflash actually works , just b on new miflash version(which capable of switch 9008-9006 mode)...
it may gives errors many times...
tips to b successfull flash..
1. charge battery with external charger (most imp. )
2.if ur using pc, connect usb to motherboard usb port.( backside ports of cabinet)
3.try changing usb cables (sounds stupid but actually worked for me, as phone wont stay in 9006/9008 mode if usb signal drop)
dd wont work until u have access to fastboot/adb..
another way is make deep flash cable..
dnt wrry its very easy
Hey gals and guys,
my girlfriend dropped her Xiaomi A2 lite and no the touchscreen doesn't respond. The phone has the stock Android One and I can only access fastboot.
Code:
fastboot devices
recognizes the phone.
The recovery is the stock recovery.
Code:
adb devices
won't recognize the phone and gives me an empty line as output
I also can't access the phone via usb with my filebrowser. If I try, the phone makes a "bing"-sound and the filebrowser gives me:
Code:
unable to open MTP device
I am using archlinux and I also have a windows device available.
Is there any chance on getting pictures etc from the phone?
Any suggestions besides getting a replacement for the touchscreen?
Thank you so much.
Connecting via USB probably needs you to click something.
I'm guessing developer mode is not enabled...
If you've got a micro USB OTG cable, you could plug a mouse in.
If you boot TWRP (fastboot boot twrp-3.3.1-dees-troy.img) you should be able to get adb and usb transfers working. Don't need to install it, just boot it. Not sure if that works without unlocked bootloader.
If you've got a micro USB OTG cable, you could plug a mouse in.
Click to expand...
Click to collapse
This did the trick.
Thank you
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!!!