I'm asking coz I failed to create a gold card more than 10th times and I'm sure I followed the steps carefully buy no Luke .
What's going wrong with the goldcard like?
Have you tried using another SD?
Yes you need it.
I've a NoBrand Legend and tryed, with no success, to root it until I've created in the right way the GoldCard.
If yours does'nt work change the sd!!!
Changing mine I did goal!!!!
this is somewhat relevant,
i have an unbranded generic that was failing so ill try with a gold card so ty for that but as a side note i assume that OTA updates will work again just buy simply flashing the phone with stock generic firmware correct ?
sorry for not replying sooner my problem is this :
C:\sdk\tools>adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
adb server is out of date. killing...
* daemon started successfully *
/sys/class/mmc_host/mmc1/mmc1:*/cid: No such file or directory
quattro_rs said:
sorry for not replying sooner my problem is this :
C:\sdk\tools>adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
adb server is out of date. killing...
* daemon started successfully *
/sys/class/mmc_host/mmc1/mmc1:*/cid: No such file or directory
Click to expand...
Click to collapse
Try this! C:\sdk\tools>adb shell cat/sys/class/mmc_host/mmc0/mmc0:*/cid
it finally worked thanks man .
now i have a new problem, after finishing this step :
# Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
# In the terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
i get a red triangle on the device screen and on the command prompt i get :
Erasing cache and rebooting in RUU mode...
< waiting for device >
and nothing happens !!
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?
Hello, I recently got Ubuntu installed on my computer. I got the Android SDK set up on it, but I cannot get adb shell to work, everytime I try it this happens:
[email protected]:~$ adb shell
* daemon not running. starting it now *
* daemon started successfully *
error: insufficient permissions for device
Click to expand...
Click to collapse
This never used to happen on windows, does anyone have any idea on how to fix it?
Have you tried running it as root? It tells you in the error message that you've got insufficient permissions...
Sent from my Droid using XDA App
Hi everyone,
I am using a white Galaxy Note w/ GB 2.3.6 (KK2 kernel).
I've read in a different forum that users are able to use the exploit for KK1 works as well for KK2/KK3/KK4.
I downloaded zergRush KK1 (root + CWM), and ran the file: not-rooted-yet.bat
A CMD window pops up and the process halts after it says: * daemon started successfully *.
I have the ADB drivers installed, and both "USB debugging" and "Unknown sources" ticked.
I ran the BAT file whilst the phone was in Charge mode only.
I don't know why the rooting process + installation of CWM keeps on failing.
Please help!!
Thanks.
EDIT:
This is how CMD looks like:
CONFIRM ALL THE ABOVE THEN
Press any key to continue...
--- STARTING ---
--- WAITING FOR DEVICE ---
* daemon not running. starting it now *
* daemon started successfully *
(the process completely halts here)
I rooted my device using ODIN
entropy96 said:
I rooted my device using ODIN
Click to expand...
Click to collapse
If you rooted with a kernel you probably initiated the binary flash counter which could give you trouble regarding warranty issues
---------- Post added at 07:24 AM ---------- Previous post was at 07:17 AM ----------
entropy96 said:
Hi everyone,
I am using a white Galaxy Note w/ GB 2.3.6 (KK2 kernel).
I've read in a different forum that users are able to use the exploit for KK1 works as well for KK2/KK3/KK4.
I downloaded zergRush KK1 (root + CWM), and ran the file: not-rooted-yet.bat
A CMD window pops up and the process halts after it says: * daemon started successfully *.
I have the ADB drivers installed, and both "USB debugging" and "Unknown sources" ticked.
I ran the BAT file whilst the phone was in Charge mode only.
I don't know why the rooting process + installation of CWM keeps on failing.
Please help!!
Thanks.
EDIT:
This is how CMD looks like:
CONFIRM ALL THE ABOVE THEN
Press any key to continue...
--- STARTING ---
--- WAITING FOR DEVICE ---
* daemon not running. starting it now *
* daemon started successfully *
(the process completely halts here)
Click to expand...
Click to collapse
I think KK2 is not supported, at least not by CF Root for cwm. You can root however with DoomLORD http://forum.xda-developers.com/showthread.php?t=1329360. You`ll have root and busybox but no cwm. Download rom manager from market and flash recovery (cwm) with that. Good luck If you have connection problems try another usb port.
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.