I have a Semi-Bricked HTC Hero...
1) Was flushed (GGrrr...)
2) Phone kept working for a while (My wife tells me)
3) I opened phone up... blew it out with COmpressed air, and sat the PIECES in Rice for days....
4) Phone turns on, but will not boot... Just shows the white screen with Green HTC logo... after a few seconds.. it goes black.. and tries to boot again....
5) I CAN Boot to the FastBoot or HBOOT menus and phone stays on just fine...
a) If I switch to FastBoot (Vol Up) when USB is connected.. Phoe says FastBoot USB...
i) I WAS able to run the stock Sprint RUU to "Update" the phone....
but it does NOT solve my boot issue..... Something is still missing.....
Anybody have any ideas? I woudl like to get her two week old Hero working....
1) I bought TWO HTC Heros...
2) I have upgraded BOTH to 2.1-Update 1
so if I need to do something to pull an image off a HERO.. I have one fully functional here (unrooted.. since I have only had these phones for 1 month)
Any help from you pros woudl be greatly appreciated....
klockk said:
I have a Semi-Bricked HTC Hero...
1) Was flushed (GGrrr...)
2) Phone kept working for a while (My wife tells me)
3) I opened phone up... blew it out with COmpressed air, and sat the PIECES in Rice for days....
4) Phone turns on, but will not boot... Just shows the white screen with Green HTC logo... after a few seconds.. it goes black.. and tries to boot again....
5) I CAN Boot to the FastBoot or HBOOT menus and phone stays on just fine...
a) If I switch to FastBoot (Vol Up) when USB is connected.. Phoe says FastBoot USB...
i) I WAS able to run the stock Sprint RUU to "Update" the phone....
but it does NOT solve my boot issue..... Something is still missing.....
Anybody have any ideas? I woudl like to get her two week old Hero working....
1) I bought TWO HTC Heros...
2) I have upgraded BOTH to 2.1-Update 1
so if I need to do something to pull an image off a HERO.. I have one fully functional here (unrooted.. since I have only had these phones for 1 month)
Any help from you pros woudl be greatly appreciated....
Click to expand...
Click to collapse
The stock RUU would put all the necessary things back to default so i dont think it could be fixed by pushing/pulling anything. Its sounds like when the phone is starting to boot its just simply not able to. It could be do to a messed up hardware that got wet. Something thats necessary for the phone to boot, but not necessary for it to sit in recovery or during RUU.
Have you tried rooting the phone? Maybe if you can get it to boot far enough you could run "adb logcat" and see whats keeping it from booting.
But if you follow the OC threads at all. Some phones simply cant handle the speeds, so it puts it in a bootloop (using OC as example). Maybe something similar is happening here on a hardware level, its just not able to run so its returning to the black screen.
One more thing... Try to use the battery from the good hero in the messed up one. That has solved my problems many times my phones got wet. The battery is usually the first thing to go.
If nothing I mentioned help in anyway.. hopefully someone else will be able to. Them toilets will getcha.
But how can I root the phone if all I can get to is the boot screen (HBOOT or FASTBOOT)??
You got a secret for me?
klockk said:
But how can I root the phone if all I can get to is the boot screen (HBOOT or FASTBOOT)??
You got a secret for me?
Click to expand...
Click to collapse
I didnt think about that.. The new root method is alot more to it then the old one (1.5 method). I forgot the new one you have to be in android to do some things.
Try running the RUU again and use a fresh battery.
Fresh Battery..... from my workign HERO...
Ran HTC_sprint_hero_mr_2.27.651.6 from Sprint...
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>adb devices
List of devices attached
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>adb logcat
- waiting for device -
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
* daemon not running. starting it now *
* daemon started successfully *
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
Click to expand...
Click to collapse
That's all I could capture during the process....
Interesting that fastboot sees the device, but adb doesn't...??
Code:
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>fastboot devices
HT02RHF02979 fastboot
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>adb devices
List of devices attached
Code:
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>fastboot reboot
rebooting...
finished. total time: 0.028s
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>fastboot reboot
rebooting...
finished. total time: 0.021s
F:\Software\HTC\android-sdk_r06-windows\android-sdk-windows\tools>fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: not allow)
finished. total time: 0.001s
Phone shows the following at this time when I boot into the fastboot menu
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
Click to expand...
Click to collapse
Try this. Run the ruu don't plug your phone in. Once it starts open up task manager and go to processes and right click on ruu exe or whatever the name is (just woke up not trying to think) and open up file location. A new window will open scroll to rom.zip copy that to your desktop then close the window and then the ruu. Now place the rom.zip on your sd card and rename it to HERCIMG.zip. Now if your phone ain't off turn it off then restart it holding the vol down key and red power button it should restart and scan your sdcard. Find hercimg and start to apply it
If you ran the stock RUU and it worked, try running the 2.1 Test release that was leaked a while back. That came already rooted.
Got HRCIMG.zip on the SD card ...
Had to use my other phone to transfer the fiel to the SD Card.. (so we knwo the SD Card is good!)
But when thebricked phone starts up.. and HBoot searches for HERCIMG.zip, it doesn't seem to find it..??? I suppose it could be that the phone doesn't see the card? Any way to verify that?
klockk said:
Got HRCIMG.zip on the SD card ...
Had to use my other phone to transfer the fiel to the SD Card.. (so we knwo the SD Card is good!)
But when thebricked phone starts up.. and HBoot searches for HERCIMG.zip, it doesn't seem to find it..??? I suppose it could be that the phone doesn't see the card? Any way to verify that?
Click to expand...
Click to collapse
HMMMM that is strange. Maybe so you can't get into recovery either? I'm trying to remember how but it's not coming to me try two things. Using fastboot try to run the system image from your sd card. Also try the ruu in hboot or fastboot usb. Or manually running the ruu from fastboot using adb
This is why I don't use my phone around the toilet!!
Good Luck!
&RoidRage said:
This is why I don't use my phone around the toilet!!
Good Luck!
Click to expand...
Click to collapse
So what do you do while your taking a sh!+
Lol I read news from the Genie widget while I'm on the crapper. Keeps me occupied for way too long. I was in for an hour once and my parents started to get worried xD
thatguythatdid said:
So what do you do while your taking a sh!+
Click to expand...
Click to collapse
You use it like this. Just make sure to lean over the toilet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thatguythatdid said:
HMMMM that is strange. Maybe so you can't get into recovery either? I'm trying to remember how but it's not coming to me try two things. Using fastboot try to run the system image from your sd card. Also try the ruu in hboot or fastboot usb. Or manually running the ruu from fastboot using adb
Click to expand...
Click to collapse
I'm new to all this SDK stuff... so I might require some help here...
1) is that ROM.ZIP a REAL ZIP file? because when I capture it, and try to open it with WInZIp.. it gives an error..
if I o to the HBoot Menu, and then hit <HOME> for Recovery, the phone just imediately starts booting over and over again.... Just the white screen with green HTC in the middle....
I can't run the stock RUU while the phone is in HBOIOT mode.. gotta have it in FastBoot USB....
I'll be back on my computer in bout 45 minutes
-------------------------------------
Sent via the XDA Tapatalk App
klockk said:
I'm new to all this SDK stuff... so I might require some help here...
1) is that ROM.ZIP a REAL ZIP file? because when I capture it, and try to open it with WInZIp.. it gives an error..
if I o to the HBoot Menu, and then hit <HOME> for Recovery, the phone just imediately starts booting over and over again.... Just the white screen with green HTC in the middle....
I can't run the stock RUU while the phone is in HBOIOT mode.. gotta have it in FastBoot USB....
Click to expand...
Click to collapse
Yes it is but it uses lzma compression. Do you have the sdk setup yet? and in your system path? You are using windows right? what version? I got a way that I just tested for you that will work in fastboot
Looks liek the battery must have died sitting here on the FastBoot menu...
Guess that means it's not "Charging" either.....???
pull the battery then put it back in then plug it in to your wall charger don't turn it on do you see the light?
Related
Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
TomCarter21 said:
Try to root my LG Optimus 4X HD and the cmd window say:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
Well.. Thats scared me. Now, my phone is soooo slow, I could uninstall the System Backup Test, but, my phone still very VERY slow.
Please, help me :crying:
Click to expand...
Click to collapse
Do the "factory reset". Erasing all data of course...
To try factory reset from recovery menu
1. turn off the phone
2. press vol down + power
3. waiting vibrate 2 times and release button
4. choose wipe data/factory reset
after that re-root again
don't forget setting debugging mode
before root.
Sent from my LG-P880 using xda app-developers app
First step would be to disconnect any other Android device.
Second one, put the phone to Airplane mode, you can do with some patience even with the SystemBackup.apk installed. Switch USB mode to "charging only".
If that doesn't help, you can still do a reset.
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
XperiaPlayer said:
Do you have the Android SDK installed and are you running the root.bat as an Administrator?
Click to expand...
Click to collapse
Sorry @XperiaPlayer but, I don't have the Android SDK installed, and my root goes perfect...
You're sure that matters?
Regards
Shift + right click the folder where the root.bat is located and type adb devices (or adb.exe devices) and paste the output here.
Reference : http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions
The tool may be downloaded here. It may be used as follows:
1. Extract the entire contents of the zip file.
2. If you are using Windows, ensure you have installed the latest Motorola USB drivers available for your phone.
3. Ensure your device has been rooted and you have a working installation of “su”.
4. Ensure USB Debugging mode is enabled on your device.
5. If you are using Windows, navigate to the extracted directory and execute “run.bat”. If you are using Linux or OS X, navigate to the extracted directory in a terminal and execute “./run.sh”.
Download >>http://vulnfactory.org/public/motopocalypse.zip
@Djrbliss Wins the bounty of $835
Donate to Dan [LINK] to say thanks
Details on how DJrbliss did this : http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html
FAQ's
Do I need to ditch safestrap?
-No. You can leave Safestrap where it is for now.
Can I flash a normal recovery?
-Yes, at the moment there are existing CWM and TWRP (new and recommended recoveries that Hascode made. Stock recovery is inside the FXZ files and it can be flashed alone.
Can I Flash Anything I can do now?
-Yes, but things need to be developed at this point, this is NEW territory for Motorola
Can I now flash different kernels or radios?
-Yes, you can flash ANYTHING you want
Is my phone basically the same as the Dev edition now?
-Yes, from what we can gather, anything that boots on the dev edition will also work on your unlocked device
How to I Get Rid of the ANNOYING "Bootloader Unlocked Warning" Boot screen?
-Once you have unlocked you bootloader and are afraid of the annoying "Bootloader Unlocked" warning which comes everytime you reboot.
here is a solution by @tucstwo which replaces it with the moto logo.
Just make sure you've got your drivers installed, USB debugging is enabled and that you have UNZIPPED this package BEFORE you run it.
Download Link Below
http://d-h.st/JSx
Unzip
Plug in Phone
Hit "Run"
Thanks A Million
Unbelievable.!!!! Thank you so much. I am whatever comes before noob when it comes to this stuff. And this was so simple. I also did this on Win 8 so it can be done on this OS. Can't wait to see what all everyone comes up with!!!
DMK1111
Atrix HD JB 4.1.1 rooted and now Unlocked !!!
This by far is the easiest way ive ever seen.Ive owned every atrix and this rocks OUTSTANDING JOB GENTELMEN
any one got a link to TWRP?
Franzferdinan51 said:
any one got a link to TWRP?
Click to expand...
Click to collapse
http://goo.im/devs/Hashcode/vanquish/twrp-2.4.4.0-recovery-vanquish.img
Here's the RAZR HD thread with instructions Pretty much the same as the CWM ones I posted, only you have to make a backup first thing when it boots into TWRP after its install.
I've read that Hashcode is going to write a TWRP just for us so I'm going to wait until then.
Thanks
Sent from my MB886 using Tapatalk 2
Thank you so much now I have mi Atrix HD with unlocked bootloader
I did it successfully. Thank you.
does any one have link to stock 4.1.1 for dev device i want to try it on my att atrix hd since we have the bootloader unlock
i cant get it to work i have a razr m this is what i get
[*]
[*] Motopocalypse: Motorola bootloader unlock script (Windows version)
[*] v1.0
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Supports the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*]
[*] Before continuing, ensure that your device has been rooted and you have
[*] a working "su" installation, that USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will permanently void the warranty on your device. This
[*] is not reversible. I am not responsible for any damage to your phone
[*] as a result using this tool.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Device found.
[*] Pushing unlock tool...
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Unlocking phone...
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Cleaning up...
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Unlocking complete. Rebooting into bootloader mode.
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Press enter once the phone has rebooted into bootloader mode.
Press any key to continue . . .
Did you extract the files first?
Sent from my MB886 using xda app-developers app
Some users facing issue on Windows 8 please extract and try to run on windows 7..it will work
Sent from my Golden'd Atrix HD MAXX using xda app-developers app
L7iharsha said:
Some users facing issue on Windows 8 please extract and try to run on windows 7..it will work
Sent from my Golden'd Atrix HD MAXX using xda app-developers app
Click to expand...
Click to collapse
im on windows 7 and i extracted to the desktop im a newb so maybe im doin something wrong im on 4.1.1 and i extracted to desktop and run run.bat do i need to put it in factory mode and i also have safestrap installed
R u installed Motorola Drivers and did u connected your phone in MTP Mode?
Sent from my Golden'd Atrix HD MAXX using xda app-developers app
Is your phone in usb debugging mode along with what he said.
Sent from my MB886 using xda app-developers app
Yeah I got the drivers installed im gonna reinstall and see if that works
*I reinstalled the drivers and the only driver not installing is Motorola Networking Interface
If this dont work ill return to stock and reroot my razr m
Sent from my SCH-I605 using xda premium
Dewaynelives said:
Yeah I got the drivers installed im gonna reinstall and see if that works
*I reinstalled the drivers and the only driver not installing is Motorola Networking Interface
If this dont work ill return to stock and reroot my razr m
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
i think that's the coz if u are on custom rom return to stock enable usb debugging usb drivers on pc and then try again it should work
Make sure you don't run the unlock with battery low condition. 20% battery is enough.
I think its a prob with my computer tried to re root using batman utility And git the same error :/ SMH
Sent from my SCH-I605 using xda premium
Hey guys, having a big problem here. Pretty much what the title says. I got my new (used) XT862 this morning, it had been reset to a fresh rom and wasn't rooted. I was so excited to finally get it that I started modding straight away.
First of all, I forgot to jot down the exact version number of the rom. I know already this was really stupid, but I can't do anything about it now... It was 2.3.4... I'm guessing it might have been the original 890? Is there any way to find this out from the recovery menu?
I'll try to describe what I did as completely as possible, I don't know if something might have gone wrong during the process or what.
First I installed Safestrap 3.05 from this link, not realizing that I had to have root (duh). It seemed to install fine, then when I ran it I got the standard "stopped responding" error with the "force close" button.
I then rooted it using Motofail, first I forgot to switch to root on my PC and it stopped at "daemon started successfully" so I hit CTRL+C until it dumped me back to the command line. Then I changed users on my desktop with su, ran it again and it worked perfectly, the superuser app on the phone showed up and it was operating normally.
(Here's what happened the first time I ran Motofail from my non-root user acct, I had to hit CTRL+C twice, once after "daemon started successfully, once after "waiting for phone to reboot" at which I rebooted the phone manually. Was still booting fine at this point.)
Code:
[*]
[*] Motofail: Universal Motorola Gingerbread Root Exploit (Linux version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
^Cerror: protocol fault (no status)
[*] Device found.
[*] Deploying payload...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: insufficient permissions for device
error: insufficient permissions for device
[*] Owning phone...
error: insufficient permissions for device
[*] Rebooting device...
error: insufficient permissions for device
[*] Waiting for phone to reboot.
^C
After rooting it was still booting fine so I think the problem was not there. Once everything was finished and I was back at the home screen I re-ran Safestrap which appeared to be running normally. I was planning to install Minimoto but I ran "create recovery image" first which I figured couldn't hurt. Well, Safestrap worked for a minute, then crashed (the "not responding - force close" error screen came up) and trying to run it again just crashed it immediately.
I did nothing else, just rebooted the phone not realizing the crash had apparently messed up my bootloader? Now I just get a boot loop, it plays the little Droid animation over and over again.
When I boot into the menu with M+power I don't get a Safestrap menu, and running "recovery" from there just gives me a screen with an /!\ icon and the Android character. I get the same screen if I try to boot with X+power.
I've tried to download the fast unbrick rom from here but neither of the links work... The old Dropbox link is long gone and the new Mediafire mirror says its allotment of 10 free downloads per week has been exceeded... infuriating!
Can anyone give me some advice or steer me in the right direction? I was so excited to get my new phone, I'll be heartbroken if I've managed to brick it for good! I don't want to do anymore damage without advice... please help?
********** // **********
EDIT: I found a mirror for fast/easy unbrick and that worked, so I'm now back to the stock 890 rom with functional bootloader and am much relieved. Two questions though:
1 - Can anyone shed some light on what went wrong during the safestrap process that bricked the phone? Was the fact that I tried to install it before I rooted it the cause?
2 - There is still a /safestrap directory on my internal storage (containing only the files "active_slot" and "translate"), should I delete this? Are there other bits of Safestrap left behind that I should get rid of too?
I will eventually try again as I'd really like to run Minimoto on this thing but I want to understand what I did wrong first.
Any info appreciated, thanks!
xjas said:
EDIT: I found a mirror for fast/easy unbrick and that worked, so I'm now back to the stock 890 rom with functional bootloader and am much relieved. Two questions though:
1 - Can anyone shed some light on what went wrong during the safestrap process that bricked the phone? Was the fact that I tried to install it before I rooted it the cause?
2 - There is still a /safestrap directory on my internal storage (containing only the files "active_slot" and "translate"), should I delete this? Are there other bits of Safestrap left behind that I should get rid of too?[/b]
I will eventually try again as I'd really like to run Minimoto on this thing but I want to understand what I did wrong first.
Any info appreciated, thanks!
Click to expand...
Click to collapse
1. I'm not sure why, but I can tell you that I have rooted using Motofail and installed Safetrap 3.05 multiple times without issue. Also, you should realize that Safestrap creates its /system, /data, and /cache directories for each ROM slot on "internal storage", so you need to make sure that you keep enough space there to fit the ROM slots. It's pretty much a given that you should use an external SD card and have the camera app, etc., store data on external SD rather than internal storage. I'd also avoid running apps on "internal storage".
2. It won't hurt to delete those files.
So, you should be able to:
- clear out enough storage on "internal storage". Make sure that you have at least 1 GB more than the data partition you want to create available, though I would want more
- enable USB debugging and root using Motofail
- *then* install Safestrap and install recovery
- do a full reboot to make sure that both the Safestrap menu pops up and the phone restarts fully without looping, etc. (In other words, make sure that stock boots and runs fine.)
- then create a ROM slot, activate it, flash Minimoto and have fun.
Well, went back through the whole process and it went great the second time. Now have Minimoto 1.7 running on a 3 GB partition (probably way overkill??) I'm really enjoying the minimalism in this release, no more sifting through pages of uninstallable crap in the menu to get the stuff I actually use. The extra speed & free memory makes a nice bump up from the HTC Dream (with 1.5 Cupcake!) this phone replaces.
Thanks for the advice, still no idea what went wrong the first time but I'm happy it's working how I want now.
I just bought Htc one ywsterday and i was unlocking the bootlaader today and root, and i'm trying to flash custom rom, but i can't copy anything to my storage... i did install sdk and the drivers and everything, tried lots of things, tried with adb push but it's not working, and now i'm pissing off... don't know what's the problem/.....???
p.s when i type
adb devices it says:
*daemon not running*. starting it now on port 5037 *
*daemon started succesfuly*
List of devices attached
HT35***** device
P.s.s I tried to adb sideload a rom and i get :
*daemon not running*. starting it now on port 5037 *
*daemon started succesfuly*
error: closed
Please help...
So when you plug your HTC device into the computer...go to start-computer and you dont see htc one as a media device? It should also pop up with options to open files in your device when you first plug it in
No no, the device pops out but the problem is the copyng starts and then it stucks... even for files that are 1mb
EDIT: Never mind.
sauprankul said:
EDIT: Never mind.
Click to expand...
Click to collapse
?
Sent using my HTC One from that FBI van parked down the street.
Unplug the USB and replug. Make sure the screen is unlocked. Sometimes happens.
Sent from my HTC One using xda app-developers app
also do not use a USB 3.0 port on your computer
Hey,
So I unlocked the boot-loader and installed CWM Recovery and flashed to- http://forum.xda-developers.com/showthread.php?t=2026675 but it doesn't go any where from the loading screen then I tried installing Pac-Man ROm same thing keeps loading in the boot screen doesn't go further my device is S-on and I don't know if it is rooted ? I'm sort of a noob at rooting any ways can some one tell me why this is ?
Cheers
For a start you need to get rid of CWM. It does weird and wonderful (not in a good way) things to this phone. Try TWRP or the one from Wild Child (sorry cant remember the name of it). Second, being S-on requires you to manually flash the boot.img using fastboot or you just get bootloops. Best thing you could do is read thoroughly through the pinned post as they contain all the info you need.
Spectrejester said:
For a start you need to get rid of CWM. It does weird and wonderful (not in a good way) things to this phone. Try TWRP or the one from Wild Child (sorry cant remember the name of it). Second, being S-on requires you to manually flash the boot.img using fastboot or you just get bootloops. Best thing you could do is read thoroughly through the pinned post as they contain all the info you need.
Click to expand...
Click to collapse
WHat does this mean" manually flash the boot.img using fastboot "
Thanks
it means flashing the boot.img or boot image to the phone while in bootloaders fastboot option using fastboot in a command prompt. I suggest taking time to read all pinned post in development area several times till you understand it before doing anything more, lest you end up with a bricked phone.
Here is a link to a good start http://forum.xda-developers.com/showthread.php?t=1416836
As i said read it several times to make sure you know what you are doing is right.
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Mihir1997 said:
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Click to expand...
Click to collapse
Where are the attached files mate ?
Oh LOL...
http://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Mihir1997 said:
Oh LOL...
http://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Click to expand...
Click to collapse
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Why is this ?
dinukap4 said:
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Why is this ?
Click to expand...
Click to collapse
Is ur phone plugged in? is USB debugging on in the dev options menu?
Mihir1997 said:
Is ur phone plugged in? is USB debugging on in the dev options menu?
Click to expand...
Click to collapse
ok did that now waiting to load fingers crossed
About 5 min passed still loading :/ Should I wipe anything ?
Edit- Tried with both CM and pac same :/ did everything correctly btw what does "now, on your computer, set up adb" Mean ?
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1AXVJ00209 recovery
C:\android-tools\android-tools>adb reboot bootloader
C:\android-tools\android-tools>fastboot devices
HT1AXVJ00209 fastboot
C:\android-tools\android-tools>fastboot flash boot boot.img
sending 'boot' (3570 KB)...
OKAY [ 0.796s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.350s
C:\android-tools\android-tools>
that is like the thing that the next steps explain.
so, did you fastboot flash the boot img?
it has to be the boot from the rom you want.
Mihir1997 said:
that is like the thing that the next steps explain.
so, did you fastboot flash the boot img?
it has to be the boot from the rom you want.
Click to expand...
Click to collapse
When I try to do the CMD stuff on this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It tells me -
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Click to expand...
Click to collapse
And if I give this command -adb reboot bootloader
C:\android-tools\android-tools>adb reboot bootloader
error: device not found
Click to expand...
Click to collapse
But if i go to recovery and enable Debugging it passes, But I cant enable it and come back to the Fast boot screen because debugging will be disabled and I get the same thing-
If done with recovery debugging-
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1AXVJ00209 recovery
Click to expand...
Click to collapse
Bump!!
BUMP! Please help me out
Is this an HTC vivid ? screenshot doesn't look like one...
Lol, wrong forum. This is NOT an HTC Vivid. You have to atleast know what phone you have. Go to the forum for your device. but either way. This image suggest you have not plugged a UDB into the phone. If you had, it would say "fastboot USB"
esloan said:
Is this an HTC vivid ? screenshot doesn't look like one...
Click to expand...
Click to collapse
Mihir1997 said:
Lol, wrong forum. This is NOT an HTC Vivid. You have to atleast know what phone you have. Go to the forum for your device. but either way. This image suggest you have not plugged a UDB into the phone. If you had, it would say "fastboot USB"
Click to expand...
Click to collapse
I got that off google images lol not my phone anyways I got it to work, but it doesnt have play store and my memory car isn't accessible ? I tried with 2 mem cards both the same cant download anything
dinukap4 said:
I got that off google images lol not my phone anyways I got it to work, but it doesnt have play store and my memory car isn't accessible ? I tried with 2 mem cards both the same cant download anything
Click to expand...
Click to collapse
Play store Fix: flash Gapps (google apps) - you can do a search on google. Download the correct one. if you have a rom with Android 4.2.2, use a Gapps for 4.2.2
Memory card: What rom are you using? go into the Rom forum and post there for help.
Mihir1997 said:
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Click to expand...
Click to collapse
$$$ post right here -- Thanks for putting this up -- Huzzah Huzzah