Database Users

HTC wildfire 2.2.1 rooted with sucess

Since January i been waiting to root my phone. Htc wildfire 2.2.1
I already tried with unrevoked, and a lots of other ways and never with sucess annd today i have been sucess
I root my wildfire with alpharev to put S-Off and then with SuperOneClickv1.9.5.
Restart and voila.....
Go to hxxp://alpharev.nl/x/beta/ & download the windows version
2. When it asks you for the serial, enter your phone's serial number. Go to Settings > About phone & enter your serial. Copy the code given into notepad
3. Make sure you turn on USB debugging in Settings > Application > Development
4. Install the HTC Driver. Mine is in the memory card that came with the phone
5. Extract & run alpharevx.exe. Use the code given earlier. Then connect your phone. It should detect & your phone should display USB debugging mode
6. Wait for it to complete. Once it is completed, you can remove your phone.
7. To check turn off your phone. Then press volume down & power. On top it should display alpharevx & s-off
Clockwork recovery
1. This is to enable you to install a custom rom, and also for backup
2. Get the fastboot tool for windows
3. Copy the fastboot file you downloaded to the alpharevx folder. Copy the folder to drive C so it is easier to run command prompt. Rename the folder to wildfire
4. Download the recovery for Wildfire. Extract & rename it to wildfire.img
5. Open command prompt. Type cd c:/wildfire & fastboot flash recovery wildfire.img
6. Download & install HBOOT driver from unrevoked. Go into bootloader (volume down & power), select fastboot. Connect your phone & it will display fasboot usb cable
(take this part from web - Author: Joel512)
Next step just need to download and run SuperOneClickv1.9.5 and restart
I don`t known if you people already know. If so I apologize
Sorry for my Inglish

It would be more useful if u can share the video 'how-to' in YouTube I'm yet trying dis coz on Mac rite now.

Damag3 said:
Since January i been waiting to root my phone. Htc wildfire 2.2.1
I already tried with unrevoked, and a lots of other ways and never with sucess annd today i have been sucess
I root my wildfire with alpharev to put S-Off and then with SuperOneClickv1.9.5.
Restart and voila.....
Go to hxxp://alpharev.nl/x/beta/ & download the windows version
2. When it asks you for the serial, enter your phone's serial number. Go to Settings > About phone & enter your serial. Copy the code given into notepad
3. Make sure you turn on USB debugging in Settings > Application > Development
4. Install the HTC Driver. Mine is in the memory card that came with the phone
5. Extract & run alpharevx.exe. Use the code given earlier. Then connect your phone. It should detect & your phone should display USB debugging mode
6. Wait for it to complete. Once it is completed, you can remove your phone.
7. To check turn off your phone. Then press volume down & power. On top it should display alpharevx & s-off
Clockwork recovery
1. This is to enable you to install a custom rom, and also for backup
2. Get the fastboot tool for windows
3. Copy the fastboot file you downloaded to the alpharevx folder. Copy the folder to drive C so it is easier to run command prompt. Rename the folder to wildfire
4. Download the recovery for Wildfire. Extract & rename it to wildfire.img
5. Open command prompt. Type cd c:/wildfire & fastboot flash recovery wildfire.img
6. Download & install HBOOT driver from unrevoked. Go into bootloader (volume down & power), select fastboot. Connect your phone & it will display fasboot usb cable
(take this part from web - Author: Joel512)
Next step just need to download and run SuperOneClickv1.9.5 and restart
I don`t known if you people already know. If so I apologize
Sorry for my Inglish
Click to expand...
Click to collapse
Hey thanks for the SuperOneClickv1.9.5 info!!! I was searching for a one click rooting alternative!!!

imkr said:
It would be more useful if u can share the video 'how-to' in YouTube I'm yet trying dis coz on Mac rite now.
Click to expand...
Click to collapse
What are you trying on Mac.
AlpharevX will not support Mac platform right. Only windows and Linux supported. Easiest is Linux. Live CD is perfect.
Sent from my HTC Wildfire using XDA App

bharatgaddameedi said:
What are you trying on Mac.
AlpharevX will not support Mac platform right. Only windows and Linux supported. Easiest is Linux.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Yes! it doesn't working on Mac

HEy I have successfully turned S-OFF. When I try doing the Clockwork recovery thing it gets struck at waiting for device!! Any advice??

