[Q] Can't use any other ROM after flashing mg2195's CM10 - HTC Vivid, Raider, Velocity

Ok so for shiz and giggles i wanted to try out cm10 so i did.. now that i've tested it and tried to recover from a back up and tried other roms but they all get stuck in a boot loop. tried flashing all different kinds of kernels including faux's. although i didnt see this as a thing that could be wrong with CM10 but i cant mount the phone anymore so i've been downloading different roms straight to the phone.. is there anybody out there that can help me figure out how to fix this? i still havnt tried the RUU so i'm downloading that now but i figured it may take awhile for anyone to answer so i posted this first. i'm technically a newb to this whole android rooting and flashing roms thing but i'm a software engineer so i'm not completely out of my element. edit: my carrier is ATT btw.. also i used the AIO toolkit 2.1 thing to do all the rooting and flashing CWM 5.5.0.4

RujinXERO said:
Ok so for shiz and giggles i wanted to try out cm10 so i did.. now that i've tested it and tried to recover from a back up and tried other roms but they all get stuck in a boot loop. tried flashing all different kinds of kernels including faux's. although i didnt see this as a thing that could be wrong with CM10 but i cant mount the phone anymore so i've been downloading different roms straight to the phone.. is there anybody out there that can help me figure out how to fix this? i still havnt tried the RUU so i'm downloading that now but i figured it may take awhile for anyone to answer so i posted this first. i'm technically a newb to this whole android rooting and flashing roms thing but i'm a software engineer so i'm not completely out of my element. edit: my carrier is ATT btw.. also i used the AIO toolkit 2.1 thing to do all the rooting and flashing CWM 5.5.0.4
Click to expand...
Click to collapse
My cm10 is not the problem...sometimes recoveries go bad on this phone...try downloading a recovery and flashing it...if it doesn't work just wait for that ruu
Sent from my SGH-I997 using Tapatalk 2

mg2195 said:
My cm10 is not the problem...sometimes recoveries go bad on this phone...try downloading a recovery and flashing it...if it doesn't work just wait for that ruu
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
i didnt mean anything by it.. it just seemed that it was the problem what with i couldnt use any other rom anymore.. other than the calls not working it looks very pretty.. very snappy.. cant wait for more updates.. so yeah apparently i'm a retard because i was seriously up all night trying different things.. dead tired.. i never thought to try a rom that i previously got working properly.. so i just did that and it works.. so basically all those other roms i tried wernt flashing correctly or maybe i was doing something wrong in the process that made them boot loop.. but now i know backups on this phone go bad.. thanx for the tips.. and your rom..

RujinXERO said:
i didnt mean anything by it.. it just seemed that it was the problem what with i couldnt use any other rom anymore.. other than the calls not working it looks very pretty.. very snappy.. cant wait for more updates.. so yeah apparently i'm a retard because i was seriously up all night trying different things.. dead tired.. i never thought to try a rom that i previously got working properly.. so i just did that and it works.. so basically all those other roms i tried wernt flashing correctly or maybe i was doing something wrong in the process that made them boot loop.. but now i know backups on this phone go bad.. thanx for the tips.. and your rom..
Click to expand...
Click to collapse
alot of vivid owners had/having problem with cwm , i avioded it. and use the other recover that was in the all-in-one tool .. think the name is WCX recovery .. and i have no issue

[email protected] said:
alot of vivid owners had/having problem with cwm , i avioded it. and use the other recover that was in the all-in-one tool .. think the name is WCX recovery .. and i have no issue
Click to expand...
Click to collapse
same- its also in the WCX root pack in the superguide

Related

[Q] Seriously? Why does my new captivate constantly brick?

Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device

Every ROM I flash gets stuck on the flash screen. Thoughts?

