Develop Bugs

[q] flashing cm7!?

when flashing the build for cm7 could i do it using ClockWork Mod v2.5.1.2 or is there a special recovery i need to flash before trying to put cm7
reason i ask is because on the MT4G you need to flash recovery to v3.0.0.0+ before flashing cm7 build
if someone could please responf on this thread or pm me would be awesome!
Thank You

pretty sure you can just flash it the regular way.. wouldn't see why not as the gingerbread roms are flashed through the regular cwm also

bomber889 said:
pretty sure you can just flash it the regular way.. wouldn't see why not as the gingerbread roms are flashed through the regular cwm also
Click to expand...
Click to collapse
my next question, i tried rooting the phone using the unrevoked program but after it tries running the root it come with an error
"ERROR:Failed to get root. Is your Firmware too new?"
does anyone know anything about this?

Jlom117 said:
my next question, i tried rooting the phone using the unrevoked program but after it tries running the root it come with an error
"ERROR:Failed to get root. Is your Firmware too new?"
does anyone know anything about this?
Click to expand...
Click to collapse
well sounds like you already have the latest Clockwork installed? if so, I believe UnRevoked comes with a downgraded version so I would try and downgrade the version on your phone see if it helps

Well I'm able to go into recovery it's just when I try and use rom manager or titanium backup it comes up saying the phone doesn't have root privileges so I thought it wasnt rooted properly. If I'm rooted because I can go into recovery and it shows s= off in h boot then how do I fix the privileges part of it all?
Sent from my HTC Glacier using XDA App

Jlom117 said:
Well I'm able to go into recovery it's just when I try and use rom manager or titanium backup it comes up saying the phone doesn't have root privileges so I thought it wasnt rooted properly. If I'm rooted because I can go into recovery and it shows s= off in h boot then how do I fix the privileges part of it all?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This happened to me after I used unrevoked. It ran successfully, I tested w/ rom manager and it worked. I then rebooted a few minutes later and tried using several other root apps and none could obtain root privelages. So, I flashed a custom ROM (cyanogen 6.1) then had full root access again. Maybe that will help?

pokedroid said:
This happened to me after I used unrevoked. It ran successfully, I tested w/ rom manager and it worked. I then rebooted a few minutes later and tried using several other root apps and none could obtain root privelages. So, I flashed a custom ROM (cyanogen 6.1) then had full root access again. Maybe that will help?
Click to expand...
Click to collapse
ok cool ill try that! THANKS!

sounds like superuser isn't installed or you aren't letting it have privileges
Sent from my ADR6300 using XDA App

pete_kowalski83 said:
sounds like superuser isn't installed or you aren't letting it have privileges
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
ok everything went through for the root and privileges, now im having an issue flashing cm7..... is there something special i need to do to flash it?
when i try flashing through recovery using 2.5.1.2 it aborts the installation please help, ive been trying to this for my gf for the passed 2 days.
Thanks
EDIT: still same issue, what do I do to fix?

Installing new update with s-off?

Is it possible to install the new update with s-off. I have a stock rom and read the new update supposed to fix the battery threshold and I like the look. I know its not rootable yet but ive been reading some have been successful and just put amon ra recovery on it.Anyone know?
Sent from my HTC Evo using XDA Premium App

My cousin installed it and his WiFi tether works and he is able to nand backup
Sent from my PC36100 using XDA Premium App

You can just get the rooted version of it on this site if you do the ota you will lose root and so far there is no way to get it back yet .
Sent from my PC36100 using XDA App

Why install the OTA when there are complete ROMS here that are better than what you're gonna have with stock 2.3.3???

mizzouse said:
Is it possible to install the new update with s-off. I have a stock rom and read the new update supposed to fix the battery threshold and I like the look. I know its not rootable yet but ive been reading some have been successful and just put amon ra recovery on it.Anyone know?
Sent from my HTC Evo using XDA Premium App
Click to expand...
Click to collapse
It is possible if you're s-off with Unrevoked Forever on Froyo. I had to switch to Amon Ra in order to install the update and then reflash Amon Ra after the update. Had to update Superuser after that but after that was fully rooted on the update.

