I've been having a problem with phone calls putting them on speaker. The volume of the external speaker is comparable to the volume of the ear piece. This is only in calls, music and notifications seem to be fine. It was fine before I rooted, but seems to be goofed up on JB roms. I rooted with the brand new 2.20 root method. I tried things like Volume+ and nothing seems to make a difference. I've tried all the basic things like wiping cache/dalvick. What are the chances it's a bad device?
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
DvineLord said:
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
Click to expand...
Click to collapse
yes, i posted it there because at the time i thought the problem was specific to that rom (i think it started with the codename rom). but after being on more than one rom (i'm now on the jb build 4) i don't think it is. or it may be specific to jb roms. i'm not sure. i thought i would ask before i just go flashing away... i'm also wondering if anybody else is having this problem.
i followed you all the way till "fix permissions", is this another tab in twrp?
with all the changes right now with CM10 which is base for alot of jb roms its hard to determine the cause. unless you are using a jb aosp build before the kernel changes which is basically anything after 10/01 then you might have some unique issues.
fix permissions is under advanced
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Didn't work, but sandy just knocked out the power so I think this can wait a while haha
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Crappyvate said:
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Click to expand...
Click to collapse
i will definitely take this under consideration
DvineLord said:
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Click to expand...
Click to collapse
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
ck4794 said:
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
Click to expand...
Click to collapse
relock bootloader and ruu...if that does not do it you have a hardware issue.
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
ck4794 said:
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
Click to expand...
Click to collapse
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
That's also why you should always do a clean install/full wipe/factory reset when you experiment with different roms (aosp/sense)
Crappyvate said:
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
Click to expand...
Click to collapse
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
ck4794 said:
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
Click to expand...
Click to collapse
good luck. :highfive:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
ck4794 said:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
Click to expand...
Click to collapse
http://dl3.htc.com/application/htc_o...s_08022012.exe
Crappyvate said:
http://dl3.htc.com/application/htc_o...s_08022012.exe
Click to expand...
Click to collapse
bad link
ck4794 said:
bad link
Click to expand...
Click to collapse
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Crappyvate said:
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Click to expand...
Click to collapse
i saw some where i think that this ruu would get me back to square one, unrooted. is there anything like that i should know about before i run this ruu? also i've never run an ruu, is it one of those i put it on my c: drive run it and it will do the work?
Related
I've been playing around with a Nexus S 4G that I have lying around and never used, and I've ran into a few problems, but you've all been helpful. I rooted all my old EVO 4G's without any problem, but the other day I rooted my NS4G using a one click/simple root and downloaded ClockWorkMod etc. But now for some reason It seems like I've almost lost my root? Is that possible? I still have the little unlocked symbol when booting up.
I've searched this forum and Google and haven't found anything, which could possibly be because I don't know what to look for. I've never had this happen :/
Currently running the stock 2.3.7
Nobody? I just need a little help.
Did you flash a superuser.zip after you installed clockworkmod?
SeeNah said:
Did you flash a superuser.zip after you installed clockworkmod?
Click to expand...
Click to collapse
I thought I had... But no lol
Thank you. Sorry for pretty much making a useless thread :/
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
SeeNah said:
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
Click to expand...
Click to collapse
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Slap-Yourself :) said:
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Click to expand...
Click to collapse
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
SeeNah said:
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
Click to expand...
Click to collapse
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Slap-Yourself :) said:
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Click to expand...
Click to collapse
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
stellar said:
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
Click to expand...
Click to collapse
I'm not sure if I'm supposed to post links to videos or not. But I'm in love with some of the features this guy has on his NS4G
https://www.youtube.com/watch?v=IKdyAm3CgHc
He said it was a nightly etc.
The hidden status bar and bottom menu hidden is amazing. I also like the inverted G-Mail and Facebook. Is this all separate from the Nightly ROM?
I'm having a problem flashing both the AOKP (rohan - milestone 6.2) and CM9 (vinvinvinster - alpha 5) builds to my phone. I appear to be experiencing the same issue with both so I was hoping someone could help. I managed to flash both properly, but when I try to start my phone, both get hung in the boot animation forever. No restarts, just plays the boot animation on a loop. Has anyone else experienced this, or is there some way I can gather more info about what is happening? Any ideas? Thanks.
theplagiarist said:
I'm having a problem flashing both the AOKP (rohan - milestone 6.2) and CM9 (vinvinvinster - alpha 5) builds to my phone. I appear to be experiencing the same issue with both so I was hoping someone could help. I managed to flash both properly, but when I try to start my phone, both get hung in the boot animation forever. No restarts, just plays the boot animation on a loop. Has anyone else experienced this, or is there some way I can gather more info about what is happening? Any ideas? Thanks.
Click to expand...
Click to collapse
Just a few questions about your situation...
1. What carrier are you on? I just have to get this out of the way first to rule out that you don't have an international version.
2. Did you do a factory reset before flashing?
3. Bootloader unlocked? (again...this is just to rule this out)
4. What recovery are you using? CWM or TWRP?
5. Have you tried flashing any other roms? CleanROM? Nocturnal? If so, have you had any issues with those booting?
stnguyen09 said:
Just a few questions about your situation...
1. What carrier are you on? I just have to get this out of the way first to rule out that you don't have an international version. AT&T. Flashed the Evita version of both.
2. Did you do a factory reset before flashing? Yes. Have gone through several installs of the stock RUU in between tries.
3. Bootloader unlocked? (again...this is just to rule this out) Yep.
4. What recovery are you using? CWM or TWRP? TWRP
5. Have you tried flashing any other roms? CleanROM? Nocturnal? If so, have you had any issues with those booting? The only one I got to boot was the RebelROM Senseless one.
Click to expand...
Click to collapse
Answers in the quote.
theplagiarist said:
Answers in the quote.
Click to expand...
Click to collapse
Darn you for not having the international version and making this super easy =P
Just for clarification...since you have to relock your bootloader to run the RUU, you are definitely unlocking again before you try flashing, right? Again, not trying to patronize, just rule stuff out.
Maybe you could pull a logcat from hboot and see if it contains any information? I'm not even sure if you can do that but maybe someone else can chime in on this.
theplagiarist said:
I'm having a problem flashing both the AOKP (rohan - milestone 6.2) and CM9 (vinvinvinster - alpha 5) builds to my phone. I appear to be experiencing the same issue with both so I was hoping someone could help. I managed to flash both properly, but when I try to start my phone, both get hung in the boot animation forever. No restarts, just plays the boot animation on a loop. Has anyone else experienced this, or is there some way I can gather more info about what is happening? Any ideas? Thanks.
Click to expand...
Click to collapse
When you go to install CM or AOKP ROM do you wipe /system before install? When I came from a Sense Based ROM I had to wipe /system before installing a AOSP ROM or it would hang at the HTC screen.
So steps should be
1: load into recovery
2: do a factory wipe and then manually wipe /system
3: Install CM or AOKP then reboot
4: after the ROM loads up reboot to recovery again and install GAPPS
This is exactly what I did when coming from CleanROM to a AOSP ROM.
stnguyen09 said:
Darn you for not having the international version and making this super easy =P
Just for clarification...since you have to relock your bootloader to run the RUU, you are definitely unlocking again before you try flashing, right? Again, not trying to patronize, just rule stuff out.
Maybe you could pull a logcat from hboot and see if it contains any information? I'm not even sure if you can do that but maybe someone else can chime in on this.
Click to expand...
Click to collapse
Yeah I have been unlocking every time. No problem I'd probably ask the same questions.
P_Dub_S said:
When you go to install CM or AOKP ROM do you wipe /system before install? When I came from a Sense Based ROM I had to wipe /system before installing a AOSP ROM or it would hang at the HTC screen.
So steps should be
1: load into recovery
2: do a factory wipe and then manually wipe /system
3: Install CM or AOKP then reboot
4: after the ROM loads up reboot to recovery again and install GAPPS
This is exactly what I did when coming from CleanROM to a AOSP ROM.
Click to expand...
Click to collapse
I will give this a try. I may just grit my teeth and live with sense until the kernel is available and more stable/full featured stuff starts coming out
Thanks to everyone.
I was running the ruu 1.7x with PA because I had a soft brick a few weeks ago, just last night I tried flashing King Cobra in TWRP. Upon rebooting it gave me trouble but I eventually got the phone to boot up all the way. Everything worked except and I couldn't call or text but I can receive them. I thought maybe installing the latest update would solve the problem but I'm still having the same issue. EVERYTHING got wiped no backs up no nothing, am I screwed?
Sent from my HTC One X using xda app-developers app
Check your apn settings and make sure your using the correct settings for your carrier.
Grnfinger said:
Check your apn settings and make sure your using the correct settings for your carrier.
Click to expand...
Click to collapse
I did that when I was running KC and now on the stock software, I thought it was because I was on 1.7x and flashed KC cause I didn't have this problem with PA, so I did the update ruu tool to 2.20 and the problem still persist :/
WOOOWWW.
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
Since you already unlocked the phone with HTC dev unless you changed your cid before the ruu you can unlock again with the same token and install twrp and flash a rooted rom.
You will just need to flash the boot.img from fastboot before the rom
Sent from my HTC One XL using Forum Runner
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
As long as you left your phone SuperCID, then you can reunlock and re-root.
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
droidnamedjakke said:
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
Click to expand...
Click to collapse
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Butters619 said:
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Click to expand...
Click to collapse
It didn't solve the problem I still can't flash the .zip fix nor is the issue gone. Should I try flashing a different Rom and see if that takes care of it?
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I'll try this when I get home from work at 2:30, thanks for giving the advice. But what do you mean "even flash external"?
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I did a full wipe of everything and installed CleanROM but to no avail I'm still getting the error as listed before. I don't understand everything was wiped for my HOX why is it still doing this?
I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.
Hey guys, I have a problem with my camera on every aosp ROM I've tried. I don't know what's wrong with it, on opening the camera app it gives me "camera error: can't connect to the camera" I've tried reflashing the roms and everything but to no avail, maybe someone can help me? Thanks in advance!
If you are s-on, did you flash boot.img using fastboot?
Did you do a factory reset (in recovery, not in bootloader) and wipe cache before installing each new custom ROM?
redpoint73 said:
If you are s-on, did you flash boot.img using fastboot?
Did you do a factory reset (in recovery, not in bootloader) and wipe cache before installing each new custom ROM?
Click to expand...
Click to collapse
I'm s-off so I don't need to flash the boot.img and yes I've tried full wipes and wiping the caches but nothing seems to work, I'm going to restore a backup of viper and see if it's working on that ROM.
Edit: No go on viper either, I'm not sure what's happening.
Maybe RUU and start over again?
If that doesn't fix it, might be a hardware failure.
redpoint73 said:
Maybe RUU and start over again?
If that doesn't fix it, might be a hardware failure.
Click to expand...
Click to collapse
Yeah I'm gonna try to RUU today and see how it goes.