I just bought a used Hero as a temporary phone and I'm trying to get off the stock rom. I rooted the phone and flashed a MIUI rom. It got stuck on the splash screen during boot. Not feeling like dealing with it, I just ended up RUUing it. Then I rerooted it and tried another rom...same deal. Now I back to stock again. Any thoughts on how to fix this?
Thanks
You didn't firate anything, did you?
Try manualy flashing the boot.img in the rom from fastboot. Sometimes thats the problem.
Regards
Sent from my Galaxy Nexus using XDA
oohaylima said:
You didn't firate anything, did you?
Click to expand...
Click to collapse
Urban dictionary tells me that means fake pirating...? If that's the case, no. I haven't even installed anything let alone log into my google account.
EDIT: I'm guessing you meant firerat. Nope, I haven't messed with anything.
flakesdk said:
Try manualy flashing the boot.img in the rom from fastboot. Sometimes thats the problem.
Regards
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Good idea. I'd need abd for that though to run the commands right? I'm really trying hard to avoid installing it on my computer.
Why ?? If your going to be modding your phone s-off,eng-bootloader & adb are all tools you will definitely need. If not then you may have a few headaches down the line if something goes wrong.
#Root-Hack_Mod*Always\
laie1472 said:
Why ?? If your going to be modding your phone s-off,eng-bootloader & adb are all tools you will definitely need. If not then you may have a few headaches down the line if something goes wrong.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I won't be doing anything beyond flashing a custom rom.
I just dug up my Hero. It had CM6 previously. I tried flashing an updated ROM and it does not get past the HTC logo. I tried 4 different ROMs. Using CMW recovery. Wipe/Format all...and nothing.
Yeah I'm completely out of ideas. I may just have to suck it up and install adb.
Which version of CWM are you running? I've used 2.5.0.1 for all of my ROMs and never had a problem. I should have the zip to flash through recovery and the HERCIMG flashable through HBOOT if you wanna try.
Sent from my PC36100 using xda premium
Adb is a breeze to install. Takes less than 20 min. Pm me if and when you wanna set it up, and believe me when I say you will not regret it. Adb makes modding your phone a little easier.
#Root-Hack_Mod*Always\
scl23enn4m3 said:
Yeah I'm completely out of ideas. I may just have to suck it up and install adb.
Click to expand...
Click to collapse
What radio do you have? I remember people having issues when using the older radio (.27) instead of the newer (.29). Then again, it might not make a difference at all either. Just a thought.
i second drunkpilots radio idea, thats what gave me a headache for an hour the other night wondering why my cm7 wouldnt boot, updated to newest sprint radio and bam booted right up
Alright I just upgraded my radio. What's the best/easiest way to root it from here since I'm back to stock now?

[Q] Velocity 4G (VODAP120) boot loop / can't RUU

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.

[Q] Problems Installing - ★AMCHA Rom v5.00

