Related
I see the mods have posted a sticky thread on the developers page linking to Radio downloads - very useful!
http://forum.xda-developers.com/showthread.php?t=563757
Couple of questions:
Which is the latest?
How do you install them?
I am alternating between two ROMs - Modaco 3.1, and Villian 2.1
So which is the right one to install.
cheers all
the ascending numbers in the radio name doesn't make you curious? obviously the highest number is the newest.
and since you know how to install different roms the hint "in signed update.zip format" should also ring a bell for you...
First, thanks for the reply.
I didn't want to assume anything, so thought I would ask.
Second, I have only ever had to install a radio once before, using the terminal ( a process I'm not too comfortable with as I don't know what I'm doing - instead only copying instructions ). I did not know that a signed zip means it will install from Recovery in every instance.
Update - So following your lead I've flashed the latest Radio - using Recovery. Now I can't start my phone, I get a graphic of an open box with an arrow coming out of it to a phone next to the box. I get the same if I try to start in recovery.
Any ideas?
wait!!!
i might take a few minutes, but for gods sake wait!
edit: now that i looked at your timestamp i hope you waited and your phone works now. the out-of-the-box logo is the actual flashing part. pulling the battery during that phase has bricked devices in the past...
Thats why I ask the questions!
I did pull the battery - but luckily for me I did not brick my phone!!
I am so glad that you asked this before I tried it... I may have panicked and done the same...
'The out-of-the-box logo is the actual flashing part' - this is good to know, thanks.
Also, coming from WinMob, it is recommended to use a certain radio depending on which ROM you are using... therefore, I totally understand your question about which radio is the right one for the ROM (the latest one is not always better)
I've searched the forums, and maybe I've just not searched correctly, or for the right thing, but I've not been able to find any information specific to my problem.
Anyways, here's what's happening.
Just picked up a new Sprint HTC Hero, followed step by step instructions to root the phone, no problems whatsoever. Made my nandroid backup, saved to the root of my sdcard, no issues there.
Immediately afterward, I downloaded the Black Sense skin, stuck it in the root of the sdcard, renamed to update.zip like instructions said, turned the phone off and rebooted in recovery, installed the update from the sdcard, rebooted, and now is stuck in a boot loop.
I get the sprint animation, the hero logo with the little android guy, and the HTC splash screen, and then just goes back and does it again.... forever. I have not loaded any other ROM or done anything else with the phone, just rooted the phone, dl'd the theme. Now I have heard about loading a different ROM on the phone, but is this required for the Themes to work? If it is, how would I be able to tell which ROM's are compatible with my phone? Sorry guys, I'm new to this, just trying to pick up info as I go.
Most all of the other threads I have found are directed to other phone users who have installed a Hero ROM on a Tmobile G1 or something like that. I haven't been able to find anything specific for my device, so I'd appreciate any help you all can give. I'm sure its a pretty simple fix, any help?
I had the boot-looping problem on my rooted T-Mobile G2 Hero, and I fixed it by wiping everything from the recovery menu. I dunno if this will help you, since I'm not sure what the differences between Sprint, HTC and T-Mobile's version are, but it might be a good start. :S
thanks
thanks for the quick reply. As usual, I found a boatload of info right after I posted the original thread. I think what I needed to do was to download find and download a rom that is compatible with my version of Hero and android, then find a theme that I like, and then try to update with the theme.
That's about as far as I've got, I'm poring over every bit of info I can find, but its confusing as hell, and poor grammar makes it even harder to understand.
nuformzdesign said:
thanks for the quick reply. As usual, I found a boatload of info right after I posted the original thread. I think what I needed to do was to download find and download a rom that is compatible with my version of Hero and android, then find a theme that I like, and then try to update with the theme.
That's about as far as I've got, I'm poring over every bit of info I can find, but its confusing as hell, and poor grammar makes it even harder to understand.
Click to expand...
Click to collapse
If you did a nandroid backup? boot into recovery and restore the backup, that should reset everything unless you flashed the skin and then did the backup? in that case download a rom for the cdma hero (guessing thats what you have?) rename it update.zip and put it onto your sdcard, boot into recovery and wipe EVERYTHING!, then flash your update.zip. only install themes for specific roms.
yea, had no problem with making the nandroid backup, and after the boot-loop, I pulled the battery and then booted in recovery to restore. No problems there.
I guess I just didn't get enough info before I started messing with the device. Thanks for the help tho.
So, firstly, big thanks to the devs here. Gt ADB up and running and started the seemingly easy process f flashing ClockworkMod.
However, I'm not getting to ClockworkMod after resetting. If I try booting into recovery, it stays on the birdie splash screen with "Recvery key detected" and "Booting recovery kernel image" in the upper left.
Not finding any options for alternate recoveries or a fix for this.
I bought it used and the original owner had done some stuff to it so perhaps I was not meant to flash Clockwork from here.
Tap UI version is TnT Lite v5.0.0
Kernel version is 2.6.32.9-00001-g0e0c333-dirty
The standard ClockworkMod does not work properly with TnTLite 5.0. You need the one that was specifically compiled for that ROM.
Go here: http://forum.xda-developers.com/showthread.php?t=998663
and scroll down to the bottom of the first post for a link to the compatible version.
I thought that might be the case although I was told I could flash CLockworkmod once 5.0 was on there.
I'm normally a bit better at figuring all this out but starting in the middle of someone else's work has me at an awkward spot.
I've been searching with little luck. Any chance of pointing me in the right direction?
What about a complete factory reset? Would it be advised at this point?
I editted my previous post with a link to TwoTapsX (Experimental) which is identical to TnTLite 5.0. That should get you going but I'm not sure how much damage might be done at this point. I would try just installing the compatible version of CWM and see if that works. If not, we can look at other recovery options.
Just in case... Are you familiar with nvflash? http://forum.xda-developers.com/showthread.php?t=861950
Just started reading about nvFlash and paused to ask the questions before hacking away blindly at my new toy.
I really appreciate you pointing me in the right direction.
I enjoyed the ROM he put on here but, like the poster under me, my data suddenly got deleted and I like to try various ROMs anyway so I set to work.
I rarely leave my tablet running the same ROM for more than 12 hours ;-)
Be aware that switching away from this particular one can be a bit tricky. I find that doing a cache and data wipe before starting helps to boost the success rate. I also try to down grade to stock 1.1-3588 before loading anything else. If that fails it usually results in nvflashing back to factory stock.
Ack! Okay, in what is sure to be yet another Windows 7 issue, I'm having trouble running the .bat file for nvflash.
Are you sure it is the Bat file. Windoz7 64 need a different driver for NVFLASH.
The drivers I used appeared to work. I will try again.
Damn, I'm sorry. I swear I'm usually better at figuring all this crap out for myself. Once I'm back to stock, I can work from the beginning. This is like being dropped into the middle of a David Lynch flick with zero context.
When I run the batch command, it says that nvflash.exe is not recognized as an internal or external command. Weird.
Did you extract both archives to the same directory?
I sure did. I did take it to mean the gtab folder should remain intact within the nvflash folder instead of mixing the contents altogether in one folder. Right?
Everything else seems to be in order.
Putting any recovery zip on the sdcard produces the same results. Thankfully, everything seems to be working aside from the recovery. Maddening!
I think they need to be intermixed. Would have to check the original thread or look at the .bat and .cfg files to be sure... but if I recall properly they do.
All the files from both zips should be in the same folder, otherwise the batch file can't find nvflash and you get that error.
Good luck!
Wow. If that's what it was they need to put a dunce cap on my avi. Thanks for all the help. I shoulda had the guy put it to stock so I could start from scratch.
I'll try that when I get home.
Thanks again!
Sent from my HTC Vision using XDA Premium App
Sleef,
You are in a world of hurt -- and I say that not making any negative comment
toward the advice you already have been given.
TnT Lite 5.0.0 (which is now TwoTapsx) is a second generation ROM Roebeet did
based on the UAT 3991 update posted by VS in a kind of test mode.
The second generation ROM is not compatible in many respects with the original ROMS
up to 3588 -- some of the internals that normally are changed in an update have been modified.
So, as you have been properly warned by others, you cannot run stock CWM. You
also have to be careful downgrading to stock before moving to stock or another ROM.
To get out of 5.0.0 you need to:
1. Read Roebeet's TwoTapsX thread so you know what you are working with:
http://forum.xda-developers.com/showthread.php?t=998663
2. You need to NVFlash back down to stock. Normally we'd tell you to follow
the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Since you already have been working with this, I'd step-by-step make
sure of your setup and that it is right.
My best suggestion would be for you to set up and follow the NVFlash thread above
exactly and see if you can get a good flash. If you do, it will take you down to what
we call bekit 1105, which is stock version 2638. If you get there and boot successfully,
then when you turn on wifi it will soon update you to OTA 3588. Then
you can carefully pretty much do what you want.
If you don't get a successful flash (because the tab has had so many different,
difficult to handle things on it), then all of us will have to help you find a successful
path.
Good luck,
Rev
P. S. -- What the other guys have been telling you is good -- I've just tried to
put it in perspective so you'd understand where you're at and be organized in
your approach.
Quick clarification... I think Rev meant to say "Is NOW TwoTapsX" rather than not which is why that thread is referenced later. The name change was necessary to differentiate the two development paths.
Thanks for popping in Rev. I've been meaning to pop in but I've been... practicing my recovery methods... don't ask...
Yep.
Fumblefingers strikes again. Thanks.
Rev
Alright so, I need help with my HTC EVO 3D.
*Now don't worry I've tried every search and used every resource nothing that will anwser or fix my specific circumstance.
I rooted my HTC EVO 3D, and everything was fine, all ran like normal. (With the intention to install custom ROM's.) I found one that appealed to me, the ViperROM. After following multipe tutourials strictly, I had the problem of when I restarted my phone it wouldn't load to normal interface. I just got to HTC logo backed on a white screen for about 10-15 seconds then it would turn off and restart, to the same proccess of going into the white screen.
Now before people start coming up with anwsers I will list everything that I've tried, hoping that some expert or someone with a great deal of knowledge will help me out:
> Tried installing the ROM again, multipe times actually
> Wipe Delvik Cache and Cache Partition along with Factory Reset and data wipe in all possible sequences
> Assuming somthing was wrong with the ROM, I tried installing other ROM's, also strictly following tutourials and having the same result
> I put the RUU file on my phone but it won't automatically flash, so I tried saving as a .ZIP and installing it and it aborts
I'm becoming extremely frustrated and dissapointed that I even rooted my phone and went into this.
Now, does anyone have a solution or idea of my problem?
Feel free to ask furthur questions if I forgot to mention some details.
Thanks.
When you try to RUU, are you downloading a zip or an exe? Exe files need to be ran from your computer. Zips need to be named correctly (don't add a zip if you don't see it) and flashed through the bootloader. Flashing an RUU through recovery won't work.
Assuming you can access recovery, do you have a nandroid backup you can restore? If you can't or you get the same result, try running an RUU from your computer.
If all else fails, try the Evo 3D forum. I'm sure you could pm a moderator to move this thread over there.
Good luck!
Supersonic Evo 4G | MIUI | Tapatalk
Alright, thanks for that. It gave some understanding but when I start the Installation Wizard, it says my phone is connected? Any thoughts?
And I'm very new to this site would you possibly be able to ask a mod. for me? Or give me the name of one? Thanks.
How do I restore my backup file
I believe that USB debugging must be turned on for the RUU to run. I'm from the original Evo, but the steps should be similar. Try running the RUU from fastboot - it should be an option on your hboot (bootloader) screen. Also be sure that you have the correct drivers installed. I've never personally RUU'd myself, so I can't offer much more guidance on that part.
If you can't get the RUU to run, you can always use a zip file through hboot, just be sure to download the correct one. For the Evo the file must be named PC36IMG.zip... it'll be different for the 3D - I think it starts with PG.
If you made a backup in recovery then you can restore it by following the same steps, just choose restore instead of backup. You should've made a nandroid backup prior to flashing - it's in every guide. If you used Rom Manager, then bout into recovery and you should see a backup/restore option. Choose restore and select the backup.
If you did use Rom Manager, I suggest doing everything manually once you get your phone back up and running. Rom Manager hinders your learning experience and restricts your control over your device. Find your roms on XDA and download them from their thread. Do your backups from recovery, wipe and flash from recovery. You may have done it manually and still ended up in this situation, but I'm just giving my perspective on automated flashing.
To have the thread moved, use the report button on the first post. There should be an option that says that you need the thread to be moved. I'll report it for you tomorrow if you can't figure it out.
Good luck, I hope you get everything worked out :]
Supersonic Evo 4G | MIUI | Tapatalk
Hello,
I have an S-on 4g LTE unlocked with bootloader and running Viper 2.2. I've been getting those annoying update messages, so I thought I'd try a different ROM. I tried to switch to the Avatar ROM on the forums: http://forum.xda-developers.com/showthread.php?t=2207395, but I couldn't get it to take. I read somewhere that I needed to extract and load the boot.img file through ADB first, so I did that but it still didn't take. I could install the ROM, but I can't get it to boot past the "HTC: This build is for development purposes only" screen. It hangs there for a while, then the screen goes black, and eventually it loops back.
So then I decided to just go back to Viper 2.2, but that won't take. It's doing the same loop-back. I did a full backup before starting, so I tried restoring that but it made no difference. I thought maybe I needed to do the adb boot.img thing again using the boot.img file from the viper 2.2 file, but there's no boot.img in any of the viper files I have. So I tried looking on the forums, but all the boot.img file links I found were expired/dead/long gone.
So I need some help in figuring out how to get this phone back. I can get it out of the bootloop by pulling the battery and then do hboot via the downvolume + power button, and then I can get into teamwin recovery from there. But after that, I don't know what to do. Any advice/help to get back on my feet would be greatly appreciated!
Nevermind...got it! I tried installing the stock kernel from here http://forum.xda-developers.com/showthread.php?t=1770978 and it booted back up finally.
I kind of thought that's what I needed to do, but I was at the point where I didn't want to keep touching (or more like breaking!) more stuff until I knew what to do. Thanks anyway!