There are several stock rooted versions of the OTA available, there's no reason that you need to lose root just to have the latest update.
If you are keen on losing root though, then go for it. You can install it with S-Off just fine, and since it'll remain S-Off you'll be able to flash a recovery on there and re-root by flashing a rooted rom.
If your intent is to have the latest update but also have root, then just flash one of the already-rooted stock roms available in the Android Development forum.

To hip kat, I actually don't like any custom roms, I'm an ogee only person and I tweak what I want or need myself. To tempe, how did you get clockwork off first assuming you had it? Also I used the unrevoked3 method but since mine is sprint, it automatically does a perm nand unlock.
Sent from my PC36100 using XDA Premium App

mizzouse said:
To tempe, how did you get clockwork off first assuming you had it?
Click to expand...
Click to collapse
Well, easiest is to just use Rom Manager to flash alternate recovery, that's what I did before running the OTA. After, you'll need to do it manually. If you search here on "recovery" you should find threads that have the pc36img.zip files for both Clockworkmod and Amon Ra. After installing the OTA, turn off the fastboot option under Settings/Applications. Copy the pc36img.zip file for the recovery you want to use to the SD card, shut down your phone and then hold volume down while turning it back on. Just follow the prompts on the screen from there. After the recovery is installed you should be able to boot up and have root. If the Superuser app give you FC's search around here for the fixed superuser zip and flash it.

You can go S-on with the Unrevoked S-On tool....

I don't want s-on hip, trying to keep s-off. And thanks tempe for your help.
Sent from my HTC Evo using XDA Premium App

Ok turns out im having problems installing the update, I forgot I deleted system apps. Here's the error:
assert failed: apply_patch_check /system/app/Blockbuster_htc.apk 2eE:unknown command etc etc, ideas?

mizzouse said:
Ok turns out im having problems installing the update, I forgot I deleted system apps. Here's the error:
assert failed: apply_patch_check /system/app/Blockbuster_htc.apk 2eE:unknown command etc etc, ideas?
Click to expand...
Click to collapse
According to the error you posted, it's just the blockbuster app that your missing. Did you uninstall other system apps? Or just that. You need to have all your system apps installed for it to work. I'll attatch the blockbuster app for you. You'll need to install it to /system/app using ADB or using Root Explorer. If adb, do this
adb remount
adb push Blockbuster_htc.apk /system/app
adb reboot
If using root explorer, just copy the apk to the /system/app folder and set the permissions the same as all the other apps in the system folder.
Also, it would be much easier for you just to flash a rooted stock rom. Here's a link for ya. You'd just flash the rom like normal, from within recovery. It'd save you some hassle.
http://forum.xda-developers.com/showthread.php?t=1038701

mizzouse said:
Ok turns out im having problems installing the update, I forgot I deleted system apps. Here's the error:
assert failed: apply_patch_check /system/app/Blockbuster_htc.apk 2eE:unknown command etc etc, ideas?
Click to expand...
Click to collapse
You do know there are rooted stock versions out there and like others have said no need to unroot then root again... SMH

playya said:
You do know there are rooted stock versions out there and like others have said no need to unroot then root again... SMH
Click to expand...
Click to collapse
NOOOOO, you're not suppose to tell him..lol! I would of love for him to flash the new update and then complain about how he can't root his phone and how he wants to come back..haha

skcussrepolevedadx said:
NOOOOO, you're not suppose to tell him..lol! I would of love for him to flash the new update and then complain about how he can't root his phone and how he wants to come back..haha
Click to expand...
Click to collapse
As much as I would love to see that happen (for my own amusement), I do believe in bad karma and if you let someone do that knowing what they're about to get into then you're properly gonna get the bone too......who knows, your phone might just blow up on the way to work while you're playing angry birds or some crap...hahahaha

I've already chosen to just do the rooted ota but I'm trying to figure out if I need to flash the radio. The second link in the topic is showing 2.15.00.04.08 but mine is higher at 00.11.19. The combined link with pri and wimax is the one I don't know yet
Sent from my PC36100 using XDA Premium App

mizzouse said:
I've already chosen to just do the rooted ota but I'm trying to figure out if I need to flash the radio. The second link in the topic is showing 2.15.00.04.08 but mine is higher at 00.11.19. The combined link with pri and wimax is the one I don't know yet
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I don't believe flashing the radio is necessary if you're doing the stock ota, I didn't have any issues with my current radio while I was using stock 2.3.3 (or any other ROM that I've used so far)

