as the topic
newestuser said:
as the topic
Click to expand...
Click to collapse
What are you running (kernel + rom) at the moment?
And why do you want it removed?
SmG67 said:
What are you running (kernel + rom) at the moment?
And why do you want it removed?
Click to expand...
Click to collapse
im running everything stock,
installed just to quickly test so praised ArcMini custom rom. So i restored the backup later on because i didnt liked custom rom.
I felt that the battery drains a bit quicker now, i re-recalibrated and still feels like battery does drain faster than was before.
So i suspect its because i installed CMW.
newestuser said:
im running everything stock,
installed just to quickly test so praised ArcMini custom rom. So i restored the backup later on because i didnt liked custom rom.
I felt that the battery drains a bit quicker now, i re-recalibrated and still feels like battery does drain faster than was before.
So i suspect its because i installed CMW.
Click to expand...
Click to collapse
its more likely apps that are running in the background and widgets you have on the desktop, try a different rom such as lite version of cm7 and underclock your phone,
as far as my understanding goes, cmw is just a tool for installing roms backups ect and doesn't run when you are using it much like booting into a recovery panel on a pc possibly, basically it should not effect your battery drain, though I may be wrong,
I hope this help
no its not apps, because i did backup and restore and after restore battery drain started happening. If i didnt changed anything except installing CMW what else couldve cause that ? every app and configuration was the same...
no custom roms, i have tried and stock rom wins all the way except the extras 2.3 has, but still stock is more stable and graphicly better looking
so is there a way to remove ?
newestuser said:
no its not apps, because i did backup and restore and after restore battery drain started happening. If i didnt changed anything except installing CMW what else couldve cause that ? every app and configuration was the same...
no custom roms, i have tried and stock rom wins all the way except the extras 2.3 has, but still stock is more stable and graphicly better looking
so is there a way to remove ?
Click to expand...
Click to collapse
you could re-flash the original kernel, via flash tool, this will get rid of CMW and set thing to how they where, if you are using a custom kernel or stock kernel with additional modules that could also be responsible for your increased battery drain, you should be able to find the stock kernel on this forum as others have asked for it, alternatively I thing there is a way to get the stock kernel from pc companion
good luck hope this help
well im already using stock kernel...
thing is i dont want to reinstall OS i just want to remove CMW reinstalling os means i have reinstall apps and again link to link2sd
newestuser said:
well im already using stock kernel...
thing is i dont want to reinstall OS i just want to remove CMW reinstalling os means i have reinstall apps and again link to link2sd
Click to expand...
Click to collapse
Installing CWM installs Chargemon, Charger and Recovery.tar to /system/bin and 'sh' to system/xbin. I'm fairly sure chargemon and charger are custom replacements to files that already existed, so i'm not sure removing them would be wise. you can remove Recovery.tar though, which is the main CWM program. Not sure if the 'sh' file in system/xbin is safe to remove either, or what it does exactly.
In Roms that run on kernels that have CWM built in, the chargemon, recovery and the 'sh' file are not present in the ROM, so they may be safe to remove.
Make sure you keep backups of those files, or just rename them at first (just add a 2 at the end of the filename should disable them) to see if it leads to any problems, before you remove them altogether.
SmG67 said:
Installing CWM installs Chargemon, Charger and Recovery.tar to /system/bin and 'sh' to system/xbin. I'm fairly sure chargemon and charger are custom replacements to files that already existed, so i'm not sure removing them would be wise. you can remove Recovery.tar though, which is the main CWM program. Not sure if the 'sh' file in system/xbin is safe to remove either, or what it does exactly.
In Roms that run on kernels that have CWM built in, the chargemon, recovery and the 'sh' file are not present in the ROM, so they may be safe to remove.
Make sure you keep backups of those files, or just rename them at first (just add a 2 at the end of the filename should disable them) to see if it leads to any problems, before you remove them altogether.
Click to expand...
Click to collapse
sh is the shell. It's installed by default and I wouldn't recommend removing it under any circumstances
x10man
Related
Is it possible to make a custom ROM from an already running system? Some manufacturers don't update their phones (believe me, there are those minor companies that don't care at all), and users would be stuck to their stock ROM.
Soo, is it possible? Will copying all files from the root partition to the PC, modify with the usual tools, then zip, then flash, work?
Just curious
It's possible to work with a nandroid if that's what you mean, yes.
By the way, you shouldn't underclock your Optimus. That'll drain more battery, trust me, I did the same.
Noejn said:
It's possible to work with a nandroid if that's what you mean, yes.
Click to expand...
Click to collapse
How about not using a nandroid backup? I was thinking this would work because I had a look at the contents of the root directory of the phone, and then I had another look at a custom rom zip on my computer. I may sound stupid saying this, but I'm just curious xD
By the way, you shouldn't underclock your Optimus. That'll drain more battery, trust me, I did the same.
Click to expand...
Click to collapse
I've left the values as it is, but I forgot to update my sig. Anyway, thanks I uses the same power if the voltage isn't changed, right?
EDIT: About the ROM thing, I get it now. Never saw those .img files til now. Trying it out
OK so this probably sounds backwards from what everyone would expect. I've been using attn1's Liberated 2.2.2 FR008 rom and adding/removing apps to suite my needs. But now I want to REMOVE usb & wifi tethering! Sounds crazy but this phone is for a kid. I don't know much about developing. I'm guessing these features are built in to the OS, if so do I need to just get a custom settings.apk that doesn't give the tether options OR is there an apk i can remove (many of the apks in that rom have name that I'm not sure what they do so I left them in)? Any help would be really appreciated!
smokinbanger said:
OK so this probably sounds backwards from what everyone would expect. I've been using attn1's Liberated 2.2.2 FR008 rom and adding/removing apps to suite my needs. But now I want to REMOVE usb & wifi tethering! Sounds crazy but this phone is for a kid. I don't know much about developing. I'm guessing these features are built in to the OS, if so do I need to just get a custom settings.apk that doesn't give the tether options OR is there an apk i can remove (many of the apks in that rom have name that I'm not sure what they do so I left them in)? Any help would be really appreciated!
Click to expand...
Click to collapse
I guess you'd just have to get a new rom which does not have those options (none that I know of), but I still don't see why you need those options removed. Even if it is for a child, it doesn't really make a difference. The options can still be there and just not be used.
didnt the stock 2.1 NOT come with tethering? Its been a while, but I think thats how I remember it. So couldnt you just revert to a 2.1 rom?
CallMeAria said:
didnt the stock 2.1 NOT come with tethering? Its been a while, but I think thats how I remember it. So couldnt you just revert to a 2.1 rom?
Click to expand...
Click to collapse
Yes, the original AT&T 2.1 ROM did not have a tethering app.
tpbklake said:
Yes, the original AT&T 2.1 ROM did not have a tethering app.
Click to expand...
Click to collapse
Right, but I can't figure out how to remove the junk apps ect. from the RUU before flashing it like I can with a custom just by deleting apk's from the .zip file. Any ideas?
theonew said:
I guess you'd just have to get a new rom which does not have those options (none that I know of), but I still don't see why you need those options removed. Even if it is for a child, it doesn't really make a difference. The options can still be there and just not be used.
Click to expand...
Click to collapse
And just how do you leave the options there and be sure they will not be used??
I'm no dev but i think if you flash back to ATT 2.1 Rom and re-root to get super user i think you'll be abel to delete your ATT softwear with titanium backup... but I'm not sure. I hope this works for you
smokinbanger said:
Right, but I can't figure out how to remove the junk apps ect. from the RUU before flashing it like I can with a custom just by deleting apk's from the .zip file. Any ideas?
Click to expand...
Click to collapse
you can use adb to remove the apk's from the /system partition while the phone is in recovery after you flash the stock 2.1 RUU. You may have to reflash clockwork recovery after this, not sure if it will revert to stock recovery or not. Also, not sure on this one but you can check out the 2.1 Liberated Rom in the dev section and see if it has tethering enabled or not. Trying to remember this off the top of my head but its been so long since Ive done anything 2.1...
Yes, running the 2.1 RUU will remove Clockwork. So the full process would be to run the 2.1 RUU on the phone, then once done, run Unrevoked again on the phone. At this point I would recommend taking a Nandroid backup so you can revert any changes you make (i.e., if you have problems after deleting one of the apps).
Then you need to use adb to remove apps while the phone is in Recovery mode.
The downside of this (compared to just leaving the phone with stock 2.1 after using the RUU) is that Unrevoked automatically gives you root access in the ROM, which may or may not be what you want.
drumist said:
Yes, running the 2.1 RUU will remove Clockwork. So the full process would be to run the 2.1 RUU on the phone, then once done, run Unrevoked again on the phone. At this point I would recommend taking a Nandroid backup so you can revert any changes you make (i.e., if you have problems after deleting one of the apps).
Then you need to use adb to remove apps while the phone is in Recovery mode.
The downside of this (compared to just leaving the phone with stock 2.1 after using the RUU) is that Unrevoked automatically gives you root access in the ROM, which may or may not be what you want.
Click to expand...
Click to collapse
Root access to the rom is fine. But if I remove apks using adb aren't they still in the boot.img making it possible to simple do a system wipe/ hard reset and thus bring back all the junk apps in the stock 2.1 rom??
With all the DEVS on here it seems like there is a cleaner way to do all this...
smokinbanger said:
Root access to the rom is fine. But if I remove apks using adb aren't they still in the boot.img making it possible to simple do a system wipe/ hard reset and thus bring back all the junk apps in the stock 2.1 rom??
With all the DEVS on here it seems like there is a cleaner way to do all this...
Click to expand...
Click to collapse
No. System wipe would not revert the apps.
Help guys. I rooted a buddys fascinate. Had a backup but I accidentally wiped that too.
We were comparing phones and I had him run Quadrant and using ROM Toolbox I had him slide his CPU all the way up. Phone reboots now about a minute after you boot into the phone. Not enough time as its still loading/media scanning to get to the app and turn sliders back down.
I thought ADB would work through CWM and I could pull the app but that didn't work.
I flashed the same kernel (KGB over a touchwiz ROM) on top of it hoping it would reset but no luck.
What are my options?
reflash the rom
droidstyle said:
reflash the rom
Click to expand...
Click to collapse
i have. it still reboots about a minute after booting - i assume because ROM Toolbox is still there trying to set CPU?
Edit: also, i'm a little surprised i wasn't able to ADB through recovery? It was on the same laptop i rooted it with so I'm sure the drivers are there. Wire is OK as I was browsing the SD card.
Edit #2: ok i'm losing my eyesight. last night i saw a link to a stock eh03 kernel I was going to try. I figure if the kernel doesn't support OC'ing, i could get in. uninstall the app and flash the KGB kernel back. can you point me to the stock kernel or at least one w/out OC'ing support?
(hes running TSM EH03 btw)
Edit #3: ok found the stock kernel http://forum.xda-developers.com/showpost.php?p=19865577&postcount=140
now i just need to get off work.
damn i feel like a dip****.
Sputnikk23 said:
i have. it still reboots about a minute after booting - i assume because ROM Toolbox is still there trying to set CPU?
Edit: also, i'm a little surprised i wasn't able to ADB through recovery? It was on the same laptop i rooted it with so I'm sure the drivers are there. Wire is OK as I was browsing the SD card.
Edit #2: ok i'm losing my eyesight. last night i saw a link to a stock eh03 kernel I was going to try. I figure if the kernel doesn't support OC'ing, i could get in. uninstall the app and flash the KGB kernel back. can you point me to the stock kernel or at least one w/out OC'ing support?
(hes running TSM EH03 btw)
Edit #3: ok found the stock kernel http://forum.xda-developers.com/showpost.php?p=19865577&postcount=140
now i just need to get off work.
damn i feel like a dip****.
Click to expand...
Click to collapse
So you three fingerd into recovery, wiped data, reflashed TSM and still no dice? If so, then follow section 2 of my guide.
droidstyle said:
So you three fingerd into recovery, wiped data, reflashed TSM and still no dice? If so, then follow section 2 of my guide.
Click to expand...
Click to collapse
Recovery, and just flashed TSM over whats there. BOots into phone but not enough time to get to ROM Toolbox to turn down sliders.
Trying to avoid losing his data/text messages/contacts.
Sputnikk23 said:
Recovery, and just flashed TSM over whats there. BOots into phone but not enough time to get to ROM Toolbox to turn down sliders.
Trying to avoid losing his data/text messages/contacts.
Click to expand...
Click to collapse
your going to have to wipe data unfortunately...hopefully his contacts are synced with google and apps backed up with titanium backup. You could try pulling the sd card and putting in a pc to get contacts, pictures...etc, but the phone is going to need a data wipe.
droidstyle said:
your going to have to wipe data unfortunately...hopefully his contacts are synced with google and apps backed up with titanium backup. You could try pulling the sd card and putting in a pc to get contacts, pictures...etc, but the phone is going to need a data wipe.
Click to expand...
Click to collapse
where are contacts stored then?
and you don't think flashing a non-OC'able kernel will do the trick?
Sputnikk23 said:
where are contacts stored then?
and you don't think flashing a non-OC'able kernel will do the trick?
Click to expand...
Click to collapse
Edit* Not sure where the contacts are stored, somebody can hopefully chime in there.
Also one thing you could try is going into the sd card via pc and deleting the rom tool box app in system/app folder. I have not tried this before...so it may or may not work! You can try flashing the stock kernel, but Im not sure if that will do anything either. Never really been in this situation since I keep all my stuff backed up.
droidstyle said:
No because the kernel dont overwrite the app data...your OC app(rom tool box) still has the voltage script written in the initd folder and the stock eh03 kernel is capable of being OC'd...so nothing will change there.
Click to expand...
Click to collapse
DAMN IT.
Voltages? I didn't change voltages. Just CPU Sliders. Think the nstools reset zip might work?
Also, I followed you guide to flash TSM, so I'm pretty sure its running CWM 2.5.1 (its all red). Shouldn't I be able to adb in through recovery and take out the init.d script/modify text values for the CPU/Pull the ROM Toolbox apk/etc?
Edit: YES YES YES.. sd card via PC.. but.. how do I get to the /system/app through SD card on PC while in recovery. All I get is the SD card contents?
Sputnikk23 said:
DAMN IT.
Voltages? I didn't change voltages. Just CPU Sliders. Think the nstools reset zip might work?
Also, I followed you guide to flash TSM, so I'm pretty sure its running CWM 2.5.1 (its all red). Shouldn't I be able to adb in through recovery and take out the init.d script/modify text values for the CPU/Pull the ROM Toolbox apk/etc?
Edit: YES YES YES.. sd card via PC.. but.. how do I get to the /system/app through SD card on PC while in recovery. All I get is the SD card contents?
Click to expand...
Click to collapse
Im sorry I meant mhz not voltage lol...
scratch the sd card idea, you cant access the system from pc.
If you are familiar with adb, then yes I believe what you said above will work. One thing tho, stock kernels do not support init.d scripts. So if your on the stock kernel, the rom toolbox app must be applying the OC on boot. I think your best shot is to pull the RTB.apk via adb.
droidstyle said:
Im sorry I meant mhz not voltage lol...
scratch the sd card idea, you cant access the system from pc.
If you are familiar with adb, then yes I believe what you said above will work. One thing tho, stock kernels do not support init.d scripts. So if your on the stock kernel, the rom toolbox app must be applying the OC on boot. I think your best shot is to pull the RTB.apk via adb.
Click to expand...
Click to collapse
I haven't tried stock kernel yet. So if it doesn't support init.d, and thats how its being set - seems a valid theory that flashing it would get me back into being able to boot OK.
Whats RTB.apk?
And any ideas as to why I can't adb in when in recovery? Just a driver issue you think? I used the same laptop to root his phone so i figured drivers would be good, so I didn't explore that much last night. USB Mount worked OK obviously.
Sputnikk23 said:
I haven't tried stock kernel yet. So if it doesn't support init.d, and thats how its being set - seems a valid theory that flashing it would get me back into being able to boot OK.
Whats RTB.apk?
And any ideas as to why I can't adb in when in recovery? Just a driver issue you think? I used the same laptop to root his phone so i figured drivers would be good, so I didn't explore that much last night. USB Mount worked OK obviously.
Click to expand...
Click to collapse
(ROM TOOL BOX. APK) lol
If rom tool box is setting the OC at boot and not using init.d script, then no flashing a stock kernel wont fix it.
The samsung driver you used wont work with adb, you need the nexus google driver. A simple Google search will pull it up.
Fyi, the next time you run into issues, a full detailed writeup on the devices setup and exact methods used to get there would help alot.
droidstyle said:
(ROM TOOL BOX. APK) lol
The samsung driver you used wont work with adb, you need the nexus google driver. A simple Google search will pull it up.
Click to expand...
Click to collapse
Hmmm.. Maybe I made a false presumption (being the owner of a Nexus S 4g, totally pimped the hell out btw) that I already had those drivers. Thank you man. You pointed me in the only possible right direction.
Edit: http://forum.xda-developers.com/showthread.php?t=1459905 <-- according to that the stock kernel doesn't do OC?
Hello all devs, I have a suggestion that I think many people that cant unlock the bootloader will think very nice.
The sugestion is that the devs if they time to make a version like JJs hybrid rom for locked bootloaders.
I have also tried the Miui rom, and I removed the format script and boot.img and it booted fine without any major problems.
So my sugestion is that the devs makes their roms for stockkernel for people with locked bootloader, and makes a deletion script that removes all the files from the old rom.
Devs, what do you think about my idea?
Thats not possible to remove format script...
If you dont format system partition, it will be overloaded with applications and frameworks from Old and New ROM... the two ROM appz might not share the same sign keys... that would result in Bootloop or Series of FCs on install...
jjdoctor said:
Thats not possible to remove format script...
If you dont format system partition, it will be overloaded with applications and frameworks from Old and New ROM... the two ROM appz might not share the same sign keys... that would result in Bootloop or Series of FCs on install...
Click to expand...
Click to collapse
Here are a solution that I think maybe works:
First create a homemade format script that removes all the stuff on partiation, but it doesnt run the format options, it just deltes everything manually from recovery.
And then just remove the format script from the roms zipfile and remove the boot.img too.
Then just resign the zip file with sign by enyblock.
Thats should work, maybe somebody can try it?
DevStaffAndroid said:
Here are a solution that I think maybe works:
First create a homemade format script that removes all the stuff on partiation, but it doesnt run the format options, it just deltes everything manually from recovery.
And then just remove the format script from the roms zipfile and remove the boot.img too.
Then just resign the zip file with sign by enyblock.
Thats should work, maybe somebody can try it?
Click to expand...
Click to collapse
thats practically not possible either...
MIUI, CM9 have different appz and framework...
applications aside, who has enough time to write a delete script for more than a thousand lib and other system files?..
I am trying to find out the files that don't load on statup after installing a flashable zip on Locked bootloaders... that is better way of finding a solution..
jjdoctor said:
thats practically not possible either...
MIUI, CM9 have different appz and framework...
applications aside, who has enough time to write a delete script for more than a thousand lib and other system files?..
I am trying to find out the files that don't load on statup after installing a flashable zip on Locked bootloaders... that is better way of finding a solution..
Click to expand...
Click to collapse
But isnt there a way to just remove all folders using recursive deletion, isnt that the easiest way to make a deletion script?
And then just remove the format script and boot.img.
With my my solution ive managed to run the miui based on offcial semc ics on my Xperia Ray it worked fine.
Me: Hmm.. What is this thread?
Self: Looks to be someone requesting something from Developers.
Me: Oh - that's nice. Did they say please?
Self: Yeah looks like they kinda did. But looks like they posted it in Development!!!
Me: DOH! Is there any actual development taking place?
Self: No! It's just a discussion thread!
Me: :facepalm: Well looks like it needs to be moved to General.
Self: Hope they learn their lesson.
jerdog said:
me: Hmm.. What is this thread?
Self: Looks to be someone requesting something from developers.
Me: Oh - that's nice. Did they say please?
Self: Yeah looks like they kinda did. But looks like they posted it in development!!!
Me: Doh! Is there any actual development taking place?
Self: No! It's just a discussion thread!
Me: :facepalm: Well looks like it needs to be moved to general.
Self: Hope they learn their lesson.
Click to expand...
Click to collapse
hahahahahahahaha
you make my day hahahaha
This is why most custom ROMs require custom kernel
Needs unlocked bootloader
(actually hybrom does not contain a boot image.Thus, when you install hybrom you don't mess with your boot image at all.BUT recovery from nAa is installed in /system and while system is formated during the installation of hybrom,recovery messes with it self.That's why unlocked bootloader and a custom kernel with recovery is necessary for now to install hybrom)
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1373435
It means, that if Recovery is installed in /system folder, and you want to install custom ROM, which (mostly) replaces the system folder, Recovery would be removed and would end up in complete stop with bootloop.
If Recovery is installed in the kernel, then the whole /system partition can be removed without affecting the Recovery at all.
Also, stock kernels have quite low functionality, that's why it is not widely used.
Someguyfromhell said:
This is why most custom ROMs require custom kernel
Source: http://forum.xda-developers.com/showthread.php?t=1373435
It means, that if Recovery is installed in /system folder, and you want to install custom ROM, which (mostly) replaces the system folder, Recovery would be removed and would end up in complete stop with bootloop.
If Recovery is installed in the kernel, then the whole /system partition can be removed without affecting the Recovery at all.
Also, stock kernels have quite low functionality, that's why it is not widely used.
Click to expand...
Click to collapse
But I restored my nAa CWM backups several times and that as I know formats the system before the restore..
Yeah, about the boot.img, can we dont just mod the chargemoon to load the rom?
Or charger?
DevStaffAndroid said:
Yeah, about the boot.img, can we dont just mod the chargemoon to load the rom?
Or charger?
Click to expand...
Click to collapse
Loading the ROM is not the problem, it is the functionality.
Modifying stock kernel can be done, but if you want to make it work, you have to unlock bootloader to install it also.
Someguyfromhell said:
Loading the ROM is not the problem, it is the functionality.
Modifying stock kernel can be done, but if you want to make it work, you have to unlock bootloader to install it also.
Click to expand...
Click to collapse
But I mean the roms that are built for stockkernel like some of the miui roms?
Skickat från min Xperia ray via Tapatalk 2
So now that I have root on my phone, using Titanium Backup, WHAT should I backup? I mean... my phone doesn't have inherent instability now does it?
Or does the instability (possibly) come from xposed modules I install?
Are there sets of steps I should take before installing new root apps?
Thanks!
-Matt
Root details:
Verizon S4 (sch-i545)
Stock ROM (4.4.2)
Back up anything you would miss loosing if something happed. For me thats nothing, for others thats maybe a particular apk version, or an apps data.
What do you need to do before installing root apps? Root apps are just programs that require admin rights. Nothing magic, do whatever that app might need, which is probably nothing.
It is generally good to have a full system backup from your recovery... For when you try to do _______ and **** it up.
scryan said:
Back up anything you would miss loosing if something happed. For me thats nothing, for others thats maybe a particular apk version, or an apps data.
What do you need to do before installing root apps? Root apps are just programs that require admin rights. Nothing magic, do whatever that app might need, which is probably nothing.
It is generally good to have a full system backup from your recovery... For when you try to do _______ and **** it up.
Click to expand...
Click to collapse
Okay great! I already backed up any folders (pictures, pdfs from camsacanner, roms) to my computer via usb before rooting... so...
So when people are talking about TWRP/CWmod recovery... how is it different from stock recovery?
So basically a custom recovery is an all in one answer that allows you to back up EVERYTHING but also allows you to back up EVERYTHING in one blow?
blueman189 said:
Okay great! I already backed up any folders (pictures, pdfs from camsacanner, roms) to my computer via usb before rooting... so...
So when people are talking about TWRP/CWmod recovery... how is it different from stock recovery?
So basically a custom recovery is an all in one answer that allows you to back up EVERYTHING but also allows you to back up EVERYTHING in one blow?
Click to expand...
Click to collapse
Stock recovery will let you do a factory wipe to basically clear data and reset your system to recover from something that messes up your install and makes your phone unusable.
Custom recoveries allow you to flash unofficial files, as well as take basically a snapshot of your system. With a custom recovery you can make a backup of your phone, and almost no matter what happens, you can flash that backup and it will be like nothing happened.
So when you try and run some xposed module that isn't written well, and now makes your phone crash every 2 minutes, you can boot to recovery and flash back to the backup you took right before you installed that module, and it will be like you never did it.
The recovery images are kinda large, as its all your data/apps/the OS all in one. Many custom recoveries will have a file manager that will allow you to deal with files individually, but most typically the point is taking a snapshot of your current system so you can go back to it. I make backups before trying a new rom, that way if after a little bit I am not happy I just flash back and its like I never changed anything.