Develop Bugs

[Q] Root didn't work right, unroot won't work, wifi won't work, sweet.

I'll make this short and sweet.
i've rooted many times before, never run into anything like this.
I rooted my SGS2 E4GT with odin. used this forum.
http://forum.xda-developers.com/showthread.php?t=1265429
after root copied rom to sd and rebooted into recovery and it didn't reboot into clockwork recovery and it said E:failed to mount /sdcard (Unknown error: 0)
rebooted and wifi doesn't work now. used rom manager to try and install clockwork recovery but still wouldn't boot into clockwork on reboot.
unrooted using this
http://epic4gtouchroot.com/epic-4g-touch-unroot/how-to-unroot-epic-4g-touch/
then rerooted using this
http://forum.xda-developers.com/showthread.php?t=1342728
now wifi still doesn't work, still won't boot into recovery using clockwork
i just want to get it back to stock E4GT unrooted and working but now when i try to adb remove it gives me read only.
i'm so frustrated and just want it to work, rooted or not.
so plz any advice helps

well first off I have never used adb. second don't use that one click crap. these videos should be all you need. forum.xda-developers.com/showthread.php?t=1268548&highlight=zedomax also do not use rom manager to put in cwm. it doesn't work. let us know if you need anymore help man.
---------- Post added at 07:47 AM ---------- Previous post was at 07:37 AM ----------
also I am assuming you are still on the eg30. well tryvthis stock repacked kernel from chris41g. chris41g.devphone.org/index.php?dir=EpicTouch%2FStock+Repack%2FEG30%2FCWM5%2F use the. tar.md5 file in odin in the section pda. do NOT put it anywhere else. also make sure the only box checked is reboot. wait for odin to be done. after your phone reboots you can power down. hold power and volume up until you get into cwm.

You can also take the stock .tar that's floating around in the development section and flash it using mobile odin.

Thanks guys ill troubleshoot today and see if I can get ot working. I usually dont use the one click roots im used to rooting manually but I thought id try somethin different. Didnt work out ofcourse. I can successfully flash back to stock ROM using odin its just deleting the root thats the problem.
Sent from my SPH-D710 using XDA App

ghostin0hs said:
I can successfully flash back to stock ROM using odin its just deleting the root thats the problem.
Click to expand...
Click to collapse
I don't understand this statement. If you can successfully flash back to stock ROM doesn't that delete the root (and all your other changes) putting you back at stock? Perhaps you aren't being aggressive enough with your ODIN flash and you could use a package that flashed more components?

There are Odin tars that don't delete /data get one that does and you're fine leave it on sd forever just in case .....
Sent from my SPH-D710 using xda premium

Basically I followed the unroot tutorial. I can flash the tar it gives me through Odin but it doesnt delete superuser or fix the problems. It then tells me to use adb to remove su but I can't do to read only error
If anyone has a link for a correct tar to flash or a correct unroot tutorial let me know.
Sry guys I hate to be one of those annoying ppl posting for help but I spent all yesterday afternoon trying to figure this out
Sent from my SPH-D710 using XDA App

I think you are better off using the ODIN tar files here (they will put modem, kernel, and ROM back to stock and reset your data):
ODIN [EG30/EK02/EL13/EL26/EL29]
Multi-upload links are up and down recently but if you give me the version you need I can find a link for you.

Ok thanks so just flash all of those over with Odin through pda 1 by 1?
And version of what?
Sent from my SPH-D710 using XDA App

ghostin0hs said:
Ok thanks so just flash all of those over with Odin through pda 1 by 1?
And version of what?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Just flash whichever version you want, not all of them.
The phone shipped with EG30.
EK02 is the first OTA update.
EL29 is probably going to be the 2nd OTA update.
The other ones are leaks that didn't become official updates.
I would start with EK02 and see how that works for you before doing anything else.

k im flashing EK02 now. so just flashing this with odin will remove root and superuser?

ghostin0hs said:
k im flashing EK02 now. so just flashing this with odin will remove root and superuser?
Click to expand...
Click to collapse
Yes. In your case, I would recommend backing up, then using the "Full" version that resets your user data. If you did the NoData version, that is fine too. Just backup and perform a ##786# reset from the dialer. You can get your MSL by typing "getprop ril.MSL" in a terminal window. It is case sensitive and Swype keyboard likes to capitalize "I" even though you told it not to.
Don't start restoring stuff until you use the stock system for a couple of hours and verify everything works.

