Related
I flashed Revolution HD, the latest version and when the phone re-booted it went to bootloader.
I managed to flash TWRP again and im in there, however I need to put a ROM on the phone and cant copy one on there
any ideas? adb says device not found, not sure if im doing something wrong
try fastboot devices
You can try this to sideload a rom.
http://forum.xda-developers.com/showthread.php?p=40341536
Sent from my HTCONE using Tapatalk 2
Okay, managed to get ADB working. For some reason it doesn't work on USB3 ports :S
Sideloaded a ROM, but I got no network signal, and it restarted itself within about 2 mins.
I have re-locked, and am running RUU now, if this doesn't work what shall I do?
Okay the RUU worked fine. Thanks for the help guys!
Latest versions on intl. roms are 4.2.2. They won't work on sprint. Since there is no sprint support the updater script wipes our radio and boot partition because they have a different partition table than we do. It's just f.y.I so you know what went wrong
18th.abn said:
Latest versions on intl. roms are 4.2.2. They won't work on sprint. Since there is no sprint support the updater script wipes our radio and boot partition because they have a different partition table than we do. It's just f.y.I so you know what went wrong
Click to expand...
Click to collapse
Yeah I realised, but the text in the post is VERY misleading.
http://cl.ly/image/1H3I1y2V3l3o
Maybe its just me being crazy, but I assumed anything later would work, to me that sounded like everything below 9.4 would not.
Diddo
The exact thing happened to me!!! the ARHD posts are very misleading!! I also had to do a RUU on it.. it made me made cause i really wanted that rom. Have you found any other ROM with 4.2.2 that will work with sprint htc one? I cant find anything.
SeanBond said:
I flashed Revolution HD, the latest version and when the phone re-booted it went to bootloader.
I managed to flash TWRP again and im in there, however I need to put a ROM on the phone and cant copy one on there
any ideas? adb says device not found, not sure if im doing something wrong
Click to expand...
Click to collapse
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?
Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.
well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?
AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk
If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.
My Play edition phone has been giving me endless headaches ever since the KitKat update dropped - I can't seem to get it to load.
For the status of my phone before all of this, I unlocked the bootloader, installed ClockworkMod, and used it to install a root Zip. I never wanted or tried to get S-OFF. So the bootloader shows Tampered and Unlocked, but S-ON, version 1.54. Everything worked fine, and I was happy with the phone.
Now, before I get started, my desired end-state for this phone is a bone-stock KitKat installation. I'm okay with not having root, having stock recovery and bootloader, just as long as the stock OTAs arrive and install with zero mucking around with recoveries, ROMs, backups, etc. I bought this phone because I want stock Android and the latest updates ASAP, and I'm not very happy that I've had to spend all of this time messing with it and still don't have the update.
This take starts when the little update icon for KitKat showed up, and in my innocence, I pressed it.
The phone reboots, CWM flashes the update, and reboots into it. Instead of the normal boot, I am greeted with a blue-green screen covered with little green lines, unresponsive to any input. In retrospect, I think this is because I don't have S-OFF, and the KitKat update requires a radio update which the updater includes, but can't be flashed from a modified recovery without S-OFF.
So I boot back into CWM and flash a backup to get my phone working again. I still want KitKat, of course, so it's time to search for other things to try.
First off, I try flashing a stock aftermarket ROM, the one by bigxie. Now the phone boots, but it bootloops, rebooting about 5 seconds after the lock screen comes up. With a little reading and a few questions, I get that this is also because I don't have S-OFF. Mmm, okay. Recover from backup again.
I downloaded the stock GPE RUU, pulled the stock recovery from it, flashed that, and tried to use it to install the OTA update, figuring that it would be signed properly or whatever to flash the radio. Same result as CWM. Install CWM again, restore from backup again.
My options are starting to seem a little limited. It looks like I can either get S-OFF and try the OTA again, or flash the stock GPE RUU and go back to 100% stock. Except that the instructions I found for flashing a stock RUU say that I need S-OFF for that too, though I'm a little skeptical of this - wouldn't that be only for rewriting the Model ID and Cell ID to the GPE?
First, I decide to try getting S-OFF. I get rumrunner S-OFF set up and running (moonshine doesn't have a version for me, and revolutionary doesn't support bootloader 1.54), and it does it's thing for a while, only to tell me at the end:
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Click to expand...
Click to collapse
Hmm... so I try flashing a kernel. I grabbed flar2's kernel and tried to flash it, and the Aroma installer never goes past 0%. Still reboots into exactly like it was before. Not real inclined to spend a lot of time messing with flashing kernels, since I want to end up at stock.
So next, I try flashing the stock GPE RUU, according to the above instructions. The flash fails with the message:
FAILED (remote: 99 unknown fail)
Yes, I ran the flash command twice, same result both times.
I'm downloading that again, but I'm not really sure what to do here. I'm okay at this point with flashing the stock RUU and wiping everything, if it gets me back to hassle-free stock. Should I keep trying to get that working? Or is S-OFF really necessary for that, and I need to get that figured out first? Or maybe I should just throw the phone out a window at this point.
ufmace said:
So next, I try flashing the stock GPE RUU, according to the above instructions. The flash fails with the message:
FAILED (remote: 99 unknown fail)
Yes, I ran the flash command twice, same result both times.
I'm downloading that again, but I'm not really sure what to do here. I'm okay at this point with flashing the stock RUU and wiping everything, if it gets me back to hassle-free stock. Should I keep trying to get that working? Or is S-OFF really necessary for that, and I need to get that figured out first? Or maybe I should just throw the phone out a window at this point.
Click to expand...
Click to collapse
I'm in much the same situation as you, S-ON with H-Boot 1.54, and Rumrunner/Moonshine keep on giving me the same errors you got. The only thing I have to contribute so far is, you cannot flash RUUs until you have S-OFF.
I've been searching for a proper insecure kernel for rumrunner to do it's magic with, but haven't found anything yet.
Fireye00 said:
I'm in much the same situation as you, S-ON with H-Boot 1.54, and Rumrunner/Moonshine keep on giving me the same errors you got. The only thing I have to contribute so far is, you cannot flash RUUs until you have S-OFF.
I've been searching for a proper insecure kernel for rumrunner to do it's magic with, but haven't found anything yet.
Click to expand...
Click to collapse
Thanks, I was afraid of that. Do you (or anyone else) know much about this insecure kernel thing? I assumed that all of the kernels for download here are insecure, but none of them say anything about it.
36664523 18206
ufmace said:
Thanks, I was afraid of that. Do you (or anyone else) know much about this insecure kernel thing? I assumed that all of the kernels for download here are insecure, but none of them say anything about it.
Click to expand...
Click to collapse
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Fireye00 said:
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Click to expand...
Click to collapse
Thanks. I found a reference to a carbonite ROM that supposedly worked here. I'll try and flash that or that Renovate one when I have time.
Fireye00 said:
I'm not quite sure, but I've seen some mention around the forums that installing other ROMs can fix the issue. I'm trying to flash Renovate, which someone reported success with. I'll keep you updated on what I find.
Click to expand...
Click to collapse
Thing's I've tried tonight:
* Tried moving from a USB Hub (Multi-TT) to a port on my mobo, No change.
* Flashed Renovate 7.0. Selected the APEX launcher, but when I got in, apex kept on crashing.
* Flashed Renovate 7.0 again, and this time selected GEL (Google Experience Launcher), which worked this time. Proceeded to run rumrunner, got to Pouring (2), but it errored out saying WTF are you doing (system reset itself in the middle of pouring)
* Moved to a new USB port, tried running rumrunner again, SUCCESS!
Resulting rumrunner output from working run:
Code:
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)............................
pouring (2).........
Waiting for ADB (27/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
Do note that during pouring 1 and 2, it rebooted twice, apparently that is normal.
ufmace said:
Thanks. I found a reference to a carbonite ROM that supposedly worked here. I'll try and flash that or that Renovate one when I have time.
Click to expand...
Click to collapse
I finally got S-OFF working with the linked ROM. It was a faster download than the Renovate one, so I thought I'd give it a try, and it's good. Just flashed and wiped data, didn't bother to set anything up or install anything. At least I'm finally making some progress here!
First, I'm going to restore my CWM backup and see if the factory update flashes properly now. If that doesn't work, I'll probably try the RUU. I'll post an update with the result.
ufmace said:
I finally got S-OFF working with the linked ROM. It was a faster download than the Renovate one, so I thought I'd give it a try, and it's good. Just flashed and wiped data, didn't bother to set anything up or install anything. At least I'm finally making some progress here!
First, I'm going to restore my CWM backup and see if the factory update flashes properly now. If that doesn't work, I'll probably try the RUU. I'll post an update with the result.
Click to expand...
Click to collapse
I was able to flash the 4.4 RUU without any trouble. My phone now works perfectly, whereas before I would sometimes get app crashes and junk. Now to take a fresh 4.4 backup, and revel in the awesomeness.
Grats on getting S-OFF finally!
Fireye00 said:
I was able to flash the 4.4 RUU without any trouble. My phone now works perfectly, whereas before I would sometimes get app crashes and junk. Now to take a fresh 4.4 backup, and revel in the awesomeness.
Grats on getting S-OFF finally!
Click to expand...
Click to collapse
Finally done! The update on my backup didn't work, same blue screen. So I just flashed the RUU that I had, let it pull all of the updates, and ran them. And this time, the KitKat update finally worked! So now I have a new, blank phone with KitKat to restore back to how I had everything set up.
I'm planning on leaving all of the system stuff bone stock. No root, recovery, nothing. All because, when the next update drops, I want it to just install without spending the better part of my free time for a week or two hacking around with it.
Incidentally, did you find an actual 4.4 RUU? The one I used was the launch RUU with 4.3, so it needed 2 OTA updates to get to 4.4.
ufmace said:
Finally done! The update on my backup didn't work, same blue screen. So I just flashed the RUU that I had, let it pull all of the updates, and ran them. And this time, the KitKat update finally worked! So now I have a new, blank phone with KitKat to restore back to how I had everything set up.
I'm planning on leaving all of the system stuff bone stock. No root, recovery, nothing. All because, when the next update drops, I want it to just install without spending the better part of my free time for a week or two hacking around with it.
Incidentally, did you find an actual 4.4 RUU? The one I used was the launch RUU with 4.3, so it needed 2 OTA updates to get to 4.4.
Click to expand...
Click to collapse
I had downloaded a 4.4 RUU back when it first hit for the HTC One, filename of "RUU-HTC_One_GE-4.4-3.58.1700.5.zip". I'm pretty sure it's the one on this thread, named "RUU Zip M7 Google Edition 4.4 3.58.1700.5 ".
Bit of a post-script, the 4.2.2 OTA update for my phone just dropped yesterday night. I let it install normally, and everything just worked. Now that's what I'm talking about!
Hello guys,
I'm in a bit of a pickle here....
I've got a HTC One which I've rooted and unlocked though not S-Off by the looks of things and I had SinLess rom installed fine, it started playing up so I though I'd update it. Bung the new one version on there via sideload and install... Marvelous.
Only now, it gets to the welcome screen as silly ol' me did a factory wipe as well as all cache and after about 5 seconds of Welcome - Choose language. It restarts.
I then decided to try a new rom, so grabbed Android Revolution. To no avail either....
On bootloader it shows as HBOOT - 1.54
S-On
**TAMPERED**
**UNLOCKED**
What can I do to actually get a working rom on this thing?
If there is any more details I need to give please say so as this is my first time flashing something as complicated as this. All my old android devices were far far simplar :crying:
- Here's the facepalm moment - I didn't do an nandroid backup due to it not working and I wanted to put a new ROM on there so I didn't look into getting it working. If I could injure myself I would.
Any help will be greatly appreciated. :good:
Kind regards, Ian.
Jeffaruni said:
Hello guys,
I'm in a bit of a pickle here....
I've got a HTC One which I've rooted and unlocked though not S-Off by the looks of things and I had SinLess rom installed fine, it started playing up so I though I'd update it. Bung the new one version on there via sideload and install... Marvelous.
Only now, it gets to the welcome screen as silly ol' me did a factory wipe as well as all cache and after about 5 seconds of Welcome - Choose language. It restarts.
I then decided to try a new rom, so grabbed Android Revolution. To no avail either....
On bootloader it shows as HBOOT - 1.54
S-On
**TAMPERED**
**UNLOCKED**
What can I do to actually get a working rom on this thing?
If there is any more details I need to give please say so as this is my first time flashing something as complicated as this. All my old android devices were far far simplar :crying:
- Here's the facepalm moment - I didn't do an nandroid backup due to it not working and I wanted to put a new ROM on there so I didn't look into getting it working. If I could injure myself I would.
Any help will be greatly appreciated. :good:
Kind regards, Ian.
Click to expand...
Click to collapse
Hey your'e stuck in a boot loop, its usual
just download a good stable rom
clear data/ cache
flash the rom and you'll be out of it,
If this thing doesnt work out download the orignal RUU and get back to stock
Tech.Nik said:
Hey your'e stuck in a boot loop, its usual
just download a good stable rom
clear data/ cache
flash the rom and you'll be out of it,
If this thing doesnt work out download the orignal RUU and get back to stock
Click to expand...
Click to collapse
Yeah, after attempting to install 3 different roms.
Sinless, ARHD and SkyDragon, I'm going to try a different recovery as I'm currently using TWRP 2.6.3.3 and I know there is an update but also I want to see if CWM can do anything with the 6.0.4.3 version....
Jeffaruni said:
Yeah, after attempting to install 3 different roms.
Sinless, ARHD and SkyDragon, I'm going to try a different recovery as I'm currently using TWRP 2.6.3.3 and I know there is an update but also I want to see if CWM can do anything with the 6.0.4.3 version....
Click to expand...
Click to collapse
Hello,
To no avail, after trying different recoveries, nothing.
Looks like I've got a metal slab...
It just keeps restarting itself at the welcome screen, the only other thing I can think of would be to fully wipe EVERYTHING on the phone but I'm not sure that's too good of a move either...
Argh.
You have to be s-off to run these Roms
Hi XDA,
I have an AT&T Vivid
- Original stock ROM: Android 2.3.4, HTC Sense 3.0, Kernel 2.6.35.13-gc1166ee
- Unlocked
- S-OFF
- TWRP 2.6.3.0
I've tried numerous ROMs from this forum, which other 'Vivid' users claim to work great, but every one of them crashes moments after loading. The ONLY one that works is my restore. I clear everything possible before any flash, and I've even wiped the internal clean with a total factory reset; still crashes.
The ROMs do load, and they run fine, only until I begin interacting with them. CM for instance will crash after I press "next" while selecting a default language for initial startup.
Does this sound familiar to anyone? Please help
TheMrGuy said:
Hi XDA,
I have an AT&T Vivid
- Original stock ROM: Android 2.3.4, HTC Sense 3.0, Kernel 2.6.35.13-gc1166ee
- Unlocked
- S-OFF
- TWRP 2.6.3.0
I've tried numerous ROMs from this forum, which other 'Vivid' users claim to work great, but every one of them crashes moments after loading. The ONLY one that works is my restore. I clear everything possible before any flash, and I've even wiped the internal clean with a total factory reset; still crashes.
The ROMs do load, and they run fine, only until I begin interacting with them. CM for instance will crash after I press "next" while selecting a default language for initial startup.
Does this sound familiar to anyone? Please help
Click to expand...
Click to collapse
This doesn't sound familiar to me at all, but first you should search the forums on updating your ROM to ICS and updating your bootloader. I would also try flashing the boot.img from the ROM even though you're S-OFF, as it can't hurt.
Overstep setup wizard
projectisaac said:
This doesn't sound familiar to me at all, but first you should search the forums on updating your ROM to ICS and updating your bootloader. I would also try flashing the boot.img from the ROM even though you're S-OFF, as it can't hurt.
Click to expand...
Click to collapse
Hi, I had a simmilar problem with my HTC vivid. I found fix of this problem you must to press left-top corner, then right-top corner, then bottom-right corner , and right-bottom corner. It automatically passes setup wizard.
Same here
sorry to bring this up again but i have the same problem.
Did you found a solution to this issue?
I found something strange, when the rom came up it only crashed after it vibrated the first time. If i lock the screen and unlock, it wont crash.
godzec said:
sorry to bring this up again but i have the same problem.
Did you found a solution to this issue?
I found something strange, when the rom came up it only crashed after it vibrated the first time. If i lock the screen and unlock, it wont crash.
Click to expand...
Click to collapse
Have you updated the boot loader? There are threads with detailed instructions on how to do it. Not positive it will work, but we need to eliminate the possible first.
Sent from my HTC Vivid 4G using XDA Free mobile app
projectisaac said:
Have you updated the boot loader? There are threads with detailed instructions on how to do it. Not positive it will work, but we need to eliminate the possible first.
Sent from my HTC Vivid 4G using XDA Free mobile app
Click to expand...
Click to collapse
Hi made the updates instructed here. So now my Hboot is 1.85.2525 S-OFF JuopunutBear, I have the SuperCID (CID with 11111111). What am i missing????
godzec said:
Hi made the updates instructed here. So now my Hboot is 1.85.2525 S-OFF JuopunutBear, I have the SuperCID (CID with 11111111). What am i missing????
Click to expand...
Click to collapse
Hmm, your Hboot seems to be newer than mine. Mine is:
S-OFF
HBOOT-1.85.0025
MICROP-0360
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 1 2012,17:09:49
At this point I don't know why your roms are doing the funky monkey. I will post again in the future if I think of something though.
projectisaac said:
Hmm, your Hboot seems to be newer than mine. Mine is:
S-OFF
HBOOT-1.85.0025
MICROP-0360
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 1 2012,17:09:49
At this point I don't know why your roms are doing the funky monkey. I will post again in the future if I think of something though.
Click to expand...
Click to collapse
1.85.2525 is the s-off version of 1.85.0025