[Q] Stil. . . - Hero, G2 Touch Q&A, Help & Troubleshooting

Well, my phone wont even recognize that it is plugged into my computer.. it won't recognize the sd card in it either, is there a way i could fix this with the carebear screen? like get an img of a rom and name it to where it loads it..? i really need this fixed...

Dont think there is anything you can do from your recovery. But there is a thread over at the modaco site called "No SD, No adb" which might be helpful?

you have a link..? lol, this is killing me...

http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/

ok, i read it.. call me a newb, but by saying
- Reboot into a special mode by sending "fastboot oem rebootRUU"
what does he mean..? lol, the cmd on the pc..? or..?
figured it out... following instructions -.-;

Related

Help plz!

I just updated my phone through wifi, somekind of system update i guess.. but after i've updated it and restartet it, it just freezes at the 'hero' screen (infinit loop boot maybe?) i just got the phone (used though) the only thing i can do is go into the fastboot screen, but i dont really know what to do now.. i've done various things to try to get further but the only difference have been that i've seen a screen showing a phone with a red triangle with an ! in it..
I normally never waste other peoples time with these problems, but this is ****ing annoying, if anyone could help me.. i would really appreciate it...
The phone isn't flashed just original rom..
Was it rooted before the update? This kind of thing happend to me with a Desire. I he'd done an ota update after root and got infinite boot loop.
The only thing to do, was to flash original ruu. I guess you should do so. Just search the forum for Hero RUUs. I'm sure you'll find.
Sent from my HTC Hero using XDA App
actually my friend had tried to root it without success, and me being a noob to it tried to do so too, but got stuck in the cmd where it just showed downloading FAILED.. so no it wasn't rooted.
But thanks for the reply just needed to know what to do ^^
Elgaard2 said:
actually my friend had tried to root it without success, and me being a noob to it tried to do so too, but got stuck in the cmd where it just showed downloading FAILED.. so no it wasn't rooted.
But thanks for the reply just needed to know what to do ^^
Click to expand...
Click to collapse
So did it help?
arvan said:
So did it help?
Click to expand...
Click to collapse
going to try it now, found the ruu's you were talking about, if you got time afterwards would you help me to root it? would be nice, still thanks for the help though
dammit seemes like i've been here before... i've tried doing it with no success, like i said i can only go into fastboot usb mode.. it locks at the 'hero' screen so cant get into the OS to get the original ROM reinstalled :S
If you've got the latest ruu, then going to fastboot is enough. You must open fastboot, connect usb and run the exe. It's the only way.
Sent from my HTC Hero using XDA App
it can't find my phone.. i've read some threads about some people having the same problem running window 7 x64, i figure it might be because i didn't install any drivers for the phone before, only used it through usb to recharge and usb stick.. but i've tried downloading the ADB software etc. still nothing.
It is a driver problem. Download latest htc sync. It has all the drivers. Helped in my case.
Sent from my HTC Hero using XDA App
awesome thanks, going to try it now
boot into recovery, do hard reset (this would erase every thing though)
and you need help to root? what is the version of your software?
it's still not working i'm getting [170] error... so i've searched for this problem and found some different methods to figure out what to do now, the weird thing is that in cmd when i type "fastboot devices"... it finds my device, that i already knew.. BUT when i type "adb devices" it just writes "List of devices attached" = nothing.. absolutly nothing.. soo guess i'll just have to figure out how to do next now..
how do i do that? explain it like i'm a moron ^^
well did it, still infinit loop :S
i really REALLY dont hope this ends up with me getting a crappy iphone instead..
now i know that it only get into something called cleanstorage.. not the recovery mode...
Wait. What have you done exactly? You don't need neither recovery, nor adb.
Adb won't see your device, because there's no working os on it. You just neet 2 things that will repair the phone. Htc sync and latest RUU EXE file. If you have htc sync, turn the phone into fastboot, plug usb cable and you will see 'fastboot usb plug' on the phone. Now open 'device manager' on pc (right click on Computer>properties>device manager o the left panel). If the drivers are ready, there will be 'Android>my htc'. If not, look on the taskbar near the clock. There mite be some mooving icon saying 'installing driver softwere' or something like that. Wate for some time. I wated about a minute till it said 'device is ready'.
Whet drivers are ready, run the RUU exe file. Say 'yes' to everything and don't touch the phone. It should do th job.
Try this steps and tell what happened.
Sent from my HTC Hero using XDA App
Oh and don't forget to hard reset. It is the 'clean storage'.
Sent from my HTC Hero using XDA App
dude i've done everything that you've said before, and now i did it again it doesn't work.. i still get the ERROR [170] USB-CONNECTIONERROR..
- if this makes any difference, for me it isn't called 'my htc' - it's 'ADB Interface' > 'HTC Bootloader'
- i've installed the ADB **** that didn't work, then uninstalled the driver, then downloaded the 'HTC Sync' and installed it, so it is the driver from 'HTC Sync'
i've might have found both the problem and solution now
okaay, it's a driver problem, now im trying it on my laptop, it then got to ERROR [131] instead xD haah well a bit progress is better than no progress at all..
____________________________________________________________________________________________________________________
Now it works! damn awesome, thanks!