ok cool it worked. thanks again man. im gonna let it chill stock for a while but everything is working fine for now. now once i get around to wanting to root it again, got any good forums i can use? i'm kinda fed up with odin at this point to be honest sijce this is the first time i've ever used it to root and it caused all this haha, so i would prefer to do it manually. so any good links would be appreciated.

Look at the Auto Root sticky in the development section.
ODIN itself isn't the issue (you'll be appreciative of ODIN if you have a bad install). The issue is what content you are giving to ODIN.

Alright I'll try but the auto root is what I used the second time to root and it didn't work
Sent from my SPH-D710 using XDA App

ghostin0hs said:
Alright I'll try but the auto root is what I used the second time to root and it didn't work
Click to expand...
Click to collapse
Instead of saying it didn't work, choose Option F to enable the scroll buffer, then run Option A and post the log between BEGIN LOG and END LOG.

k did auto root. root successful, wifi and everything works. superuser is installed, and cwm. but when i reboot into recovery i see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and can't flash rom. i researched this error and everyone says toggle signature verification. i go into apply update from sd and i have no option to toggle. so ya.

ghostin0hs said:
k did auto root. root successful, wifi and everything works. superuser is installed, and cwm. but when i reboot into recovery i see this:
and can't flash rom. i researched this error and everyone says toggle signature verification. i go into apply update from sd and i have no option to toggle. so ya.
Click to expand...
Click to collapse
that would be the stock recovery you are on. you need a new kernel that has cwm installed on it. flash one of those such as rogue gunslinger through odin. remember to odin the. tar.

mmk went here
http://forum.xda-developers.com/showthread.php?t=1341564
downloaded tar
odin gives me this error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> rogue_ET-1.4.0-gunslinger-odin.tar.md5 is invalid.
<OSM> End...

1st make sure root is installed properly, if not follow this method: http://www.youtube.com/watch?v=Be2evusAwOM
Once you have root, you need clockwork mod, follow this method to install clockworkmod with your current set up: http://www.youtube.com/watch?v=jZRnH-_XZmM

Cwm touch based - rommanager

Touch based cwm for sgs 2 is possible.
Found this on the cwm website.
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.1.5-galaxys2.zip
Rename zip to recovery-update.zip and place it in /clockworkmod/ folder.
And boot to recovery from rommanager.
Its only temp flash recovery as normal for rommanager.
Can also be downloaded and flashed via rommanager but that requires premium account.
Kudos to the cwm guys for getting this done.
Should probably say that my from flashing ocd has gone straight up.
Sent from my GT-I9100 using Tapatalk

What is thee extra over 5.0....?
Sent from my GT-I9100 using XDA App

marcel112 said:
What is thee extra over 5.0....?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Touch based cwm

have a look
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Following the steps I did not start the new recovery

some informations
e:missing bitmap password_highlight (its come verry much)
than
-- installing package ...
finding update package ...
opening update package ...
verifyng update package ...
e: failed to verify whole-file signature
e: signatureverification failed
installation aborted

So its probally not signed, try disable singnature verify and then flash again

DirkTeur Velserbroncx said:
So its probally not signed, try disable singnature verify and then flash again
Click to expand...
Click to collapse
How can I do that?
Sent from my Samsung Galaxy SII using Tapatalk

ghizzo22 said:
Following the steps I did not start the new recovery
Click to expand...
Click to collapse
Make sure that you haven't recovery-update.zip within this folder yet...
That was my problem..I deleted this file,uploaded new file and it's working great

DonChulio25 said:
some informations
e:missing bitmap password_highlight (its come verry much)
than
-- installing package ...
finding update package ...
opening update package ...
verifyng update package ...
e: failed to verify whole-file signature
e: signatureverification failed
installation aborted
Click to expand...
Click to collapse
I got this problem to.
Equineq said:
Make sure that you haven't recovery-update.zip within this folder yet...
That was my problem..I deleted this file,uploaded new file and it's working great
Click to expand...
Click to collapse
I still got the problem like above?
Sent from my Samsung Galaxy SII using Tapatalk