So I've tried installing this half a dozen times, I did a full wipe I'm using the i9305 and installing this using both kernel options for the knox based bootloader, after it completes installation it says complete, reboot the phone and I end up stuck at the Samsung Galaxy s3 black screen and it never boots into the os.
I noticed while installing this it installs some modem not sure what one it is but I thought perhaps that was the issue, to installed went straight into download mode and flashed a optus modem i've been using for my phone rebooted but still same issue.
Would appreciate some help with this, I've tried searching the thread for similar issues no such luck.
Thanks
Demonic Wraith said:
So I've tried installing this half a dozen times, I did a full wipe I'm using the i9305 and installing this using both kernel options for the knox based bootloader, after it completes installation it says complete, reboot the phone and I end up stuck at the Samsung Galaxy s3 black screen and it never boots into the os.
I noticed while installing this it installs some modem not sure what one it is but I thought perhaps that was the issue, to installed went straight into download mode and flashed a optus modem i've been using for my phone rebooted but still same issue.
Would appreciate some help with this, I've tried searching the thread for similar issues no such luck.
Thanks
Click to expand...
Click to collapse
maybe your using a old recovery?
MaHo_66 said:
maybe your using a old recovery?
Click to expand...
Click to collapse
Thanks but it's not that, I wasn't even aware of having to use the newer one for the recovery till recently and have been using the one for the old recovery even tho I have the new one... either way, I tried installing both the new and old recovery's same results.
Demonic Wraith said:
Thanks but it's not that, I wasn't even aware of having to use the newer one for the recovery till recently and have been using the one for the old recovery even tho I have the new one... either way, I tried installing both the new and old recovery's same results.
Click to expand...
Click to collapse
i see, well your 2 posts away from being able to post in development thread, you will get better help in rom thread try a full wipe anyway and install the rom with default aroma settings, maybe the problem lies in some setting you change in aroma installer..
MaHo_66 said:
i see, well your 2 posts away from being able to post in development thread, you will get better help in rom thread try a full wipe anyway and install the rom with default aroma settings, maybe the problem lies in some setting you change in aroma installer..
Click to expand...
Click to collapse
True, that could be it, except i thought of that myself and just hit next next next to the end and hit install to see if it would help matters it didn't. Yeah I tried posting there to begin with, but even if your an advanced person you have to post here first lol fun times
I did think maybe there's a newer version of philz recovery out and mine just buggers it up some how it offers to install 6.41.6 not sure what my version is.. it crossed my mind tho but I wouldn't presume that's the most likely of causes.
Demonic Wraith said:
True, that could be it, except i thought of that myself and just hit next next next to the end and hit install to see if it would help matters it didn't. Yeah I tried posting there to begin with, but even if your an advanced person you have to post here first lol fun times
I did think maybe there's a newer version of philz recovery out and mine just buggers it up some how it offers to install 6.41.6 not sure what my version is.. it crossed my mind tho but I wouldn't presume that's the most likely of causes.
Click to expand...
Click to collapse
hmm.. well philz 6.41.6 is the latest one a.t.m and roms these days need up to date recovery so you can give it a shot if you are not on philz yet. here is the latest one http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
flash it with odin then try again, hopefully this will fix your problem
MaHo_66 said:
hmm.. well philz 6.41.6 is the latest one a.t.m and roms these days need up to date recovery so you can give it a shot if you are not on philz yet. here is the latest one http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
flash it with odin then try again, hopefully this will fix your problem
Click to expand...
Click to collapse
Yeah unfortunately that didn't work either, was worth a shot tho now I can post in the proper place.
Demonic Wraith said:
Yeah unfortunately that didn't work either, was worth a shot tho now I can post in the proper place.
Click to expand...
Click to collapse
haha yeah man

rom flashing help

Ok so I rooted my phone and its rooted at&t us. when i go to recover i don't see any back up options,every time i flash from my sd card it wipes my phone out iv'e flashed roms on my old phone so its not like i don't know what i'm doing. can anyone help am i doing something wrong that's why it's not flashing thanks in advance.
tdogin said:
Ok so I rooted my phone and its rooted at&t us. when i go to recover i don't see any back up options,every time i flash from my sd card it wipes my phone out iv'e flashed roms on my old phone so its not like i don't know what i'm doing. can anyone help am i doing something wrong that's why it's not flashing thanks in advance.
Click to expand...
Click to collapse
What recovery are you using, and what are you trying to flash?
I have rom manger and twarp none of them seem to be working I tried superuser from rom manger wont work also used unity rom every time i flash it wipes it out and i cant flash a backup cause theirs no option
tdogin said:
I have rom manger and twarp none of them seem to be working I tried superuser from rom manger wont work also used unity rom every time i flash it wipes it out and i cant flash a backup cause theirs no option
Click to expand...
Click to collapse
Well I'm taking it you haven't read up too much on the status of the S5 for AT&T and Verizon, but the bootloader is locked and encrypted with no known workaround so you can't flash a custom recovery.
The only option for recovery is Safestrap. http://forum.xda-developers.com/showthread.php?t=2794087
tdogin said:
Ok so I rooted my phone and its rooted at&t us. when i go to recover i don't see any back up options,every time i flash from my sd card it wipes my phone out iv'e flashed roms on my old phone so its not like i don't know what i'm doing. can anyone help am i doing something wrong that's why it's not flashing thanks in advance.
Click to expand...
Click to collapse
You really need to do a lot more reading I'm not being rude but by what you're posting leads me to believe you've jumped into the AT&T S5 and didn't know what you were getting into. Every device is completely different. If I were you I'd try to do quite a bit more research before going any further before you brick your device I'd start here.
http://forum.xda-developers.com/showthread.php?t=2697270
"You stay classy San Diego"
Sent from my XKRom Gold LimiTed powered A900G

Categories

Resources