Database Info

Fatal error on HTC 710

HI,
I have a fatal error on my HTC S710. After switching the phone on I get 3 horizontal bars on top a red bar with VOX ONBL 1.34.000 in the middle a green bar with SPL 1.34.000 and the a blue bar with CPLD -04
I have tried to upgrade to 1.34 but no success
After about 30 hard reboots I can get the phone working for 5min and then it hangs again and the 3 bars pop up.
So I think I need to completely reinstall WM 6 but can't find the file on this site?
And what tool to use the flash the rom??
Thx,

Go to the HTC site and download the official ROM! http://www.htc.com/support/support.htm it's in the e-club section and is only for HTC devices (not SPV's etc).
BTW google "S710 rom" reveals a lot of results. You could try that first.

Tho,
thanks for your reply. Have Downloaded and upgraded the ROM from HTC E-club. However now the phone hangs completely can't if get it to start up normally. Tried Hard reboots soft reboots even pressing the menu buttons above the 1 and 3 key and then pressing the power button.

Where does it hang when booting? If you're able to get to at least the black HTC screen, then the ROM was written however might have bad blocks in memory.
Try a hard reset with SIM and SD out of the device, hold the two soft keys and press power, hit the Green call start button when it prompts you - leave the phone for at least 15 minutes to be on the safe side. Then flash this; ftp://xda:[email protected]_Vox_ARA_1.27.415.4_4.1.13.47_02.98.90.exe
and let us know what happens.

thx for the info h4waii.
However a hard reset does work. Acourding to the HTC technical helpdesk the boot loader is stuck, so it cant read the operating system files to boot the phone in to windows.
Also the Active Sync doens't reconises the phone any more.

H4waii,
I can get into the bootloader. I read on an other post that you said "If the ROM is corrupt, this is your best way of "recovering" your phone, if the ROM was flashed properly, after getting into the bootloader, run ruurun 0 and ResetDevice to boot it back into OS."
But how do run that ruurun. Still can't sync it with my laptop??

You need a terminal emulator, you can use MTTY. It's attached in the Vox USPL sticky and I will get you the link for the boot loader recognized commands.
EDIT: Here is a link to the USPL sticky that has MTTY attached: http://forum.xda-developers.com/showthread.php?t=330909
and here is a link to the the Wiki for Hermes boot loader, many of the commands will work on the Vox: http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
There is also a tool for the Universal that resets the DoC instructions, you might want to either give that a try or look at the command 'task 28 55aa'.
You do this at your own risk also, just wanted to throw that out there.

Something can be useful for hacking rc30

1- Plug your phone to PC (with debugg mode)
2- Power off
3- Home + Power
You will see : PC find G1 device (you can see flash disk icon in my computer), but we can use "adb devices" to find G1. I think HTC has one software and driver to mount G1 in this mode. If we can find this software, we can flash any G1 device.

sounds interesting...

Hmm..
my g1 doesn't show under ADB here - are you running JF's "edited" rc30?
I can see the storage coming up if I pull a dmesg when the handset has booted into the recovery app, but can't mount things.

almost sounds like fantasy
I think what your thinking of the way the HTC loader was used to flash WM roms.
I don't know for sure if any of the htc devices that are close enough to the dream, and those loaders were made for flashing WM devices, the memory locations of the flash on a g1 are completely different , in time who knows, there has been a DEV phone and the same thing your refering to (bootloader) and it will flash any thing you ask it to, just no way to get this open dev bootloader on a ota RC30 G1 as of yet I think this will be how its broken but who knows, maybe somebody could recode an htc win xp flasher app for WM....
Bhang

HTC doesn't rely on the recovery console. If they are going to reflash a G1 they will use the bootloader in conjunction with a signed DREAIMG.NBH file.

Dosent adb shell allow root access to the phone via your computer regardless of whether or not its ota rc30? or am i miss-undrstanding?

I just get a display of a phone and a triangle with an ! in the middle when i power+home... what's up with that?

debro012 said:
Dosent adb shell allow root access to the phone via your computer regardless of whether or not its ota rc30? or am i miss-undrstanding?
Click to expand...
Click to collapse
Only if you have Mod RC30 v1.2 installed.
debro012 said:
I just get a display of a phone and a triangle with an ! in the middle when i power+home... what's up with that?
Click to expand...
Click to collapse
That's what the recovery tool looks like. Press Alt+L to bring up text.

Problems rooting.

Hi im trying to root my Sapphire... Can't get adb to work or fastboot? When i fillow any instructions (even from google android forums) i try to run fastboot and it opens a cmd window then immediately closes? i read that sometimes windows can be too corrupt so i got a new hard drive, Reinstalled windows and still cant do it?
All i want to do is root my magic to install apps to sd PLEASE HELP!

lol
you need to open cmd and change directory to the tools folder which contains the adb and fastboot files and proceed from there entering all adb and fastboot commands within command prompt as it calls the program to execute eg adb pull

http://www.karrderized.com/romguide/
Try referring to that - step 8 explains using cmd to open a command prompt so you can run fastboot. It's a guide for installing a new ROM, but the same principles apply.