Hi Guys,
Need a bit of help here.
I bought the clockworkmod touch yesterday, I flashed it, but when I went into recovery it wasn't touch, so I wiped cache, dalvik cache etc...and then isntalled the update.zip to no avail it said "E: failed to verify whole-signature", I tweeted @clockworkmod, and he said it was because I was using SpeedMod Kernel.
So I moved over to Siyah kernel, installed that fine and restored my data/cache using CWM when it booted. I then try to flash ClockworkMod Touch through ROM Manager, the green bar fills, and then says "Succesfully downloaded ClockworkMod recovery!"
I click ok, and then go to "reboot into recovery" I'm presented with red text that says:
E:missing bitmap password_highlight (code-1),
E: missing bitmap password_confirm_45 (code-1),
E: Missing Bitmap password_retry_45 (code-1)..."
I'm then presented with:
Installing Package...
Opening Update Package
Verifying Update Package...
E:Failed to verify whole-file signature
E:Signature Verification failed.
Installation aborted
I've then gone into three button method, and tried to apply, /sdcard/update.zip and it comes up:
Finding update package
Opening update package
E: Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
I'm running the following setup:
Model:GT-I9100
Android: 2.3.5
Baseband version: I9100XXK14
Kernel Version: [email protected] #294
Build number: Gingerbread.XWKJ1
I would like it if I could get this fixed without using Odin, as i'm at work most of the time and because of some stupid drive encrytion I can't put my phone in without encrypting it, BSkyB's rules apparently. I have tomorrow off, so I can if neccesary boot my laptop up and fiddle with odin.
Just wanna get this sorted, I purchased this and wanna use it.
Any help is much appreciated.

Nagarebozhi said:
I got this problem to.
Sent from my Samsung Galaxy SII using Tapatalk
Click to expand...
Click to collapse
Hey
As i said before,this recovery should be integrated into the kernel itself
If u flash this then its a fakeflash
It would disappear after a reboot
And toggle signature verification to flash this file and be sure u are flashing this from CWM recovery and not the stock recovery...

is there any way to get cwm recovery touch everytime? I want it after reboot as well...

sahibunlimited said:
Hey
As i said before,this recovery should be integrated into the kernel itself
If u flash this then its a fakeflash
It would disappear after a reboot
And toggle signature verification to flash this file and be sure u are flashing this from CWM recovery and not the stock recovery...
Click to expand...
Click to collapse
The fakeflash doesn't work ether.
Sent from my Samsung Galaxy SII using Tapatalk

Nagarebozhi said:
The fakeflash doesn't work ether.
Sent from my Samsung Galaxy SII using Tapatalk
Click to expand...
Click to collapse
That's what i said
U can't flash this CWM recovery
This should be included in the kernel(as Doomlord have included in x10 custom kernel)
So wait for a custom kernel for stock that include this...
And the Most important tip before u start flashing ur phone
BACKUP UP UR EFS BEFORE FLASHING PHONE,sometimes after flashing roms u loose imei and signal so restoring EFS will solve that..
Backup EFS using H-TOOL from market

sahibunlimited said:
That's what i said
U can't flash this CWM recovery
This should be included in the kernel(as Doomlord have included in x10 custom kernel)
So wait for a custom kernel for stock that include this...
And the Most important tip before u start flashing ur phone
BACKUP UP UR EFS BEFORE FLASHING PHONE,sometimes after flashing roms u loose imei and signal so restoring EFS will solve that..
Backup EFS using H-TOOL from market
Click to expand...
Click to collapse
Didn't find any H-TOOL on market do you have a link?
Edit: did you meant ktool?
Sent from my Samsung Galaxy SII using Tapatalk

4.0.2 (ICL53F) TO 4.0.4 (IMM76K) Error Status 7 in CW Recovery on Verizon Nexus

I am having all sorts of problems trying to update to 4.0.4 (IMM76K) from 4.0.2 (ICL53F) on my Verizon Galaxy Nexus. I have seen this discussed across multiple threads with not clear solution. I wanted to start a thread dedicated to this issue. Here is what is happing.
I started with Stock ICL53F Rom, Rooted, and clockwork recovery. I tried applying the zip update from this thread. I got the error seen here.
I then downloaded the stock rom from google and installed it with the instructions on droid-life. I then installed the galaxy nexus toolkit, selected option 9 to load clockwork recovery without overwriting the default recovery. It is still erroring out with a status 7, it is saying something about build.prop

anyone else in the same boat?

