i was running sensehero 1.4, i decided to try out wesgarner's beta WGBuild9 for him. it booted and all, there were some bugs. i replied to his thread and then restored my nandroid from before hand. it just sat at the initial boot logo, not either of the animations, the carrier one. i waited quit a while and then pulled the battery. tried a wipe and reboot, no dice. tried fastboot erasing system, data then reflash, still sits at boot logo. no i am watching the logo while waiting to see if a different rom (cyans latest stable) will boot.. any ideas? recovery and fastboot still work fine.
gwydionwaters said:
i was running sensehero 1.4, i decided to try out wesgarner's beta WGBuild9 for him. it booted and all, there were some bugs. i replied to his thread and then restored my nandroid from before hand. it just sat at the initial boot logo, not either of the animations, the carrier one. i waited quit a while and then pulled the battery. tried a wipe and reboot, no dice. tried fastboot erasing system, data then reflash, still sits at boot logo. no i am watching the logo while waiting to see if a different rom (cyans latest stable) will boot.. any ideas? recovery and fastboot still work fine.
Click to expand...
Click to collapse
If you can get into bootloader, or recovery, you're not completely bricked.
gwydionwaters said:
i was running sensehero 1.4, i decided to try out wesgarner's beta WGBuild9 for him. it booted and all, there were some bugs. i replied to his thread and then restored my nandroid from before hand. it just sat at the initial boot logo, not either of the animations, the carrier one. i waited quit a while and then pulled the battery. tried a wipe and reboot, no dice. tried fastboot erasing system, data then reflash, still sits at boot logo. no i am watching the logo while waiting to see if a different rom (cyans latest stable) will boot.. any ideas? recovery and fastboot still work fine.
Click to expand...
Click to collapse
u r not bricked if u can get into recovery and fastboot, just perform your nandroid restore, wipe and u should b good, u might have to pull the sd card and reboot without it
Since you have so many posts I'm surprised you would post in the wrong forum. Anyway since your coming from a hero rom you need to follow these instructions http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F and that includes doing this line "Download the Android 1.6 Recovery Image (it has "-ota-" in the filename): ". Even if you have done it before you must do it again.
psychoace said:
Since you have so many posts I'm surprised you would post in the wrong forum. Anyway since your coming from a hero rom you need to follow these instructions http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F and that includes doing this line "Download the Android 1.6 Recovery Image (it has "-ota-" in the filename): "
Click to expand...
Click to collapse
What does post have to do with anything?
There were some issues with nandroid that were fixed in the new version, but you must wipe before installing the backup since the ext is also backed up.
psychoace said:
Since you have so many posts I'm surprised you would post in the wrong forum. Anyway since your coming from a hero rom you need to follow these instructions http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F and that includes doing this line "Download the Android 1.6 Recovery Image (it has "-ota-" in the filename): ". Even if you have done it before you must do it again.
Click to expand...
Click to collapse
yea i just was coming back to delete this and post in the 'think i bricked' thread lol
i tried wiping my ext fs as well. i'll check out that link and see what happens with it
i just noticed in that wiki is says
Code:
# Magic32A and Rogers Dream users: Download the 32A/EBI1 kernel latest version
i have a 32b board though...
I know the answer to your question What count as a brick. How about this thread being closed
gwydionwaters said:
yea i just was coming back to delete this and post in the 'think i bricked' thread lol
i tried wiping my ext fs as well. i'll check out that link and see what happens with it
i just noticed in that wiki is says
Code:
# Magic32A and Rogers Dream users: Download the 32A/EBI1 kernel latest version
i have a 32b board though...
Click to expand...
Click to collapse
You should have wiped and what method did you do to install the wesenger rom?
If you didn't flash the 1.6 recovery image then that's your problem. It's not the same thing as RA's or Cyan's so your not overwriting those recovery images. You must flash it first then the rom all without rebooting.
I've been getting these problems a lot lately for whatever reason. Anyways, I fixed it every time by wiping, then flashing the official HTC 1.6 OTA update zip. You'll probably have to dig a bit for it, since the links appear dead on the HTC support site. From there, you can flash a custom ROM no problem.
psychoace said:
If you didn't flash the 1.6 recovery image then that's your problem. It's not the same thing as RA's or Cyan's so your not overwriting those recovery images. You must flash it first then the rom all without rebooting.
Click to expand...
Click to collapse
....Thats only for cyanogen bacause of the cease and desist order..Wesengarner and dwang didnt recieve that from google...They have all google apps already, cyan cant include them in his rom only...
lstevens86 said:
I know the answer to your question What count as a brick. How about this thread being closed
Click to expand...
Click to collapse
awe, how helpful of you
Ace42 said:
You should have wiped and what method did you do to install the wesenger rom?
Click to expand...
Click to collapse
i flashed it as an update, no wipe. he requests no wipes in the thread for the beta.
gwydionwaters said:
i flashed it as an update, no wipe. he requests no wipes in the thread for the beta.
Click to expand...
Click to collapse
He means no wipe from previous ver of his rom..Not a hero rom.
oh i'm trying the coming from a different rooted rom instructions for cyan, i will see how it goes in a minute
gwydionwaters said:
oh i'm trying the coming from a different rooted rom instructions for cyan, i will see how it goes in a minute
Click to expand...
Click to collapse
Cyan rom installation only refers to his for wesengarner just do this..
1.Wipe all
2.Fix EXT
3.reboot recovery
4.Flash
5.Bam
Ace42 said:
Cyan rom installation only refers to his for wesengarner just do this..
1.Wipe all
2.Fix EXT
3.reboot recovery
4.Flash
5.Bam
Click to expand...
Click to collapse
oh i know, i am moving to cyan. i was only using WG for test purposes for his beta. it booted into cyans latest now. jeeze that was scary thanks everyone for your help, sorry i posted in the wrong place
im just amazed we havnt been given a nice big REPORT button to stop people posting in the wrong place
lol i can only imagine, i just panicked. and the forums are so crowded. also when you search it doesn't link to the posts with results just the threads with post with results, would help if search worked better. just a thought imho
someone can delete this, i would but there is no delete for me?
gwydionwaters said:
lol i can only imagine, i just panicked. and the forums are so crowded. also when you search it doesn't link to the posts with results just the threads with post with results, would help if search worked better. just a thought imho
someone can delete this, i would but there is no delete for me?
Click to expand...
Click to collapse
When you search, there IS an option to give results as either threads or individual posts. I suggest taking a couple minutes just to play around with the advanced search screen... it's surprisingly powerful, but most noobs don't use it. The little drop down Search is useless in comparison.
Related
I installed the senseHero but now the phone part, it hangs on boot
even if you reinstall a new firmware hangs on boot
helps me
did you do a complete wipe before installing?
Wrong forum. try the Dream Q&A or in the ROM's thread.
Mookie_Jones said:
did you do a complete wipe before installing?
Click to expand...
Click to collapse
Yes, I have also tried to change SD
heres the best help you can get
http://bit.ly/6pPHDJ
oh sorry
close this thread!
this is the log file -> http://federico.homeip.net/log2.txt
Umm, i have a tiny problem
after flashing a rom (cyan 5.0.5.2), the nexus doesnt boot anymore
before this i had flashed the recovery 1.7.0.
adb devices does not see it, so i cannot reflash another recovery. fastboot sees it, but gives an error about multiple links, so it cannot flash
its stuck at the big 4-color X
i can enter the recovery, wipe/flash anything, but it still wont boot, no matter what rom i flash
pls help
thank you
Wrong forum.
i have the same problem..it wont restore my back up either just stucked at the X screen with the lock
I had the same problem with C 5.0.5.1
I flash back C 5.0.5., (wipe everything before). then the phone boot OK.
Then I flash C 5.0.5.1 and is OK now.
mijou said:
I had the same problem with C 5.0.5.1
I flash back C 5.0.5., (wipe everything before). then the phone boot OK.
Then I flash C 5.0.5.1 and is OK now.
Click to expand...
Click to collapse
omg thank you i was having a heart attack!
bobdude5 said:
omg thank you i was having a heart attack!
Click to expand...
Click to collapse
indeed. me too!
thank you, it works!
cyan should put a notice somewhere for everybody to see that you cannot install directly 5.0.5.2
Are you guys even flashing Gapps?
I think i noticed this coming from a wipe as well.
You must wipe, Flash CyanMod, Flash Gapps.
I originally forgot Gapps, and got stuck, and then upon flashing it booted up fine.
raven2000 said:
Wrong forum.
Click to expand...
Click to collapse
why is it wrong forum?? its rom development related
cobrax2 said:
why is it wrong forum?? its rom development related
Click to expand...
Click to collapse
nah, this is more of a q/a topic Plus those who poke around in this forum are those willing to help. Always a good idea to post questions/problem threads in the q/a.
I was trying to flash a new kernel, and so i wiped the 2 caches and now im stuck on the Clockwork Recovery Screen. I try rebooting, and all it does is just go back to the Recovery screen. Please help, i want to use my nook color again.
Do you have previously created backup on your SD card ?
If so just restore.
Unfortunatly, i didnt. I just got it a couple days ago and am brand new to all these mods.
me too
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
OMG, I LOVE YOU! No really, thank you so much!!! It works perfect!
Your welcome...........
Solidsnake726 said:
OMG, I LOVE YOU! No really, thank you so much!!! It works perfect!
Click to expand...
Click to collapse
I think this is beginning of beautiful relationship
Some additional info that may be relevant or not...
Some users have reported that after clearing the dalvik cache in CWR (as part of the process to flash a custom kernel), the screen locks up and they are unable to return to the main recovery screen.
This was resolved by 1) hook up your nook to the wall charger, 2) hold the power button which will force a reboot, 3) after your nook reboots to its normal screen, restart the kernel flash procedure from the beginning, 4) after you clear the dalvik cache, do not touch anything for at least 30 seconds
After step 4, CWR usually doesn't lock up and you should be able to navigate back to the main recovery screen to finish the kernel flash process. For some reason or another, the nook just needs a little time after clearing the dalvik cache before you can press any buttons.
yan2000kee said:
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
Click to expand...
Click to collapse
I have had the same issue as the OP using ROM Manager to install 3.0.0.5 on 1.1.0 using Auto-Nooter 3.0.0. I was able to use the quoted method to break out (for the record I did so before reading this post ). However, I ran into the problem again after a full reroot and am still looking for a permanent solution to the problem.
yan2000kee said:
This just happened to me as well. I even had a backup image and restored, but it would still loop. I used the following zip which removes clockwork recovery (thanks to the OP that originally posted this) and it then it worked.
Give it a shot
Click to expand...
Click to collapse
Sorry for being a noob but what do I do with this file? Just put it on root and run it in CWR?
Moorfrost said:
Sorry for being a noob but what do I do with this file? Just put it on root and run it in CWR?
Click to expand...
Click to collapse
Yes. Boot into CWR and select the zip file from the SD card and flash.
eyecrispy said:
Yes. Boot into CWR and select the zip file from the SD card and flash.
Click to expand...
Click to collapse
Thanx a million, worked like a charm.
Thanks... But one other question...
Thanks for this got me out of the CWR bootloop, but now I'm stuck on the android splash screen.
UPDATE: Just tried to start all over and now it got me a bit further, but to a black screen with a white banner up top that says "Android System"...
Another noob question, sorry. Will this also restore the stock BN recovery? Regardless, thanks.
lekofraggle said:
Another noob question, sorry. Will this also restore the stock BN recovery? Regardless, thanks.
Click to expand...
Click to collapse
yes it does , just did it my self
Lifesaver! Thanks!
Maybe this should be linked to original thread.. So that things are made clear..
Sent from my HTC Desire using XDA App
Sorry to bump this thread, but OP's issue of being stuck in CWR happens to me every time I try to install the overclock kernel on my Eclair nook.
Any advice on what I can do to successfully overclock?
Anoxymoron said:
Sorry to bump this thread, but OP's issue of being stuck in CWR happens to me every time I try to install the overclock kernel on my Eclair nook.
Any advice on what I can do to successfully overclock?
Click to expand...
Click to collapse
I found a work around. Open cwr..flash recovery, exit recovery, reboot from quick boot . Once rebooted go back to cwr flash recovery, reboot into recovery, clear cache flash zip..reboot. This has worked numerous times for me.
bratliff said:
I found a work around. Open cwr..flash recovery, exit recovery, reboot from quick boot . Once rebooted go back to cwr flash recovery, reboot into recovery, clear cache flash zip..reboot. This has worked numerous times for me.
Click to expand...
Click to collapse
This is assuming that CWR is on internal memory.. if you are booting CWR from SD.. you need to take out the SD card then boot up.
Hello, I recently unlocked my bootloader and flashed a recovery. I flashed a new ROM, TikTak 4.42. After flashing the rom from CWM it started and went to a constant blue screen.
I flashed a new recovery via fastboot and flashed the rom again, it started but when it got to the locale selection and restarted after 2 seconds. This would repeat over and over. I decided to do a wipe, but inadvertantly wiped my storage too.
I pushed another ROM to the device via adb and flashed that via CWM, same problem as the constant rebooting. I tried to flash a RUU from fastboot but got a "Signature Fail" error.
My phone has access to the bootloader and recovery. My storage is empty so I have no roms on my phone. In mounts and storage it always says "mount /system" and "mount /data". Could this be a problem with system?
If you have any questions please ask, I'm quite new to all this so may not have included everything necessary. If anyone can help me fix my phone totally, I could make a small donation thorugh paypal
Thanks in advance
SK
SteveKeith said:
Hello, I recently unlocked my bootloader and flashed a recovery. I flashed a new ROM, TikTak 4.42. After flashing the rom from CWM it started and went to a constant blue screen.
I flashed a new recovery via fastboot and flashed the rom again, it started but when it got to the locale selection and restarted after 2 seconds. This would repeat over and over. I decided to do a wipe, but inadvertantly wiped my storage too.
I pushed another ROM to the device via adb and flashed that via CWM, same problem as the constant rebooting. I tried to flash a RUU from fastboot but got a "Signature Fail" error.
My phone has access to the bootloader and recovery. My storage is empty so I have no roms on my phone. In mounts and storage it always says "mount /system" and "mount /data". Could this be a problem with system?
If you have any questions please ask, I'm quite new to all this so may not have included everything necessary. If anyone can help me fix my phone totally, I could make a small donation thorugh paypal
Thanks in advance
SK
Click to expand...
Click to collapse
You need to read and understand these two threads and then you will be able to resolve your problem
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Both great threads and they cover all you need to know and understand
TikTak 4.42..? :laugh:
my guess is that it's cwm causing your problems, may I suggest trying twrp instead
L0rdNels0n said:
You need to read and understand these two threads and then you will be able to resolve your problem
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Both great threads and they cover all you need to know and understand
Click to expand...
Click to collapse
Thank you both for the replies, I'll be sure to read them now, and will try TWRP.
I can't seem to find an RUU for my device, it's hutchinson 3g, uk, which has the 3 digits 771. I can't find that in any of the listed RUU's
beanbean50 said:
TikTak 4.42..? :laugh:
my guess is that it's cwm causing your problems, may I suggest trying twrp instead
Click to expand...
Click to collapse
I tried flashing the rom with twrp but have the same problem, it boots up, gets to the choose location menu and then reboots. If it's important, when I'm in the bootloader it says "OS- (blank)"
SteveKeith said:
I tried flashing the rom with twrp but have the same problem, it boots up, gets to the choose location menu and then reboots. If it's important, when I'm in the bootloader it says "OS- (blank)"
Click to expand...
Click to collapse
damn, I wish I had a good memory as someone else had the same problem about a week ago (I think it was in the viper thread) i'll try to find it for you, but don't hold your breath!...
Edit:
found it..!
hope it helps you
http://forum.xda-developers.com/showpost.php?p=48816309&postcount=23652
beanbean50 said:
damn, I wish I had a good memory as someone else had the same problem about a week ago (I think it was in the viper thread) i'll try to find it for you, but don't hold your breath!...
Edit:
found it..!
hope it helps you
http://forum.xda-developers.com/showpost.php?p=48816309&postcount=23652
Click to expand...
Click to collapse
Thank you for helping! I think I may have worded my last reply badly. My recovery works, I'm currently on twrp, and I can flash a rom. When i flash the rom, I reboot the system, goes through boot screen etc, gets to choose locale i.e UK, USA, its the normal android start up, then it just crashes and reboots
SteveKeith said:
Thank you for helping! I think I may have worded my last reply badly. My recovery works, I'm currently on twrp, and I can flash a rom. When i flash the rom, I reboot the system, goes through boot screen etc, gets to choose locale i.e UK, USA, its the normal android start up, then it just crashes and reboots
Click to expand...
Click to collapse
well, your nearly there!
it might be worth trying 'fastboot erase cache' to flush out any gremlins
beanbean50 said:
well, your nearly there!
it might be worth trying 'fastboot erase cache' to flush out any gremlins
Click to expand...
Click to collapse
I installed the stock rom, worked fine. I used the TWRP as you said and the thread from Lord Nelson. If you would PM me your paypal email I could make a small donation to say thank you
SteveKeith said:
I installed the stock rom, worked fine. I used the TWRP as you said and the thread from Lord Nelson. If you would PM me your paypal email I could make a small donation to say thank you
Click to expand...
Click to collapse
no need for that, just happy to help you out
beanbean50 said:
no need for that, just happy to help you out
Click to expand...
Click to collapse
Thank you It's much appreciated
you can also try this recovery , its bad ass! http://forum.xda-developers.com/showthread.php?t=2201860
ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?
cantuluis said:
ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?
Click to expand...
Click to collapse
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.
cmerlyn said:
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.
Click to expand...
Click to collapse
I dont know what i was running originally. However i am back in business!!!
I found the superguide followed it regarding the RUU and luckily i got my phone to work again.
I want to try flashing the CM11 again, i am guessing that either i am doing something wrong or maybe TWRP is not working correctly on my phone and not flashing the rom as it should.
Any known issues with TWRP and the vivid? shall i try another recovery?
Are the following steps pretty much what i should do to flash it
1. factory reset
2. system reset
3. clearing caches
4. flash boot.img (i am s-on)
5. flash rom
6. flash gapps
any suggestion is welcomed
Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
it is 1.85.0025
additional info:
After recovering the phone i decided to lock the bootloader and start all over again. I re-root and then, instead of installing TWRP i used CWM and obviously, got a nand backup.
O tried flashing again CM11 and got the exact same results. Stuck in the initial HTC screen forever. Tried to restore my NAND Backup and the result was also exactly the same as before, phone would get the htc screen, then the beats audio and att animations and then will stuck onthe att screen forever.
This is weird, i must be doing something wrong here...
Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.
"Small mistake"
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments
I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.
Yuskow said:
I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.
Click to expand...
Click to collapse
Yes i do have access to bootlader and recovery, i actually was able to bring back to life the phone using RUU. So the issue now is not that the phone is bricked but that anything i try to load on it fails, being CM11 or even the NAND backup that i took with this same phone just after installing recovery, nothing seems to work.
I was googling around and so another person that had similar behavior on his vivid but didn't posted if he was ever able to fix it...
Yuskow said:
Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.
Click to expand...
Click to collapse
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?
You tried reading the following post: http://forum.xda-developers.com/showthread.php?t=2642575,? It's different from what I showed above, there describes another way to recover your vivid by projectisaac:fingers-crossed:
cantuluis said:
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?
Click to expand...
Click to collapse
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.
Yuskow said:
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.
Click to expand...
Click to collapse
ok guys i am now officially an idiot.
Problem came down to be that i was using the wrong boot.img, i didnt know that the correct one is INSIDE the rom zip. I tried it once more and now i am running CM11
thanks for your suggestions and sorry for taking your time on this newb learning experience
alosegon said:
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments
Click to expand...
Click to collapse
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
thanks for clarifying that
Glad you're up and running.
Btw, this ROM is amazing, so much better than the stock at crap
Sent from my Vivid 4G using Tapatalk