Database Users

[Q] Botched UniversalAndroot Attempt - Am I screwed?

(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks

Try the 2.1 downgrade in my sig below.

Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!

Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?

Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?

It's the ADB drivers, what OS are you using?

I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!

HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.

Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?

HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player

Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?

HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en

Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro

[Q] Duth(netherlands) G1 Cant Root

T-mobile G1
Firmware version 1.6
Baseband Version 62.50S.20.17U_2.22.19.26I
Kernel Version 2.6.29-00479-g3c7df37
[email protected] #19
Build Number DRC92
Hi guys ,new in here.
I have a T-mobile G1 that i Bought From Netherlands . I wanted to root and upgrade it into cyanogen but i had to downgrade it first into 1.5 or 1.0 . i tried many links and guides but i always get the 00028002 error and then the rainbow screen with the Serial0 error. many had the same problem but no clue ... Any Ideas??? i am 100% sure that the format of my SD is FAT32 but not sure about the file i download. i tried many.I cant even install the original SPL.
Thanks in advance!
on the Rainbow screen it shows these for me :
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.2

i have same problem

Can somebody pleas help us? of is a way or not , because is stressfull to waith for a message

What is easier than trying to downgrad is useing exploid exploit
Here is a draft of the steps:
http://forum.xda-developers.com/wiki/index.php?title=User:Ezterry/G1_1.6_To_Custom_Firmware
I made it in a rush so clean if need be.. but don't completely re-write if you want to do that post elsewhere.
As for the problem with downgrading is the files are only intended for US/UK dreams and you don't have one of those..
however my steps above are probably also safer for those with said dreams.. since it tries to avoid the brick potential with dangerSPL

Now i have been trying that link, but i cant go forward from step 3
run the following adb commands:
* adb push exploid /sqlite_stmt_journals/exploid
* adb push flash_image /sqlite_stmt_journals/flash_image
* adb push recovery-RA-dream-v1.7.0-cyan.img /data/local/recovery-RA-dream-v1.7.0-cyan.img
* adb push spl_1_33_2003.zip /sdcard/spl_1_33_2003.zip
* adb shell chmod 755 /sqlite_stmt_journals/exploid /sqlite_stmt_journals/flash_image
* adb shell /sqlite_stmt_journals/exploid

red_net0 said:
Now i have been trying that link, but i cant go forward from step 3
Click to expand...
Click to collapse
You run them from your computers command line..
Is there an error?

IT dosnt work and yes i have that line from cmd on my computer

red_net0 said:
IT dosnt work and yes i have that line from cmd on my computer
Click to expand...
Click to collapse
Unless you give details I'm not sure how you expect anyone to help
"It doesn't work" could mean:
1) adb/fastboot isn't properly installed on your computer
2) you are not running adb from the directory with the files
3) you are making a typo in the command line (or I made a typo in the commands in that document.. unlikely but not impossible)
4) phone doesn't have USB debugging enabled or is not plugged into the computer
5) Your USB port on the phone is fired.

Ok i think the first adb running and the 2cond I think? How can i running that adb ?

red_net0 said:
Ok i think the first adb running and the 2cond I think? How can i running that adb ?
Click to expand...
Click to collapse
Try either the xda thread for adb/fastboot/sdk or the adp1 developer site
wiki page said:
[size=+2]Install ADB/Fastboot[/size]
For this to work I expect that you have adb/fastboot installed on your computer and understand that adb/fastboot commands are entered into your computer; not the phone
The XDA thread on setting this up is: http://forum.xda-developers.com/showthread.php?t=532719 Otherwise additional information is on the htc adp site: http://developer.htc.com/adp.html#s2
Click to expand...
Click to collapse
Many windows users find it easiest to put the files in the tools directory with adb. That said I'm primarily OSX and set up the path to allow me to access the commands anywhere.

I have been trying to install adb but i dont have the SDK Setup.exe file!

2cond thing that i see is
that
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
I dont have a rooted HTC Dream

That line lies; adb is used by developers on non rooted devices all the time..
the setup is the windows drivers..
Questions about adb *if* posted in the adb thread will be read by many more windows users that may be able to help.
You don't need to pm if you are asking the question in this thread.

