So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Shamrock13 said:
So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Click to expand...
Click to collapse
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
MrMeester said:
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
Click to expand...
Click to collapse
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Ya, cm 10.1 has better bat life. I liked liquidsmooths settings better though. Carbon doesn't seem to be as stable atleast for me. But it seems like no one else is having the problems I'm having. I recommend twrp recovery. Run it, see what you think. PM me if you need help.
Shamrock13 said:
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Click to expand...
Click to collapse
Yes you are right, it is the update one.
Sent from my DROID RAZR HD using Tapatalk 4
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Shamrock13 said:
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Click to expand...
Click to collapse
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
I took an xt 925 today, but i have some knowledgment from my Razr I, which is + - the same procedure/flash.
I want to install some custom roms, so basically all i have to do is unlock my bl, install a custom recovery and try out?
I'm asking that, because i'm on jelly bean, but its a carrier based firmware, and i dont know if this model got any limitation which break me up.
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Shamrock13 said:
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Click to expand...
Click to collapse
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
The thing is, I couldn't get back into recovery at all. I had to try like 50 times holding down the buttons to finally get it to even boot to the recovery select screen, and even then it wasn't a sure thing if I were going to get it to boot into recovery. I flashed another ROM, and it still didn't work. I read on the Droid forums that you need to mount system first and then flash, so I tried that and my phone booted up right away.
was kicsnia
mentose457 said:
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
Click to expand...
Click to collapse
Yeah, the brave little toaster! Old school and under rated. Ha ha!
Disable Moto Services. No root, no unlocked bootloader needed. You will never see any update nagging. Even when you turn off/on your phone.
Sent from my DROID RAZR HD using xda app-developers app
Related
Hey guys,
This is my very first post, just to let you all know, so please have some patience! Thanks!
Anyway, so I have a Nexus S 3G (Canada) and I have rooted it, unrooted it, installed roms and everything. I works...for the most part. It's giving me all sorts of different little errors and what not. So I was wondering, how can I COMPLETLY start ALL OVER, as in, factory new, like when you buy a new phone (without the carrier stuff). I wanted to start fresh, fresh out-of-the-oven kind of start, do you understand what I mean? FACTORY FRESH. Thank you all so much in advance!
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
[email protected] said:
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
Click to expand...
Click to collapse
Thanks for the reply, I've already done that, and I'm still getting errors and other weird things, like not going out of airplane mode, failing to download the OTA 2.3.6 Update (I'm on stock 2.3.1 unrooted, I think), and I don't know if this is normal, but ClockworkMod Recovery is still there. Am I still rooted or something? Plus, when I try to flash a restore, from let's say Gingerbread 2.3.6 Stock, it says MD5 mismatch! How about if it's an ICS AOSP Build, it gives me the normal white Google logo like normal, but then just stays stuck there.
Is the anyway to erase EVERYTHING and start over like NOTHING was ever done to the device? Like when they are first distributing the the device and no one has ever touched it? Is there anyway to do just that?
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
lodxcol said:
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thanks for your excellent reply, but I have also already done that, EXACTLY that, multiple times too. Dalvik, battery stats, factory reset/delete all user data, wipe cache partition and fix permissions. What else is there left to do?
Thank you all so very much!!!!
I have fixed my Nexus S!!!
HeroKhar said:
I have fixed my Nexus S!!!
Click to expand...
Click to collapse
how did you fix it?
lodxcol said:
how did you fix it?
Click to expand...
Click to collapse
I reinstalled the newest update with the vanilla recovery
Sent from my Xoom using XDA Premium HD app
My wife's phone is rooted and has been running BAMF for a long time. Well, it's slow as nuts right now and she asked me to redo it. I've been using Jellyblur on my phone, she liked it, and asked that i install that. Well, i can't for the life of me get the phone to boot with a new rom. Multiple downloads, and even downloaded about 3 different roms and it won't get past the white HTC screen.
I can reload my backup I made and it will start up just fine, but it just DOES NOT want to boot with a new rom.
I'm doing full wipes and I even copied the file I installed on my phone to her phone and tried installing that. No go.
Any ideas?
Thanks!
damon
SubliminalME said:
My wife's phone is rooted and has been running BAMF for a long time. Well, it's slow as nuts right now and she asked me to redo it. I've been using Jellyblur on my phone, she liked it, and asked that i install that. Well, i can't for the life of me get the phone to boot with a new rom. Multiple downloads, and even downloaded about 3 different roms and it won't get past the white HTC screen.
I can reload my backup I made and it will start up just fine, but it just DOES NOT want to boot with a new rom.
I'm doing full wipes and I even copied the file I installed on my phone to her phone and tried installing that. No go.
Any ideas?
Thanks!
damon
Click to expand...
Click to collapse
You likely need to update the Recovery.
I'm guessing it has some older form of Clockwork Mod Recovery on it.
You should update to 4ext.
That link is the app that you use as an interface for while in Android OS and it also installs the Recovery.
Install it while in Bamf, load the app and install recovery for HTC Thunderbolt.
Then try updating the rom, good luck!
If you end up liking it, support the dev and buy the full version of the controller app.
The recovery is free and so is the app I linked you however...
Recovery was indeed out of date. Thanks a million ..wouldn't have thought of that!
Sent from my Nexus 7 using Tapatalk 2
SubliminalME said:
Recovery was indeed out of date. Thanks a million ..wouldn't have thought of that!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No problem.
Glad you got it resolved.
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
I would give Jellybro a try. Seems to be fairly popular ROM based on CM10
http://forum.xda-developers.com/showthread.php?t=1791751
Make sure you make a nandroid backup and know how to flash beforehand.
i agree! jellybro is the sastest jb rom here !
I'm using paranoidandroid 1.9.5 its very smooth and fast but WiFi tethering is not working
Sent from my Nexus S using Tapatalk 2
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
I think CM9 is still faster overall although it isn't buttery smooth like JB or CM10.
chronophase1 said:
Since you need to wipe the phone either way, have you tried a factory reset yet? It's worth a shot. You never said whether or not you did. But if you're looking for more features all baked in, go with a custom ROM
Click to expand...
Click to collapse
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
You should try the jellybro rom because its super fast.
Sent from my Nexus S using xda premium
Try doing a full wipe/system reset. My Nexus S OTA to JB a few weeks ago. Even at stock, it was fast. No lag.
If you are experiencing lags, it is likely your phone's filled with resource contending stuff.
BTW, I've seen flashed in CMREX Beta9 JB. Boot up is insanely fast. Everything works.
Also you can try the V6 Supercharger mod. It helped my other phone - Gingerbread equipped XT615 Motoluxe speed up quite nicely.
Shahpur.Azizpour said:
My boot loader is already unlocked so I shouldn't have to wipe for root, right? I'm just not sure if CM10 is worth it. Don't know if nexus s is capable of keeping it fast with Android 4.x...
Click to expand...
Click to collapse
Mine runs very well on JB. You're already rooted and whatnot, all you need to do is backup via recovery. Properly wipe the phone and flash. There's a few 4.1 ROMs out there. Give them a shot and see what you like. The phone is still pretty quick despite its age. Like I said. The phone may just need to be cleaned up. I've never had mine lag, personally.
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Shahpur.Azizpour said:
Should I wipe SD partition too? It takes ages to backup the SD partition to a PC first...doesn't seem to support USB 2.0...
I would try a factory reset first to see what happens...
Click to expand...
Click to collapse
From my understanding just do a factory reset/wipe, wipe the dalvik cache and then flash your ROM.
Shahpur.Azizpour said:
I'm running stock jb and sadly its very laggy and many taps will result in many second of waiting. Even Google search takes ages to start.
Are the cyanogen Roms better? Is there already a working cm10 rom available?
Click to expand...
Click to collapse
First try change kernel..
Nocerino's Rulez with RAScarlo's ROM features TriNitY
I've had the same issue and came here to see if others shared. JB was initially pretty solid (I initially did a full wipe), but now it lags real bad. Google Now is the worst offender. It takes at least 5 seconds to appear, and then a good chunk of time to allow me to input text. It's too much.
I'm going to keep looking for another ROM, but honestly, I was counting on the fact that stock would be the most reliable. I've also had trouble using my radio to make calls / use data. I'm disappointed as I figured these problems were previously mostly due to custom ROMs. All I want is a stable, simple ROM that functions consistently.
Google Now was fast for me initially but it's super slow now but I doubt this is a ROM issue.
Everything else is fast and smooth.
Sent from my Nexus S using xda premium
I think its time to upgrade...just waiting for a nexus without pentile screen.
Do a full wipe, clear cache
This is the best time to check as many roms as possible. no need to worry about losing anything as you should of backed it all up by now. So clean slate and try some different Roms. To say stock is laggy does sound strange. So back up everything, even whats on your SD.
Clean start.
Best backup program to save apps and data - Titanium backup
Best app for everything else (app manager, processes etc..) - Romtoolbox.
Now go have fun!
try Xenonhd v6.0 and Air kernel JB weekly.
My phone is better than new with this combo. I am not going to try anything else until these give me a serious issue (I dont think they will)
Ok, I have an AT&T HTC One X. I have already rooted the phone and I have been running Venom Rom successfully for quite some time now. I decided I wanted to give some other roms a try today and I am running into some weird issues that I can't seem to figure out. To clarify my set up, I am not trying to run any custom kernels or anything that would potentially cause the issues I am experiencing. The roms I have tried and had these issues on are King Kang, Paranoid Android, and CM 10 official. With each the issues are always the same. First of all, I can't even type anything because Android Keyboard keeps force closing. Secondly, none of my hardware keys work at all except the back key, volume rocker, and power (home and recent apps do not function at all except to vibrate). Basically it leaves the phone completely unusable. I have gone back to Venom Rom for now because I have NEVER had any issues out of it. If anyone has any ideas why I am being plagued with these issues I would appreciate some feedback because I can't seem to find anyone else experiencing these kinds of issues honestly. Also I might add that I used a method to downgrade my HBOOT to, I believe, 1.09 instead of 1.14 because of the need to flash kernels separately with 1.14. My phone has worked flawlessly installing any ICS roms. This seems to only happen with JB roms. Thanks for your help in advance guys!
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
redpoint73 said:
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
Click to expand...
Click to collapse
Yeah, I of course did a factory reset and wiped cache and dalvik.
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
guitarjuggalo said:
Yeah, I of course did a factory reset and wiped cache and dalvik.
Click to expand...
Click to collapse
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
guitarjuggalo said:
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
Click to expand...
Click to collapse
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
redpoint73 said:
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Click to expand...
Click to collapse
Yes, I am on 1.09 for sure and using TWRP.
InflatedTitan said:
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
No, I haven't done a titanium backup. When things didn't work for whatever reason in any of those roms I just went back to the nandroid backup I had for Venom Rom that I did before jumping to any of those roms.
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
InflatedTitan said:
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it is very weird. I have never encountered these kind of issues. I have been using android since the original G1 on T-Mobile and haven't encountered issues with roms this horrible. Installing any of those roms makes my phone pretty much unusable. All 3 of them (haven't tried others) exhibit the same issues. Android keyboard force closes over and over again and won't ever pull up, and the home and recent apps buttons don't work at all. Also just about any Google app or service I tried to use was crashing out.
What are you using to download?
Sent from my One X using Tapatalk 2
InflatedTitan said:
What are you using to download?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Downloading through wi-fi on my computer and sending it to the phone via USB. Also dried downloading directly to the phone over wi-fi. Results are all the same.
So, it appears that nobody has an answer?
Did you check the md5 of the zip before flashing?
I had a problem where the Rom would install fine but issues loading. Md5 of the zip on my pc was good but was bad on my sdcard. Got messed up while transferring I guess.
Also try updating to latest twrp
Sent from my HTC One XL using xda app-developers app
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
lauterm said:
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I officially feel retarded. Thank you so much! That was indeed the issue. FML lol :good: :victory:
Its amazing that gapps controls so much that it even screwed my hardware keys with the wrong version. I really appreciate all the suggestions guys.
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
powerkatwedel said:
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Yeah I have the latest build if twrp and I think I already has the correct Mode from a prior rom. I didn't even check to verify guess I got too excited. I'll check and report back. Thanks.
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
powerkatwedel said:
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
Click to expand...
Click to collapse
Any other ideas that may be causing this?
powerkatwedel said:
Any other ideas that may be causing this?
Click to expand...
Click to collapse
Here is another user solved the issue, take from the thread:
"What I did was upgrade my recovery with Goo, I removed the SD card, I wiped the internal memory (not sure if this is necessary but what the hell), factory wiped, installed 7.1, once the phone booted up I logged in to gmail, let it sync, didn't install anything else and rebooted just to make sure it reboots fine, and it worked. Then I installed all my apps with TB without data, just the apps. That is what I did. I had the same problem as you for two days and was frustrated but then I read that if you upgrade your recovery it would work fine. I am assuming you are trying to wipe cache and it is telling you that it can't be mounted, that is another problem I was having, so I am assuming that by wiping the internal memory it cleared that problem up. I hope this helps you out. Hopefully someone here can either back up what I am saying or call me crazy and help you out. Good luck."
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
powerkatwedel said:
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
Click to expand...
Click to collapse
I was never able to get the WiFi to work, so I switched roms and was able to get everything working on Wicked. Thanks for all the help.