Related
Hi ,
when i try to flash my phone using the rom "ICS Passion v13"
i have these errors :
E:Failed to verifity whole-file signature
E:signature Verification Failed
Installation aborted
Download fresh, try again.
Sent from my SGH-T959 using XDA App
Redmartianducky said:
Download fresh, try again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I did not understand what you say ?
My first inclination would be a bad download, try a different dl location and try again.
Sent from my SGH-T959 using XDA App
Redmartianducky said:
My first inclination would be a bad download, try a different dl location and try again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i have tryed with another rom , same problem
Where in the process are you getting these errors? There are multiple steps to installing ICS that this could occur. What ROM are you running right now? If stock, is it 2.1 or 2.2? Do you have CWR installed? Is it installed with Update.zip or through ROM Manager? Did you flash CM7 before ICS?
Simply putting that you got this error is not enough information for us to diagnose and help.
Edit::: also please don't spam the other posts with "Good" or "Great to hear that" to get your post count up like was done in Themes and Apps section. There are many threads to that you can post in to get the count up legitimately.
Woodrube said:
Where in the process are you getting these errors? There are multiple steps to installing ICS that this could occur. What ROM are you running right now? If stock, is it 2.1 or 2.2? Do you have CWR installed? Is it installed with Update.zip or through ROM Manager? Did you flash CM7 before ICS?
Simply putting that you got this error is not enough information for us to diagnose and help.
Edit::: also please don't spam the other posts with "Good" or "Great to hear that" to get your post count up like was done in Themes and Apps section. There are many threads to that you can post in to get the count up legitimately.
Click to expand...
Click to collapse
hi ,
i have the stock rom (2.2) CWR is not installed , i have not Flash CM7 before ICS
That is the problem. Go to my guide in the General or in my sign and follow it.
it rooted? you have the right CWM rec on it? im not a pro but i know that might be it
You must install CyanogenMod 7 before install a ICS rom.
it's the best form if you dont wanna have problem with the bootloader and bricked your phone!!
I suggest you start here:
http://forum.xda-developers.com/showthread.php?t=849028
ascallop said:
I suggest you start here:
http://forum.xda-developers.com/showthread.php?t=849028
Click to expand...
Click to collapse
hi ,
i have use your link for installing ICS , i have do it .
but i have a problem :
when i click on any thing i have this : Unfortunatley , The process android.process.media has stopped ?
how i fix this ?
After installing it, did you let it settle for 20 minutes before using the phone?
If you did, try flashing again, or download the rom again.
Sent from my SGH-T959 using XDA App
I happen to me the first time I load the Passion 13. So I delete the passion zip file from where I will load it (download folder in my case), then redownload the passion 13 zip file and copy it to the download folder. It works for me.
Jacendb said:
After installing it, did you let it settle for 20 minutes before using the phone?
If you did, try flashing again, or download the rom again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hi ,
i didn't wait
so i try to reflash .
paranoxxx said:
hi ,
i didn't wait
so i try to reflash .
Click to expand...
Click to collapse
this is what i did, when helping my friend boot it up,
you have to make sure your rooted
then install ClockWorkMod recovery onto the phone,
then install CM7 after it boots back to recovery
then wipe data and cache
then install ics passion wait for it to boot all the way back to recovery for the last time
install the clean up patch and the phone will work perfect
i had the same problem, thats what i had to do make sure it worked perfect
Jacendb said:
After installing it, did you let it settle for 20 minutes before using the phone?
If you did, try flashing again, or download the rom again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
what if you didn't let let it settle for 20 minutes? I didn't most of thing seems alright, except that the dial keys seem to be sticky if I hold it a hair too long, like when you try to do quick dial, the key will stay selected and you can't dial other numbers until it unstick.
I'm using Passion 13, not sure if I have kiss 2.2.
A question for everyone: can't Passion 13 or ICS for Vibrant in general let you assign phone number for quick dial? You have to use direct dial widget?
paranoxxx said:
when i click on any thing i have this : Unfortunatley , The process android.process.media has stopped ?
how i fix this ?
Click to expand...
Click to collapse
Usually a boot into recovery, fix permission and wipe cache and dalvik cache will clear this up. But sometimes it is just a bad download too.
Kaptinkrunk said:
this is what i did, when helping my friend boot it up,
you have to make sure your rooted
then install ClockWorkMod recovery onto the phone,
then install CM7 after it boots back to recovery
then wipe data and cache
then install ics passion wait for it to boot all the way back to recovery for the last time
install the clean up patch and the phone will work perfect
i had the same problem, thats what i had to do make sure it worked perfect
Click to expand...
Click to collapse
This is a Guide on putting ICS ROMs on your Vibrant that explains everything.
ciditin said:
what if you didn't let let it settle for 20 minutes?....
I'm using Passion 13, not sure if I have kiss 2.2.
Click to expand...
Click to collapse
It is always a good idea to let the phone go through a "settling" period after you flash it. There are RAM tweaks to finish, media scanning and a host of other things that need to be completed as you just installed a completely new operating system on your phone. Especially don't log into Market or Titanium and start restoring as this can cause problems long term. What is 20 mins compared to problems and hassles for the next few days/weeks.
If you don't know if you have Kiss 2.2 on your phone, then you don't have it b/c you have to flash it. See HERE
Hey guys, I continually get this error message upon manually forcing my phone into recovery. I'm on UCLF5 ICS OBJECTION from btw with the latest version of cwm. I would appreciate some help with regard to what exactly it means and how I can fix it.
Also my phone won't shut down properly. The lights on the bottom buttons stay on and I have to manually force it to reboot like I do to get it into recovery. The shortcuts in the rom aren't working for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
tmb993 said:
Hey guys, I continually get this error message upon manually forcing my phone into recovery. I'm on UCLF5 ICS OBJECTION from btw with the latest version of cwm. I would appreciate some help with regard to what exactly it means and how I can fix it.
Also my phone won't shut down properly. The lights on the bottom buttons stay on and I have to manually force it to reboot like I do to get it into recovery. The shortcuts in the rom aren't working for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I would put it into download mode and run odin or the Off ics to redo/repack your folders, then put CWM back on....idk
Just putting some ideas in, maybe the guru's will jump in on the thread...
Before nuking it like that... try going to mounts and storage and formatting cache
Although I'm not even sure that error is anything to worry about honestly...but i don't do nandroids personally so Idk for sure.
And Joe....stop quoting the op, please?
Does this error have anything to do with the CWM version being used? Its calling for the external sd card isn't it?
No it's calling on the /cache partition which is in the phone...
But it could be the cwm version, it's looking for a recovery log that it can't open.
I can't do anything with the cache. Its like it doesn't even recognize it. I noticed this when I went to throw another rom on and clear out my caches and it would just freeze. I left it for a half hour once just for the heck of it but it didn't do anything. I had to reboot the phone into recovery again.
Sent from my SAMSUNG-SGH-I717 using xda premium
And I have the latest version of cmw installed.
Sent from my SAMSUNG-SGH-I717 using xda premium
What will "fix permissions" do?
I would downgrade cwm, I've been using brawway's touch version since he released his latest, without issue and i think that was in April or may
And fixing permissions, makes the permissions of all apps and .jars be what they should be.
Example: apps in /system/app need rw-r-r permissions, sometimes pasting some of those in will not set them correctly, and if you're doing a bunch at a time is a real pain to go through individually and change them, so that option makes sure everything everywhere matches the permissions needed. So, not applicable in this case.
Well I managed to get another rom on anyway so I don't think its big deal now. I think I might just leave my phone alone now
The collectives 4.04 aocp rom is pretty freaking sweet lol.
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
And fixing permissions, makes the permissions of all apps and .jars be what they should be.
Click to expand...
Click to collapse
Thanks for the explanation.
What is the equivalent of the chkdisk dos command to make the android system rebuild the directory structure? Can you do that through a terminal emulator?
i dunno if there is one other than just reflashing
So basically just flash a new cwm over the one I have now?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yes
this is the version I've been using for months
If u could get it to boot. And manually set permissions for android.policy.jar that would fix the shutdown issue.
silver03wrx said:
If u could get it to boot. And manually set permissions for android.policy.jar that would fix the shutdown issue.
Click to expand...
Click to collapse
Thanks, I decided to switched roms and the problem went away completely. So thats one down
studacris said:
Yes
this is the version I've been using for months
Click to expand...
Click to collapse
Awesome. Ok, last question. I'm assuming I can just load this onto my phone via Odin like I did my original version of cmw?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yeah, That or there is also a .zip that can be flashed from your current version of cwm.
If doing it that way after it flashes go to advanced option and reboot recovery, then once in the new one, clear caches and see if that fixes the issue.
Or, just use Odin then boot into recovery and wipe, either way is up to you, but seeing as how it's cwm that's the issue, i might lean towards using Odin myself... Just note that will increase your flash counter iirc, if you care.
studacris said:
Yeah, That or there is also a .zip that can be flashed from your current version of cwm.
If doing it that way after it flashes go to advanced option and reboot recovery, then once in the new one, clear caches and see if that fixes the issue.
Or, just use Odin then boot into recovery and wipe, either way is up to you, but seeing as how it's cwm that's the issue, i might mean towards using Odin myself... Just note that will increase your flash counter iirc, if you care.
Click to expand...
Click to collapse
Ok great. Thanks guys!
Sent from my SAMSUNG-SGH-I717 using xda premium
Samsung SCHi717 OnlyOne Goldie SMS error
Has anyone else ran into the issue of the stock SMS notifications not going away? When I get a txt message, regardless of how many, it always says I have an unread message. This happened with OnlyOne HYFR and then With Goldie also. Is this a known issue, or is there a way I can just quickly correct this?
Also, I can't find anything that says how to diable the scrolling wallpapers. I wanted static wallpapers for each home/menu screen.
Any advice is appreciated.
-Bugz
bugzinc said:
Has anyone else ran into the issue of the stock SMS notifications not going away? When I get a txt message, regardless of how many, it always says I have an unread message. This happened with OnlyOne HYFR and then With Goldie also. Is this a known issue, or is there a way I can just quickly correct this?
Also, I can't find anything that says how to diable the scrolling wallpapers. I wanted static wallpapers for each home/menu screen.
Any advice is appreciated.
-Bugz
Click to expand...
Click to collapse
Wrong thread.
Sent from my SAMSUNG-SGH-I717 using xda premium
Ok. I've decided to try to give the rom located below a whirl.
According to the install instructions it says not to wipe but to use the aroma installer to chose wiping options.
However, when I flashed the rom within CWM 5.5.0.4 it installed saying updated was installed. I didn't see any sort of "installer" prompting me to wipe anything.
So I guess I'm just confused as to what was supposed to happen. I also flashed the fix from thebill for the dual usb mount and now I no longer have a status bar and I constantly get "system ui has stopped" and "usb has stopped.
Any help would be appreciated.
http://forum.xda-developers.com/showthread.php?t=1755549
westcal98 said:
Ok. I've decided to try to give the rom located below a whirl.
According to the install instructions it says not to wipe but to use the aroma installer to chose wiping options.
However, when I flashed the rom within CWM 5.5.0.4 it installed saying updated was installed. I didn't see any sort of "installer" prompting me to wipe anything.
So I guess I'm just confused as to what was supposed to happen. I also flashed the fix from thebill for the dual usb mount and now I no longer have a status bar and I constantly get "system ui has stopped" and "usb has stopped.
Any help would be appreciated.
http://forum.xda-developers.com/showthread.php?t=1755549
Click to expand...
Click to collapse
flash the rom again without wiping anything
rolgar20 said:
flash the rom again without wiping anything
Click to expand...
Click to collapse
He said he didn't wipe anything. From what I'm understanding the aroma installer didn't start. Are you sure you downloaded the aroma version?
Sent from my MB855 using xda app-developers app
Jaemostoriginal said:
He said he didn't wipe anything. From what I'm understanding the aroma installer didn't start. Are you sure you downloaded the aroma version?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Regarding knowing if I downloaded the Aroma version...No, actually I'm not sure. To be honest I was quite confused by the "download" page. I've downloaded/flashed many roms but I was not clear on what was supposed to be downloaded and flashed this time. There were links left and right.
I went to the "All Builds will be Located HERE" section of the OP then went to jokersax development page and selected the AOKP Build 7 under Th3Bill section. If that's not the correct version then please let me know where I'm to find the correct one.
I installed that one because when clicking the Aroma Installer link on the OP I was not sure about what exactly I was looking at since I've never used it and it's my understanding that it's built into the rom. Also, after I flashed the rom sans Aroma Installer, I no longer have the sd card viewable when connected via usb to pc so I flashed the usb fix and my notification bar disappeared with no way of accessing it, along with a "system ui" error and a "usb" error that decided to pop up nonstop. Would that be due to the aroma installer not running at all during installation? I flashed the rom again and the errors went away and my notifcation bar came back. Sorry for the ?'s but the unaccessible sd card has become a real pain in the arse.
I appreciate the responses guys.
westcal98 said:
Regarding knowing if I downloaded the Aroma version...No, actually I'm not sure. To be honest I was quite confused by the "download" page. I've downloaded/flashed many roms but I was not clear on what was supposed to be downloaded and flashed this time. There were links left and right.
I went to the "All Builds will be Located HERE" section of the OP then went to jokersax development page and selected the AOKP Build 7 under Th3Bill section. If that's not the correct version then please let me know where I'm to find the correct one.
I installed that one because when clicking the Aroma Installer link on the OP I was not sure about what exactly I was looking at since I've never used it and it's my understanding that it's built into the rom. Also, after I flashed the rom sans Aroma Installer, I no longer have the sd card viewable when connected via usb to pc so I flashed the usb fix and my notification bar disappeared with no way of accessing it, along with a "system ui" error and a "usb" error that decided to pop up nonstop. Would that be due to the aroma installer not running at all during installation? I flashed the rom again and the errors went away and my notifcation bar came back. Sorry for the ?'s but the unaccessible sd card has become a real pain in the arse.
I appreciate the responses guys.
Click to expand...
Click to collapse
For some reason I thought 7 was the ICS build but its the JB. There is no aroma for JB yet he just hasn't updated the op yet since he just changed the ICS aokp thread to the JB one. He updated to build 8 so download that one and the USB fix should be built in already.
If you continue to have problems don't hesitate to post on the aokp thread though I don't mind helping here lol
Sent from my MB855 using xda app-developers app
Jaemostoriginal said:
For some reason I thought 7 was the ICS build but its the JB. There is no aroma for JB yet he just hasn't updated the op yet since he just changed the ICS aokp thread to the JB one. He updated to build 8 so download that one and the USB fix should be built in already.
If you continue to have problems don't hesitate to post on the aokp thread though I don't mind helping here lol
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Yeah I'm still a noob poster and apparently cannot post within the development threads.
Ok. So I had actually noticed the Build 8 and downloaded and flashed it. But I soon had more problems. Random reboots and gapps not working properly. I didn't wipe anything before doing so. Maybe that was the problem. Luckily I'd made and nandroid backup and am back on Build 7 with just the sd card still being a problem. I'd like to get the usb fix to work. Working with Build 7, how would you proceed? Just flashing the usb fix gives me the errors I posted previously.
westcal98 said:
Thanks. Yeah I'm still a noob poster and apparently cannot post within the development threads.
Ok. So I had actually noticed the Build 8 and downloaded and flashed it. But I soon had more problems. Random reboots and gapps not working properly. I didn't wipe anything before doing so. Maybe that was the problem. Luckily I'd made and nandroid backup and am back on Build 7 with just the sd card still being a problem. I'd like to get the usb fix to work. Working with Build 7, how would you proceed? Just flashing the usb fix gives me the errors I posted previously.
Click to expand...
Click to collapse
Hm not sure why you're having all these issues maybe you should just back up all your apps in TB and just try a fresh install. Might be left over data screwing your stuff up.
Sent from my MB855 using xda app-developers app
Jaemostoriginal said:
Hm not sure why you're having all these issues maybe you should just back up all your apps in TB and just try a fresh install. Might be left over data screwing your stuff up.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I was afraid I'd have to fully wipe and flash again. I appreciate your help. I'm thinking its stemming from when I followed the directions of not wiping prior to installing. Yeah, could be it.
westcal98 said:
Thanks. I was afraid I'd have to fully wipe and flash again. I appreciate your help. I'm thinking its stemming from when I followed the directions of not wiping prior to installing. Yeah, could be it.
Click to expand...
Click to collapse
No prob man just let me know if its fixed after
Sent from my MB855 using xda app-developers app
"Process system isnt responding. Do you want to close it?
wait report ok
I get this message ALOT on all the JB roms out there now; it happens after a reboot/restart, and if I click ok, things seem to work normally after a few seconds...
Anyone else seeing this alot? Anyone figure out a way to stop it?
thanks!
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnrippa said:
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
ZPaul2Fresh8 said:
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
Click to expand...
Click to collapse
did that many many times, and it doesnt help
wase4711 said:
did that many many times, and it doesnt help
Click to expand...
Click to collapse
Did you restore apps from titanium backup? If so that may be it.
_____________________
Black Star VIII
Me too
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Problem gone (i hope)
strainhunter said:
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Click to expand...
Click to collapse
Hello Again,
The problem is gone for me i found out that it has something to do either with the Theme i was using, or/and the Launcher. Because i first switched my Launcher (Nova Launcher) to the Stock one (Trebuchet) (merely just because i did not know how i should fix that problem) then at the after the first reboot with stock launcher the problem was gone, but came back after i rebooted again. So i changed my Theme (JellyBeanExtreme) and the problem did not appear again "knockin´3x on wood^^"
Maybe this can help someone who had or will have this problem.
Greetings,
Strainhunter
wase4711 said:
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
Click to expand...
Click to collapse
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
CPA Poke said:
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
Click to expand...
Click to collapse
Does that leave your apps and data in place? Never thought of that
Sent from my SGH-I717 using XDA Premium HD app
did u install the walkman app for the note?
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
jrea77 said:
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
Click to expand...
Click to collapse
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
CPA Poke said:
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
Click to expand...
Click to collapse
ya...i noticed nothing was really wrong while getting the error, it just bug me that i was getting that little pop up window. i would hit "wait" or "cancel" and it didnt seem to make a difference, it would go away and that was it. once in a while it would pop back up when getting a text or call, before i could answer the call i had to click it to make it go away to be able to answer. so i decided not to use the theme and not worry about that error.....so would it be any theme or just some themes? maybe ill try other themes and see what happens.....
And the all have the same green leaf for a home screen, so are my ROMS not being written to the right place or what. this is getting confusing. the ROM form about shows the different versions but all are skipping the setup and I have no 3G/LTE connection, only wifi.
Whatever I am doing I seem to be consistent about it
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Did you flash gapps?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
the AOPK had gapps folded in. what is odd is I have now tried AOPK and a CM10 and CM10.1 and they all seem to have the same start screen, come up after the boot like it is already installed, missing any 3G/4G connection. Now I have flashed back to EG01 and run up though iCS several times and it isn't taking the CWM now, says it installs ok but boots into stock recovery. Now I using the older CWM 5504 for the i-905 and it writes somewhere, but apparently not where it should be. I was going to try TWRP but that doens't appear to run on HC/ICS - is it JB only? I have shied away from the newer CWM for a long time because for a while they just seemed to boot-loop the tablet.
Any one have a suggested working version of CWM? This starting from scratch and rolling in all the updates is getting old - which is why I was wondering if there is a way to build my own ODIN set to just flash back to this point without having to go though reroot and install of the recovery (which apparently now I am not able to do - wts! )
Thanks!
Rob (lost) in Katy.
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
Twrp is compatible with ICS too, if im not mistaken. Go to www.droidbasement.com and download pershoots's version of cwm recovery. That should work just fine. BTW, you did make a full wipe (system, data, cache, dalvik) right? And what's EG01?
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
rgranger said:
I am now one cycle 15 and doing the last update to 4.04. every stinking rom I load goes back to the factory or the ROM starts off and ignores the setup. The really annoying thing is I have had all this setup and working before. Ahhhhhh!
Click to expand...
Click to collapse
Ok, i found another recovery laying around that seems to be working. I also found that the bug where you need to delete the script that deletes the new recovery. Once I got that far things started making sense. I guess whatever mod I was on before didn't need it. The next trick will be trynig to decifer how to do an odin backup so that I don't haver to roll though 4/5 upgrades to get here. I know someone is doing it. thanks for the help and a place to bounce ideas. will update if i come up with anything.
Rob