Problems rooting 2.3.6

Tried out both these sets of instructions:
http://androidadvices.com/root-motorola-atrix-4g-45141-gingerbread-236-firmware/2/
http://www.androidauthority.com/atrix-4g-android-2-3-6-firmware-4-5-141-root-63533/
None of them since I can't even get past step one with the command lines. The command prompt won't recognize either saying "[name] is not recognized as an internal or external command, operable program, or batch file.
When I rooted while I was using 2.3.4, I had no issues doing it manually this way. I'm at my wits end. Don't know if it's a problem on my end or just the result of Motorola intentionally trying to make it hard to root and unlock this phone(apparently rooting also voids the warranty with them).
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
moto-fastboot.exe flash preinstall preinstall.img
Click to expand...
Click to collapse
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
octahedron said:
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
Click to expand...
Click to collapse
Did you try just fastboot instead of moto-fastboot? I had to use fastboot the other day and that held me up. But if its waiting for devices then it possibly is a driver issue. Im on the xda app so going to the link you provided wont work for me. Trying uninstalling and reinstalling the drivers.
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
octahedron said:
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
Click to expand...
Click to collapse
Go to device management of the computer and under usb should be your phone (when plugged in). If you aren't seeing it, then the drivers didn't install correctly. I can't remember where I got my drivers from to point you in the direction for that.
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Just to clarify the one I'm referring to is "Motorola ADB Interface". "MB860" has everything current on it.
octahedron said:
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Click to expand...
Click to collapse
When I get on my computer, ill see if I still have all the drivers that I dl. If so will ul to dropbox and post.
Ok this is what I have. Don't know what is what so included what I've got.
http://db.tt/jKixEKQL
http://db.tt/QmpO0ZUx
http://db.tt/CEu1k5q5
The description will pop up with each download. Hope it helps.
Thanks for the help!
I went back to an old bookmark I had when I rooted with 2.3.4 and found drivers. For some reason the motohelper link in my second post in this topic was not helpful. Here's a link for future reference in case anyone needs it:
http://db.tt/XHjBBnGh
I got my phone rooted again and now that I know that works I'll probably go ahead and try unlocking my bootloader to install cm7

YES WE have a FIX for ENCRYPTION UNSUCCESSFUL BUG...HERE WE GO !!!!