ameya88 said:
HEy I have successfully turned S-OFF. When I try doing the Clockwork recovery thing it gets struck at waiting for device!! Any advice??
Click to expand...
Click to collapse
uninstall htc sync if you have it installed.

Its uninstalled, thats the first thing I did to avoid any complications!!

Now what do I do???? I waited for around 20 mins but its not going ahead!!

try this way http://forum.xda-developers.com/showthread.php?t=1130044

The guide referenced in the link above sure worked for me
Just a word of advice, the linux version of alpharevX gets stuck on 'waiting for device' on my ubuntu 11.04 so don't use it... if you are gonna be using alpharevX to root your phone do not do it on a virtual machine (wouldn't work on my winxp in VMware Player, the phone would just reboot and get stuck), do it on a proper win machine.

ameya88 said:
HEy I have successfully turned S-OFF. When I try doing the Clockwork recovery thing it gets struck at waiting for device!! Any advice??
Click to expand...
Click to collapse
After s-off, waiting for device should be in the fast boot flashing recovery process. If it is so, the device is to be connected in fastboot mode and then the command "fastboot flash recovery recovery.img" is to be entered from command prompt (command prompt cd into fastboot folder, and recovery.img is also to be kept in this folder). The waiting for device warning around 1min is normal but shouldn't take more.
Ignore if going with other process.
Sent from my HTC Wildfire using XDA App

bharatgaddameedi said:
After s-off, waiting for device should be in the fast boot flashing recovery process. If it is so, the device is to be connected in fastboot mode and then the command "fastboot flash recovery recovery.img" is to be entered from command prompt (command prompt cd into fastboot folder, and recovery.img is also to be kept in this folder). The waiting for device warning around 1min is normal but shouldn't take more.
Ignore if going with other process.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Tried it but device still gets stuck at <waiting for device> mode after I type fastboot flash recovery wildfire.img

ameya88 said:
Tried it but device still gets stuck at <waiting for device> mode after I type fastboot flash recovery wildfire.img
Click to expand...
Click to collapse
Make sure your Wildfire is in Fastboot Mode. Power Down your phone, Start with Vol Down + Power Key. This will open Bootloader Mode. Then connect to your PC with the USB Cable, Select "Fastboot' mode (By using Volume keys), and Press Power button on it.

gogusteliade said:
try this way http://forum.xda-developers.com/showthread.php?t=1130044
Click to expand...
Click to collapse
Hey thanks for the Link. I am now trying to follow the method posted in the link. Do I need to do the Hboot driver download and install thing after that or do i directly root??? Thanks by the way

3xeno said:
Make sure your Wildfire is in Fastboot Mode. Power Down your phone, Start with Vol Down + Power Key. This will open Bootloader Mode. Then connect to your PC with the USB Cable, Select "Fastboot' mode (By using Volume keys), and Press Power button on it.
Click to expand...
Click to collapse
No wonder!!! I was doing it wrong. Thanks will give it a try!!

3xeno said:
Make sure your Wildfire is in Fastboot Mode. Power Down your phone, Start with Vol Down + Power Key. This will open Bootloader Mode. Then connect to your PC with the USB Cable, Select "Fastboot' mode (By using Volume keys), and Press Power button on it.
Click to expand...
Click to collapse
I did as you said, Once I connected the phone to the PC while it was in boot loader I got a msg on the pc saying "driver not correctly installed" but I continued anyway and chose fast boot by pressing the power button. Now its giving me 4 options -> Bootloader, Reboot, Reboot Bootloader and Power down with the Title Fastboot USbB at the Top. Which do i choose??/

Are you shore u have all the files in the same folder and you need to have USB Debugger ON to.
The Alpharev take to long to finish. It`s happening the same with me.....
and you must put the code given by Alpharev website.

ameya88 said:
Now its giving me 4 options -> Bootloader, Reboot, Reboot Bootloader and Power down with the Title Fastboot USbB at the Top. Which do i choose??/
Click to expand...
Click to collapse
Don't choose anything.
This is the fastboot mode what everyone is talking about
Sent from my HTC Wildfire using XDA App

Damag3 said:
Are you shore u have all the files in the same folder and you need to have USB Debugger ON to.
The Alpharev take to long to finish. It`s happening the same with me.....
and you must put the code given by Alpharev website.
Click to expand...
Click to collapse
Yeah USB debugger is ON and all the files are in the same folder. I am just having a prob with the clockwork recovery thing. I successfully turn S-OFF

