What am I doing wrong? - EVO 4G General

Got S-Off, Superuser is installed, and AmonRa is installed. When I try to load the Evo-Deck the ROM and Gapps load with no errors. When I try to start up my phone it does the white HTC screen then goes to a black screen that says ANDROID with flashing blue letters and just sits.
I've been searching around and can't find anything, but blackscreen and android aren't exactly narrow search words on here. Is that android screen Evo-Deck trying to load or is that some kind of generic android screen that pops up when there's not ROM loaded?

Think I got it figured out ... I wasn't wiping EVERYTHING. Apparently something I was missing was causing problems. I got EVO-Deck 1.0 to just boot. Hopefully I can get the newer version to work now.

For future reference, check my sig for VRsuperwipe. Flash that like you would an app, and it wipes everything.

Related

Error updating to Open Touch 4.0 Biggie

I recently flashed to Open Touch 3.0 Biggie with no problems. I downloaded the new 4.0 and followed the steps exactly, just like 3.0. When I run flash center, everything goes normal, just like it did with 3.0....at 75%, screen goes white, and the ruu loads then. ...but, when it tries to verify the phone, it comes up with a data connection error, and the program stops. Should I flash back to the original stock tmobile rom, then try to update to 4.0? Is there something I'm doing wrong?? Thanks in advance.
dougstoner said:
I recently flashed to Open Touch 3.0 Biggie with no problems. I downloaded the new 4.0 and followed the steps exactly, just like 3.0. When I run flash center, everything goes normal, just like it did with 3.0....at 75%, screen goes white, and the ruu loads then. ...but, when it tries to verify the phone, it comes up with a data connection error, and the program stops. Should I flash back to the original stock tmobile rom, then try to update to 4.0? Is there something I'm doing wrong?? Thanks in advance.
Click to expand...
Click to collapse
yea its best to do that less problems
also you go into usb to pc from the connections tab and check the checkbox
Well, I noticed when I ran the flash center program, (when the screen goes white), and the ruu program starts up, I noticed the phone loses its sync, so I got the phone to sync up again, and now it verifies I have 3.0 and shows the version 4 as what it's going to update to. Then it actually starts with the update, I get a status bar on the phone, and then it says file is corrupt (around 10%) and quits.
If it would help to flash to original rom, how do I do that? Maybe the file I downloaded is corrupt? (nhb file)....
I didn't hard spl when I went from the original rom to open touch v3.0. Everything loaded fine. I was doing a LOT of reading, and I was under the impression you didn't have to hard spl to load open touch 4. I see the procedure on hard spl, (basically run the 3 files, run the ruu, etc..), so should I do this first, and then try to load v4.0???
dougstoner said:
Well, I noticed when I ran the flash center program, (when the screen goes white), and the ruu program starts up, I noticed the phone loses its sync, so I got the phone to sync up again, and now it verifies I have 3.0 and shows the version 4 as what it's going to update to. Then it actually starts with the update, I get a status bar on the phone, and then it says file is corrupt (around 10%) and quits.
If it would help to flash to original rom, how do I do that? Maybe the file I downloaded is corrupt? (nhb file)....
I didn't hard spl when I went from the original rom to open touch v3.0. Everything loaded fine. I was doing a LOT of reading, and I was under the impression you didn't have to hard spl to load open touch 4. I see the procedure on hard spl, (basically run the 3 files, run the ruu, etc..), so should I do this first, and then try to load v4.0???
Click to expand...
Click to collapse
that is the older method i have the newer method where it is done automatically but you can try just do a search for uspl or if u can wait till 9pm est ill send it to you with detailed instructions
I'll do some searching, but if you could send it to me, that would be great man. Thanks.

Force Closes?

