Related
Dropped my phone to carpet, about 2 ft drop but now the accelerometer acts all funky, is there a way to calibrate it? or fix it?
Thanks
The suggested calibration for the accelerometer is to open an application that uses it, hold the phone in front of you and make kind of a figure 8 pattern with your wrist.
It has worked for me a few times but not because i've dropped it, it just gets "stuck" sometimes.
Hope that helps.
I had a similar issue where the accelerometer randomly stops working properly. I was about to call T-Mobile for a replacement phone but I tried doing a factory reset and it started working again.
A 2 ft drop to carpet probably didn't damage anything. How is it acting funky? If it's "stuck" you can smack it against the top of your hand.
It leans way to the right, I have tried bubble, labyrinth and pappijump, it's the same for all three apps
Thanks
shake shake baby
Hi, this has happened to me on occasion. I just shook the thing really hard vertically up and down.
job done
install and start the tricorder-app from the market and look whats going on.
will not realy help, but maybe shows you some funny stuff ^^
neiko69 said:
Hi, this has happened to me on occasion. I just shook the thing really hard vertically up and down.
job done
Click to expand...
Click to collapse
I know this is what Nintendo recommends when Wii controllers are acting weirdly. Just smack the phone against your hand a few times (of course, try at your own risk). Can't get any worse.
I got same problem ,..just with the dif that the keybord to haz problems now.. i don get light on the keys (( any1 there that knows if i can fix it?
I had the problem where the accelerometer did not work at all anymore. A wipe helped, but since I did not want to lose all my data, I figured out, how to do it without wiping:
1. Do a backup of your data (nandroid is best)
2. Reboot your phone to recovery console (home+power)
3. Enter recovery console
4. mount /data
5. Delete *.dex in /data/dalvik-cache
6. Reboot and wait (reboot takes longer this time)
If this doesn't fix it for you:
All steps above apply, but in step 5 delete/move/rename the file /data/misc/akmd_set.txt (also in recovery console). It will be recreated. Can't tell you if this fixed it or not, because I did both things at the same time. Sorry ;-)
DON'T try this while NOT in the recovery console! You will lose space on the /data partition because of a bug!! ONLY do this in the recovery console where no system is running.
Thanks! The second one worked for me.
dicer42 said:
I had the problem where the accelerometer did not work at all anymore. A wipe helped, but since I did not want to lose all my data, I figured out, how to do it without wiping:
1. Do a backup of your data (nandroid is best)
2. Reboot your phone to recovery console (home+power)
3. Enter recovery console
4. mount /data
5. Delete *.dex in /data/dalvik-cache
6. Reboot and wait (reboot takes longer this time)
If this doesn't fix it for you:
All steps above apply, but in step 5 delete/move/rename the file /data/misc/akmd_set.txt (also in recovery console). It will be recreated. Can't tell you if this fixed it or not, because I did both things at the same time. Sorry ;-)
DON'T try this while NOT in the recovery console! You will lose space on the /data partition because of a bug!! ONLY do this in the recovery console where no system is running.
Click to expand...
Click to collapse
Can you post more in depth instuctions on doing this? Please?
I only tried this with a JF image. You definitely need root to do this.
1. Turn your phone off
2. Hold Home/House button and press red power button. Release red then home button
3. G1 should boot with lots of text into a menu
4. Press Alt+b to backup everything (optional)
5. Then Alt+x to boot into a console (press enter when prompted)
6. type "mount data" + enter
7. type "rm data/misc/akmd_set.txt" + enter
8. type "reboot" plus enter to reboot
9. Have fun with accelerometer again
More detailed than this is not possible. Hope this helps
That is more info than I needed but I'm sure if will help others, Thank you Dicer
dicer42 said:
I only tried this with a JF image. You definitely need root to do this.
1. Turn your phone off
2. Hold Home/House button and press red power button. Release red then home button
3. G1 should boot with lots of text into a menu
4. Press Alt+b to backup everything (optional)
5. Then Alt+x to boot into a console (press enter when prompted)
6. type "mount data" + enter
7. type "rm data/misc/akmd_set.txt" + enter
8. type "reboot" plus enter to reboot
9. Have fun with accelerometer again
More detailed than this is not possible. Hope this helps
Click to expand...
Click to collapse
Thanks, worked a treat
appstosd
Hi,
What would be the command line for appstosd? I ve tried your instructions but I ve got nothing in data folder because of appstosd. Please help
For apps2sd you probably need to mount /system/sd and delete the file off there.
6. type "mount /system/sd" + enter
7. type "rm /system/sd/data/misc/akmd_set.txt" + enter
Haven't tried it though. Let us know if it works.
follow as above and yeah! working again...after trying for so long to recover....haha feel so good.....
mine stopped working and i wiped myphone and it worked again. =D
Is this a possiple way to fix the calibration issue on rosie? It aborts, so maybe it was looking is the wrong spot to rewrite the file
Since yesterday I own a g1 developer version, when turning the phone on by teh power button all I see is a red, green, blue & white background with the following text..:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial0
When turning the phone on by the power button & the home button I get a white triangle with a exclamation mark, from there, the ALT+L button gives me the following:
Android system recovery utility
E: can't open /cache/recovery/command
From here you can reboot the phone, apply sdcard:update.zip or wipe data/factory reset.
I've tried different update.zip version, but when de update is going to install the following error appeared (Some update.zip versions give this, some give a line 2 error)
"faillure line 1: assert file_contains(“SYSTEM:build.prop, en nog een hele lap tekst..
Could it be that I use the wrong update.zip? Anyone a suggestion? All I want is the phone working..
a good tutorial how to patch and upgrade your phone can be found on the cyanogen mod page http://www.cyanogenmod.com/ in the wiki section. There is a foolproof description especially for the develloper version, just search for it!
From what I understand ADP1 uses different recovery procedures than retail G1s. Check HTC's ADP1 site for more details and to download a recovery image.
wrong section dude
now that you have a dream, u might want to avoid asking questions in the dev area...u will get burnt to a crisp very quickly
the search button (and google) is your best friend...use them before posting
I've followed this
1 Download the DREAIMG.nbh:
2 Place "DREAIMG.nbh" on the root of your SD card.
3 Turn your phone off.
4 Start up in bootloader mode by holding Camera + Power.
5 Hit power button to start the update.
6 Once the install completes hit action(trackball down) and your phone will reboot.
The phone is installing the update, but after a reboot it gives the same color screen I've had before.
Sounds like your camera button is messed up/stuck. Try blowing some compressed air in there or something like that, see if that helps.
I don't think it has anything to do with the camerabutton.. When I leaving the .nbh file on the sd card, en I turn the phone on, it comes with the color screen.. If the camerabutton is active, he should start the update..
Alright, I´ve made some progres..
Trough this site http://www.htcforums.com/threads/3298-POSSIBLE-SCREEN-OF-DEATH I came hier https://android.clients.google.com/updates/partner/signed-kila-ota-148830.de6a94ca.zip
This zip file is nog up anymore, downloaded it somewhere else & renamed it to update.zip, placed it on a sd card. Booted the phone with the home en power button, -> ALT + L -> ALT + S.. This is the first rom which is going to install..
Installing from sdcard...
Finding update package...
Openen update package...
verifying update package.. takes a minute
installing update...
formatting boot
extracting radio image
formatting system
copying files
After this a manual reboot with back & power button, the phone shows a kind of chip met a arrow, automatic reboot, show a white box with a arrow pointing to a phone, automatic reboot & again the rainbow screen.
Well, tried a lot, searched the internet, but can't get it to wrok..
Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you
Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.
Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
E:failed to open/etc/recovery.fstab (No such file or directory)
E:unknown volume for path[/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/revovery/log]
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
deathstoned said:
Good Morning
Very ironic,but i came here to ask about rooting my phone a year back and now i'm back in sort of the same situation..
A year back I rooted my froyo 2.2.1 based Galaxy S to a gingerbread version,then i used quite a few of the ICS roms available on this forum,had been using Cyanogen for the past few months.Yesterday i had some free time,so i thought would check out the JB roms available.
So i did the usual,download the JB version of Fishears since i had a iNand.put it in my internal sdcard..but i could not access the memory card from CWM 5.0.2.7..,so i put it in my external memory card and tried to run the zip from there,but the process got aborted in the middle,tried it twice,dint work.
Then i remembered i had faced this internal memory problem before,had to go and switch on the debugging mode in the developer option.[P.S:- i had been facing the encryption successful problem for half a year,was too lazy/busy to fix it,i just took it in my stride and rebooted a lot to get into the homepage]
So,I'm in CWM and i run the usual process and run the zip file from the internal sdcard,it started out fine,them BOOM.my phone reboots all of a sudden.When it restarts,it does not have a OS to boot into,the green android image with a red exclamation mark and a few text appears which happens too fast to read and it keeps rebooting and this process goes on.
I can still access CWM and the download mode,i tried going into CWM but the internal sd doesnt open and the zip file fails to mount from the external sd.
So i thought **** it,i'll do the rooting part again and i run up ODIN,download the semaphore 2.7.4 kernel,and i see it is just 15 mb or so,i remembered i used more than 1 file and used the pit folder also,but i read it on the semaphore website,its only 1 file and have to use it as the PDA.went to download mode and odin recognised it and the process completed without a hitch,it even showed a green PASS..
but the problem came when it had to reboot after the process,it got stuck in the "Galaxy S GT I9000" page and never moved forward.it was there for 30 minutes or so before i pulled out the battery.
Basically
1.I cant get past that page
2.I can access the CWM and Download modes
3.I accepted my mistake and thought of not doing any more mistakes,so icame here
4.When i boot into CWM mode,these errors come
Cant access the external sd from the CWM now
I dont mind any os now,as long as i can take calls.Am leaving college for home by train day after,so i need a working os as soon as possible
Thank you for reading this and thank you in advance for taking your time to help me out
Click to expand...
Click to collapse
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 1:
I) Download Android 2.3.6 Gingerbread Value Pack (XXJVU)
II) Download ODIN http://www.mediafire.com/?nhhhkm5c2j43rhw Extract Odin3 v1.7.zip to get .exe file
also download the pit file, http://www.mediafire.com/?v2rub40k1bvccj4
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
I had this problem with Paranoid Android before... the zip was corrupt.
If you are able to extract the rom with winrar/winzip/totalcmd or other program, install it, if it is corrupt, download it again again and again...
Sent from my GT-I9000 using xda premium
Samtan4326 said:
you may try this, if you can boot to download mode but make sure your is GT-I9000
Before start, please backup all your important data and phones setting. Then,
Step 2: Extract the ROM [password: samfirmware.com]
Step 3: Launch ODIN. (Don’t open Samsung Kies)
Step 4: Turn off your Galaxy S.
Step5: Put your Galaxy S into Download Mode by Press and hold Volume Down + Home + Power buttons to boot into Download Mode.
Step 5: Connect your Galaxy S with your PC using a USB cable. (Before proceed to Next Step, please make sure that ODIN detect your device)
Step 6:
Click on Odin PIT Tab
Select the PIT – s1_odin_20100512.pit
Click on Odin PDA Tab
Select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
Click on Odin PHONE Tab
Select MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5.
Click on Odin CSC Tab
Select GT-I9000-CSC-MULTI-OXAJVU.tar.md5.
Step 9: Click on START in ODIN to start flash the leaked firmware on your device.
hope this will help.
Click to expand...
Click to collapse
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
-- wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/macblk0p2
Formatting /dbdata...
formatting /cache
Deleting meta data
Data wipe Failed
-- Applying Multi-CSC..
Installing Multi-CSC
APPLIED THE csc-Code "CPW"
Successfully applied multi-CSC
Click to expand...
Click to collapse
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
deathstoned said:
Did what u said,got past odin,then it went into the setup on the phone and all of a sudden it went into the recovery screen,the message shown is
I have a option to reboot,its the samsung recovery screen..its still there,i havent touched my phone since then
Click to expand...
Click to collapse
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Samtan4326 said:
flash CF-root for xxjuv with a pit512 (repartition ticked) cf-root can download from here http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
Once rooted with CWM, enter CWM using combo keys and enter "mounts and storage" and format everything except Boot and also do the full wipes one more time
Finally Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this
issued.
http://forum.xda-developers.com/showthread.php?t=1841250 <--- this is very useful link for new user from xsenman
Click to expand...
Click to collapse
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
E:unknown volume for path [/system]
E:unable process volume! Skipping...
Checking /data...
E:unknown volume for path [/data]
E:unable process volume! Skipping...
checking /cache...
E:unknown volume for path [/cache]
E:unable process volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E;Cant mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Cant mount /cache/recovery/log
and the same for last_log
Click to expand...
Click to collapse
deathstoned said:
flashed it with CWM,went into it and in Mounts and storage there is only 1 option- "mount USB storage"
Nothing else
Below that in the CWM message area,there is
Click to expand...
Click to collapse
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Samtan4326 said:
select mounts and storage format everything except Boot and also do the full wipes one more time and power off your phone
reboot to download mode follow by Flash the JVU+Root again one more time with PIT (repartition) to resolve this issue ...you may need flashing twice or more to solve this.
Click to expand...
Click to collapse
I dont think you got what i said.I installed CFW and went into the recovery,there under Mounts and storage ,there was nothing apart from "mount USB storage"..not even Mount BOOT..nothing apart from that 1 option..when i tried to do a wipe "data/factory reset or cache" it showed me that message which i posted above.still i installed the jvu+root again (Twice actually),it was the same result,the error i posted 2 posts above.
I'm in no mans land now and cant do anything apart from my phone apart from go into download and recovery mode
Please someone help me,i've to go on a 33 hr train journey tmrw and without a phone,it'll be really troublesome
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
amerkiller1995 said:
Have you tried the EZ Recovery kit by Slaphead20?
http://forum.xda-developers.com/showthread.php?p=29114573
Sent from my GT-I9000
Click to expand...
Click to collapse
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
deathstoned said:
New developments now
I followed the steps given in the EZ recovery mode,it crashed into the same e3 recovery mode,for the heck of it i flashed the CFROOT which was provided and it worked fine..all disks were mounted fine and no errors in cwm,
went into Mounts and storage and formatted everything apart from boot and followed the rest of samtans advice
It crashed into the same e3 Rec mode again with the same meta data error message
any suggestions guys,atleast now i'm hopeful after seeing that CWM screen without any errors
Click to expand...
Click to collapse
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
amerkiller1995 said:
After flashing ez base, flash Cm9 and then if you want cm10
Sent from my GT-I9000
Click to expand...
Click to collapse
Ok dont know whether this is good or bad
I installed CM9 from the external sd as the internal sd was inaccesible in any way..the installation showed info like
"the internal sd card marker could not be found
Going ahead with installation"
the installation continues and restarts once and updates but it does not boot into the main page,it directly goes into the Encryption Unsuccessful page.When i try Reset Phone,it goes into the CWM recovery screen with some errors,
when i try to install CM10 from this recvery screen,it initially stops the installation saying the data partition layout is different and all my data will be wiped.run the .zip to go ahead with the progress.I run this it goes directly into the CWM 6.0._._ and it doesnt show any errors,i try to reboot it gets stuck on the galaxy s screen.
this situation is better than the previous condition as i know a OS can still run on my Phone..Just need to get this thing rectified now
Please if anyone could help me right now,i would be really grateful..not able to contact anyone without my phone
It might be a hardware problem... I had something similar
http://forum.xda-developers.com/showthread.php?t=1895224
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
amerkiller1995 said:
It might be a hardware problem...
But for now go to Ez recovery and then try Darky's Resuruction ROM.
Sent from my GT-I9000
Click to expand...
Click to collapse
I installed Cyanogen 9 and got through tht EU page by restarting abut 20 times or so,now i'm trying to install a working version of gapps in it.Tried 1 but the setup failed,so i flashed back to Cyanogen 9 and am not touching it till i reach home.a device capable of making and taking calls is better than nothing..
Is there a way to download contacts from gmail without gapps,the play store is not included in the original rom and i'm hesitant to go into CWM recovery mode as i will have to tackle the EU page again
Anyways thanks for your help,will have to fix this problem once and for all after i reach home
I don't know about contacts from gmail. When you're home look at my updated post above
Sent from my GT-I9000
basically
just reflash gingerbread
I tried getting into Android system recovery <3e> mode
So with the phone turned off, I pressed the Home & Power keys together
(Home = the button in the middle of the bottom of the screen side of the phone;
Power = the button on the top right hand edge of the phone)
I got the following on my screen:
<sorry, they wouldn't let me post an image>
<you can see it at https dropbox dot com at /s/3577rrr0bm5osi9/Android%20system%20recovery.jpg?dl=0
In case you can't read the photo, here is the text. Is the last but one line on the screen spelled wrong?
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
test redbend fota [FS]
-- Appling Muti-CSC --
Can't access to '/system/csc/02U/system'.
Click to expand...
Click to collapse
Any idea what that error implies for me?
(Slightly off topic - I tried doing this hoping to make a backup of the phone before trying to install CWM. But I couldn't see any option for that. Am I doing the wrong thing?)
Getting error -- Appling Muti-CSC -- Can't access to '/system/csc/02U/system
escuchandomal said:
I tried getting into Android system recovery <3e> mode
So with the phone turned off, I pressed the Home & Power keys together
(Home = the button in the middle of the bottom of the screen side of the phone;
Power = the button on the top right hand edge of the phone)
I got the following on my screen:
<sorry, they wouldn't let me post an image>
<you can see it at https dropbox dot com at /s/3577rrr0bm5osi9/Android%20system%20recovery.jpg?dl=0
In case you can't read the photo, here is the text. Is the last but one line on the screen spelled wrong?
Any idea what that error implies for me?
(Slightly off topic - I tried doing this hoping to make a backup of the phone before trying to install CWM. But I couldn't see any option for that. Am I doing the wrong thing?)
Click to expand...
Click to collapse
did you change CSC (region customization)?
the error doesn't imply anything, you can ignore it.
daniga74 said:
did you change CSC (region customization)?
the error doesn't imply anything, you can ignore it.
Click to expand...
Click to collapse
I didn't consciously change CSC (but the phone came from the UK with O2 carrier customisation and now has a Spanish SIM in it).
Thanks, I will ignore the error and its misspelling and look for another way to back up the phone..
you can fix this, press *#272*your IMEI#,, now choose your country region code.
remember its reset your phone if you change your region.
Sorry for my english XD
even i had that problem but it does not pose a problem the phone works