Hey guys,
I am regular on the Dream board and I will be getting a MyTouch 3G. Are you able to root this phone as of yet? If so, can someone point me in the right direction for a tutorial?

Like i mentioned T-Mobile forums as of right now the MyTouch 3G with Google is not rootable yet. No one has yet found away around the locks on the device yet.

TheArtiszan said:
Like i mentioned T-Mobile forums as of right now the MyTouch 3G with Google is not rootable yet. No one has yet found away around the locks on the device yet.
Click to expand...
Click to collapse
That's whatI thought, but then I saw this thread and it seemed like there was a way.

isnt the mytouch the htc magic just renamed for outside restricted carrier sales? htc always do this! you can always check by powering on the device by holding power and back button and see what info comes up, if its the same i imagine the process would be the same too, i think its just because the mytouch is a recent release that no one has been round to trying it imho

Thanks for the replies but i dont know much about cmd/console commands. Im not very techy on pc's anything i know i taught myself. If i knew how to start the console with the right directory id be fine.
http://androidcommunity.com/forums/f54/htc-magic-root-access-17456/
This is walkthrough im trying to use

in windows use START->RUN (or press <WINKEY>+R), type cmd and hit enter.
this opens the command window.
Using the command "cd" you can change directories.

Right i can get device info but when i goto fastboot boot recovery-new.img it just says cannot load recovery-new.img?
Everything i need is in the right folder, Ive changed directories (cd D:\Android) in my case and still nothing!
Im sure there are others out there like me who'd like some help

DONE.....for aol the noobs (like me) all i did was type first part of command eg. fastboot boot then copied and pasted the file i wanted

Turn your phone off, hold back while you turn phone back on, you should see a screen with 3 skateboarders.
Reply the text you see on that screen.
This will tell us if your phone is possible to root yet, and if so how.

i was a bit hasty it fastbooted
Sapphire PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAPP100000)
CPLD-10
RADIO-2.22.19.261
Apr 9 2009 23:30:40
FASTBOOT USB

now its different since i booted HSPL it says ENG S-OFF G instead of SHIP S-ON G

MyTouch rebooting loop

