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?
Related
Okay, so after seeing how most people have flashed their phones, I'm tempted to do this sooner rather than later.
So my phone being rooted/unlocked now.
The next step is to back up, I have Titanium Pro, am to only backup apps with it?
Is that considered a sufficient back up of the phone?
I'm running Eclair 2.1update1 - T959UVJI6
I keep reading about Odin, etc so this is throwing me for a loop as to how to do this.
Then I just download a ROM that I like, load it on my microSD and flash through there, (volume button, power button, pressing, etc)?
Thanks, appreciate any help.
You can back up everything with titanium pro. But most people use it to.restore 3rd party apps or to uninstall or freeze apps. Also make sure you have rom manager installed and flash clockwork recovery. Put your rom of choice on your internal sd card not your external micro sd card.
Powered by Axura with a dash of Voodoo
Odin is mostly used when you mess up your phone and it wont work. Search around and read up and download odin and the correct files and have it on hand for.when you bork up your phone.
Powered by Axura with a dash of Voodoo
koooba said:
Okay, so after seeing how most people have flashed their phones, I'm tempted to do this sooner rather than later.
So my phone being rooted/unlocked now.
The next step is to back up, I have Titanium Pro, am to only backup apps with it?
Is that considered a sufficient back up of the phone?
I'm running Eclair 2.1update1 - T959UVJI6
I keep reading about Odin, etc so this is throwing me for a loop as to how to do this.
Then I just download a ROM that I like, load it on my microSD and flash through there, (volume button, power button, pressing, etc)?
Thanks, appreciate any help.
Click to expand...
Click to collapse
In titanium backup just click backup all app+data
Do NOT backup red text apps their system apps and will give you a headache later.
Download rom manager and click first option and flash clockwork.
Then press install rom from SD card
It will boot into recovery if its green text recovery press reinstall packages then it'll reboot and go there again click reinstall packages again.
Now its set.
Go to install zip from SD card.
Then again
And find ur rom.
Press install.
Wait till its done.
Done
GreggoryD502 said:
You can back up everything with titanium pro. But most people use it to.restore 3rd party apps or to uninstall or freeze apps. Also make sure you have rom manager installed and flash clockwork recovery. Put your rom of choice on your internal sd card not your external micro sd card.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
Is the free version of ROM manager sufficient or are they identical, except one has ads?
ROM manager meaning this one correct? Made by clockworld?
http://www.appbrain.com/app/rom-manager/com.koushikdutta.rommanager
Thank you.
xriderx66 said:
In titanium backup just click backup all app+data
Do NOT backup red text apps their system apps and will give you a headache later.
Download rom manager and click first option and flash clockwork.
Then press install rom from SD card
It will boot into recovery if its green text recovery press reinstall packages then it'll reboot and go there again click reinstall packages again.
Now its set.
Go to install zip from SD card.
Then again
And find ur rom.
Press install.
Wait till its done.
Done
Click to expand...
Click to collapse
Don't backup the red ones? But if they're part of the system....?
I already did, so maybe I'll check my microSD card and delete it and do it over by unchecking the red? lol
Yes the free version is sufficient to flash roms.
Powered by Axura with a dash of Voodoo
...and this program, correct?
http://www.appbrain.com/app/clockworkmod-launcher/com.koushikdutta.launcher2
koooba said:
Don't backup the red ones? But if they're part of the system....?
I already did, so maybe I'll check my microSD card and delete it and do it over by unchecking the red? lol
Click to expand...
Click to collapse
Its fine to back the red ones up. Just make sure after you flash a new rom that you don't restore any of the red ones. That's when you run into issues.
Powered by Axura with a dash of Voodoo
Gotcha, because the ROMS already have the system files (red), overwrite issues, etc. Understood.
koooba said:
Gotcha, because the ROMS already have the system files (red), overwrite issues, etc. Understood.
Click to expand...
Click to collapse
The force is strong with this one!
Powered by Axura with a dash of Voodoo
lol come on now, I admit I'm a noob with all this.
I'm fairly confident with tech stuff, but hearing "bricking" etc, really got me so paranoid about it. lol
koooba said:
lol come on now, I admit I'm a noob with all this.
I'm fairly confident with tech stuff, but hearing "bricking" etc, really got me so paranoid about it. lol
Click to expand...
Click to collapse
I know what you mean. I still get nervous everytime I flash something and wait for it to boot up. Just make sure you have odin and the right files loaded on your pc invade you goof up.
Powered by Axura with a dash of Voodoo
lol @ nervous when booting up... that'll be me no doubt.
As for Odin, that's tomorrows adventure, getting it.
Right files on my PC? I thought everything is done strictly via the phone (flash) way. I have Kies installed and my computer does recognize the phone. I'm assuming Odin is the only concern left for me?
koooba said:
lol @ nervous when booting up... that'll be me no doubt.
As for Odin, that's tomorrows adventure, getting it.
Right files on my PC? I thought everything is done strictly via the phone (flash) way. I have Kies installed and my computer does recognize the phone. I'm assuming Odin is the only concern left for me?
Click to expand...
Click to collapse
You have to download some files on your PC for Odin so u can go to a safe rom that wont brick on ya
Yea after you download odin you will need 2 different files. Ones a tar file and the other is a pit file. You only use these via odin. Just be patient when your waiting for it to boot up after flashing. Especially if you flashed a rom that has a voodoo kernel. It will take a good 10-15 minutes to convert. Just let it be.
Powered by Axura with a dash of Voodoo
xriderx66 said:
You have to download some files on your PC for Odin so u can go to a safe rom that wont brick on ya
Click to expand...
Click to collapse
I'm assuming that this would be sufficient for my needs.
http://forum.xda-developers.com/showthread.php?t=804850
I've looked around and this was the only place this factory ROM was available.
GreggoryD502 said:
Yea after you download odin you will need 2 different files. Ones a tar file and the other is a pit file. You only use these via odin. Just be patient when your waiting for it to boot up after flashing. Especially if you flashed a rom that has a voodoo kernel. It will take a good 10-15 minutes to convert. Just let it be.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
I was thinking Team Whiskey or Axura, still on the fence with either of these two.
But 10-15 minutes??
I took my SC card out and popped it into my PC, no files other than my music and pictures.
I then renamed the location from TitaniumBackup to external_sd/titaniumbackup, restarted the phone, opened TB to do a batch backup and there were no files listed. I renamed the default save location back to TitaniumBackup and the files were there.
Confusing.
How do I set the batch backups to save to my external SD card?
Or what am I doing wrong?
Im kind of confused as to what you are trying to do. Why would you want to save your titanium backups to your external sd card? There is really no reason to.
Powered by Axura with a dash of Voodoo
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Just curious as to if this is rooted or just fixed to allow use of CWM?
Nevermind just read the full post!!
So just to make sure, I could use the one zip to return to full stock but with the 1.2 update? Also will this work if I have CM7 and CWM on my emmc? So reboot into CW, format \system and \data then flash the update-nc-stock-1.2-signed.zip, then Reboot. At that point, I should be 100% 1.2 stock, sound about right?
I thinking about returning to stock and just run CM7 for my SD if this is an options.
Thanks,
Derek.
DGarmon said:
So just to make sure, I could use the one zip to return to full stock but with the 1.2 update? Also will this work if I have CM7 and CWM on my emmc? So reboot into CW, format \system and \data then flash the update-nc-stock-1.2-signed.zip, then Reboot. At that point, I should be 100% 1.2 stock, sound about right?
I thinking about returning to stock and just run CM7 for my SD if this is an options.
Thanks,
Derek.
Click to expand...
Click to collapse
Assuming you haven't fooked up any paritioning by using the "dual-boot" stuff you can return to 100% stock by doing the folllowing:
Download the update-nc-stock-1.2-signed.zip above
Flash the zip with CWM (either from emmc or sdcard)
Use CWM to factory reset the device (wipe /data and /cache)
Reboot into 100% stock froyo
If you have modified your partitions this will not work.
This won't work off of an sd right?
I'd like to modify this so it just installs to my dual boot partition.
I've done this before with flashing kernels, but there are more partitions here to take care of.
I figure if I'm going to change the updater script to mount the correct block partitions then I should also have it wipe /data and /cache on the secondary partition.
Any ideas on syntax?
sassafras
Thanks
Once we have a rooted version I'll probably check it out for fun.
nemith said:
Assuming you haven't fooked up any paritioning by using the "dual-boot" stuff you can return to 100% stock by doing the folllowing:
Download the update-nc-stock-1.2-signed.zip above
Flash the zip with CWM (either from emmc or sdcard)
Use CWM to factory reset the device (wipe /data and /cache)
Reboot into 100% stock froyo
If you have modified your partitions this will not work.
Click to expand...
Click to collapse
But then I'm stuck with stock froyo - I can't go back to CM7 after I've satisfied my curiosity, right?
Hmmm, have to think about that......then, again, maybe not.
nemith said:
There are two files.
Click to expand...
Click to collapse
Many thanks for these.
Please post MD5's of these so that we can be sure that the download was successful (some may want to store the file for later use).
BTW, free MD5checker can be found at getmd5checker.com
HarleyChick said:
But then I'm stuck with stock froyo - I can't go back to CM7 after I've satisfied my curiosity, right?
Hmmm, have to think about that......then, again, maybe not.
Click to expand...
Click to collapse
Create a backup first.
Thanks for the files nemith. Much appreciated.
Sent from my NookColor using Tapatalk
Hey nemith, would it be okay if I used this as a base for a rooted version? Give you full credit of course, just dont feel like going through the hassle of the updater script and what not.
msgnyc said:
Create a backup first.
Thanks for the files nemith. Much appreciated.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I guess I wasn't clear the first time: if I use this method, am I stuck with B&N's version of Froyo until someone figures out how to root this one, or can I just reflash CM7? And I'm not sure I understand the difference between both of the zips that nemith has produced.
In any case, thanks nemith - I always appreciate the work that the devs do!
HarleyChick said:
I guess I wasn't clear the first time: if I use this method, am I stuck with B&N's version of Froyo until someone figures out how to root this one, or can I just reflash CM7? And I'm not sure I understand the difference between both of the zips that nemith has produced.
In any case, thanks nemith - I always appreciate the work that the devs do!
Click to expand...
Click to collapse
If you dont like this, just boot into a bootable clockwork recovery and flash cm7 or whatever you want. You wont be stuck on this.
One zip removes Clockwork Recovery and puts the stock recovery back. The other leaves Clockwork Recovery intact.
I'd assume, leaving it intact allows you to flash back to any backups or any other Rom if incase you do not like the official build.
I'm at work so I'm unable to test it out.
Or you can always just use a bootsble SD with clockwork on it to reflash whatever ron or backup you have.
Sent from my NookColor using Tapatalk
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
My rooted BN1.1 with auto-nooter 3.0 does NOT have CWM in emmc. Can I use update-nc-stock-1.2-signed.zip to go to 1.2 unrooted?
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
Any way you could make something would allow you to flash 1.2 onto a secondary parttion for those of us who are dual booters?
So Ive got this thing rooted but I for the life of me cannot get the market to work. I have the vending.apk and googleservicesframework.apk under /system/app but market will not show up in my app drawer on the stock or adw launcher. Under manage applications, market or googleservicesframework arent there either. Does the nook have other dependencies? If anyone with some experience could throw some suggestions my way. ADB isnt currently working without the driver. Ive added other apps that are showing up and working perfectly.
Did you modify the build.prop?
Sent from my Nook Color using XDA App
scoutcamper said:
Did you modify the build.prop?
Sent from my Nook Color using XDA App
Click to expand...
Click to collapse
Nope didnt touch it, im usually devving for the evo, so modding that isnt normally needed for gapps. What would need to be modified in the build.prop?
The device code will have changed and prevent market access. Try pulling the device code from a froyo device with market access like Droid X.
Sent from my Nook Color using the XDA App
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.
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
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
jeff5347 said:
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
Click to expand...
Click to collapse
Well what ROM are you using for starters.
that might be important right.. .sorry.. its aokp 6
Ok. Well if you can get back into BSR, try and wipe the dalvik cache in the advance settings. I never use the fix permissions option. Maybe that did something to your device.
did that too. Still on the boot logo. is a sbf in order
jeff5347 said:
did that too. Still on the boot logo. is a sbf in order
Click to expand...
Click to collapse
Well I wouldnt see why it would do that if you just wiped cache and fixed permissions. Did you have any other mods on there? Were you using the patched CM7 BSR and not the original one?
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
jeff5347 said:
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
Click to expand...
Click to collapse
That one is fine to use on Eclipse. But pretty much any other ROM we have (CM7, CM9, CM10, AOKP, Paranoid Android and I think even MIUI), you need to use the CM7 BSR named "MOTODX2_Bootstrap-CM7-signed.apk" which is found in the CM7 thread. That may have been the problem.
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
jeff5347 said:
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
Click to expand...
Click to collapse
I think CM10 is more stable than any of the ICS ROMs. But with the stability, there comes other small issues that the ICS ROMs dont have. Its a trade off. Main issues of CM10:
1. Messing with bluetooth may cause phone to crash durring calls. Reboot fixes it until bluetooth is messed with again. (Might be fixed with an update)
2. Storage is in a different location. Not really an issue but its also swapped back to the original 4gigs for the internal. All your files will be flipped after using other ROMs for so long. (not a huge deal)
3. Due to the storage being moved around, apps that are stored on the SD card will disappear after reboot. (will probably be fixed in the future)
4. Flashing ROMs in recovery wont work. If any update comes out, you have to either SBF and update or nandroid back to ICS and update. (again, not a huge issue)
Other than that, I cant really think of any bad stuff. Its faster and I have no random reboots. I recommend it if you can live with the issues I mentioned which are honestly not bad.
Also, with the BSR files, in case you dont know already. When you are on stock 2.3.4, you first use the original BSR. Then when you flash CM10, you install the CM7 BSR.
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
jeff5347 said:
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
Click to expand...
Click to collapse
1. I use bluetooth every now and then but I never turn it off. It seems that toggling the bluetooth on and off or visa versa triggers the issue and a reboot fixes it again.
2. I forget what Eclipse had. Its been so long. But ever since CM7, the flip flop mod has been included in all the ROMs which meant you got your SD card (which the droid X2 comes with 8GB) as internal storage and the actual 4GB internal storage was turned into the "external storage." CM10 reverted back to the original 4GB internal and 8GB external.
3. Everything you download and install on your phone will usually be installed on the internal storage. I think if you have apps over a certain size (which isnt very many. Mostly games), they are installed on your SD card. Those are the ones the system has a problem reading after a reboot. the actual files you have downloaded from XDA will still be there. Just installed apps might disappear.
4. Not really sure what you are asking here. But if you get A2 installed and up and running and A3 comes out, You will pretty much need to start over. But for me, thats fine. I use Titanium Backup and restore everything after a wipe anyway. What data are you referring to?
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
jeff5347 said:
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
Click to expand...
Click to collapse
Honestly, I dont even know what MD5sum means. I'm not that tech smart. lol. I know thats the right file name though. And if you got it from here: http://goo.im/gapps you should be fine.
hahaha neither do i lol yea thats where i got it.. again thank you
No problem. If you have any other issues, just reply here and I'll help out.
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
jeff5347 said:
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
Click to expand...
Click to collapse
Pete's can be a PITA... If usb debug is enabled and unkown sources is checked just keep trying. I've had to "one click" 5 or 6 times before it works right. Close the program between tries. Also make sure your phone isn't in PC charge mode or anything.
Sorry for not updating this. After trying for 2 hrs I started trying everything. It turned out I had to use the cable that came w the dx2. No other cables worked
Sent from my MB870 using xda premium
Ah, my bad I should have read the time stamp. Anyway yea, the cable is a big deal (even though that sounds crazy.)
---------- Post added at 10:54 PM ---------- Previous post was at 10:43 PM ----------
Lol oh and btw MD5 checksums are
"The MD5 checksum for a file is a 128-bit value, something like a fingerprint of the file. There is a very small possibility of getting two identical checksums of two different files. This feature can be useful both for comparing the files and their integrity control."