Strange Bootloop problems!!!

Ok, i have a mytouch 4g that has never been rooted. The problem with the phone is that all of the sudden when i try to turn it on it wont get pass the splash screen. It will just turn off and reboot to the splash screen over and over. Thing is that i can get into Hboot quite easily. I tried to reflash the stock IMAGE file and it does it well without problems. But once its done and i hit power to reboot, the phone just starts to bootloop again doing the exact same thing. I know its kinda odd but i read somewhere that if i can get into Hboot the eMMc is not fried. But then what should be the problem?

enelyam said:
Ok, i have a mytouch 4g that has never been rooted. The problem with the phone is that all of the sudden when i try to turn it on it wont get pass the splash screen. It will just turn off and reboot to the splash screen over and over. Thing is that i can get into Hboot quite easily. I tried to reflash the stock IMAGE file and it does it well without problems. But once its done and i hit power to reboot, the phone just starts to bootloop again doing the exact same thing. I know its kinda odd but i read somewhere that if i can get into Hboot the eMMc is not fried. But then what should be the problem?
Click to expand...
Click to collapse
Sounds like hardware problem = warranty replacment
RcMix 3D Darkside Glacier HD
Tdj's Demonspeed v7 Kernel
Virtuous OC Damean
ClockWorkMod Recovery 5.0.2.0

Thanks, thats what i thought. Just wanted to ask so if someone have seen this before maybe there was a solution for that. But yeah, something is not right and i also think its a hardware issue.

Same prob here...anything like odin for htc? Engineering mode? I used two diff zip files tha were supposed to be the same recovery/ stock image/zip... think it i15img.zip or something... one does not do anything cept try and parse and restart other goes thru ok ok ok ok ok ok then skips the tp tp writes and says deferred or something but looks to get the job done but nah... what are the tp writes I skips...think they are right before the radio write...arg too tired
Sent from my SPH-D700 using XDA App

vizionforever said:
Same prob here...anything like odin for htc? Engineering mode? I used two diff zip files tha were supposed to be the same recovery/ stock image/zip... think it i15img.zip or something... one does not do anything cept try and parse and restart other goes thru ok ok ok ok ok ok then skips the tp tp writes and says deferred or something but looks to get the job done but nah... what are the tp writes I skips...think they are right before the radio write...arg too tired
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
HTC's too pro to have odin
the stock image file is named "PD15IMG.zip" and should be flashed in the bootloader.

Same here, this one skip the tp tp saying Bypassed on the second tp but everything seems to run ok. Only thing is that when i hit power after the update it will just start with the bootloop again. Since this is a friend, I dont really know what version it was running. But i do know its never been rooted or anything like that. Its on .86.000 and S-on and everything. Im going to try the gingerbread just for fun and see what happens.

thinking tese are Gingerbread update fails?
Let us know how the gingerbread turns out...Someone must have a recovery zip? Its obvious the two files I am trying to flash named the same thing are not the same thing or one is corrupted....211mb takes an hour on my connection now ANYONE HAVE A RECOVERY ZIP? Is there a program like odin(OK NOW I KNOW TO USE CMD AND ADB) Now I need a mytouch button press sequence to get to ENGINEERING MODE? to write to the frickin thing...I thought HTC was gonna be better than Samsung in this respect...I have one good mytouch4g that I can get the serial using the command 'adb devices' that is once mytouch is booted up...so question is how do i get to engineering mode in my bad my touch(which wont boot) so I can PUSH the file in command line interface.

vizionforever said:
Let us know how the gingerbread turns out...Someone must have a recovery zip? Its obvious the two files I am trying to flash named the same thing are not the same thing or one is corrupted....211mb takes an hour on my connection now ANYONE HAVE A RECOVERY ZIP? Is there a program like odin(OK NOW I KNOW TO USE CMD AND ADB) Now I need a mytouch button press sequence to get to ENGINEERING MODE? to write to the frickin thing...I thought HTC was gonna be better than Samsung in this respect...I have one good mytouch4g that I can get the serial using the command 'adb devices' that is once mytouch is booted up...so question is how do i get to engineering mode in my bad my touch(which wont boot) so I can PUSH the file in command line interface.
Click to expand...
Click to collapse
Turn the phone completely off, and turn it on again using volume down+power buttons. This enters hboot, or bootloader, where you flash the stock PD15IMG.zip file.
Sent from my HTC Glacier Sense 3.5 using xda premium