LukeJS said:
I am having all sorts of problems trying to update to 4.0.4 (IMM76K) from 4.0.2 (ICL53F) on my Verizon Galaxy Nexus. I have seen this discussed across multiple threads with not clear solution. I wanted to start a thread dedicated to this issue. Here is what is happing.
I started with Stock ICL53F Rom, Rooted, and clockwork recovery. I tried applying the zip update from this thread. I got the error seen here.
I then downloaded the stock rom from google and installed it with the instructions on droid-life. I then installed the galaxy nexus toolkit, selected option 9 to load clockwork recovery without overwriting the default recovery. It is still erroring out with a status 7, it is saying something about build.prop
Click to expand...
Click to collapse
All the instructions and explanations are available here...

efrant said:
All the instructions and explanations are available here...
Click to expand...
Click to collapse
That is how I tried installing the update but am getting a status 7 error. At this point I have actually tried a few of the methods listed on that post.

LukeJS said:
That is how I tried installing the update but am getting a status 7 error. At this point I have actually tried a few of the methods listed on that post.
Click to expand...
Click to collapse
I was referring more to the notes in that post, not the methods. In order for the update to install you need to have ALL the original stock files that were in /system. Judging by the photo you posted, you had modified your SystemUI.apk file. Modifying ANY file on /system will cause the update to fail. You need to replace you modified SystemUI.apk file with the stock one, as is explained in the notes in that post...

efrant said:
I was referring more to the notes in that post, not the methods. In order for the update to install you need to have ALL the original stock files that were in /system. Judging by the photo you posted, you had modified your SystemUI.apk file. Modifying ANY file on /system will cause the update to fail. You need to replace you modified SystemUI.apk file with the stock one, as is explained in the notes in that post...
Click to expand...
Click to collapse
Thanks for the reply, I have gone back to fully stock. I downloaded the stock ROM from google's website.
I then ran the following commands, all completed successfully:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
Rebooted into recovery and executed
fastboot oem lock
I then booted back to stock android copied the update.zip to the phone and used the nexus toolkit to unlock the bootloader (option 3), load CWM without overwriting the recovery option 9, and flash the zip. I am still getting a Status 7 error assert failed: getprop("ro.products.device") == "toro" || getprop("ro.build.product") == "toro" error. whattttt theee?? See the attached picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?

LukeJS said:
Thanks for the reply, I have gone back to fully stock. I downloaded the stock ROM from google's website.
I then ran the following commands, all completed successfully:
I then booted back to stock android copied the update.zip to the phone and used the nexus toolkit to unlock the bootloader (option 3), load CWM without overwriting the recovery option 9, and flash the zip. I am still getting a Status 7 error assert failed: getprop("ro.products.device") == "toro" || getprop("ro.build.product") == "toro" error. whattttt theee?? See the attached picture
Any ideas?
Click to expand...
Click to collapse
First off, a few things:
1) why are you re-locking your bootloader (by typing fastboot oem lock) only to re-unlock it again with a toolkit? Makes no sense.
2) I would use the recovery I linked to in the other thread, not the one you are using. There have been a number of reports that the touch version is not working properly...
3) I wouldn't use a toolkit until you know how to do things yourself, as it is very difficult to see what the toolkit is doing and, in turn, it is difficult to troubleshoot.
4) Now that your bootloader is unlocked, follow the steps in Method 2 of my previous link, and forget about the toolkit.

efrant said:
First off, a few things:
1) why are you re-locking your bootloader (by typing fastboot oem lock) only to re-unlock it again with a toolkit? Makes no sense.
Click to expand...
Click to collapse
Yeah, I only did it once for completeness to go back to full stock and I was just trying everything at this point.
2) I would use the recovery I linked to in the other thread, not the one you are using. There have been a number of reports that the touch version is not working properly...
Click to expand...
Click to collapse
Okay I am going to try it with recovery-clockwork-5.5.0.4-toro.img
4) Now that your bootloader is unlocked, follow the steps in Method 2 of my previous link, and forget about the toolkit.
Click to expand...
Click to collapse
Awesome!! The none touch version of the recovery did the trick. Thanks a lot!

LukeJS said:
[snip]
Awesome!! The none touch version of the recovery did the trick. Thanks a lot!
Click to expand...
Click to collapse
Glad it worked!
Moral of the story: Follow the instructions in the step-by-step as written - do not deviate unless you know that what you're doing will work.

efrant,
I have followed this post with your instructions to LukeJS. I am still getting the same error 7 that he was getting. Not sure what to do from here.