Hi, I have a MT3G and a G1 before that. I have experience flashing roms and other stuff. I have had the MT3G for sometime and noticed that I can't flash roms anymore since I get FC errors after the boot up. Even the latest CM mods don't let me sign in, and I have to skip the initial sign in to find the market FCing every time I open it. This is getting really annoying, and some roms won't even get past the boot screen without a fix uid mismatches which allows me to boot up, but still gives me some errors, like no android keyboard to sign in or FC on settings or other important things. Any help would be appreciated!
are you wiping the phone completely... list things in your signature like what recovery image what rom you are using at the time are you using a different SPL the community needs to know these kind of things to help you out...
I had this same problem when trying to flash Cyanogens latest.
Go ahead and find version 4.2.1.8 or 4.2.1.9
Wipe everything, then flash one of those.
Everything should work, I would advise not to upgrade to 4.2.12.2 or whatever because I experience home not responding upon reboot. Have to wait a couple times, then it's ok.
Well, I would put it in my sig, but for some reason, I can't edit it. Here's what I've got.
I had the SPL 1.33.2005 then recently 1.33.2009.
I've had problems like this on my G1 as well and never really understood the problem. I have the latest RA v1.5.2 recovery.
I do perform a full wipe and have tried to follow what someone else posted about installing a fresh rom and to fix the apk uid mismatches and a command in terminal, although neither seem to last long. Sometimes I can wipe and do an install of any rom 10 times and still get FC on startup. I fix the apk uid mismatches in recovery to be able to get further, but will usually start to have problems in other settings and apps.
I have a general idea on what to do, and usually wipe the data and everything else about 2 times. I just don't know if it's something I'm doing that's causing this.
I just searched around for the differences of SPL's and read from Amon_RA that they aren't really different besides being able to allow certain roms to run. I'm wondering if the reason I can't run certain roms is because I don't have Haykuro's Death SPL? Is the Death SPL only .2005?

[SOLVED] 2.1 Rooting issue & GSM Hero (White screen, green htc logo, stuck)