Alright I did the de-odex rooted ota but now the problem is once booted up, I cant update the prl or profile, it gives me an error. Im re-wiping the dalvik cache to see if that fixes it but is there any other steps I should try?
Side question, is a stock rom that came with the phone or an ota update a odex or de-odex?

Thanks for this thread, I have been searching high & low to see if S-Off would stay off or automatically turn back on. Thanks for the clarification!

Verified!
pnewgaard said:
Thanks for this thread, I have been searching high & low to see if S-Off would stay off or automatically turn back on. Thanks for the clarification!
Click to expand...
Click to collapse
I ended up testing myself to know for sure and S-Off will stay off if you do the OTA update. If you want to start rooting again, just download Amon_Ra Recovery, and Bam, flash any Rom you want! Thanks for the starting of the thread! Confirmed!

[Q] Trying 2 understand few thing things after/about rooting!

So i have rooted the htc DZ and tried out multiple roms... Till now i used to use the CWR to wipe the data/cache before loading a new rom.. Yesterday i decided to try SuperWipeG2+ without reading much(not trying to understand what it exactly does).
After i flashed it, i by mistake hit the reboot now in CWR and it hung at the boot screen. To fix this i removed the battery and put it back in,since power on was not working. When i did so it went to HBoot and started flashing the 1.34 PC10IMG file present in the sdcard which i did not remove after rooting.
Query:-
1) Should i have removed 1.34 PC10IMG?
2)If i ever face a similar situation like mentioned above will it enter the recovery,if the1.34 PC10IMG file was not present ?(i did try to do away with updating the 1.34 PC10IMG,but always entered the HBoot on every subsequent restart and never allowed me to change the options from flashboot to anything else).
2a)If it does not enter recovery, then what is it to be done?
3)Currently i have stock 1.34 rom which says i do not have root(check this by installing rom manger )! but when i check Boot page, it says S-off and other Hboot etc.
I did run from step 1. to root DZ and it was back to good old rooted condition.
(Did a lot searching and reading but i couldn't answer the above questions- hence the thread also just not comfortable experimenting too much,might end bricking the phone )
Non-rooting query:-
4)Also what is use of app2sd/partition of sd-card!
i mean, as per my understanding this(app2sd) can"only"be used when there is partition in you sd-card which allows apps to be moved to sd-card,but when using MIUI rom i still can move most of the user apps to sd-card..
If these questions has been already asked and replied or even already explained please forgive me for creating this thread and please provide the link.. Would appreciate a lot..
Thanks..

Anyone ... Sorry abt the long post...
Sent from my HTC Vision using Tapatalk

I only know no.4
Since Froyo, you dont need this app. You can move it to your sd card under the Application setting. But, not all apps can be moved (such as task manager, pre installed app). You dont need to create partition, just install it and run it.
Anyway, since our DZ has internal memory 1,5 GB, I never moved apps to sd card
Cheers

Thanks ... 1 cleared.. 3 to go...
Sent from my HTC Vision using Tapatalk

For the other q's
Yes you should remove the PC10IMG from your sdcard.otherwise you can't get into recovery through bootloader.
(although you could boot to fastboot, and if you have the eng bootloader boot a recovery through terminal/cmd)
Did you run the "./root_psn" step of the rooting guide? If not that might be the error with not perm-root
-Nipqer

Nipqer said:
For the other q's
Yes you should remove the PC10IMG from your sdcard.otherwise you can't get into recovery through bootloader.
(although you could boot to fastboot, and if you have the eng bootloader boot a recovery through terminal/cmd)
Did you run the "./root_psn" step of the rooting guide? If not that might be the error with not perm-root
-Nipqer
Click to expand...
Click to collapse
Thanks for replying..
I did run "./root_psn"..

MEkANiK said:
Thanks for replying..
I did run "./root_psn"..
Click to expand...
Click to collapse
ROM Manager is just checking for su, I believe; try downloading SuperUser by ChainsDD from the market and flashing the su binary with it and then loading ROM Manager.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
ROM Manager is just checking for su, I believe; try downloading SuperUser by ChainsDD from the market and flashing the su binary with it and then loading ROM Manager.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I did try that but did not work.. it still kept saying /system/bin/su missing... anyways I removed the PC101M file and now any issues I am still able to enter recovery..
Sent from my HTC Vision using Tapatalk

