hello friends. have p509, 2.2 froyo, have rooted z4root, have cwm v5.0.2.0 installed. when I boot to recovery, I get the CWM menu, but no functionality - I can browse the top menu, but select any item and it misfires: [I get the logo].
The error msg is simply E:Bad boot message, "recovery"
the handset functions ok - boots fine, no issues that I can see.
Should I just overwrite this with a different recovery like amonRA or TWRP or should I flash the same cwm again?
Does CWM have a problem running from a 34GB SD Card? I searched my error and did not find on exact handset but on another and this was the implication, and a patch was offered for that handset, so I don't know if that is relevant here.
thanks for your guidance
c
cognus said:
hello friends. have p509, 2.2 froyo, have rooted z4root, have cwm v5.0.2.0 installed. when I boot to recovery, I get the CWM menu, but no functionality - I can browse the top menu, but select any item and it misfires: [I get the logo].
The error msg is simply E:Bad boot message, "recovery"
the handset functions ok - boots fine, no issues that I can see.
Should I just overwrite this with a different recovery like amonRA or TWRP or should I flash the same cwm again?
Does CWM have a problem running from a 34GB SD Card? I searched my error and did not find on exact handset but on another and this was the implication, and a patch was offered for that handset, so I don't know if that is relevant here.
thanks for your guidance
c
Click to expand...
Click to collapse
CWM 5.0.2.0 is buggy. I'd recommend changing to another recovery. I use a touch version on my P509, but it will only allow installation of P500 ROMs. There is a work-around for this tho. In the ROM is a file -> META-INF/com/google/android/updater-script. There is an 'assert' statement at the top of that script that can be edited to specify P509, or it can be removed all together. Of course, you can also use OOne ROM Editor to trim the ROM and remove the assert statement automatically.
The error message
E:Bad boot message, " recovery"
Click to expand...
Click to collapse
can be safely ignored. You'll get that every time you boot into recovery.
That error message means you dont have SD-ext. Ignore it.
Re-flash the recovery, cwm 5.0.2.0 is stable. Have you re-map your your hardware buttons?
If no.. try other keys.. menu button is to select.. when you see logo use power button.
Recovery is not related to your sd card size. 32GB is max our phone can support!!
FINALLY found a way to nuke CWM. I reloaded it a half dozen times but always the same outcome - zombie. thankfully did not brick.
finally found a GOOD correct instruction about flashing new recovery via LGMDP, added the partition file to the folder with Amon/thunderg and successfully got that one loaded. I can't count how many 'guides', tuts, steps, suggestions I read that never once mentioned the need for the partition.mbn file.
thanks for your responses, however.
rr0yy said:
That error message means you dont have SD-ext. Ignore it.
Re-flash the recovery, cwm 5.0.2.0 is stable. Have you re-map your your hardware buttons?
If no.. try other keys.. menu button is to select.. when you see logo use power button.
Recovery is not related to your sd card size. 32GB is max our phone can support!!
Click to expand...
Click to collapse
cognus said:
FINALLY found a way to nuke CWM. I reloaded it a half dozen times but always the same outcome - zombie. thankfully did not brick.
finally found a GOOD correct instruction about flashing new recovery via LGMDP, added the partition file to the folder with Amon/thunderg and successfully got that one loaded. I can't count how many 'guides', tuts, steps, suggestions I read that never once mentioned the need for the partition.mbn file.
thanks for your responses, however.
Click to expand...
Click to collapse
Glad you got it worked out. Requiring the partition.mbn is not a normal procedure around here. That's why it was never mentioned. I've flashed countless recoveries on the P509 which is identical to the P500 and then also on the P506. Apparently somehow your partition tables got screwed up.
wish I understood that better. I had the same issue with two different sd cards employed - everything else about the handset/rom etc all worked swell. never an issue... just the doggone CWM. I did notice on the small 2gb card that the optimus never would illuminate the Format option - I wiped it and wanted the handset to format but no option allowed. formatted it then with sdformat [win7].
the 32gb sandisk had been my main squeeze for a couple years on the p509
cognus said:
wish I understood that better. I had the same issue with two different sd cards employed - everything else about the handset/rom etc all worked swell. never an issue... just the doggone CWM. I did notice on the small 2gb card that the optimus never would illuminate the Format option - I wiped it and wanted the handset to format but no option allowed. formatted it then with sdformat [win7].
the 32gb sandisk had been my main squeeze for a couple years on the p509
Click to expand...
Click to collapse
Windows doesn't handle partitioning correctly for Linux file systems. Try this tool instead. I've never used it, although I do have it installed. It does come highly recommended.
Related
Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
GManLynx said:
Hey fellow G2x's. I rooted my phone today and attempted to install CM7 nightly #56. FIrst of all...
I tried just downloading the rom via rom manaer, clicked wipe data and wipe cache. When I did it tried to install and asid "Could not open cm7nightlyetc..." And then it proceeded to reboot itself as if it was a new phone.
I then tried to do it via recovery. First whenever I click install from zip card then choose zip from sdcard, the only file I can see is LOST.DIR/ even though I deliberately moved the rom into the sdcard/. I was met with the same problem.
During both the encounters. a triangle with an ! appears, with a little android dude next to it. WHat does this mean? What do I need to do to fix this?
Click to expand...
Click to collapse
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Alright, I'm sorry but I came the G2.... And I was wondering what NVFlash is? I'm gonna google it, but it will be nice if you answer it too.
Setting up NVFlash
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
darbear5610 said:
Here's the guide to setting up NVFlash. It's a moderately challenging process, but it's seamless after getting it put on your G2x. This is the only way to get CWM without issues. http://forum.xda-developers.com/showthread.php?t=1054492
Oh, and remember to go into C: on your computer and make the folder "G2x". This is where you put the files from NVFlash.
Click to expand...
Click to collapse
yup and when u get ready for commands u can copy and paste them
techboydino said:
First rule of G2X/Tegra2 club... don't use Rom Manager. Use CWR for all your flashing needs. *Install CWR via NVFlash only.
Click to expand...
Click to collapse
First - the above is the truth - learned the hard way by many.
From the "triangle" comment, I would have thought you were not able to get into recovery anymore, but you said you had tried flashing in recovery - are you still able to get into recovery? Also, when you said you moved the file to the SD - internal or external?
You could re-download the ROM on you computer and/or move the one you downloaded when in USB connect mode if you can connect through USB. and then try flashing it again.
Otherwise - did you do an nandroid back-up first (add that to the G2X Club rules). If so, and you can get into recovery, you can restore it through recovery. If not, you are truly back to square one (except for rooted).
At some point, you need to NVflash a real recovery. The one-click method in the Dev section is the easier way to go. If you can't get into recovery (you only see the triangle and it only does a factory reset), then you HAVE to start there.
Yeah I am still able to get to recovery mode. And external sdcard.
I think i'm just gonna go staright to the NVFlash way. I have a history class today so I have a hour and a half to burn.
And thanks guys for all the inputs.
I'm loving my G2x so far. So fast and sleek
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Alright thanks. I just installed via NVFlash and now I will try again to install CM7
player911 said:
All you need to do is NVFlash once, just so you can get into recovery on a bootloop (Power+VolDown)
After you install NVFlash once, you can use RomManager all you want (I do).
Rom Manager will install a temp recovery initially, but it won't affect your permanent NVFlash recovery. So just do both. Rom Manager will work perfectly fine without doing a NVFlash, but an NVFlash just enables the option to get into recovery on a cold boot.
Every day, I launch Rom Manager and it will find the latest Nightly and download it plus Google Apps, prompts for Full Wipe, Backup, or Cache options, then it will reboot, flash the items, and reboot back into Android.
So, again, NVFlash just enables Power+VolDown to get into recovery but Rom Manager works great without it. You SHOULD do BOTH initially and just get it out of the way.
Click to expand...
Click to collapse
Agree with all the above (I have and use both), except for making nandroids, which was not mentioned above. The only ones where I have had a check-sum issue with trying to restore are nandroids I did with ROM Manager. I would stick with doing them straight from recovery.
Others have had issues with flashing nightlies also, but I have not noticed that as I always head straight to recovery to flash.
Question - I had flashed real recoveries with ROM manager on MT4G - why the "false" recovery issue on G2X?
So player, once I have NVFLASH and CWM, I can download ROM manager to backup/restore/flash any ROM from the list without worrying about anything?
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
I would redownload the zip file over the computer, happened to me before with a different rom, make sure it doesnt unzip. and then drag it to your SD card.
Okay I am perfomring that now, will edit with results.
My goodness... I think you fixed it for me. I feel like an idoit. I've been saving it to hte internal Sdcard i didn't even know that was possible.
Damnit... same problem.
Yay I got it. Thanks so much guys for all the help.
GManLynx said:
Hey, I installed the 4.0.0.3 and I still have the same problem. I can't see any roms I put on the SD card, and when I try to install it by naming it update.zip it gives me the same error. Any ideas?
OKay so here is what happens
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directoy)
Installation aborted
THere is definately a file there. I just named it that cause it wont shop up when i choose zip from sd card.
Click to expand...
Click to collapse
The ROMs were probably going to the internal SD by default. Just move them with a file manager to the external SD (unless you set up recovery to use the internal SD).
Also, do not rename them update zip - leave the names as-is so you will know what your are dealing with if you have multiple ROMs .
Then you flash it as a zip file on SD card - not as "update.zip" - that would be for the OTA update - if we ever actually see one for the G2X!
Good job Gman
Different roms put the external SD card in different places.
By default Rom Manager is set to read/write to /sdcard/... not /sdcard/external_SD that is the norm with the stock(based) roms.
Once you have CM7 on there and everything setup under standard conditions, Rom Manager will work as it should.
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links
First, my apologies for 1) starting a new thread regarding a question that's been asked many times, and 2) making this so long. But I've tried all the possible solutions I could find, so far to no avail.
I've been running Emancipation, and decided to upgrade to Uniporn when b38 was released. No problem running the aroma installer, and no surprises after the installation when reboot hung at Samsung logo. But when I rebooted into recovery, the screen was distorted and most illegible.
I quickly found Nunhugger's instructions to Odin ICS Recovery. Not so easy on a Mac though. I tracked down the Mac port of Odin, but couldn't get it to recognize the phone. Eventually, I figured out how to install the Mac version of Heimdall, and used that to flash the zImage file extracted from the infuseICSrecovery.tar file. The Heimdall flash appeared to be successful, but it didn't fix the Recovery corruption.
I could still click through Recovery (though couldn't see what I was selecting) and was eventually able to choose to to reflash Uniporn through trial-and-error counting the number of various combinations of clicks. But got an error that the file was corrupted (don't remember exact wording of error message).
Of course I had backed everything up in recovery before trying all this, so I tried to recover from there. Uh oh, same error message. Nandroid files were corrupted, too.
Eventually, I was able to return to Emancipation after copying the file to my external card, and installing from there. Recovery was back to normal, and everything appeared to be working normally.
Confident that I hadn't bricked my phone, I tried installing Uniporn again. Again recovery was in its messed-up state. Since aroma wouldn't work at all in the corrupted recovery, I've been sticking with the non-aroma Uniporn installer. Working from my external card, I finally got it installed successfully. Yay!
Recovery is mostly usable now but still not right. Here are some things I've tried already based on answers I found in the Uniporn dev thread: 1) Flashed zImage file extracted from Nunhugger's infuseICSrecovery.tar file with Heimdall on Mac; 2) Flashed Entropy's UniKernelZip from Recovery; 3) Flashed boot.img file extracted from UnikernelZip.zip with SGS Kernel Flasher; 4) Flashed zImage file extracted from Nunhugger's infuseICSrecovery.tar file with SGS Kernel Flasher; 5) Upgraded to Uniporn b39; 6) Repeated steps 2 through 4 while running b39.
Here is a piece of information that may be relevant: While running Emancipation, I often got an error message that my sd card was unexpectedly removed. Or an error message that it was blank or in an unsupported format. Thinking that the problem was with my external sd, I would shut down, pop open the battery and sd card, clean the contacts, put everything back together and reboot. Everything would work for a while until I got one of those messages again. Thinking it may be a software issue was one of my main reasons to upgrade to Uniporn. Except that I later realized that it must be the INTERNAL sd card that was unexpectedly unmounting, since the phone wouldn't run apps from the sd card and apps are on the internal card not the external. Maybe hardware problems after all? Maybe that's why installers and nandroid restore wouldn't run from internal card?
Attached images are 1) colorful snow that flashes on the screen for a half-second or so between Samsung logo and Uniporn startup animation; 2) What recovery currently looks like. Recovery was less legible actually before flashing Entropy's kernel, and returns to less legible version after flashing infuseICSrecovery.
Does anyone have any ideas at all how to fix this? Thanks for your help!
Msg, relay done...
Sent from my SGH-I717, Black Star.
Flash GB bootloaders.... Use caution.
Sent from my SAMSUNG-SGH-I997 using xda premium
Your issue is bootloaders and I do not think more. This will get rid of the distortion on recovery, but I cannot speak for possible sd corruption or bad flash issues that happen. Lets fix the color distortion first.
Assuming you can use Odin, go here:
http://forum.xda-developers.com/showthread.php?t=1613523
and read the directions. Download this for Odin or find the one for Mac you used if that is what you are doing:
https://dl.dropbox.com/u/16149362/Odin3 v1.7.zip
then go to the FAQ in that thread and look at #1. There is a tar file for you to download and put in the pda slot. Do it and flash the file.
When all is done with SUCCESS, reboot your phone and come back and report any further issues. Recovery should be readable.
BTW, ICS recovery is to help when stuckin a bootloop from flashing and ICS rom. It fixes nothing else, including the distortion.
To whom ever can help out, I have a Galaxy Tab 2 7.0, and cannot seem to get my problem resolved by myself. I have somehow inadvertently managed to install an update.zip that had or had no relations to this particular OS of this particular model of android.
My problem is that I wanted to be able to, migrate my apps to the external SdCard or extSdCard, and I think I used an update.zip designed for the cellphone HTC Evo 4g. Not realizing that I will be later unable to use the restore feature from a previous backup I had made using CWM 6.0.1.0 to recover from my inadvertent mistake (not to comfortable making a backup, and thinking I can restore properly anymore, like I can on my cellphone that I am spoiled with).
Silly of me to think I could use an update.zip designed for another type of device such as the HTC Evo 4g, but… (anyway my bad what was I thinking…?). The update.zip, by the way is "dtapps2sd-2.7.5.2-signed", like I mentioned this is clearly designed for the HTC Evo 4g, and not for the Samsung GT2 7.0.
The problem I experience now is not complete lose of my GT2 7.0 device I can still install and change out OS through the CWM-Recovery and install apps through the Android Market. I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Now my question is, how is-it possible to resolve this issue. I have tried to complete a fresh install of the OS, CWM-Recovery, and also attempted to wipe everything possible that the recovery will allow, but I am not expecting much, as I cannot even get the backup and restore feature to work efficiently enough to provide me with what I need it to do…
I have provided this post with a download of the update.zip I used as well as the version of the OS I have provided my Samsung GT2 7.0. If anyone can shine some insight on what direction I should attempt to do to resolve this issue I would be more that interested to take a look at what I could use to correct this error of mine…
-Samsung GT2 7.0 - OS (Use the Download link above the Rosewell signature)
http://forum.xda-developers.com/showthread.php?t=1784318
-dtapps2sd-2.7.5.2-signed
http://www.mediafire.com/?7jpc5oudzt6o76p
I might be comfortable to ADB Shell into my device to make changes, or if one was able provide me an update.zip/script that would be great. Also is there a better recovery out there than the ClockWorkRecovery.
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Sent from my GT-I9300 using xda app-developers app
Mohamedselim said:
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Click to expand...
Click to collapse
Mohamedselim, Thanks...
Will look into this..., any links by the way in regards to the "fresh firmware with a pit file"...?
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
imnuts said:
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
Click to expand...
Click to collapse
Yeap...!, I have tried this already, have had no promising results...
This is the only compatible version of a .pit file...;
http://forum.xda-developers.com/showthread.php?t=1642744
Can anyone provide me another one for the GT-p3113...?
Just checking in..., and wondering if anyone has a solution for this...?
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
RomsWell said:
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
Click to expand...
Click to collapse
MultipleMonomials said:
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
Click to expand...
Click to collapse
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Ok, so I was successful in taking RomsWell and MultipleMonomials advice, and was able to return my device back to "Normal" state, including "Stock Recovery". But I still have the original problem as in my request I asked in my first post...
I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Click to expand...
Click to collapse
I think now, if I cannot get a sizable remedy..., is just to try and send it in Samsung so they can take a look at it...
Any suggestions...?
FYI; I have also tried connecting to Kies, but due to the inability to posses a "MTP" (Media Transfer Protocol), is the reason I cannot connect to my SdCard & extSdCard. I can "PTP" (Picture Transfer Protocol) into it, using "adb shell", but not using "MTP"...
So I do not know how much "MTP" has to do with this relationship of the other three items that I mentioned in my bullet list in my quote, but...
Anyway, I don't know what I am trying to say, but thank you two, for getting me this far...!
grassy-sneakers said:
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Click to expand...
Click to collapse
Did you try formatting internal storage in CWM?
MultipleMonomials said:
Did you try formatting internal storage in CWM?
Click to expand...
Click to collapse
I am not quite confident on how much this will work. As I have tried this multiple times to wipe "Wipe Factory/Data", "Wipe Cache", including all the partitions under the "Advance" section found in CWM Recovery. Even using TWRP Recovery.
Per this post; I just attempted to flash a "Stock Rom", but not before doing a factory/data, cache wipe using "Stock Recovery", including after a successful install...
No luck, the same problem still exist as above...
Ok, this was all just the rudest experience I put my self threw. As I have an HTC Evo 4g - cellphone and have become comfortable with installing ROM's, Kernels, and Updates.zips, as well as, other modification. All threw the Recovery designed for this particular device, and don't get me wrong there has been a couple of times. Maybe more than a couple, more like a few times I have installed incompatible downloads I find in the XDA forums. Which makes this screw up, difficult form me to know that as long as you can get into a Download/Bootloader or a modified Recovery designed for a particular device that was successful flashed correctly. Well the screw up are easily redeemed/recoverable.
So, to make a long story short. After having called Samsung Customer Care (the 1-800-SAMSUNG) number, it seems to have been a External SdCard getting in my way from having been real short from sending my Tab off to the repair department (where ever it is...). I in fact already had it in an envelope, all I needed was an address to send it to. Anyway the nice person on the other side of the phone requested that I remove my External SdCard, and confirm that I was able to get into my "Storage" tab under my settings. Well after success getting this option back, I then made the suggestion that maybe my Eternal SdCard is corrupt or incorrectly formatted. She then agreed maybe this is the case. After ending the phone call. I quickly restarted my Tab, again only to find out that I was no longer receiving the error messages like mentioned above, which is great, because after multiple flashes of "Stock Roms w/Stock Recovery", and forcing myself to believe that it was a system install error. It in fact the External SdCard in place preventing me from throwing my Tab against the wall / in the mail to Samsung Repair Center...
"Man what an ordeal...!!!"
Thanks to all that helped with the suggestions, as to what direction I most defiantly tried.
I am now in the process, since I am living back in Stock mode. To receive an OTA (Over The Air) Update, and am still in the process of seeing if this thing still possess any residual silent errors...
I will keep you posted.
If not, well it off to happy rooting for me...!!!
That is it, my problem is resolved. Damnedest thing this problem of mine, it seems the only thing I screwed up was the micro SdCard. to the point it was the cause of all the error I received when I started up the device, as well as when I attempted to access my storage through me settings options...!!!
Now re-rooted, and a happy camper, Cheers...!
My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.
Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.
WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.