[Solved]
Hi there.
I got hold of this second hand phone.
I dont think its been modified in any way yet.
Last night the phone asked me about doing a update. So i did.
After the green progress bar completed i got to a white screen containing a green htc logo. And its stuck there in a loop.
So... I cant turn my device on... whyyyy? :'(
All i can do is to get into the standard htc recovery.
And into the hboot. Some place there it says:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009,19:43:30
I have done a wipe and a hard reset. Still it get this white screen on death. (WSOD) Im sodding of to bed...
You now know that it doesnt have a nandroid backup, and that I cant connect the phone via a usb connection to pc. And I dont have any custom recovery installed.
Ive tried to recover from a offical rom with a update.zip copied with a card reader onto the sd. Ive tried a few. The recovery see's the file. But when i try to install it it says "Verification failed Installation aborted"
Ive tried the recovery-RA-hero-v1.7.0.1.img, but without a usb I cant figure out how. Is there a way around for installing RA with just a sd card?
Please, does anyone have a good solution here.
Or some helpfull info to point me in the right way.
Sincererly,
Thor
See these threads similar,... Should be easy to sort.
http://forum.xda-developers.com/showthread.php?t=786938
and http://forum.xda-developers.com/showthread.php?t=787483
Good morning
Thanks, ive been looking at that.
My Win7 pc wouldnt show the ADB Interface in manage devices.
Only thing that pops up is a disk drive called HTC Android Phone USB Device, USB Mass Storage Device and a USB Composite Device.
Im gonna try this on my windows xp machine later today.
Hope it finds my phone, if not... what can i do?
So you need to update drivers as per the link in those threads,... Have you done that already pal?
Sent from my HTC Hero using XDA App
Hi again
Yes, I followed every step on that RUU driver guide on my win 7. But the drivers doesnt pop up as they should.
So I cant install the correct drivers since it doesnt show.
Halfway solution!
I got a breakthrough.
1. Remove the battery and replace it.
2. Hold volume down/up and tap power button. (htc enters hboot)
3. Taps back (enters fastboot)
4. Connects USB Cable (fastboot changes to fastboot usb)
5. Computer finds device My HTC.
Then i run this:
_HTC Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
I got this from the htc pages. The software says i have ROM version 3.32.405.1
So i have a newer one installed then the one they have on web!?
I choose update on the software, now it tries to install 2.73.405.5
I got a half working usb connection now.
Fastboot restarted and changed to RUU USB.
Then i get a Error: 140 / 131 Bootloader version fail.
Can it be that the hard reset ive done messed up the bootloader version.
For me it looks like the phone is still in a new version ROM.
Anyone vise got anything to say about this?
Kind regards,
Thor
Aha,.... Ok, thats probs because the RUU you're using is older than the ROM already installed.
Try this one... RUU_Hero_HTC_WWE_3.32.405.1_R_Radio_63.18.55.06P_6 .35.15.11_release_signed.exe
That is the unbranded ROM,...
Wow
Suddenly everything klicked back into place!
Im past the white screen of death!
That RUU link was flawless for my device.
And the fastboot RUU USB installed everything.
Im back in business.
Much appericated m8
No problem. Now do us a favour and put [SOLVED] into your thread title. Thanks.
So...
Any suggestions on what i should do with it now?
Gotta root it i guess.
Then install recovery RA.
Any suggestions for a good rom to try?
Thanks again,
Thor
theres loads, but my suggestion would be villainrom 12 for a 2.1 sense rom, or froydvillain for a 2.2 rom
Ok
How do i know if i have a 2.1 sense rom or a 2.2 rom?
Or was that a dumb question from me, since you meant to install those?
Im kind of new, just left ye olde nokia behind
lol... Ok,... So you used the 3.32 RUU yeah? That is stock 2.1. If you used the other one, that is 1.5. Use BTDAGs guide in my sig to find out how to flash custom ROMs.
I also recommend Villain 12 for 2.1,... Or Froyd for 2.2. Depends if you like the SenseUI or not. Take a look at both in the Dev section.
Ok
Yes, I definitly want to have the Sense UI.
So then i wanna try out installing a villainrom 12 on a 2.1 sense rom.
Settings - Software Information now says:
Firmware version: 2.1-update1
Baseband version: 63.18.55.06PU_6.35.15.11
Kernel version: 2.6.29-063c4d24 [email protected] #1
Build number: 3.32.405.1 CL191507 release-keys
Software number: 3.32.405.1
This is what i have on it now.
I tried doing the phone software update again, when it asked me again.
Got the same error. So I did the usb install over again. All ok again.
Note: The update it tries out is 3.32.405.2 (5.87MB)
So... can i follow BTDAG's guide from here?
Or do i have to downgrade or update something first?
Guess i have to choose Superuser for Android 2.0~2.2 when i do the rooting with androot.
I got a problem in that guide when typing su in the terminal window.
I didnt get the "Super User Request Prompt" as it told about.
Ive now tried terminal from both usb and the terminal emulator.
WHen i try to do the SU or the flash_image recovery command i get permission denied!?
Without su rights i can do the flash_image recovery /sdcard/recovery.img command, since i need the su permissions.
Thanks again,
Thor
Hi again
I cant seem to get the SU rights i need.
Ive used universal nandroid for the rooting! (it tells its now ok)
But i cant flash in the custom recovery image.
Ive now tried a different approach:
1. Installing the ROM Manager and trying out ClockworkMod recovery(its installs ok)
2. Then I boot into recovery by holding the home(house) and power on, I get the white screen of htc death again and it goes into a black screen with a red triangle and a ! on it.
3. Then I release home and power on.
4. Presses down volume up and taps power on.
5. The hero boots into the standard recovery!?
(I think the way im starting up, are reflashing the recovery. am i right?)
Clockwork also have a "flash RA 1.7 recovery" option, ive tried that one too.
But with the same result...
Any one know about this?
Best regards,
Thor Elvin
Solution for life!
After a lot of surfing i found it!
This great tut worked for my device:
http://www.villainrom.co.uk/forum/s...o-Root-The-2.1-RUU-or-OTA-Update-For-The-Hero
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Great thanks to Pulser for a great tut.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!!
QUOTE=thorelvin;8284640]After a lot of surfing i found it!
This great tut worked for my device:
Pulser did...
I got a blue carebear in the background, and im making a big grin!
Now im rooted and backed up.
Edit: VillainROM12 installed 1
PEACE Y'ALL!!![/QUOTE]
Dude, nice that you got sorted. I have kids so Carebears are good to have around. Respect to Carebears, and at the same time it would be cool and revisit the forum and thank Pulser, else thank him here as Pulser_g2 (i think). He sort of wrote, reworked the tut originally from the cdma version here. Sorted me too going 2.1 to 2.2. I had shedloads of fun with roms in between but its only thanks to him.
I guess this could be classed as one of those "Circle of life" philosophy budhist type **** things cuz the answer was really where you started, but for me... its all about takin care of the Carebears....
For the record his contract ends around May so get your Hero fix requests in early...!
Soz Pulser... And massive thanks for the opening to a new dimension for my hero...

[Q] My phone freezes after 123456 GO GO GO!!! even after new installation...