Steve.Klu said:
efrant,
I have followed this post with your instructions to LukeJS. I am still getting the same error 7 that he was getting. Not sure what to do from here.
Click to expand...
Click to collapse
So you are NOT using the touch recovery, correct?
Sent from my Galaxy Nexus using Tapatalk 2

I am not using touch.
Loaded the recovery-clockwork-5.5.0.4-toro.img
Loaded the stock ICL53F as the instructions said.
Bootloader is unlocked.
Followed method 2.
Started the whole process over from the start, error 7 seems to have gone away now, the update has loaded and I am up and running with IMM76K now. Thank you for the help you gave in this thread, a life saver.

LukeJS said:
I am having all sorts of problems trying to update to 4.0.4 (IMM76K) from 4.0.2 (ICL53F) on my Verizon Galaxy Nexus. I have seen this discussed across multiple threads with not clear solution. I wanted to start a thread dedicated to this issue. Here is what is happing.
I started with Stock ICL53F Rom, Rooted, and clockwork recovery. I tried applying the zip update from this thread. I got the error seen here.
I then downloaded the stock rom from google and installed it with the instructions on droid-life. I then installed the galaxy nexus toolkit, selected option 9 to load clockwork recovery without overwriting the default recovery. It is still erroring out with a status 7, it is saying something about build.prop
Click to expand...
Click to collapse
Guys - you'll find that although the first part of these errors may be the same, there are many reasons for a Status 7. Reading through the whole error message gives you an idea about what is causing the failure. For example -- if you see an "assert failed" message, it will be followed by some indication of a test being performed that must succeed, or else the update will abort. In my case, the "system.prop" file on my device was being compared with what should be an equivalent file in the zip; my use of a feature in Volume+ had inserted 3 new lines in my system.prop file, so the assert failed. When I took those three lines out -- the assert succeeded and the update ran to completion.
Suggestion: try the update again, and share an image (or type/copy the text) of the FULL error message - don't leave anything out. Good chance that we'll have a much better idea about what's causing your issue, and how you can go about fixing it.

Why are people trying to flash an OTA update.zip file in CWM or other custom recoveries? If it is truly and OTA update.zip, return to the stock build that it is updating, bootloader, modems, system, kernel and recovery (everything). Put the update.zip file on the root of the internal SD Card. Boot into stock recovery and apply the update. If you are on stock recovery, it will work just fine as long as all of the other pieces are in place as well. You don't need to lock the bootloader to flash an OTA update.zip, and it should apply just fine in stock recovery.

jonstrong said:
Guys - you'll find that although the first part of these errors may be the same, there are many reasons for a Status 7. Reading through the whole error message gives you an idea about what is causing the failure. For example -- if you see an "assert failed" message, it will be followed by some indication of a test being performed that must succeed, or else the update will abort. In my case, the "system.prop" file on my device was being compared with what should be an equivalent file in the zip; my use of a feature in Volume+ had inserted 3 new lines in my system.prop file, so the assert failed. When I took those three lines out -- the assert succeeded and the update ran to completion.
Suggestion: try the update again, and share an image (or type/copy the text) of the FULL error message - don't leave anything out. Good chance that we'll have a much better idea about what's causing your issue, and how you can go about fixing it.
Click to expand...
Click to collapse
If you would have read the whole thread, you would have seen that his issue was that he was using a touch recovery, which is known to have issues with installing OTA updates. He flashed the non-touch version of CWM, and successfully solved his issue 2 weeks ago.
---------- Post added at 07:05 PM ---------- Previous post was at 07:02 PM ----------
imnuts said:
Why are people trying to flash an OTA update.zip file in CWM or other custom recoveries? If it is truly and OTA update.zip, return to the stock build that it is updating, bootloader, modems, system, kernel and recovery (everything). Put the update.zip file on the root of the internal SD Card. Boot into stock recovery and apply the update. If you are on stock recovery, it will work just fine as long as all of the other pieces are in place as well. You don't need to lock the bootloader to flash an OTA update.zip, and it should apply just fine in stock recovery.
Click to expand...
Click to collapse
1) If I am using CWM, why would I flash back to a stock recovery, just to apply the update, to then flash back CWM, when CWM can easily do it?
2) The stock recovery will not apply the update.zip file from /sdcard. It will only apply it from /cache.

efrant said:
If you would have read the whole thread, you would have seen that his issue was that he was using a touch recovery, which is known to have issues with installing OTA updates. He flashed the non-touch version of CWM, and successfully solved his issue 2 weeks ago.
Click to expand...
Click to collapse
Oops! My bad.... :banghead:
Sent from my Galaxy Nexus using XDA