Unstick my heart
I should be able to communicate with device using adb push in command line interface hboot then? I dont see any device serial with adb devices
...Was hoping there was an engineering mode like samsung has...Well some different output here getting me excited...Img zip (211mb) that used to just stall with the other stock image zip I used (that does not parse) has at least allowed the img crc to work... below are my output pictures
http://www.flickr.com/photos/[email protected]/6447958131/
and this is the .zip (output picture of it anyway) (312mb)that I first used, seemed to work better than the one I had to rename in a recent post in Q&A forum, that said the zip that seems not to work unstuck img crc so now it reads hmmm....any ideas?
http://www.flickr.com/photos/[email protected]/6447957849/

vizionforever said:
I should be able to communicate with device using adb push in command line interface hboot then? I dont see any device serial with adb devices
...Was hoping there was an engineering mode like samsung has...Well some different output here getting me excited...Img zip (211mb) that used to just stall with the other stock image zip I used (that does not parse) has at least allowed the img crc to work... below are my output pictures
http://www.flickr.com/photos/[email protected]/6447958131/
and this is the .zip (output picture of it anyway) (312mb)that I first used, seemed to work better than the one I had to rename in a recent post in Q&A forum, that said the zip that seems not to work unstuck img crc so now it reads hmmm....any ideas?
http://www.flickr.com/photos/[email protected]/6447957849/
Click to expand...
Click to collapse
Once the phone is in bootloader, connect it to the computer, and you should see "fastboot USB" on the phone. Then open up adb, and type
Code:
fastboot devices
Sent from my HTC Glacier Sense 3.5 using xda premium
EDIT: here, download THIS FILE, rename it to PD15IMG.
then place it in the ROOT of your SDcard (not in any folders)
turn off and reboot the device into bootloader
bootloader should find the file and ask if you want to update
not sure if this is the method you used... tell us how it goes

Hmm Command did not say i had any devices (blank line) but my command line interface is in fastboot / adb(whats the differnce?) seems like it sees it? tell me if Im wrong... The command 'Fastboot devices' brought up long dir of commands, then I tried the following commands faastboot push and update PD15IMG (See pic below) Thanks for your help! I will try your zip! (but I would like to push from command line fastboot)
http://www.flickr.com/photos/[email protected]/6448265267/
Currently downloading ur zip thx...23 mins left :\
THANKS!

vizionforever said:
Hmm Command did not say i had any devices (blank line) but my command line interface is in fastboot / adb(whats the differnce?) seems like it sees it? tell me if Im wrong... Fastboot devices brought up long dir of commands for adb? then I tried following commands (See pic below) Thanks for your help! I will try your zip! (but I would like to push from command line fastboot)
http://www.flickr.com/photos/[email protected]/6448265267/
Click to expand...
Click to collapse
does your device say that it's "fastboot USB" somewhere on it? if it says "HBOOT USB", manually scroll to fastboot and select it.

no it does not seem to see it is connected
http://www.flickr.com/photos/[email protected]/6448372103/
I know USB works because it attempts to orange led flashes/charges before it turns on but it does not say usb after fastboot
still waiting for download...29 mins remaining at 72kb per sec groan

vizionforever said:
no it does not seem to see it is connected
http://www.flickr.com/photos/[email protected]/6448372103/
Click to expand...
Click to collapse
hmm.. might be because you don't have the engineering bootloader.
my mom's is S-on as well, and computer can't see it through fastboot.
anyway, just use the method i told you, move it onto the SDcard manually

Computer cant see it, but can it write to it?(i want to try) What is proper command to push pd15IMG in adb/fastboot? should I do it in adb or fastboot on computer? and what mode on phone: hboot or fastboot? thx G

vizionforever said:
Computer cant see it, but can it write to it?(i want to try) What is proper command to push pd15IMG in adb/fastboot? should I do it in adb or fastboot on computer? and what mode on phone: hboot or fastboot? thx G
Click to expand...
Click to collapse
i meant taking out the SDcard and connecting the SDcard to the computer, and transfer files that way.

