Related
Ok Guys heres what I,e got
Firmware ver 2.1-updat 1
Baseband ver 32.36.00.28U_4.06.00.02_2
Kernal ver 2.6.29-b7e82785
Build Num 1.19.707.7 CL171460 release keys
Software num 1.19.707.7
Browser ver Webkit3.1
Ok. now I,ve spent probably about 24 hours during the past three days trying to root the thing. made a gold card after about 10 attempts, have tried and tried to root the thing, have tried 3 or 4 different methods, most fail becase either I loose USB connection to the fone when navigating to Bootloader. From there on in she all over rover. Actually I,m not sure I have the right ROM to add to the fone, but I,d really like to get to the point where it asks for the rom. I,ve aged about 10 years since embarking on this venture, and still the thing is as bought. The phone isnt branded, bought it thru ebay from Hong Knog I think, has asian english which aint no fun. Have loaded Morelocal2 on but it still aint nice.
Can someone who has rooted one of these with similar ver software email me whith there secrets please before I go totally insane or really root the thing against a brick wall.
Cheers Guys.
Try the tutorial in my sig (second link). You should have no problems rooting with that.
It provides you with the required downloads for rooting. Just download and flash your ROM of choice in place if the 'rootedupdate.zip' file.
Please state any errors you recieve while attempting root.
-------------------------------------
Sent via the XDA Tapatalk App
Rooting Desire
I,ve tried your link, now my wife has been helping me, she cant get it to install either, I,ve even got to the stage of watching in Device manager what happens when it goes into Bootloader/recovery mode. the link between the HTC and the computer breaks,SOOOOOOO as I,ve stated before I have a very good understanding on HOW to root the thing, its just that for some reason I cant keep the phone connected thru the USB . I think this is the only prob I have. Something else that also happens is I get a Customer ID failed message half way thru step 1
What ever system I try to use to root this thig thats where I end up.
Wifie is going to try one more time, this time we are going to try the fone with a default startup to look at the disc not the HTC Syn.
Please keep trying to help guys
Rooting Desire
OK Heres the wifie update,
Screen says,
Pushing update file to device
error: device not found
error: device not found
Now wipe and apply rootupdate.zip from the recovery image menu.
Error: device not found
[email protected]:/mnt/cdrom/root$
So there we go guys, thats it in a nut shell
Try using the TinyCore method, I had all sorts of issues in Windows but this worked first time...see this post...
http://forum.xda-developers.com/showpost.php?p=6710081&postcount=2
obviously download the right Live CD for your bootloader
Also if you are trying to root in windows, make sure you have HTC Sync installed.
Desire root
Yep, I,m using the tiny core app followed the instructions in the link as advised. Still loses connection at bootlader/recovery
When you get back to Bootloader, how long do you wait before trying to run? As I normally leave it 5 or so seconds and then it's fine...if you do it too quick it'll say no device found
Which TinyCore CD did you download? I'm assuming you have HBOOT 0.80 on your device before you started?
Rooting a desire
An answer to your question, I,m using the tcl_r4_desire_hb80 file. when you ask how long are you waiting , I reckon it taks me more than 5 seconds to type in sudo ./step2.sh
I could try it again and wait longer.
Desire a rooted phone
Nope sorry guys, I,ve tried god dam everything, still wont connect afetr step 1 with tcl_r4_desire_hb80.
Somehow I need to be able to force a usb connection.
hey I tried this on Vista and XP, thought XP might be better. is there a stand alone app to force USB drivers when tcl_r4_desire_hb80 boots into termial screen
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
socktug said:
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
Click to expand...
Click to collapse
I too was thinking that there is a possibility of his device being bricked, especially when receiving errors indicating that the device cannot be found in recovery.
Rooting desire
OK, wondered that myself,
connected phone to PC, sync straight away with fone
reconnected it to pc in disk drive mode and connected, checked in My Computer and the disc drive was there with all my files.
Suppose that means everything there is ok to
OK if it isn't usb bricked then it's got to be a driver issue. My suggestion would be to follow the tutorial in the dev section and use tiny core linux.
Rooting desire
OK guys,,, so heres where I,m at, so far all info gained from you lovely people has been to no avail.
What I,m getting is this
In device manager I am watching what happens when the Desire goes from fastboot to bootloader. In bootloader I get "Android 1.0 with the yellow tiangle indicating it aint set up with drivers. In fastboot I get "My HTC" under Android USB Devices. now in either Bootloader or fastboot I,m only getting one or the other, and as I said, the triangle under "Android 1.0"
Now Ive gone to Android 1.0 and tried to add a driver, seemingly thers not a driver in the world that will work with Android 1.0. All driver in my Sdk dont work. The driver installer asks for a driver but wont except anything trown at it.
First, via your phone, go to Menu > Settings > Applications > Development and ensure the USB Debugging option is selected.
Try a different USB port.
I actually think you need to create a Gold Card even though you have stock rom 1.19.707.7
Try the Gold Card.
-------------------------------------
Sent via the XDA Tapatalk App
I have the exact same issue on win.7 64bit.
Try ignoring the no android 1.0 issue, continue to put your phone into recovery with the volume down and power buttons. Wait about 10 seconds after you see the black screen with red triangle, and then click on recovery windows.bat. Works for me everytime.
Windows takes it's time to see and install devices so it may be that you are trying things too quickly after connecting the usb lead.
Whilst reflashing my diamond touch with a new rom at the stage where you disconnect and hold vol down and back button to start the rom off I had the back off and the battery fell out. Now if I do the above it comes up saying no image found then says trigger usb host and red flash saying usb retry enter usb. Have I meesed my phone up or is there a way to get the image back any help will be welcomed. I can still connect via mtty but the device doesn't come up in my computer anymore or wont connect via active sync.
tonictone said:
Whilst reflashing my diamond touch with a new rom at the stage where you disconnect and hold vol down and back button to start the rom off I had the back off and the battery fell out. Now if I do the above it comes up saying no image found then says trigger usb host and red flash saying usb retry enter usb. Have I meesed my phone up or is there a way to get the image back any help will be welcomed. I can still connect via mtty but the device doesn't come up in my computer anymore or wont connect via active sync.
Click to expand...
Click to collapse
dont worry .. nothing is lost
bring up the phone in bootloader .. vol down reset
connect the usb cable, on screen should write USB (instead of serial)
and now just run the customRUU.exe file that is usualy in archive you downloaded the rom, and just follow the instruciotions.
(like you are flashing without mtty! from computer)
hi man, have you tryed to reinstall drivers ? i don't know what happends to your phone but i'm really sad for you hope it's nothing That can seriously damage it so if i was you, i'll try to reinstall all drivers and use mtty from the 1st step, may be it will work. feed beck plz
R.seed said:
hi man, have you tryed to reinstall drivers ? i don't know what happends to your phone but i'm really sad for you hope it's nothing That can seriously damage it so if i was you, i'll try to reinstall all drivers and use mtty from the 1st step, may be it will work. feed beck plz
Click to expand...
Click to collapse
Now if I do the above it comes up saying no image found then says trigger usb host
Click to expand...
Click to collapse
he forgot to put image on the phone, or to rename it diamimg.nbh ...
reinstall DRIVERS !?
vicai said:
he forgot to put image on the phone, or to rename it diamimg.nbh ...
reinstall DRIVERS !?
Click to expand...
Click to collapse
yes..youre right..i did the same thing, after i've mtty (after type task 8), i forgot to initiate ROM flash and did hard reset+clear memory, so the image (diamimg.nbh) in movinand memory is erased.
So, we still can flash with custom RUU. bring your device in bootloader, you will see serial mode change into usb, then execute custom RUU.exe. follow the instruction.. but make sure your battery is enough..
Hope it help you..
Thanxs Vicai, did as your post recommended and working fine now, thanxs for the quick response
tonictone said:
Thanxs Vicai, did as your post recommended and working fine now, thanxs for the quick response
Click to expand...
Click to collapse
welcome
glad to help
hi every body
yesterday i was checking out program ROM MANAGER and i found option install rom . so i did it but after phone restarting . at it stucked at frist black screen and there is no any response or move ... then i entered into AMOR_na recovery to reinstall another rom ... i surrprise that i cann't mount SD card ... and now i can't plug my desire to pc to install anoher rom and and my cell phone cann't see my memory card ... please help what can i do ... urgent
thanks for all
odda said:
hi every body
yesterday i was checking out program ROM MANAGER and i found option install rom . so i did it but after phone restarting . at it stucked at frist black screen and there is no any response or move ... then i entered into AMOR_na recovery to reinstall another rom ... i surrprise that i cann't mount SD card ... and now i can't plug my desire to pc to install anoher rom and and my cell phone cann't see my memory card ... please help what can i do ... urgent
thanks for all
Click to expand...
Click to collapse
Enable the SD Card functionality: Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
thank you for reply
but sory for asking how to enter this command from phone or form pc ... and which tool to do that from pc .... i am just beginner
thank you once again
thank you so much ... it is done and solved ..... mant thanks
Please how did you do that? I have the same problem.thanks
You must've Android sdk installed. In and from the tools folder of your sdk open cmd prompt and enter the command as long as you have booted your phone in fastboot by shutting it down and the turn it on by pressing back button + power on
Sent from my Desire HD using XDA App
thank you for helping us
but i have another problem in my HTC desire
i found after installation rom that the (bluetooth )not workig and (usb debubbing ) not working too ( just for charge only no more action )
now my moblie all thing working normaly and i have root ( AMON_RA ) and working too and i can see my memory card but NO BLUETOOTH NO USB
i try to change radio but it is not working and i tried to change rom but it is not working too ... kinldy do u have any soulution .....
thank you so much in advance
does it take long for the charge to start? usb mass storage doesn't work? i think you have usb brick. have a look here. read http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
thank you i will feed you back soon
and please what about Bluetooth
after you try it, let me know. about flashing a radio!? are you s-off. i need to know about rom and radio you have flashed recently.
odda said:
thank you i will feed you back soon
and please what about Bluetooth
Click to expand...
Click to collapse
find my moblie infomation
bravo pvt3 ship s-on
hboot -0.93.0001
microp-051d
touch panel-synt0101
radio-5.11.05.14
my radio 32.49.00.32u_5.11.05.27
kernel 2.6.32.15-gd96f2c0 [email protected]#1
software number w1002 2.2 arabic
this rom installed from ce4arab.com
thank you once again in advance
You should try downgrading to a different radio version first and if the issue still persists, then try flashing a different ROM as your current ROM may have an issue with Bluetooth, which could also explain why it is not functioning for you.
i am downgrading my radio to 32.46.00.32U_5.10.05.17_2 and as the same bluetooth not working and i USB debugging not working too .... and i notice that USB tethering i can't check the box ....
you have to know something i was sufring from could't see my memory card . and i solve it by installing ABD KIt ...
and i notice too it s take long time to start charge ... and if i plug my phone to PC it always searching for Qualcomm CDMA Technologies MSM ?
any advice ?
thank you for support me
odda said:
i am downgrading my radio to 32.46.00.32U_5.10.05.17_2 and as the same bluetooth not working and i USB debugging not working too .... and i notice that USB tethering i can't check the box ....
you have to know something i was sufring from could't see my memory card . and i solve it by installing ABD KIt ...
and i notice too it s take long time to start charge ... and if i plug my phone to PC it always searching for Qualcomm CDMA Technologies MSM ?
any advice ?
thank you for support me
Click to expand...
Click to collapse
I think you may have a driver issue. Disconnect your phone, completely un-install HTC Sync and its associated drivers, restart your PC, re-install HTC Sync, reboot your phone, ensure the 'USB Debugging' option is selected via the phone, and then connect it to your PC after it restarts.
If you have the same bluetooth error, even after changing radio versions, then I would advise you to try either a different working custom ROM that is stable, or even revert back to stock ROM by running your original RUU (use a Gold Card also if necessary), and then check if your Bluetooth is functional. If it is, re-root and install the working custom ROM of your choice.
You have Ian brick. Follow the link I gave you a few posts ago.
Sent from my Desire HD using XDA App
i have one ques.
if i have backuped my last normal rom i was have by rom manager ... and i have it
can i restore it by rom manager and fix all error i have ... ?
i am using AMON_RA recovery
because i am afraid from loseing my cell phone
odda said:
i have one ques.
if i have backuped my last normal rom i was have by rom manager ... and i have it
can i restore it by rom manager and fix all error i have ... ?
i am using AMON_RA recovery
because i am afraid from loseing my cell phone
Click to expand...
Click to collapse
Restoring a Nand will not work. There are different drivers on the PC host, and different firmware controlling USB on the phone. Try the unbricking guide in post#8 and also try what I suggested above.
Let us know how you get on.
thanks for every one helpme in this issue
but i would like to tell you all problems solved by USB-Brick soulution
as you told me before ... i create image from ( r3-tinycore_2.10-desireroot ) on CD and boot my lap from CDrom .. and then do some steps to git CID ... and then i modefied img files and restore ot to my phone and restart and all thing go's well ...
for more details about that i am ready ...
thank you once again
odda said:
thanks for every one helpme in this issue
but i would like to tell you all problems solved by USB-Brick soulution
as you told me before ... i create image from ( r3-tinycore_2.10-desireroot ) on CD and boot my lap from CDrom .. and then do some steps to git CID ... and then i modefied img files and restore ot to my phone and restart and all thing go's well ...
for more details about that i am ready ...
thank you once again
Click to expand...
Click to collapse
Great news, glad you have a properly functional device now
How you did it
odda said:
thanks for every one helpme in this issue
but i would like to tell you all problems solved by USB-Brick soulution
as you told me before ... i create image from ( r3-tinycore_2.10-desireroot ) on CD and boot my lap from CDrom .. and then do some steps to git CID ... and then i modefied img files and restore ot to my phone and restart and all thing go's well ...
for more details about that i am ready ...
thank you once again
Click to expand...
Click to collapse
Please see my problem here:-
http://forum.xda-developers.com/showthread.php?t=923282
It's similar to you. Please guide me to resolve.
Thanks.
Evening everyone
Got a BIG problem with my phone today and having searched and read i still cant fix it
Ok a little about my phone: Rooted with amon recovery, recently s/off, CyanogenMod 7 rom and kernel, -32 radio..
Right here is the problem...
Did a nandroid backup in recovery of the rom i was using ^^ and all seemed fine, i then rebooted my phone,, booted up, waited for everything to work and then i noticed my apps weren't there?
Went into storage and it showed no memory card,, so i rebooted phone hoping this might fix but it didn't.
Plugged my phone into laptop and a message flashed up "usb device not recongnised" i though Sh!t whats happened ?
So i booted my phone into recovery to mount the sd and a message again "error cant mount sd"
Clicked reboot phone and now its stuck on the "why so serious" screen ???????
Ive dloaded the sdk tool but really not sure what i should be typing in there ??
Anyone with a little time care to help me out please lol ???
Cheers
EDIT: I have flashed nearly every rom on xda since i rooted about 4 months ago without any problems, always did the wipes in recovery before flashing so really dont know what has happened here ?
Try formatting SD card, if that doesn't work, reflash recovery
Sent from my Vanilla Tazz using XDA App
Hi mate.
Forgot to mention i did format sd card on pc "fat32" using a sd card reader but that aint solved it
Not re flashed recovery though....
Edit: how can i re flash recovery if my lappy wont recongnise phone
knipp21 said:
Try formatting SD card, if that doesn't work, reflash recovery
Sent from my Vanilla Tazz using XDA App
Click to expand...
Click to collapse
chrisvr4 said:
Hi mate.
Forgot to mention i did format sd card on pc "fat32" using a sd card reader but that aint solved it
Not re flashed recovery though....
Edit: how can i re flash recovery if my lappy wont recongnise phone
Click to expand...
Click to collapse
Looks like you have been usb bricked, look this forum for usb brick fix, its not the fault of the rom, it just sometimes happens. Got it once too, easely to fix.
Sent from my HTC Desire
Im not blaming the rom not one bit as its been running fine this morning up untill i did the backup.
I have read and read that much my heads spinning %-( there's hek of a lot to take in and being a rather noooooob im lost as to what i should do
Worstenbrood is right, that's.just a USB brick, don't worry, it's an easy fix. Search Modaco for USB rickrolled.
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
You can skip step one.
Not to worry ? im bricking it lmao
I really aint got a clue about the fastboot thingy if you have a little time could you give me a step by step of how its done
cheers
Download the SDK and then use the command prompt to run the fastboot command from the Modaco tutorial.
There are quite a few guides for fastboot, just Google it
Hi
I just ran the command and when entered it said fastboot not found?
You need to run it from the directory containing fastboot.executive (in the SDK).
thanks for the replies
i have tried that but im getting 'adbwinapi.dll is missing from your computer'
i have re-installed sdk and still wont work?
Did you do this
Windows XP / Vista
Right click on the My Computer icon and select the properties tab.
Select the Advanced tab and click the Environment Variables button.
In the new dialog box dowble-click on Path (located under System Variables) and type in the full path location to the tools directory.
Has to be done for it to work
If you have never used sdk before Google for a good install & how to use guide
whooohoooo right solved the sd problem, new rom flashed and powered up Many Thanks guys "but" i still cant use the usb on laptop ?
When i plug usb in it the phone only charges ? and an usb not recognised message ?
did u install the htc drivers from the htc website? i was having problems with connecting my phone dowloaded those and un-installed sync and all was fixed!
i get 'usb not recognised message' every now and then on my home pc and the works pc both running Windows 7 64bit.
I found that usually when it pops up about
'usb not recognised message'
i just unplug the cable then back in a few seconds after the message then it usually connects ok. sometimes it takes a few attempts.
thats with 'HTC Wildfire_setup_3.0.5481' installed for the 64bit drivers.
Thanks very much guys for all your help managed to get the usb fixed by installing htc sync
But now i have another problem i noticed today is Bluetooth wont turn on ? is there a fix out there for this ?
cheers
Im experiencing strange reboots now with phone plugged into laptop via usb, and on the status bar on phone it show usb debugging and then dissapears and comes back and when i unplug usb the phone reboots?
I wiped the laptop yesterday and phone seemed fine and now the troubles have come back
In logcat error im also getting this message when i enable bluetooth
attempting to remove unknown iface (usb0), ignoring
bt_enable: Timeout waiting for HCI device to come up
Seems as if the brick has actually fooked my phone up good and proper !
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?