I thing
I have the problem that i cant downgrade i have been 1 month trying to downgrade my g1 no lukky!:S

Try downgrading to RC7.....instead of RC29.
I had DRC93 (Dutch G1) and I followed the follwing link step by step
http://forum.xda-developers.com/showthread.php?t=727688
remember to use RC7
.....mine is working perfectly

[Q] root problem "device not found"

Hello ..
Sits and try to root my legend, but can not really get it to succeed. Coming to Step 2
What it says
* Error device not find *
* Error device not find *
And so it will not rise further
Someone who knows how I fixer this problem?
/ Ns_

Seems like you don't have an ADB-Driver for your Legend.
do you have HTC Sync installed? The ADB-Driver is contained in that Utility

just tryed with Htc sync installed, and i says the same!

Legend Root Step 2
Pushing required files to device...
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found

just tryed to downgrade it... That also fails.
when i Run the RUU it says Waiting for bootloader, and times out. :S

[Q] Troubles with ADB on Windows XP SP3. Help.

Hi,
I have a Windows XP SP3 (i386) that just won't let me use ADB. It doesn't work in ways I will describe shortly, and it never worked, on none of the ROMs I had. I had four roms in total in the past 3 weeks: Rooted original 2.1, non rooted JPM, rooted Kyrillos 3.0 and now I run rooted Lestatious 2.0 Build 1.2.6, akin' to go for 1.7.0.
I am primarily a Linux user (fedora 14 x86_64), and adb works fine for me there. As does ADB over WiFi (both Linux and Windows). For all my needs so far, Linux was enough, ODIN worked from the start, so I never bothered to find what's wrong with the Windows' adb.
But trying out Lestatious, I now have the need to update the rom using Windows, and it wouldn't be bad at all to use some other already prepared scripts for Windows I stumple upon on the forums.
As far as drivers go, I have the freshest Kies installed. I have the necessary Android SDK parts installed. Debugging mode is selected on the phone.
Actually, I am at the point where I have the WHOLE Android SDK installed, and have spent way more time on researching and googling and debugging than I would've needed to convert Lestatious' batch scripts into bash ones. And almost literally, pulling my hair out.
I'm no total noob when it comes to flashing/hacking/rooting/modding devices. I've even done my own Pandora battery switch mod for PSP for God's sake!
But this just stumps me....completely.
All this behaves the same, no matter what combination of starting and killing adb I do, pulling cable out, disabling debugging mode, plugging in, unplugging, enabling debugging, plugging in, etc. It also makes no difference whether I use Android SDK adb or, let's say, Lestatious' supplied adb.
Also note that I have both tools and platform-tools folder in my PATH variable.
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
myserialno;-) device
C:\>adb remount
error: protocol fault (status 72 65 6d 6f?!)
C:\>adb shell df
error: protocol fault (status 2f 64 65 76?!)
C:\>adb shell ls
error: protocol fault (status 73 71 6c 69?!)
C:\>adb root
error: protocol fault (status 61 64 62 64?!)
Although it does give me protocol fault, the device does disconnect/reconnect:
Code:
C:\>adb usb
error: protocol fault (status 72 65 73 74?!)
Phone does reboot:
Code:
C:\>adb reboot
error: protocol fault (no status)
Have to break this one, because it never returns:
Code:
C:\>adb shell
^C
Any help will be greatly appreciated.
Thank you.

can i post reply?

[email protected] said:
can i post reply?
Click to expand...
Click to collapse
STOP! NOW!
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO

Sounds like a Samsung USB driver issue to me. Make sure you got the right ones. Are you using 64-bit or 32-bit windows?