[December 6,2013][ROM] [PrimoC] Stock-Rooted Virgin Mobile HBOOT 1.57.0000

View attachment primoc_boot_unsecure.imgPlease excuse my absence. I will not be watching this thread for the time being. Hopefully if you have any questions, they can be answered by using the search option or someone else with this device that happens to check this thread will be kind enough to help.
!#I'M BACK#!​
soon enough we won't need this thread, because we will all be able to RUU lol-Dec 6, 2013
beaups said:
posted on rumrunner.us. should work for both primou and primoc. Note, it is highly recommended (mandatory?) to be on a normal sense-based ICS rom and using an unsecure (preferably stock based) kernel. If you get poor results with other configurations, don't bother asking for help please!
Click to expand...
Click to collapse
S-OFF is here rumrunner.us
Huge thanks to beaups
This rom is probably most compatible with rumrunner
The boot.img inside is unsecure so flash away and GO GET S-OFFED!!!
Here's the unsecure boot.img that I used to achieve s-off.
View attachment primoc_boot_unsecure.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Added init.d support
Added Root Permissions with Chainfire's SuperSu
This ROM was cooked with dsixda's Android Kitchen
Thank you and credit goes out to the both of them.
CLICK HERE TO DOWNLOAD

I have posted this ROM for safetynet/fall-back purposes.
I've noticed fellas posting please help, I forgot/didn't make a backup.
This is for you. Worried and maybe even a little scared that your phone is now a beautiful paper weight.
This ROM is completely stock with added init.d support and root.
It is still odexed, and with stock kernel.( I'm still learning/attempting to build one with extra governors and over clocking abilities ).
Instructions below....

1. Unlock your Bootloader by following the instructions at htcdev
1a. If you've succesfully unlocked your Bootloader, that means you have your fastboot files on your PC and know in general how to use them.
2. Download an openrecovery of your choice. I personally use TeamWinRecoveryProject 2.2.0 without any issues at all. (See the attached File)
3. Place the recovery.img that you have chosen into your fastboot folder.
3a. Change the name of the .img to recovery.img (just easier that way when sending the flash command)
4. Now open a terminal while in the fastboot folder.
4a. On Windows- hold shift+right click the mouse then click open command terminal here.
4b. On Ubuntu- CTRL+ALT+T to open a terninal then cd fastboot.
5.fastboot flash recovery recovery.img​
5a. ^^^^^ Type this into the terminal. ^^^^^
5b. You now have a custom/openrecovery.
6. After the recovery.img is flashed, reboot your Bootloader.
6a. fastboot reboot-bootloader​
7. After booted back into bootloader, use your volume-down button to highlight Recovery.
Now press your Power button to select it.
7a. Now your are in Recovery!
8. Click Wipe, then Cashe, then Dalvick, then Factory Rest, then System.
8a. This will wipe all of your phone nice and clean for a fresh install.
9. Click Home, then Install, and find the ROM.zip, click it, then install. Let it finish installing the click Wipe Cashe/Dalvick.
10. Navigate back to the Home screen and click Reboot, then Bootloader
10a. I hope you have a copy of the ROM.zip on your PC.
11. Open the ROM.zip and copy/extract the boot.img from inside it and place it in your fastboot folder.
12. Open a terminal once again.
13.fastboot flash boot boot.img​
13a. Let it finish.
14. fastboot reboot​
15. Enjoy.
These instructions are for use with TWRP (TeamWinRecoveryProject) They may be different using CWMrecovery (ClockWorkMod).

I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here

lostboybinns said:
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
Click to expand...
Click to collapse
u flashed shpongle? that means u are GSM not CDMA so this ROM just simply won't work
as for returning to stock, u can always flash a sense kernel duh

This is for primoc CDMA Virgin Mobile

I just downloaded and flashed to test, everything is working....Just like stock

This should allow me to update my PRL, right?

YUP!

Turns out it was a network fluke?

wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...

russellvone said:
Turns out it was a network fluke?
Click to expand...
Click to collapse
What was a network fluke?

I'll cross reference the updater-script to another one I've used on a different Rom I cooked and have been running for over two weeks..... See if there are any differences between the two.

lilrob1213 said:
What was a network fluke?
Click to expand...
Click to collapse
I was replying to zombiegirl's question about updating her/his PRL

Matt_the_Geek said:
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
Click to expand...
Click to collapse
Ok I found a difference in the updater-script, the update binaries are identical so that shouldn't be the issue. Problem I have is that I don't have a working computer to fix the updater-script. It won't be until June 26th that I can apply it. Sorry for the inconvenience.
P.S. are you flashing with TWRP?

Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.

Matt_the_Geek said:
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Click to expand...
Click to collapse
If you downgrade TWRP to 2.3 you should be fine.
Sent from my One V using xda premium

ah, I'm on 2.5, so I'll look into that...

did the downgrade to TWRP 2.3.0.0, still the only thing i can install is Rhythimc Rom, everything else fails to install... unless i just got some really crappy downloads, so i'm off to try to dl the roms again...

Actually, instead I swapped out recoveries for CWM. aaaand it worked.

[Q] Cannot flash any custom ROMs

Hi Guys,
I have searched for a few days and ready through many threads on this but I simply cannot get my One X to accept a custom ROM.
Here is the info:
One X Tegra
Currently running 4.1.1 stock but rooted
Hboot is 1.36.0000
Radio is 5.1204.163R.30
Currently I have the latest CWM installed (downloaded yesterday from the CWM site) and I had TWRP before that.
I have tried no word of a lie at least 10 ROMS and they all fail with an error. CWM says "Error in *Rom.zip location* (status 7) Installation aborted"
I have redownloded and downloaded from different sites, I have cleared all the cache/data partitions many times, I have tried flashing on the device and using tools. I have tried a different USB cable and a different computer. I have flashed loads of ROMS onto countless smart phones thanks to the guys at XDA but this one has me stumped.
Any suggestions are welcome.

location of file
qazax said:
Hi Guys,
I have searched for a few days and ready through many threads on this but I simply cannot get my One X to accept a custom ROM.
Here is the info:
One X Tegra
Currently running 4.1.1 stock but rooted
Hboot is 1.36.0000
Radio is 5.1204.163R.30
Currently I have the latest CWM installed (downloaded yesterday from the CWM site) and I had TWRP before that.
I have tried no word of a lie at least 10 ROMS and they all fail with an error. CWM says "Error in *Rom.zip location* (status 7) Installation aborted"
I have redownloded and downloaded from different sites, I have cleared all the cache/data partitions many times, I have tried flashing on the device and using tools. I have tried a different USB cable and a different computer. I have flashed loads of ROMS onto countless smart phones thanks to the guys at XDA but this one has me stumped.
Any suggestions are welcome.
Click to expand...
Click to collapse
after reading this I guess the problem is in the location of the file cwm is not able to find it....
BTW I recommend twrp

@SidDev said:
after reading this I guess the problem is in the location of the file cwm is not able to find it....
BTW I recommend twrp
Click to expand...
Click to collapse
Thanks for replying. I had the same issue with TWRP, it started the install and then said there was an error. Good thing I had a backup I could restore as it partially flashes then fails.

qazax said:
Thanks for replying. I had the same issue with TWRP, it started the install and then said there was an error. Good thing I had a backup I could restore as it partially flashes then fails.
Click to expand...
Click to collapse
do you know how to flash via adb if yes try that after that your custom recovery might work

qazax said:
Hi Guys,
I have searched for a few days and ready through many threads on this but I simply cannot get my One X to accept a custom ROM.
Here is the info:
One X Tegra
Currently running 4.1.1 stock but rooted
Hboot is 1.36.0000
Radio is 5.1204.163R.30
Currently I have the latest CWM installed (downloaded yesterday from the CWM site) and I had TWRP before that.
I have tried no word of a lie at least 10 ROMS and they all fail with an error. CWM says "Error in *Rom.zip location* (status 7) Installation aborted"
I have redownloded and downloaded from different sites, I have cleared all the cache/data partitions many times, I have tried flashing on the device and using tools. I have tried a different USB cable and a different computer. I have flashed loads of ROMS onto countless smart phones thanks to the guys at XDA but this one has me stumped.
Any suggestions are welcome.
Click to expand...
Click to collapse
What rom you want to install and which recovery did you use?
Tap via Tapatalk

khairulez said:
What rom you want to install and which recovery did you use?
Tap via Tapatalk
Click to expand...
Click to collapse
Trying to get CMod11 installed. Tried on CWM and now I am on TWRP.
Just tried ADB Sideload using the WinDroid Universal HTC Toolkit. Result:
"Can't install this package on top of incompatible data. Please try anoth
E:Error executing updater binary in zip"
When I try gapps I get:
"Set_metadata_recursive: Some changes failed"

qazax said:
Trying to get CMod11 installed. Tried on CWM and now I am on TWRP.
Just tried ADB Sideload using the WinDroid Universal HTC Toolkit. Result:
"Can't install this package on top of incompatible data. Please try anoth
E:Error executing updater binary in zip"
When I try gapps I get:
"Set_metadata_recursive: Some changes failed"
Click to expand...
Click to collapse
Flash cm11 using cwm,may i know which version?
Tap via Tapatalk

This one for sense 5 and lower roms (no kitkat support) :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
This one for all roms :
https://www.dropbox.com/s/ls4vu15ilpryf36/twrp#2.img

khairulez said:
flash cm11 using cwm,may i know which version?
Tap via tapatalk
Click to expand...
Click to collapse
cm-11-2104-8-4-snapshot-m9

Mr Hofs said:
This one for sense 5 and lower roms (no kitkat support) :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
This one for all roms :
https://www.dropbox.com/s/ls4vu15ilpryf36/twrp#2.img
Click to expand...
Click to collapse
I just flashed that second one. Tried to flash the ROM I listed above and I get E:Unable to mount '/usb-otg'

qazax said:
cm-11-2104-8-4-snapshot-m9
Click to expand...
Click to collapse
I mean cwm recovery version not cm rom version.
That's twrp version not support usb otg.correct me if i'am wrong.
Tap via Tapatalk

khairulez said:
I mean cwm recovery version not cm rom version.
That's twrp version not support usb otg.correct me if i'am wrong.
Tap via Tapatalk
Click to expand...
Click to collapse
Oh I see, I don't have it installed at the moment, can you suggest a version that does support USB.otg please?

Flash philz 5.15 that i linked. Mount the sdcard inside the recovery as a usb disk in the mounts and storage menu. Wait litreraly minutes to let it pop up at the pc and copy a rom to the internal sd. Stop using usb otg

qazax said:
Oh I see, I don't have it installed at the moment, can you suggest a version that does support USB.otg please?
Click to expand...
Click to collapse
Use this recovery if you want flash cm11 rom:

khairulez said:
Use this recovery if you want flash cm11 rom:
Click to expand...
Click to collapse
Thanks for this, what is the best way of flashing this to make sure it works properly?

qazax said:
Thanks for this, what is the best way of flashing this to make sure it works properly?
Click to expand...
Click to collapse
-renamed it as recovery.img
-fastboot flash recovery recovery.img
-fastboot erase cache
Done !
Tap via Tapatalk

khairulez said:
-renamed it as recovery.img
-fastboot flash recovery recovery.img
-fastboot erase cache
Done !
Tap via Tapatalk
Click to expand...
Click to collapse
OK, I did that but got the same error. Downloaded cm11 again and had the same problem. Tried cm10 and that flashed correctly. Gets stuck on the CMOS animation though. Clearing cache etc doesn't allow it to boot. Ugh!

qazax said:
OK, I did that but got the same error. Downloaded cm11 again and had the same problem. Tried cm10 and that flashed correctly. Gets stuck on the CMOS animation though. Clearing cache etc doesn't allow it to boot. Ugh!
Click to expand...
Click to collapse
Try flash another rom like sense based rom.use recovery that Mr Hofs give you.
EDIT: Don't know why that recovery give error when flash cm11,it's kitkat based recovery.
Tap via Tapatalk

Hi Guys,
Firstly sorry for the late reply, been quite busy.
Secondly thanks for all the help, I finally managed to get CM installed with a combination of the suggested recovery, a different USB cable (I think this was the killer) and several attempts in fastboot etc.
My current problem is as shown:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So battery life is pretty poor (even though i had the battery replaced with a new one!) So far I have set my location to battery saving, and manually chosen my mobile network which has improved it somewhat, but I am struggling to make one day with very little use. I know the battery is working well because I was n the phone for a while and it did not drop much.
There are no kernel or partial wakelocks that I can see, but as the screenshot shows there is quite a big discrepancy between Awake and screen on.
The only thing I can find (and please excuse my lack of understanding and ability with better battery stats) is that under Alarms, com.google.android.gms shoes as "54%"... so not sure on that one... halp?