THERE IS A FIX FOR EU BUG.....i wasted one day on actually finding out whats going on with our devices....our devices have been basically USB BRICKED...and not CORRUPTED LIKE THAT...we have to correct this thing" can't mount dev block mmcblk0p1"
THOSE GUYS WHO HAVE RECOVERED FROM THIS BUG HAVE BASICALLY SOMEHOW SWITCHED THEIR SDCARD ON....
Our phones SD CARD HAS BEEN SWITCHED OFF BY THE ENCRYPTION UNSUCCESSFUL BUG.....
PROOF...READ THE POSTS ON ALL THE PAGES AND THEN ARGUE WITH ME
-http://forum.xda-developers.com/showthread.php?t=563298
-http://forum.xda-developers.com/showthread.php?t=691639
-http://androidforums.com/desire-tips-tricks/365476-guide-usb-brick-fix.html (MOST IMPORTANT)
the basic thing is that we just need to find how to execute fastboot commands.....i read some pages fastboot refers to bootloader screen and bootloader screen means RECOVERY SCREEN......when i go to the recovery screen and run ADB and execute command all it says after executing the command <waiting for device> (i have checked adb devices...and my device is mounted properly)
WE CAN SWITCH OUR SDCARD ON IF WE CAN EXECUTE THESE COMMANDS SOMEHOW-
fastboot oem rebootRUU
fastboot oem enableqxdm 0
fastboot oem eraseconfig
fastboot oem powerdown
THEY MEAN-
fastboot oem rebootRUU - probably this one doesn't make any sense, but I used it too as a first step
fastboot oem enableqxdm 0 - disables SD card lock (enables SD usage)
fastboot oem eraseconfig - clears and fixes misc parition
fastboot oem powerdown - normal shutdown using fastboot, since I got stucked in recovery saying RUU when I used only the first two commands. I thought it's normal, took out the battery, and restarted, but then I was facing with this Bluetooth/USB storage problem.
PLEASE UPLOAD YOUR PHONE FILES(some 1 who is not having an encrypted device with internal sd working and dont upload your EFS by fault happy woody?)i will swap your files with my phone files and check if the phone starts working with aroma manager!!!
WE HAVE TO EXECUTE THESE COMMANDS...OR OTHERWISE WE ARE ON OUR LUCK....SO PLZ DEVELOPERS...HELP US !!!!!! xD... AND READ THE POSTS AND QUESTIONS...FIRST IN THESE LINKS..I AM CURIOUS TO FIX THIS BUG BECAUSE THERES SOMETHING VERY SPECIAL IN THAT USB STORAGE...WHICH I CANNOT AFFORD TO LOSE...PLEASE HELP.....
manu_ha2001 said:
There are so many of you suffering from this bug...but no one wants to help...fk man if i recover my mem card then it ill help u too. ...**** off guys and help if possible
Click to expand...
Click to collapse
You do realize that all of the developers have lives outside of Xda right? Many even have kids and a full time job. Not to mention that they provide their work to the community for absolutely free. Who are you to speak disrespectfully to them? Please be more considerate and less demanding.
Sent from my Wicked Galaxy S3
I have ben waiting for weeks now and who tr hell do u think u are ? If u dont wanna help then please stfu and i do realise that ie why i have been waiting so patiently so dont teach me dude
And i didnt said the comment for developers..they are for normal users who just seek for help but dont want to help ..i respect each and every developer o the community
Been looking around some with your information. Found this thread for i9000
http://forum.xda-developers.com/showthread.php?p=9204586
Fastboot is not the same as our Recovery or Download screen. It is the Forced Download screen. There is a key combo to get into it on i9000. But the question is can we figure out a way to get into it on our Vibrant?
Clearly you were referring to the developers. I know this because in your first post you explicitly ask the developers (in red) for help before in your second post talking down on those who did not come running to your aid (which clearly include the developers from your first post). Either way, your second post (as well as your posts in response to me) are extremely rude, and disrespectful..not to mention the unnecessary cursing. With that being said, you are reported.
Cheers.
Sent from my Wicked Galaxy S3
Thread closed
Rudeness and disrespect are against the rules
And will get you no help on XDA