Thom47 said:
Sounds like a Samsung USB driver issue to me. Make sure you got the right ones. Are you using 64-bit or 32-bit windows?
Click to expand...
Click to collapse
Thanks for taking interest in my problem.
I'm using 32-bit Windows XP (with SP3).
I did not fiddle with any drivers, I would if I found any . The drivers were installed with the Samsung Kies software. I also tried uninstalling and installing Kies. The Kies is version Kies_2.0.0.11032_12_9.exe downloaded from UK Samsung Support for Galaxy i5800.
Just to be sure, and because I have access to two completely identical machines (yes, hardware and software is the same, except the Android part).
On one machine I have the complete Android SDK, earlier version of Kies (updated yesterday to the latest version).
On the second machine I have only the latest Kies (never updated, installed it this morning). And no SDK, just Lestatious' adb.exe and AdbWinApi.dll.
The behavior stays the same.
Thanks

Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.

Thom47 said:
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Click to expand...
Click to collapse
Thanks. I will try it as soon as I get home from work.
Thanks again.

Thom47 said:
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Click to expand...
Click to collapse
So, I used usbdeview to uninstall the device first. Then I uninstalled Samsung Kies. And finally Samsung USB drivers that get installed with Kies automatically.
I rebooted, just to be sure. Installed the drivers linked in Thom47's post, and rebooted again.
I ran the adb start-server. Connected my device (which was correctly recognized, just as before). The end result is the same. Although status gives a bit different numbers:
Code:
C:\Documents and Settings\Miki>adb shell ls
error: protocol fault (status 1b 5b 31 3b?!)
C:\Documents and Settings\Miki>adb shell
^C
But looking at the adb client source code, I see that the numbers represent 4 Bytes of data read from some file descriptor when getting adb status. It's a bit too late to follow up what file descriptor, but as readx (used to transfer the first 4B from file descriptor into buffer) is sometimes used for reading device drivers because of its portability, this definitely points a finger to some sort of driver issue.
Just thought that it might help to list connected devices when the phone is plugged in (debugging mode, of course):
ADB Interface->Samsung Android Composite ADB Interface
Disk Drives->SAMSUNG GT-I5800 Card USB Device
Modems->Samsung Android USB Modem (is this supposed to be here?)
USB Controllers->SAMSUNG Android USB composite device
Click to expand...
Click to collapse
Update: I just quickly skimmed through the code to see what is the file descriptor, and it's actually just a socket connection to ADB port. So, if I understood it correctly, the first 4B read by readx are reply from the device (?!). Still could be driver related in my opinion.
Thanks

Right, well that's where my knowledge on linux and stuff ends, so I think you should make a new thread to some general forum, since this might not be related to our phone only.

Will do. Thanks for the help.
--
Sent from my GT-I5800

Can't get Hello World running

Hi Guys,
I'm trying to start some Android development however I've run into a couple of problems during Dev environment set up. I've been following the adt-bundle install instructions as I opted to use the ADT bundle.
This first problem is that the Android Virtual Device Manager will not run. I get a message saying "Failed to execute tools\android.bat The system cannot find the specified file". No idea what to do about that one.
The second is that I cannot run my app. I'm trying to run it on my phone (HTC Desire C) how I keep getting the message :
Code:
[2013-07-13 07:33:37 - MyFirstApp] ------------------------------
[2013-07-13 07:33:37 - MyFirstApp] Android Launch!
[2013-07-13 07:33:37 - MyFirstApp] The connection to adb is down, and a severe error has occured.
[2013-07-13 07:33:37 - MyFirstApp] You must restart adb and Eclipse.
[2013-07-13 07:33:37 - MyFirstApp] Please ensure that adb is correctly located at 'C:\Program Files\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\adb.exe' and can be executed.
I've tried resetting adb via command prompt using adb kill-server and then restarting using adb devices and checking that a device is connected however it doesn't seem to make a difference.
I've also tried connecting my N7 tablet up and install the usb drives in the sdk and I get the same errors
It's incredibly frustrating and I would really appreciate some guidance.
Thanks in advance
Samishal

[2013-07-13 07:33:37 - MyFirstApp] Please ensure that adb is correctly located at 'C:\Program Files\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\adb.exe' and can be executed.
is your adb there? and is it executable? (are you running as admin?)

I have also got same error AVD error.. ihad solved it by opening this file "C:\android\sdk\tools\android.bat" and updating its component..