Currently my phone is unusable. It displays the green screen with the myTouch logo for a minute or so then goes black and starts over. I can get to recovery mode, and I tried flashing the only copy of CM I have avaliable from there, which is 4.2.3, but it got stuck at the step "Deleting files..." Here's how I got to this point:
I wanted to get Navigation, but every time I tried to install it from market it said something along the lines of "The package is not signed correctly." I got the attached zip from this wave (You need a Google Wave account to view. Currently invite only.) Here's some relevant bits from the wave:
Here. I'll attach the zip file. Just install it like you would a build. If you don't see it afterwards, I hear you have to install Google Voice to make it work.
So i just go into recovery and install any zip for that?
Yup, exactly. Only downside is... with every update to Cyanogen's mod, you need to reupload the navigation.
Click to expand...
Click to collapse
I was on the latest CM at the time (which I think is still the latest) and this was posted before Nav was in the Market. I installed this zip and I had Nav, but there was an even newer version of Maps in Market, and I installed that and it worked this time. Only thing was, this zip somehow changed my version number of CM, and CM Updater said I was three updates behind again. I figured I'd go ahead and try running the latest CM zip and see if Maps still worked, and it did. But after a while, it randomly rebooted on me. This kept happening for a while, but it was only every couple days, so I figured I'd see if it was still doing it after the next CM update and if so I'd post about it then.
Just today a new version of Google Maps was in Market, and I downloaded it and installed it and played with it for a bit. Then later the system rebooted and I am where I am now. Just keeps rebooting after the myTouch screen.
My recovery image is just the normal Android one, I think. (It says Android system recovery <2> at the top and Build: CyanogenMod v1.4 + JF at the bottom, but it's always said that even before Nav and working fine on 4.2.7.)
Other stuff that ran/might have ran in background: Google Voice, Google Listen, Wifi power widget... There's probably more that I'm not thinking of right now. Will add later if I do.
My recovery image doesn't let me mount my card and I don't have an SDHC reader, but obviously I can get one, since it will probably be needed to fix this.
Only reason I'm not completely freaked out right now is anti-anxiety meds. Please tell me it's not a brick, because I'm not supposed to take any more today.

It's not bricked. Do you know how to fastboot? Download Amon_RA's recovery 1.5.1G and from there fastboot it and replace your current G1 recovery. This rom allows you to mount your SD card, and from there you can put in a new rom on your phone and flash it again.

I did some searching on fastboot, and I got to the fastboot screen on my phone, but I don't understand what to do on my computer's side. I'm running XP SP3. Edit: I also have another partition running OpenSUSE, but I haven't used it in forever and I'm not very good with it. XP options are preferable.

Okay, I wanna make sure I got this right before I continue. I got the Android SDK from Google, and I got the file recovery-RA-sapphire-v1.5.1G.img from this thread. So from a command prompt in the tools directory of the SDK, I should run "fastboot update recovery-RA-sapphire-v1.5.1G.img"?
Edit: Nevermind, I want the flash command like it says in the thread I linked to. Duh.
Edit: So I did fastboot flash recovery recovery-RA-sapphire-v1.5.1G.img and it just said < waiting for device > even when I clicked Fastboot USB on the phone. I keep getting the add hardware wizard and ignoring it. Am I supposed to install a driver for this or something?

Sorry to repost with nothing new to say, but I've searched and looked through other threads and I just can't figure this out. I really need my phone to work.
I hold back and push power on the phone, a white screen comes up with Sapphire pvt 32B... Fastboot. I plug it in to my USB cable and it changes to Fastboot USB. I get a found new hardware wizard and just hit esc.
I type "fastboot flash recovery recovery-RA-sapphire-v1.5.1G.img" in command prompt and it just says "< waiting for device >" forever.
I can push the trackball and the screen goes black for a second and then comes back with the exact same thing. I get the wizard again.
What am I missing?
Edit: Okay, I found the driver and now I get "sending 'recovery' (4050 KB)... FAILED (remote: not allow)"

jomasecu said:
Sorry to repost with nothing new to say, but I've searched and looked through other threads and I just can't figure this out. I really need my phone to work.
I hold back and push power on the phone, a white screen comes up with Sapphire pvt 32B... Fastboot. I plug it in to my USB cable and it changes to Fastboot USB. I get a found new hardware wizard and just hit esc.
I type "fastboot flash recovery recovery-RA-sapphire-v1.5.1G.img" in command prompt and it just says "< waiting for device >" forever.
I can push the trackball and the screen goes black for a second and then comes back with the exact same thing. I get the wizard again.
What am I missing?
Edit: Okay, I found the driver and now I get "sending 'recovery' (4050 KB)... FAILED (remote: not allow)"
Click to expand...
Click to collapse
what spl do you have? does it allow fastboot?

I don't know.

Tried to apply a rescue OTA on a Pixel 2 stuck on reboot screen, and it didn't work

I experienced the exact same problem stated here (sorry can't link due to being a newb): forums.androidcentral.com/google-pixel-2-pixel-2-xl/872399-pixel-2-xl-stuck-boot-screen.html
I had maxed out the storage capacity to my device, the phone started acting funky and then it forced a reboot on its own. During the reboot, it got stuck at the 'G' logo with white background and it never got past it.
I tried to apply a Rescue OTA of my Pixel 2 following guide: drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view (my build # OPM1.171019.019) but I still get stuck at the Google 'G' logo with white background on the reboot after the adb sideload step. I am completely lost on what to do next. I am new to Android and my Google skills are being tested so I appreciate any guidance.

I assume you have everything important backed up. (If you don't, you will after this.)
(As for a computer not booting because there was too much on it, ask anyone familiar with the AS/400. You can't IPL [boot] if there's too much running when you shut down.)
Try https://developers.google.com/android/images. Download 019 if you want to stay on the February update or 021 if you want to end up updated to March. Unnzip the file to some handy folder on the PC. Open the flash-all.bat file (in a text editor), go to the last "fastboot" line (it's line 23 if your editor gives you line numbers) and remove the "-w " part (remove the dash, the w and either the leading or the trailing space). Save the file. Drop to a command prompt. Boot the phone to recovery. Connect it to the PC. Run the flash-all file. It should restore the phone.
If that fails, put back the -w (fastboot -w update image-walleye-opm1.171019.019.zip 0r fastboot -w update image-walleye-opm1.171019.021.zip), reboot to fastboot again and try. (This will wipe all your stuff, which is why everything important should always be backed up. That, and a truck driving over the phone you just dropped.)
If the full flash fails, contact Google. My first one was in even worse shape - the only things I could do from fastboot were get the barcodes, power off or restart fastboot. They stand behind their phones. They replaced mine. (You can send yours back and wait for the new one or get the new one and use the same carton to send the old one back, which is what I chose [if the postal service messes up - and I've seen it happen - it could be a while before getting a new phone]. They email you verifying the conversation and there are 2 attachments - an RMA [Return Material Authorization] that you include in the box and a shipping label. Cover the entire shipping label with tape, just in case it rains on the box. (It's USPS if you're in the US, so just stick it in your mailbox.)
And back up anything you don't want to lose from now on.

Hello,
I have the exact same problem. Thing is, my Pixel ( first edition ) is not recognized by any device ( Mac/Windows ) when I plug it in. So I can't adb / fast boot it at all. Any suggestions? Thanks

DagiDashi said:
Hello,
I have the exact same problem. Thing is, my Pixel ( first edition ) is not recognized by any device ( Mac/Windows ) when I plug it in. So I can't adb / fast boot it at all. Any suggestions? Thanks
Click to expand...
Click to collapse
Do you have the proper drivers installed? In usb options, have you selected file transfer, as it defaults to charging when connected? Android debugging ticked? As long as all of these are "yes", you should be good as far as ADB.
For fastboot, hold power+volume down to get into bootloader mode. Connect your phone and type 'fastboot devices'. If you see the s/n of your phone, you're good to go.

Any help one this topic? I am having the same issue and there is no BAT file for newer builds, I am, trying to install anything past August 19th 2019 because that is the current version the pixel is stuck on