Hi there,
Its been couple of months that my phone froze during web browsing. And when I pull the battery out and reinserted, the phone would go through the booting and either freezes right after 123456 go go go or it would freeze during the Android Logo loading. It would take me many battery pull outs and re inserts to get it back on. During this time, I ran Hyperdroid 2.3.4 on NAND with Mgldr 1.13.
yesterday I tried to reinstall the OS, i task29, reflash the radio to 2.15... and reinstalled mgldr1.13. I have chosen Typhoon's 2.3.5 NAND CWM. After the installation, the same problem of not being able to go past 1234 go go go persists. I tried to pull out the battery again and after few try i managed to log in to Android.
It seems, the longer the battery is out, the more effective it is in booting the OS. I am seriously concerned about HW issue. Please help me identify the problem.
Thanks
Did you try installing the stock Winmob ... then doing a clean android installation (complete with re-installing the HSPL)?
I am going to do that next. It seems, all freezing during normal operation happens when I am browsing on Edge (my phone is incompatible with 3G on the network i am).
Secondary note, when I remove battery and reinsert, not only I cant make it back to Android boot but also, when I load up Mgldr Recovery, the AD Recovery function also does not load beyond 12345...
I am going to load a WinMo 6.5 ROM probably NRG's and reinstall HSPL.
Parsian86 said:
I am going to do that next. It seems, all freezing during normal operation happens when I am browsing on Edge (my phone is incompatible with 3G on the network i am).
Secondary note, when I remove battery and reinsert, not only I cant make it back to Android boot but also, when I load up Mgldr Recovery, the AD Recovery function also does not load beyond 12345...
I am going to load a WinMo 6.5 ROM probably NRG's and reinstall HSPL.
Click to expand...
Click to collapse
as I said before... use the stock windows, not the cooked ones (you can get it off the HTCs website)...
maybe,,, make sure you have the right partion size for your rom. check your roms page, it should say what size you need. if you have the wrong size, your phone can do all kinds of stupid things. speaking from my own screw up thinking i had the right size,,,
Sorry for the late response. I am now flashing it with STOCK ROM. I couldnt first find on HTC thats why I went and download the NRG's ROM. Today I just found that HTC pulled the ROM and now they are only available on T-mobile website so eventually I got it and now installing it. I will update about the progress
Thanks
So I downloaded the ROM and put my phone into HSPL screen by pressing volume. I open the .exe file (ROM) and set it to install. However, during the installation, the process gets stock around 18% and I waited it out couple of times for more than 10 minutes and does not go pass that.
I tried to Task29 it and re-flash it but the problem maintains.
UPDATE: I re run HSPL and restore to SPL 2.8... and then run the Stock Rom installation. This time, it finished the installation however, when it booted up, it got stock on the pink logo "stick together"... I tried to hard reset by holding the Up and Down Volume and when i did it, and when through the manufacturing reset process, the problem maintains. I cannot get into Stock WinMo.
Thanks
My phone has the exact same problem. Doesn't anybody have a solution for this?

Reverting to stock problem

I managed to break my original HD2 a while ago and I've only just decided to replace it. I have another main phone but I loved that I could pretty much do anything with my old HD2. I had a bit of experience with installing cooked ROMs before moving on to installing Android and WP7 on it.
As I had a bit of experience with playing about with software recovery/updates, I decided to buy a phone that was described as "booting to a white screen" off ebay. I thought it would be a fun little hobby to get it working again.
My first few steps would be to get it to stock and start playing with it from scratch.
I booted into the bootloader and tried to flash a stock ROM but it kept freezing at 0%.
I've since managed to change the SPL version from 2.08 HSPL (I could get the phone to boot into MAGDLR 1.13, so they must've been playing with WP7 or Android NAND) to 3.03.
When I try to install the unbranded stock ROM, I get an error telling me that "This Update Utility cannot be used for your PDA Phone." I assume that I'm trying to install unbranded firmware on a branded phone. Is there a way to find out what branding the phone has as I can't get it to boot up? Am I going about this the right way or have I missed something obvious?
Thanks for your help!
EDIT:
I installed 3.03 HSPL to install the stock ROM and it completed the install process. However, after turning it on, it froze on the white HTC screen where it shows the Radio & ROM version. I pulled the battery out and now it freezes on a blank white screen. I'm out of ideas at the moment. Any help would be appreciated :s

Categories

Resources