Understood what u meant, just wanted to try usb push ind adb while file is downloading...

vizionforever said:
Understood what u meant, just wanted to try usb push ind adb while file is downloading...
Click to expand...
Click to collapse
don't think that's gonna work :/
sorry

ehh crap same thing skips tp writes....Still stuck, any other .zip to try? HTC Device(without seperate engineering mode does not seem to more "pro" (but the htc windows drivers, they seem more robust
What to do now :| ???
thx G
---------- Post added at 09:36 PM ---------- Previous post was at 09:12 PM ----------
same thing bootloop
computer now sees a unknown usb device anyone have the .inf? Google search for "mytouch .inf" showed only 6 results none I can use... Would rather use a .inf and install from disk than use .exe
EDIT: flashed http://forum.xda-developers.com/show....php?t=1174344
not it writes to #7 TP but not #8 still in bootloop... Now cant flash cause that is most recent... Can I try to flash any custom roms? or... My s is on

Its a waste of time people, sorry to say but this is definetly a hardware issue and its been spreading all over the world with people having issues on that same subject.

[Q] Stuck in safe mode

Hi everybody.
I don't know how it happened (I just wanted to do a reboot in the recovery mode), but now I've got the blue led when normally turn my phone on. I can't even access to the fastboot (blue led too).
The only thing I can do, is boot in the safe mode, by booting my phone (connected to the charger) after removing the battery... I tried "reboot to bootloader", without success...
I think it's because of the recovery, because I had some problems during the installation of my last ROM, a few months ago. So I'd think I must flash a new recovery.
ow can I get out???? ADB? Special "trick"? Factory reset from the ROM? Flashing a new recovery (I don't know how...)?
Thank you, Roumaru

I tried to flash a new recovery with ADB, and then reboot to the bootloader, but it didn't work.... I'm really stuck!

Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app

george.wgx said:
Try RUU method if you are able to acces bootloader mode ,or try to search the forum or look into FAQ,for the answer of your problem.
Sent from my HTC Magic using xda app-developers app
Click to expand...
Click to collapse
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet

Roumaru said:
I can't access to the bootloader... I can just access to the safe mode! It's really strange. I'll search in other forums, but I haven't found any answer yet
Click to expand...
Click to collapse
Install mumilover's Fastboot Commander. Connect it to your PC with a USB cable, turn it on, and run Fastboot Commander. It will display a bunch of information about your phone that will help us diagnose the problem.
Just cut and paste the info it gives you. If it doesn't work, just tell us what information you see on the phone's screen.
You should see something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
CPLD-10
RADIO-6.35.07.29
Aug 4 2009, 19:43:30
Later.

DasBub, he cannot acces bootloader,so he 's not able to see that info

george.wgx said:
DasBub, he cannot acces bootloader,so he 's not able to see that info
Click to expand...
Click to collapse
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?

DasBub said:
Yes, I understand that he can't get into HBOOT, FASTBOOT, or Recovery using physical buttons. But there are other possibilities we can check. I don't know his skill level, knowledge about the device, or the complete state of his device, so I'm trying to build a clearer picture.
If fastboot reports nothing, what about adb? If adb reports nothing, check device manager to see if it's even noticed by the PC.
When I said "just tell us what information you see on the screen" what I meant was "tell us what the screen is showing, even if it is nothing at all and the blue LED is on". My fault.
I'm curious about the whole "safe mode" business. Is it truly booting into safe mode, where you can see the words "safe mode" on the screen, or is it something else?
Click to expand...
Click to collapse
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest

Yeah dude there is fix for you its named JTAG Google it and you will find out what is it.
In my country its cost me 40 Euro to fix i hope in your is cheaper or even better - you can make your own

Roumaru said:
I took a look at "fastboot commander", but naturally I need to be in the fastboot to make it work, and I can't access fastboot...
I can NOT boot in HBOOT, FASTBOOT, and Recovery, but when I remove the battery, put it in the phone, plug my charger, and then press the power button, the phone boot normally, except he's in the "safe mode" (can't access some applications, no network). I can control my phone with ADB, but when I tried "adb reboot bootloader", the blue led was here again...
I also tried the RUU method, but the RUU doesn't recognize my phone.
I think it would be good if I could do a "total reset" of my phone, like flashing it or something that can reset the bootloader.
Thank you for your interest
Click to expand...
Click to collapse
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.

Please don't post Q&A in the development section.
Thread Moved
Moderating from my One Xl

DasBub said:
Could you try something? Make sure your phone is accessible using adb, then do this:
adb -s [serial number for phone, without brackets] reboot oem-78
The serial number can be found using "adb devices".
That should reboot you into RUU mode. If it doesn't work, safe mode should still be accessible.
Click to expand...
Click to collapse
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!

Roumaru said:
Doesn't work, the blue led is coming again...
Another idea, except Jtag? Because I don't want to spend money on my Magic, and I don't think I've got the material to do the Jtag...
However, thank you everybody!
Click to expand...
Click to collapse
Hey, we're not giving up yet
You can access ADB, so it may be possible to push a recovery image onto the device and flash it.
For the original instructions, click this link and focus on Step 9.
Here's a shortened version:
Download roottools and unzip it somewhere on your PC.
With your phone in Safe Mode and connected to your PC, open a command prompt.
If you know which radio you were on (3.X or less, or 6.X), cd to that directory in roottools and push the recovery image.
Example: If you have 6.X, you would
cd c:\roottools\6.35Radio\​adb push Recovery-RA-hero-v1.6.2.img /sdcard​
Next:
cd to the "App" directory of roottools, then
adb push flash_image /data/local/tmp
adb shell
su
cd /data/local/tmp
chmod 777 flash_image (you might have to use /data/local/tmp/flash_image or ./flash_image)
flash_image recovery /sdcard/Recovery-RA-hero-v1.6.2.img​
If you get through that with no errors, we should be good. If it throws an error at "su" then you should try using SuperOneClick to get temporary root.
If it flashes without errors, you can try "adb reboot recovery" and see what happens.

Resolved
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru

Roumaru said:
A few days ago, the "safe mode" logo disappeared. Really didn't understand why, but now my problem is solved!
Thank you for all, Roumaru
Click to expand...
Click to collapse
That's great news! Everything works normally now?
I have heard that a stuck button or trackball is a possible cause. Maybe that was the problem with your phone, but it became unstuck?
Cheers!

[Q] N4 Broken Screen, Desperate, Kit Kat 4.4.2, Stock Everything, No USB Debugger

Hello,
I just came back from my honeymoon and all of my pictures are on my N4. Of course before I pull the pictures, I drop the phone is the screen is cracked and the touch does not work anymore.
I'm really desperate to get these pictures. I've read all over online but my problems are this with all of the help out there:
My phone is the latest 4.4.2 on T Mobile.
It has stock EVERYTHING (bought straight form google), and the USB debugger is not enabled. (next phone I get this is the first thing I'm enabling.
I've been trying to follow instructions online but a lot of items have changed between last year and Kit Kat now and some steps such as unlocking the bootloader seems to wipe out everything on my phone.
I've been trying to use ADB and Freeboot but really havent gotten anymore.
I've also read that I can maybe use a usb mouse to substitute and unlock my phone? USB OTG? How do I know if my nexus has that enabled?
I'm even considering getting a new screen so I can try to replace the current one and get my photos. I dont care what happens to the phone but the pictures are priceless to me.
Is there any thread or guide that incorporates 4.4.2? the more detail the better of course.
Much thanks in advance.

have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...

Shubhamqweasd said:
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Click to expand...
Click to collapse
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.

zhanism said:
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
Click to expand...
Click to collapse
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652

Shubhamqweasd said:
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Click to expand...
Click to collapse
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.

zhanism said:
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
Click to expand...
Click to collapse
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.

acejavelin said:
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
Click to expand...
Click to collapse
I have same problem with broken screen, i bought for 56$ full kit on ebay, no need separate glass from screen. took me 1h20min, never done before but what a relief seeing everything working

You do not need USB debugging to transfer files. On windows, open file explorer and with your nexus 4 connected it should appear on the left side as Nexus 4. Or if you have osx use http://www.android.com/filetransfer/.

Need help unlocking bootloader

I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.

What do you get if you run "adb devices"?

thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?

I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.

blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk

Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here

DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.

blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters

Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.

twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?

blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.

I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command

twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.

Let us know how it turned out ?

Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.

blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.

blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.

Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".

Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?

blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it