Hey guys my buddy asked me to root rom and install a kernel on his one v from virgin mobile. being as i have done this before to multiple phones i was happy to help. i unlocked the bootloader, rooted it. everything was smooth up til there. i did not put a rom on it yet because he urged me to install a kernel so he could overclock his one v. i was aprehensive but i did it anyway. now his phone wont work. im not surprised but i need to fix it. ive tried installing roms to make it work because the backup ive created in twrp wont boot. so im thinking its a kernel problem. no matter what rom i use it will either not boot it will freeze at the screen that says htc and with the red wording below it. or it will boot into the rom and then freeze or run for about 30 sec then restart and it will repeat this until it dies. ive looked everywhere for ways to get it back to stock ive flashe countless roms none work ive flashed many kernels and none work as well. please help. i would like to get it working on a rom with a working kernel but i will put it back to stock if i have to. any help is greatly appreciated. thank you for your time.
You could flash a ruu ....but the problem is you don't have your software number ...or you have to go to another Rom ...which will make the phone boot normally .but don't forget to flash its specific kernel ...if you don't so that the Rom won't boot
What he said. I recommend using the RUU to restore back to stock.
Re-reroot/unlock it, then read more on which kernel to use. You most likely are using the wrong kernel.
What rom are you using currently - ?
What Kernel did you flash - ?
What error do you get with TWRP - ?
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Nazz45 said:
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
Click to expand...
Click to collapse
Nazz45 said:
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Click to expand...
Click to collapse
Ok. That's good. You use the same ICS kernel with the same ICS roms. No need to keep reflashing. I wouldn't flash a JB rom using a ICS kernel though.
Use this zip - http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
1. Extract the Boot.img from that zip and Fastboot flash boot boot.img in Bootloader
2. Wipe everything. Factory Reset, Dalvik, and System.
3. Flash an ICS based rom, Sense, or CM9.
4. Flash this after rom to get wifi working the zip above or below to fix Wifi.
http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
Just ran the RUU and it did work everything is back to stock. the sprint RUU worked. i ran into a snag installing the Android SDK it wouldnt recognize that i had my Java JDK. even after messing with my registry it still wouldnt work so i just downloaded the x86 jdk and it worked. its unfortunate cuz now i have a jdk in x64 and x86 and its taking up space on my ssd. oh well i hope it doesnt mess with eclipse. i am now going to unlock the bootloader again and re root it and install probably cm9. thank you for all your help i will post again after i attempt to re unlock reroot and rom. thanks again
Related
I've been flashing ROMs on my One V for a while now. I've tried out the CM10 beta, CM9 beta, JMV4, Paranoid Android, most of them out there.
However, now they will not flash. Does anyone know why? I tried to go back to the CM9 ROM using the same file (I even re downloaded it) and it fails to flash.
I'm using TWRP 2.2 and have been. I even reflashed TWRP and reformated my SD. What went wrong?
because you are trying to flash cdma roms
cm10 is for cdma
ur device is primo u
soo u need to flash that only.. i mean the primo u roms
Sent from my HTC One V
I know the difference. I have PrimoC. I have Virgin Mobile in the US. I'm wondering why the ROMs that were working for me will no longer flash.
I'm not trying gsm ROMs for PrimoU
Alrighty. Lot of helpful people around here LOL
instead of being a sarcastic btard how about you expand on why they wont flash? errors? what?
That's exactly my question lol Why won't they flash? I flashed them and they worked fine. I went to flash to a different ROM and it says flash failed in red letters. I tried flashing a ROM that previously worked and it said flash failed. I know how to flash ROMs as I have been successful in the past with the same files. I ended up just flashing stock and unrooting. Do you think it's possible that it was bricked? As I"m not sure exactly what a bricked phone acts like because I've never had it happen.
jacobcummings said:
That's exactly my question lol Why won't they flash? I flashed them and they worked fine. I went to flash to a different ROM and it says flash failed in red letters. I tried flashing a ROM that previously worked and it said flash failed. I know how to flash ROMs as I have been successful in the past with the same files. I ended up just flashing stock and unrooting. Do you think it's possible that it was bricked? As I"m not sure exactly what a bricked phone acts like because I've never had it happen.
Click to expand...
Click to collapse
well cant answer about the issue but chill out ur phone not bricked...:silly::silly::silly::silly:
bricked looks as bricked sounds ur phone becomes dead and it remains nothing more than a piece of asooted plastics and metals!!
jacobcummings said:
That's exactly my question lol Why won't they flash? I flashed them and they worked fine. I went to flash to a different ROM and it says flash failed in red letters. I tried flashing a ROM that previously worked and it said flash failed. I know how to flash ROMs as I have been successful in the past with the same files. I ended up just flashing stock and unrooting. Do you think it's possible that it was bricked? As I"m not sure exactly what a bricked phone acts like because I've never had it happen.
Click to expand...
Click to collapse
Are you using the CDMA version of clockworkmod? That's the other issue sometimes faced.
No, I use TWRP instead of CWM. I never got the CWM to work right. TWRP has been great. I'm not sure what happened. I just relocked boot loader and went back to stock. I'll try everything again once there are things 100%.
Plus, it's hard for me to give up the Sense camera and weather widget! lol
Off topic ...
jacobcummings said:
No, I use TWRP instead of CWM. I never got the CWM to work right. TWRP has been great. I'm not sure what happened. I just relocked boot loader and went back to stock. I'll try everything again once there are things 100%.
Plus, it's hard for me to give up the Sense camera and weather widget! lol
Click to expand...
Click to collapse
Could you please send me TWRP, cause I also have problems with CWM and I can't download it, cause the link in the threat is dead. Maybe you have dropbox or something else to share it ...
What problems are you having with cwm? I'm not having any issues...
Sent from my One V using xda app-developers app
MasterTec said:
What problems are you having with cwm? I'm not having any issues...
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Herr you can see:
http://forum.xda-developers.com/showthread.php?p=30471406
Send from my HTC One V using xda app-developers app
Do you still need the recovery file? I didn't see this until now. I have it.
jacobcummings said:
Do you still need the recovery file? I didn't see this until now. I have it.
Click to expand...
Click to collapse
I got a new sdcard, now it works with TWRP and i think it would work with CWM also.
Thank you, no need at this moment.
help_rom
hey there;i am using the custom rom: my-onev-4fx_software number: 2.22.401.1
i wanted to install the official ruu; my first RUU was (asia_wwe_1.58.707.3)_ i have downloaded this rom;
i know that i cant install this now because of the lower image version; so i installed the stock recovery ( 1.58.707.3 ) and relocked bootloader;
then switched to bootloader and run ruu;
but when i tried to install the RUU, it gave me error 155; and when i saw my bootloader it was written:
the hboot is older
update fail
so what should i do?
mohammad0089 said:
hey there;i am using the custom rom: my-onev-4fx_software number: 2.22.401.1
i wanted to install the official ruu; my first RUU was (asia_wwe_1.58.707.3)_ i have downloaded this rom;
i know that i cant install this now because of the lower image version; so i installed the stock recovery ( 1.58.707.3 ) and relocked bootloader;
then switched to bootloader and run ruu;
but when i tried to install the RUU, it gave me error 155; and when i saw my bootloader it was written:
the hboot is older
update fail
so what should i do?
Click to expand...
Click to collapse
Ok, here's what I did when I went back to stock. Run that file that you downloaded for your area. After it's done running, open up a folder or internet explorer and type %temp% That file that you ran created a couple of temporary folders and inside one of those folders you'll see a zipped file that says ROM. Copy that ROM file and paste it on your desktop, open it up and take out the recovery image and boot image. Flash the stock recovery and boot image files and then relock your bootloader and then continue on with the first downloaded file you ran.
If you locked your bootloader before flashed the stock recovery and boot image I'm not sure what to do.
mohammad0089 said:
hey there;i am using the custom rom: my-onev-4fx_software number: 2.22.401.1
i wanted to install the official ruu; my first RUU was (asia_wwe_1.58.707.3)_ i have downloaded this rom;
i know that i cant install this now because of the lower image version; so i installed the stock recovery ( 1.58.707.3 ) and relocked bootloader;
then switched to bootloader and run ruu;
but when i tried to install the RUU, it gave me error 155; and when i saw my bootloader it was written:
the hboot is older
update fail
so what should i do?
Click to expand...
Click to collapse
Not sure whether you solved your problem or not.
If not.. use the latest official RUU - http://forum.xda-developers.com/showpost.php?p=30994089&postcount=121
J hope u have a copy of ur nandroid..... now just revert to stock...then try reflashing
Sent from my One V using xda app-developers app
cybervibin said:
J hope u have a copy of ur nandroid..... now just revert to stock...then try reflashing
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I'm all good now. I think the problem was my kernel was JB and I was trying to flash a ICS ROM. Not sure though because I just ended up starting completely over and I can flash anything now.
Good than...kiss kernels I recommend
Sent from my One V using xda app-developers app
Hi guys!
Noob here. Searched through other threads but all i found is making CWM backups as well as flashing the kernel (boot.img)
Would like to know if there is a way to get the currently running boot.img?
I'm on a stock rom, unlocked booloader and rooted. Reason I need this is for easy/quick switching to stock.
I used a boot.img that was posted here on one of the threads but it seems to be for a different region (though it still worked as i was running the correct recovery file plus I had to do all the steps again). In case i have to go back to stock again this would be a faster way i think.
make a nandroid backup of ur stock rom
ul get yourself a stock kernel
or else get ur ruu available and extract urslf
Sent from my One V
paarthdesai said:
make a nandroid backup of ur stock rom
ul get yourself a stock kernel
or else get ur ruu available and extract urslf
Sent from my One V
Click to expand...
Click to collapse
Hahaha. I'm such a noob I didn't realize it's also backing up boot.img
Many thanks, paarthdesai!
Hello Guys,
I am currently on Shpongle and want to move back to stock. Reason being frequent hanging and sluggishness. I have installed the swap performance updates and greenify, but still at times, the phone gets the better of my patience.
MY Questions:
1. How do I go back to stock? I dont think I have the stock nandroid backup. I have the Unlock_code.bin that was sent by HTC.
2. Is there a lightweight Sense ROM? I like the camera, and looks, but I dont like the friendfeed and stuff.
Thanks.
thetuxracer said:
Hello Guys,
I am currently on Shpongle and want to move back to stock. Reason being frequent hanging and sluggishness. I have installed the swap performance updates and greenify, but still at times, the phone gets the better of my patience.
MY Questions:
1. How do I go back to stock? I dont think I have the stock nandroid backup. I have the Unlock_code.bin that was sent by HTC.
2. Is there a lightweight Sense ROM? I like the camera, and looks, but I dont like the friendfeed and stuff.
Thanks.
Click to expand...
Click to collapse
You can use myONEv RC9.5FX+ or Ignorance X for a lighter Sense ROM. You can remove the bloatware with titanium backup as well.
MameTozhio said:
You can use myONEv RC9.5FX+ or Ignorance X for a lighter Sense ROM. You can remove the bloatware with titanium backup as well.
Click to expand...
Click to collapse
Ignorance X does seem nice. Can I use the stock skin with it?
thetuxracer said:
Ignorance X does seem nice. Can I use the stock skin with it?
Click to expand...
Click to collapse
yes it won't look as nice though, since it has internal theming for Ignorance X skin.
MameTozhio said:
yes it won't look as nice though, since it has internal theming for Ignorance X skin.
Click to expand...
Click to collapse
Thank you. Its about to complete downloading. I will install it soon. Will use Titanium Kernel.
Thanks MameTozhio, you are very helpful!
A few questions about it
Sorry for my mistake, please remove it
Hi people.
My device is curretly like this:
N9005
Knox 0x1
TWRP recovery
Stock Kernel
Stock ROM 4.4.2
I would like to return completly to stock. I know I won't be able to be Knox 0x0 again but I want the stock recovery, kernel and ROM.
My question is: can I simply restore the firmware in Kies to get back to stock (including the recovery)?
Stock Rom: http://www.idroidspace.com/primou-original-stock-rom-for-htc-one-v-android-4-0-3-ics/
Stock Kernel and Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1221449&d=1343236979
I can't tell you if this stock rom is the original one by htc or with some modifications, I only found it and there are much more ruu uploads out there.
jonas2790 said:
Stock Rom: http://www.idroidspace.com/primou-original-stock-rom-for-htc-one-v-android-4-0-3-ics/
Stock Kernel and Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1221449&d=1343236979
I can't tell you if this stock rom is the original one by htc or with some modifications, I only found it and there are much more ruu uploads out there.
Click to expand...
Click to collapse
Thanks for the links. I have a problem. I decided I want to go back to comfortable stock ROM. I used a custom ROM, on a rooted HTC One V (GSM - Primo U). I followed the intructions: First I installed stock kernel and stock recovery. After I relocked the bootloader. I downloaded the RUU file according to my region (there are 4 european RUU version???). I connected my phone to computer and run the downloaded setup and followed the steps. Only after I started the update process, the progress bar stopped moving (before entering bootloader - the HTC One V didn't reboot into bootloader) and I got an error (155) message. What may be the problem? I have tried the all RUU files according to my region.
Thanks in advance,
Tejcsi
Tejcsi said:
Thanks for the links. I have a problem. I decided I want to go back to comfortable stock ROM. I used a custom ROM, on a rooted HTC One V (GSM - Primo U). I followed the intructions: First I installed stock kernel and stock recovery. After I relocked the bootloader. I downloaded the RUU file according to my region (there are 4 european RUU version???). I connected my phone to computer and run the downloaded setup and followed the steps. Only after I started the update process, the progress bar stopped moving (before entering bootloader - the HTC One V didn't reboot into bootloader) and I got an error (155) message. What may be the problem? I have tried the all RUU files according to my region.
Thanks in advance,
Tejcsi
Click to expand...
Click to collapse
First, install a custom recovery again. Then do a full wipe and install the rom you downloaded (PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip or PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_LITE.zip) with the custom recovery like you would install a custom rom. Then reboot to fastboot and flash boot.img (not boot-signed.img because this didn't work for me). Try to reboot and if everything works you may install recovery_signed.img, but this is only useful for ota updates, which obviously the hov doesn't get anymore.
jonas2790 said:
First, install a custom recovery again. Then do a full wipe and install the rom you downloaded (PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip or PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_LITE.zip) with the custom recovery like you would install a custom rom. Then reboot to fastboot and flash boot.img (not boot-signed.img because this didn't work for me). Try to reboot and if everything works you may install recovery_signed.img, but this is only useful for ota updates, which obviously the hov doesn't get anymore.
Click to expand...
Click to collapse
Thanks. Yesterday I've installed the PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip ROM, everything O.K., but there is no WIFI on my phone. So I decided to use the RUU. So I don't use boot_signed.img. Which boot.img can I use. Do you send me one?
Tejcsi said:
Thanks. Yesterday I've installed the PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip ROM, everything O.K., but there is no WIFI on my phone. So I decided to use the RUU. So I don't use boot_signed.img. Which boot.img can I use. Do you send me one?
Click to expand...
Click to collapse
the boot.img inside the zip file
jonas2790 said:
the boot.img inside the zip file
Click to expand...
Click to collapse
So if i use the boot.img file inside the primou_europe_2.22.401.1_stock_rooted_odex_full.zip file, the RUU can reboot the ONE V into bootloader?
Tejcsi said:
So if i use the boot.img file inside the primou_europe_2.22.401.1_stock_rooted_odex_full.zip file, the RUU can reboot the ONE V into bootloader?
Click to expand...
Click to collapse
I don't really understand your problem. If you want to reboot into bootloader just use adb reboot bootloader.
ive lost my computer HD and lost a bunch of stuff. as for ace ii related things, ive lost mg2 firmware, temp root, samsung drivers, custom recoveries and roms. custom recoveries and roms arent much of an issue since ace2nutzer, chronomonochrome and sergeyl are still actively developing. as for stock firmware and temp root, i cant seem to be able to find a good download site (site that supports resuming/pausing)
id like to humbly request an upload for the barebone basics such as stock firmware, temp root, odin and all the other you-need-these-to-install-custom-rom stuff to an easy to use download service (like google drive)
*EDIT*
my phone is currently out of order and it seems i need to reflash using odin. i was using ace2nutzers cm11 and ran into some issues. then i tried flashing chronokernel 4.4.2 when trying to upgrade to ace2nutzers more recent cm11 build, but im facing philz recovery error 'status 7' when trying to flash anything. it is currently systemless, with only recovery mode (philz) and download mode working
*EDIT2*
in philz it is stating my internal storage as sdcard1 and not 0. my external is called sdcard0
If you have ace2nutzer's kernel, install it by recovery, power off and boot on recovery again.
Then install the ROM you want.
I've never faced status 7 error with CWM recovery 6.0.5.0 of this kernel.
me too, only TWRP didnt work once, and chrono admitted it was a bug he couldnt fix.
i opened up the rom on my friends PC and it turned out it was a corrupted archive. CWM flashed it anyways and that was why i lost the OS. i dont understand why i couldnt just reflash a newly downloaded and checked archive but that too didnt work. i also tried installing the kernel again, rebooted and tried installing the rom again and nope. then removing the whole assert thing under updater-script, it only worked once when installing a kernel. annnd finally after a sleepless night i tried adb sideloading and fastboot recovery, it was a bad decision as now even recovery mode doesnt work -.-
theres a good thing though, download mode still works. im hoping someone can upload a stock rom somewhere safe. i read but dont understand why people say mg2 is preferred.
Mg2 is the newest base band but for your target it doesn't matter right now.
What model do you have, 8160 or 8160P with NFC?
sorry for the late reply, I needed something to get my mind off my old friend
its a standard ace ii, non P/L version
fonzacus said:
sorry for the late reply, I needed something to get my mind off my old friend
its a standard ace ii, non P/L version
Click to expand...
Click to collapse
Just install by Odin Russian gingerbread following instructions from YouTube video below.
After this, you'll have the phone like a brand new taken from the factory (at least the firmware).
Then, install any jelly bean stock you want.
And finally you can install the custom ROM you want.
Download Russian gingerbread from this link:
https://www.dropbox.com/s/3okawqmw8gbazns/I8160XXLK6.rar?dl=0
huge kudos, its all running just fine again with ace2nutzers cm11
im hoping dropbox wont die/expire
fonzacus said:
huge kudos, its all running just fine again with ace2nutzers cm11
im hoping dropbox wont die/expire
Click to expand...
Click to collapse
Don't worry about that, I uploaded this Dropbox link and I probably won't retire it for a long time.
This is the only 3 part stock firmware for GT-i8160 and it's the only ROM that can repair almost anything we "do" the phone.
Whatever info the Sprint techs put into your device in order for it to get service from their network, that information was cleared when I wiped /data/ and /cache/.
Shouldn't that information be saved somewhere safer?
I am now unable to get service. What do?
RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!
blksith0 said:
RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!
Click to expand...
Click to collapse
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.
blksith0 said:
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.
Click to expand...
Click to collapse
That's not correct. As mentioned several times here on xda the boot.img of 3.35.x firmware-based roms is not compatible with 3.y firmware versions where y is not the same as 35. If you're trying to use a non-sense-based custom rom (e.g. CM) you need to flash thicklizard's mono kernel. For sense-based roms you need to re-flash the stock boot.img of your currently installed firmware. After that you can use the chosen rom without problems.
Sent from my HTC One M9 using XDA Labs
So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?
blksith0 said:
So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?
Click to expand...
Click to collapse
No and no. Viper is using a boot.img for 3.35.x. You need the boot.img of your stock firmware. You could for example back up the stock boot.img with TWRP before you delete your stock rom and restore it after you flashed the viper rom. However, since the latest viper version is based on an HTC 10 port you still might face issues. Viper 4.3 on the other hand should be working fine since it's based on the HTC One M9. I'd suggest you to ask in the viper thread whether additional steps are needed for getting viper 5.3 to work on your phone.
Edit @blksith0: Sorry, I totally forgot that the viper rom has a special aroma installer with several options for the different branded M9 versions when I wrote this post. Although you might not be using the device on the sprint network you still need to choose the optimisations for sprint. Those options are made for being able to support the different firmware versions and not for the carrier you're actually using. Because of this flashing the stock boot.img shouldn't be needed in case of the viper rom.
Sent from my HTC One M9 using XDA Labs