[Q] 610 root problems

ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
says S-On . how do i gewt it to say s-off?
LordXombie said:
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
Click to expand...
Click to collapse
Sounds like you need to update to the latest version of ADB/FASTBOOT the "device offline" is usually due to an incomatible older version of ADB. Get the latest version on your PC then make sure that ADB is working before trying fastboot.
LordXombie said:
says S-On . how do i gewt it to say s-off?
Click to expand...
Click to collapse
We don't have an S-off solution for this phone yet but it is not required for root, although you will need to flash jmz's insecure kernel for changes to "/system" to stick after reboot even when rooted,
MiniBlu
i cant seem to get adb to update.
LordXombie said:
i cant seem to get adb to update.
Click to expand...
Click to collapse
Install the latest on your PC from here http://forum.xda-developers.com/showthread.php?t=2317790
MiniBlu
ok so i did that and it is still saying device offline. Now im trying a program i found on here. desire_610_root_v3.exe it was able to reboot the device into bootloader then it brought it into fastboot menu then it started to send the file then it just snags there. the file just keeps saying its sending. i dont know whats going on.
ok it still not getting teh recovery.img on the phone. it just keeps sending it with out doing anything..
ok so this htc is giving me way mopre problems then the htc one vx. i really need help. and now im kind of lost what to do. Currently all i have done is unlocked the device.
ADB says my device is there. Threw cmd i can't get it to fastboot using adb reboot fastboot. all it does it reboot teh device, it wont go to bootloader. I do have bootloader unlocked. when i go and make my device go to bootloader manually i try to do the fastboot flash recovery recovery.img it starts to send the file then fails. unknown error. what am i doing wrong?
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
LordXombie said:
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
Click to expand...
Click to collapse
That's info that more people should have. The right usb cord can be difference between failure & success. I remember I went through 6 different usb cables jailbreaking my atv2.
For this phone, however, I just used the one that came with it. But I found the automated process to be sticky (not a tech term) it seemed to freeze a lot during the process.
I wound up plugging and replugging the usb when it froze.
It rooted my phone, installed twrp but needed to flash jmz kernel manually. The root tool works though. And to be honest, until I read this I didn't even think that a different cable might fix those issues in the automated process.
The other night for fun I rooted an old kindle hd and I needed to unplug and replug to get that to work. I was using the same cable that came with HTC desire.
***Anyone ever use a fastboot cable? Apparently u need one to install a 2nd boot loader on kindle hd and I'm wondering if that type of cable would resolve issues like this? That's a question not a go ahead to try it. I know very little about that and don't know if it could possibly cause more serious issues. They're cheap on eBay and I'm getting one for the kfhd.

need help/possible adb transfer-lost all and no easy transfer mode.

best all around screw up here.
need to put everything back on. twrp didn't accept the remount. i am able to put recovery/boot.imgs on. don't know what to do about rom, how would i go about putting one back on...
sd card no reading on computer. can't even plug in to computer and be recognized.
only got recovery mode and the fastboot mode going on here.
i did read about adb file transfer, need help.
its possible to even flash the zips from putr using adb terminal i read. but not understanding. they aren't giving clear enough instructions. can someone help or just say the phone is scrwedd.
yes, i know, i screwed prolly shouldn't have done this on my own. LOL
Close please
tdiamndz said:
best all around screw up here.
need to put everything back on. twrp didn't accept the remount. i am able to put recovery/boot.imgs on. don't know what to do about rom, how would i go about putting one back on...
sd card no reading on computer. can't even plug in to computer and be recognized.
only got recovery mode and the fastboot mode going on here.
i did read about adb file transfer, need help.
its possible to even flash the zips from putr using adb terminal i read. but not understanding. they aren't giving clear enough instructions. can someone help or just say the phone is scrwedd.
yes, i know, i screwed prolly shouldn't have done this on my own. LOL
Click to expand...
Click to collapse
edit:
FIXED with sideload. my drivers doesn't recognize the phone half the time. i got lucky and it did for 15 min my surnia was recognzied by my puter while i install stock. now back to upgrading/dating to what i had before. Just got to remember not to delete certain things. Lesson learned. TY.

Categories

Resources