MEkANiK said:
I did try that but did not work.. it still kept saying /system/bin/su missing... anyways I removed the PC101M file and now any issues I am still able to enter recovery..
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
When you installed the application, did you also flash the binary? Launch the application, go into preferences and scroll to the bottom for the option to flash the binary
Sent from my HTC Vision using XDA App

[HOW-TO] CMW on LTE Version through Rom Manager

If you have any questions, concerns or problems, please post in the CDMA post because I will no longer be checking here.

theboo7 said:
This is a guide on how to get ClockWorkMod onto your LTE Galaxy Nexus through Rom Manager
Go to market, search "Clockworkmod"
Install Rom Manager*
Open up Rom Manager and select "Flash ClockworkMod Recovery"
A pop-up will come up called "Confirm Phone Model," of course choose "Google Galaxy Nexus CDMA"
Now let it install etc, then with a File Manager** with SU access, Go to system, click "Mount R/W"(if using Root Explorer) and then scroll down until you see "recovery-from-boot.p" and rename it to "recovery-from-boot.p.bak"
Close out off your File Manager and go to Rom Manager and select "Reboot into Recovery"
There you go
You should be able to boot into CWM
* Free version works
**I used Root Explorer
Click to expand...
Click to collapse
For starters that file doesnt exist under the directory "system"

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
By "that file" I'm assuming you are referring to "recovery-from-boot.p" ?

jgrimberg1979 said:
For starters that file doesnt exist under the directory "system"
Click to expand...
Click to collapse
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.

staticx57 said:
Could be because you are on a custom ROM. I am on Android Revolution HD and I don't see it at all as well. I also can directly boot from ROM Manager directly into CWM. I never touched this file at all and I never looked for it.
Click to expand...
Click to collapse
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw

theboo7 said:
I'm on stock 4.0.2
updated OP to reflect the OS version I'm talking about.
Accidental thanks btw
Click to expand...
Click to collapse
I had to do this same thing on stock to keep the stock recovery from restoring.

jermaine151 said:
I had to do this same thing on stock to keep the stock recovery from restoring.
Click to expand...
Click to collapse
Yeah it's a known bug, that's hopefully getting worked on.

Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk

dc iz 2 legit said:
Thank you for this! Now one question if I didn't do this and the stock recovery booted what would be the steps too get this recovery installed?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Then you would follow the steps in the OP

What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?

Xirix12 said:
What are the benefits to doing this final part. Is it necessary? Some say they didn't do this? Now on the Thunderbolt I didn't have to have rom manager installed and I could still boot into recovery. Is this the same? If I rename that file (which is in my system directory) will I be able to boot into cwm at any point?
Thanks I have done everything with the exception to this. Wondering if its necessary?
Edit: I guess I should have waited for a response because I went ahead and followed the steps in the OP and it came up with an android with a red triangle. Pulled that battery and booted up ok. Any info I need to be aware of? I wasn't able to boot into recovery from rom manager at first. I can now boot into recovery after reflashing CWM recovery but cannot do anything once I am in it?
Click to expand...
Click to collapse
Flashing through ROM Manager is just a simpler way to get CWM. And I'm not sure why you would have gotten the red triangle, unless you didn't rename/delete the file in system. And I haven't heard anyone say the couldn't do anything in recovery, so I'm not sure what the problem is there.

When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
When I try and change the file name it says insufficient permissions??
I have root...
Cwm doesn't stick though. I always have to boot reflash recovery and then boot into recovery through from manager..
Any suggestion?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM

theboo7 said:
Your file manager doesn't have root privileges, so until you rename/delete the file you won't be able to reboot into CWM
Click to expand...
Click to collapse
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App

civicsisedan said:
This. I was using astro but changed to root explorer and changed file name. Turned phone off and went into fast boot and then recovery and it worked.
To be clear, I was able to go into recovery before. I would have to open from manager, reflash cwm and boot into recovery.
I was just unable to power phone off and boot into recovery manually. Now I can.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Okay, so glad that you got it sorted out
Sent from my Galaxy Nexus using XDA App

this step by step process was incredibly easy. thank you!!!

reflekt2099 said:
this step by step process was incredibly easy. thank you!!!
Click to expand...
Click to collapse
Your welcome
Sent from my Galaxy Nexus using XDA App

Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk

Xirix12 said:
Thanks for the reply. I did rename it the file to .bak following the script to the t! I don't know what happened either. Since then I deleted the file entirely this time and reflashed the cwm seems to work a little better than before an now I can do things in cwm recovery. Hope nothing else goes crazy.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yeah, that file can cause problems with CWM on LTE, although it's a quick fix, I'm sure it's being worked on for future editions. And since you've been able to flash things, when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.

theboo7 said:
when you use the volume keys to high light options, does it skip one or two every now and then? That's only problem I seem to be having.
Click to expand...
Click to collapse
Same here. You gotta go slow. I selected the wrong option many times.

[Q] Is it possible to get root on primoc without flashing a kernel?

I know it's required to unlock the bootloader in order to gain root on primoc, but the directions call for flashing a kernel, and I'd like to keep my phone as close to stock as humanly possible. Is there a way to keep the stock kernel and get root, or is it the act of flashing the kernel that gets you root? The reason I ask is that I'd like to be able to use root apps, but I don't want to flash kernels/ROMs.
Sorry if this is a n00b question.
-------------------------
For any poor unsuspecting soul who finds this thread through the almighty Google... The procedure in the next post works. Apparently, if you get the latest and greatest TWRP recovery it will root for you, but the version of TWRP I found did not do that.

meaninglessvanity said:
I know it's required to unlock the bootloader in order to gain root on primoc, but the directions call for flashing a kernel, and I'd like to keep my phone as close to stock as humanly possible. Is there a way to keep the stock kernel and get root, or is it the act of flashing the kernel that gets you root? The reason I ask is that I'd like to be able to use root apps, but I don't want to flash kernels/ROMs.
Sorry if this is a n00b question.
Click to expand...
Click to collapse
Follow the instructions and flash the recovery file and not a kernel. You should now have TWRP recovery installed. Download Superuser.zip from the official website and place it in your sd card. Reboot and go into Bootloader and then into Recovery. From there press the first button and go to where you left the Superuser.zip. Select it and let it finish. Now reboot and you should be rooted.
Sent from my One V using xda premium

woohoo!
reV17 said:
Follow the instructions and flash the recovery file and not a kernel. You should now have TWRP recovery installed. Download Superuser.zip from the official website and place it in your sd card. Reboot and go into Bootloader and then into Recovery. From there press the first button and go to where you left the Superuser.zip. Select it and let it finish. Now reboot and you should be rooted.
Sent from my One V using xda premium
Click to expand...
Click to collapse
I'm so going to try that. Thanks a million!

meaninglessvanity said:
I know it's required to unlock the bootloader in order to gain root on primoc, but the directions call for flashing a kernel, and I'd like to keep my phone as close to stock as humanly possible. Is there a way to keep the stock kernel and get root, or is it the act of flashing the kernel that gets you root? The reason I ask is that I'd like to be able to use root apps, but I don't want to flash kernels/ROMs.
Sorry if this is a n00b question.
Click to expand...
Click to collapse
If you install twrp as the recovery it will promot you and root the Rom. With the stick kernel.
Sent from my HTC One V using xda app-developers app

robaho said:
If you install twrp as the recovery it will promot you and root the Rom. With the stick kernel.
Click to expand...
Click to collapse
That wasn't my experience. I had to flash the superuser.zip from recovery to get the su binary and then install the superuser app to get root to work. The general approach does work though!

meaninglessvanity said:
That wasn't my experience. I had to flash the superuser.zip from recovery to get the su binary and then install the superuser app to get root to work. The general approach does work though!
Click to expand...
Click to collapse
I am talking the later versions. Check the twrp change log.
Sent from my HTC One V using xda app-developers app

I just used the superboot for primoc that I found on one of the stickied threads in general. one click and it roots it. I've used it on all three of the virgin updates.
Sent from my One V using xda premium

demi_fiend said:
I just used the superboot for primoc that I found on one of the stickied threads in general. one click and it roots it. I've used it on all three of the virgin updates.
Click to expand...
Click to collapse
Superboot does work, but it installs a kernel as part of the directions, which is what I did not want to do.

meaninglessvanity said:
Superboot does work, but it installs a kernel as part of the directions, which is what I did not want to do.
Click to expand...
Click to collapse
Just use twrp...
Sent from my HTC One V using xda app-developers app