Database Develop

[Q] need help! Can't get nanodroid to work again.

Hi,
I read everything i could find and I still can't get anything to work properly on the phone.
Is there even a milestone wiki so i know which version my phone is?
I got the open recovery thing to work once, but i can't get it to work again, it keeps saying I have a cache error. what do i do?
also, when I install app2card, it totally ruins my phone, is that app meant for my phone?
I tried to install app2sd, but it keeps saying busy box permission failed something.
I got my phone thru ebay, how can i check the region?
I just know I have an unbranded milestone.
I google all these questions and nothing helpful comes up.

Can somone please tell me how to get into recover again?
Do i need to reflash it?
I only got into it once and installed the zip.
but when i try to run the zip again, i get an error.

If you have nandroid file in your sdcard,you can copy and paste (anything that is important to you) to your PC.
1. Take out your sdcard and pluck it to your PC if your Milestone cannot switch ON
2. Format your sdcard via PC
3. Extract G.O.T OpenRecovery v2.00 or Androidiani OpenRecovery 3.3 to the root of
your sdcard. (you'll see OpenRecovery folder and update.zip) Put the sdcard to your
Milestone and enter bootloader.(Press and hold volume up+camera key & power ON)
4. Open RSDlite and connect to your Milestone. Flash sbf to your Milestone,stock ROM
or 2.2.1 G.O.T beta version
Guide -> http://forum.xda-developers.com/showthread.php?t=696845
5. Your Milestone will be switch ON after flashing sbf is done. Turn it OFF and enter
into recovery. Press X button and power ON. Once you see the triangle and '!',
press volume up and camera key.
6. You'll see Recovery 2e, all letters in blue, select update and the rest is your choice.
You can nandroid backup if your Milestone works as before and restore your previous nandroid that you copy to your PC.

Yes i did that the first time and it worked.
but how can i get into it again to make a backup?
thanks

You mean you still can't get into the recovery mode after formatting your sdcard? Even with the button combination:
PRESS AND HOLD 'X' AND POWER ON THE PHONE, LET GO ONLY AFTER YOU SEE THE TRIANGLE AND '!' MARK ???

I get to the triangle.
and it get to the recover menu. but when i press install the zip again.
an error message pops up.
do i need to redo step 3 and 4 everytime i want to go into recovery menu?

what open recovery u r using? GOT or androidiani?
if its GOT then try switchin to androidiani to check if the problem presist, vice versa.
report back here if there is any improvement.
one more question:
when u enter the bootloader menu (pressing the up dpad and power key) wat bootloader version it states there?

Thanks
I'll try it out tonight been a bit busy this week.
does Flash sbf do anything to my system?
for example, will i need to reflash my current rom after doing Flash sbf?
I know for the x10 mini pro, after doing update.zip i will need to reflash the rom.
is it the same for milestone?

I still can't get it to work.
here are my steps.
My phone is already rooted.
and I already flashed the Recovery-Only SBF when i installed the new rom. (do i need to redo this step? Maybe I'm using an outdated version?)
Can someone link me to the file if there is a better one, all the links are dead.
I am using this version: vulnerable_recovery_only_RAMDLD90_78
I downloaded this:
http://groupoften.wordpress.com/2010/10/22/new-g-o-t-openrecovery-v2-01-launched/
I put the files on the root of my SD:
OpenRecovery
OpenRecovery-CFG (do i need this?)
update.zip
I press the Up dpad and power, I get the triangle thing.
I press the install.zip and still cache error?
E:can't open /ache/recovery/command
I don't get what the readme in the GOT is telling me to do.
it says:
create a folder in /OpenRecovery/recoveries ( for example "My_OR_MOD" i don't use space in folder name, to avoid problems)
does that mean I make a copy of the "openrecovery" folder and put it back inside the "openrecovery" folder? that means every thing will be duplicated? is this correct?
thanks
I would try the androidiani, but i can not find the english guide.
Edit:
just tried androidiani, and I'm still getting E:can't open /ache/recovery/command

Unable to flash ROM Galaxy Ace S5830

Problem solved long ago
Delete thread

Wrong thread to post in.
Anyways,
When you use "update from SD card" option the code is installed from "update.zip" in sdcard - so if there is some garbage code in update.zip it will corrupt the installed ROM on the device (or even the kernel - as might have happened in your case) and errors like bootloop and errors in recovery show up.
That being the background ... you should ask around in the galaxy ace section for specific instructions to use odin to restore your friends phone
Here's a little guide on how to flash a ROM via ODIN by me:
Requirements:
- A Windows computer
- A Galaxy Ace plugged into the computer via USB
- You must have ODIN installed , duh !
- (Windows Vista/7 compulsory) Running ODIN with Administrative rights:
- Ended KIES via Task manager:
Instructions:
1 - Download your favourite firmware here
2 - Extract the .rar out using WinRAR or 7zip (password is samfirmware.com)
3 - Check if it's a FULL package or ONE package:
FULL Package instructions:
1 - Open up ODIN (MAKE SURE ALL REQUIREMENTS ARE MET)
2 - Set your phone in Download Mode (Home + Power + Volume Down)
3 - Once you have correctly entered Download Mode and plugged in , this should appear in ODIN:
4 - Place the files in this order:
OPS - Select the file named Cooper_v1.0.ops (or anything like that)
BOOT - Select the file named "APBOOT_S5830xxxxx_CL514579_REV03_user_low_true.ta r.md5"
where "xxxxx" = Your firmware version
Phone - Select the file named "CODE_S5830xxxxx_CL514579_REV03_user_low_true.tar. md5"
where xxxxx = firmware version
PDA - DO NOT PLACE ANYTHING
CSC - Select the file named "GT-S5830-MULTI-CSC-xxxxxx.tar.md5"
where "xxxxxx" = the CSC region
EFS - Select the file named "MODEM_S5830xxxxx_CL514579_REV03.tar.md5"
xxxxx = firmware version (Be VERYVERY careful with this EFS part)
After you're done , click on "Start" and let the magic reveal itself slowly......
ONE Package method:
1 - Open up ODIN
2 - Set your phone in Download Mode while plugged into USB
3 - Tick the option "One Package" in ODIN (Refer to previous ODIN picture)
4 - Select the only .tar.md5 file
Now press start and watch the magic.....
Click to expand...
Click to collapse
more of the above here
Good luck.

.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.

Rishabh13 said:
Hello,
My friend used upd_1.zip from xda to root his phone and then flashed CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 as well as its fix.
He didn't get the "install zip from sdcard" option so, he chose the "apply update from sdcard" option and selected CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 halfway through it says "installation aborted" after this his phone doesn't proceed beyond the startup screen.
PLEASE HELP
Thanks in advance
PS: when I go to the recovery screen, a list of text comes up which says "unable to access...","cannot access cache", etc. All start with "E/..."
PPS: I am newbie of sorts and do not know how to use SuperOneClick and ODIN, though I downloaded them as recommended in http://forum.xda-developers.com/showthread.php?t=1034145
Click to expand...
Click to collapse
well your friend didn't cared to read requirements properly as to flash custom rom you need to have cutom recovery..
do odin flash to clean the things

Rishabh13 said:
Hello,
My friend used upd_1.zip from xda to root his phone and then flashed CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 as well as its fix.
He didn't get the "install zip from sdcard" option so, he chose the "apply update from sdcard" option and selected CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 halfway through it says "installation aborted" after this his phone doesn't proceed beyond the startup screen.
PLEASE HELP
Thanks in advance
PS: when I go to the recovery screen, a list of text comes up which says "unable to access...","cannot access cache", etc. All start with "E/..."
PPS: I am newbie of sorts and do not know how to use SuperOneClick and ODIN, though I downloaded them as recommended in http://forum.xda-developers.com/showthread.php?t=1034145
Click to expand...
Click to collapse
If already flash upd1.zip then reboot and flash cwm5 after that you can proceed to flash custom rom....
If not its will soft brick your ace hahahahah pls read the procedure before do flashing....
Sent from my GT-S5830 using xda premium

Right now just try to wipe everything, and format system!
Try this time to flash the custom rom correctly!
Choose zip from SDCARD and not apply update
If that doesn´t help
try flash with ODIN 4.38
SENIOR MEMBER POST +.+

Also to reboot after flashing the cwm file lol
Sent from my GT-S5830 using XDA App

Rishabh13 said:
Hello,
My friend used upd_1.zip from xda to root his phone and then flashed CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 as well as its fix.
He didn't get the "install zip from sdcard" option so, he chose the "apply update from sdcard" option and selected CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 halfway through it says "installation aborted" after this his phone doesn't proceed beyond the startup screen.
PLEASE HELP
Thanks in advance
PS: when I go to the recovery screen, a list of text comes up which says "unable to access...","cannot access cache", etc. All start with "E/..."
PPS: I am newbie of sorts and do not know how to use SuperOneClick and ODIN, though I downloaded them as recommended in http://forum.xda-developers.com/showthread.php?t=1034145
Click to expand...
Click to collapse
hey mate its easy...just root via update.zip then download cwm4 or 5 frm xda choose apply update and click on it ...there u r ..u hav th cwm wth u...once u hav the cwm clik on install zip option ...happy flashng .

scourgeofgod said:
Wrong thread to post in.
Anyways,
When you use "update from SD card" option the code is installed from "update.zip" in sdcard - so if there is some garbage code in update.zip it will corrupt the installed ROM on the device (or even the kernel - as might have happened in your case) and errors like bootloop and errors in recovery show up.
That being the background ... you should ask around in the galaxy ace section for specific instructions to use odin to restore your friends phone
more of the above here
Good luck.
Click to expand...
Click to collapse
Thanks mate!

[Q] HELP! :( Semi Bricked. Tried EVERYTHING

Ok
Please forgive me I have spent up to 7 hours today searching and trying but to no luck.
So I didnt realise what i was doing and Semi Bricked my Phone. I edited build.prop and saved it in MyExplorer(name?) to try and turn off the camera sounds and when I rebooted, it just gets stuck on the galaxy S 2 screen, boot loop.
I'm on SGSII (Australia) Stock Vodafone's ICS 4.0.3 Rooted.
I have CWM installed but tried a few things:
- I can get into Download MOde (no idea what to do here)
- I can get into CWM mode 5.0.2.7 Recovery mode but cant do anything still.
- I tried various Edify script builders to try and put the original build.prop back in but get multiple Status 0 errors whenever I try update.zip from the SD card.
- I tried rebuilding the backup on there and changing the build.prop file on there and trying to restore but MD5 check fails. Even tried rebuilding the MD5 file with the modified files and still no luck. MD5 files fails.
Would anyone have any suggestions and how to resolve this without a flash or wipe? I didnt back recent backup and will lose everything.
I am coming to a point where I really am wanting to back to Apple
There are 2 build.props attached. One is the bad one that stopped me from booting up and I found another one that was named .bak (extension taken off) I found in the same directory (/SYSTEM)
If anyone can help me build an update.zip to push in via CVM I would greatly be in your debt (I tried for 4 hours with no luck)

If you have recovery and download mode yet nothing is lost.
In first, do saved your apps ?
If you had saved them or if it doesn't matter to you, reflash a rom via recovery
LINK HERE:
http://download.cyanogenmod.com/get/jenkins/2773/cm-9-20120615-NIGHTLY-galaxys2.zip
Flash it GoogleApps folder
http://goo.im/gapps/gapps-ics-20120317-signed.zip
The rom that I attached to the reply is a CM9 ICS version, it's quitly stable and we can have some settings on it.
If it doesn't work reflash with Odin (it's with software who use the Download Mode)
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
Instructions
-Unzip the Rom Folder ( I9100XXLPQ..........)
-Open the included Odin
-Put your phone on Download Mode
-Click PDA and select I9100_CODE_I9100XXKP*_CL*_REV02_user_low_ship.tar.md5
-Click PHONE and select MODEM_I9100XX*_REV_02_CL*.tar.md5
-Click CSC and GT-I9100-MULTI-CSC-OXA*.tar.md5
-Click Start and don't touch anything still the colored case become green
-And now your phone resurrects
Reply me of results

thanks for your reply
unfortunately i didnt save my apps and havent got backups of my data either
i cant reach the file via ADB either, when i run ADB (have KIES installed and worked before) - adb devices.
nothing shows up when the phone is stuck on "Samsung GS2" screen.
do you have any recommendations around keeping my data there?

If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium

understood thanks
what if i just want to flash build.prop via update.zip?
i tried so many methods but it always fails. is anyone able to create a update.zip for me?

i used a GUI script creator to try and update it via CWM recovery mode but it doesnt seem to like it.
If i turn off signature verification, it gives me a (status 0) error saying : E: Error in /sdcard/update.zip
and if i turn on verification toggle, it says E: signature verification failed
can anyone help?

calum96 said:
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i know there are 2 types of ROMS right? the nonwipes and wipes. i really dont want the wipe versions.
the one i downloaded is 1G which i'd imagine is the wipe version if i were to upgrade via odin?
http://www.androidaddicted.com/firm...-vodafone-australia-firmware-update-1267.html

Can you mount any sd on your pc, because you can the recovery mount trick to access to your data.
When you are in the recovery menu, go to mount and storage and click on "mount usb storage" and the internal and external sd will appear on your pc.

you are posting in galaxy s thread....repost in galaxy s2 thread

I don't think so but then again I don't own a s2 but you can select advanced restore: restore data then flash a compatible ROM, then restore the data if you worried but as I said before flashing the same ROM shouldn't remove user data
Sent from my GT-I9000 using xda premium

[Q] CWM gives me a status 7 error when installing cm91

I managed to get my phone into a state where I can only go to download mode or CWM manager (no OS). This is how it happened:
- Installed latest cyanogenmod (9.1) on my Samsung Galaxy S (international version, unlocked).
- New version worked fine!
- Found out I was missing some data so I went back to CWM recovery and did a "backup and restore" > "Restore ALL (Be careful)"
- Restoring old ROM did not work ... decided to go back to cm91
- When I try to reinstall cm91 via CWM I get the following:
Code:
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ... [more similar statements]
E: Error in /mnt/sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted
Seems like the "Restore ALL" step messed up with something fundamental... does anyone have a clue in what direction I can go to resolve this? I have been searching frantically for answers but usually a "status 7" is a result from an outdated cwm or such (NOTE: I did manage to successfully install... and ICS was running very well before I did the restore and things went bad)
Seems to me that the ro.product.device property(or/and other properties) from the device has been altered in the restoration process.
- Does anyone know how I can see which value it has? (I can currently only use the CWM manager)
- Can anyone point me in a direction where I could go next to fix the situation?
Any help very much appreciated

gardarh said:
I managed to get my phone into a state where I can only go to download mode or CWM manager (no OS). This is how it happened:
- Installed latest cyanogenmod (9.1) on my Samsung Galaxy S (international version, unlocked).
- New version worked fine!
- Found out I was missing some data so I went back to CWM recovery and did a "backup and restore" > "Restore ALL (Be careful)"
- Restoring old ROM did not work ... decided to go back to cm91
- When I try to reinstall cm91 via CWM I get the following:
Code:
assert failed: getprop("ro.product.device") == "galaxys" || getprop("ro.build.product") == "galaxys" || ... [more similar statements]
E: Error in /mnt/sdcard/cm-9.1.0-galaxysmtd.zip
(Status 7)
Installation aborted
Seems like the "Restore ALL" step messed up with something fundamental... does anyone have a clue in what direction I can go to resolve this? I have been searching frantically for answers but usually a "status 7" is a result from an outdated cwm or such (NOTE: I did manage to successfully install... and ICS was running very well before I did the restore and things went bad)
Seems to me that the ro.product.device property(or/and other properties) from the device has been altered in the restoration process.
- Does anyone know how I can see which value it has? (I can currently only use the CWM manager)
- Can anyone point me in a direction where I could go next to fix the situation?
Any help very much appreciated
Click to expand...
Click to collapse
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean

erpurohit said:
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
Click to expand...
Click to collapse
Thanks for the reply!
Regarding JB, I'd rather want a stable cm build as this is my dad's phone and I'd rather not set him up with something branded as experimental (yes, I bricked my dad's phone ). Regarding GB, I'll give it a try but I'm wondering if the cm installation for GB doesn't have the same assert checks as the installation for ICS...rendering me in the same mess (I don't have the device with me right now but I'll try later today).
Is there a way to get the Samsung stock ROM somewhere?
- That way I'd at least have known a way out of this mess.
Also, I'd like to know WHY this is happening, as I'm curious about where these values are stored and how one changes them.

erpurohit said:
I just thinking - why not go back to GB and start fresh again or give a try to install Jellybean
Click to expand...
Click to collapse
Tried cm10, same error (as I expected). I edited the install script, removing the assert line. This only makes the device go unresponsive on install. I can't mount the system partition (or any other partitions for that matter)... the device appears fubar. Gonna try to use odin to install some stock rom I found. Not very optimistic though.
Any ideas for a fubar phone? Is the only remaining option to use it as a paper press?

gardarh said:
Any ideas for a fubar phone? Is the only remaining option to use it as a paper press?
Click to expand...
Click to collapse
From what you have written, it looks like you restored the old system on a new system setup, thus your CWM will give you status 7 when you try to use it for upgrade . look at status 7 errors in My Android solutions .
All you may had to do was flash the correct semaphore kernel to get back correct CWM and also check your IMEI or like erpurohit said, start from the beginning.
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

xsenman said:
From what you have written, it looks like you restored the old system on a new system setup, thus your CWM will give you status 7 when you try to use it for upgrade . look at status 7 errors in My Android solutions .
All you may had to do was flash the correct semaphore kernel to get back correct CWM and also check your IMEI or like erpurohit said, start from the beginning.
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hey xsenman,
I think I actually already stumbled upon your posts, I believe I did a PIT restore with the 512 pit and Odin just hung (for an hour or so) before I unplugged. This aggravated my situation (I realized through this whole process that there are multiple levels of fu*ked when rooting).
I finally found a way out of this mess just an hour ago by following this post: http://forum.xda-developers.com/showthread.php?t=1102881 . I reinstalled the stock ROM and then installed cm91 again and now the device is working fine. Odin did hang on me once again when I followed those instructions but I tried again, using the 803 pit file and then it finally worked (don't know if it was a coincidence).
So the state I was describing before was that the partition table was corrupted. From there nothing works (obviously).
Thanks for taking the time to help me out! I have to say I wasn't very optimistic there for a while...
Cheers,
Gardar

Noob with a similar problem
Hi Gardar, hi xsenman,
I stumbled upon this thread by googling the same error message that Gardar initially posted (The error code 7 on attemping to flash CM 9.1).
Unfortunately, being a somewhat naive noob, I feel I am not proficient/confident enough to try the solution that Gardar found for himself just yet.
My problem is that by some dumb attempt to restore to the original GingerBread 2.3.3 after initially successfully installing CM9.1 and then some time later facing some problems concerning the phone not recognizing the SIM card anymore (it said "no service" and couldn't scan for networks and wouldn't ask for the PIN after rebooting the phone), I now seem to have completely messed up the phone's system. The phone won't boot and when I try to flash it to CM9.1 again from CWMR, it aborts, giving me the code 7 error message that Gardar posted.
I was browsing through the forums here, following the links given in this thread, trying to find some answers by myself and stumbled upon this:
" Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and
replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong
Radio etc "
in xsenman's "Android Solutions for Galaxy Phones" thread
( http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 )
This seems applicable but I have no idea what to make of it. I am really lost now, so some dumbed down step-by-step guide of what to do now would be really appreciated.
A quick sum up of what state my SGS i9000 is in right now:
- The phone doesn't boot into operating system (gets stuck on the first Samsung Galaxy S logo screen)
- I can start download mode
- I can access CWM Recovery (v2.5.1.0 SpeedMod Kernel)
- through that I can mount the usb storage to connect it to my Windows PC and access the internal SD card
that is (from my noobish point of view) about all i can do.
What backup I have available:
- NANDroid backup from earlier this day, including
- cache.img (23 KB)
- data.img (51,503 KB)
- dbdata.img (17,016 KB)
- nandroid.md5 checksum file (1 KB)
%note: from what I read somewhere (and tried out), this backup seems useless for recovering to the stock android, because the sys.img is missing. Am I right about that?
- unfortunately, I have NO "EFS"-folder backup. Yes, xsenman will hate me but I can't help it now :'(
%note: I think this might be relevant concerning my phone not getting service and not asking for the PIN after booting.
A chronologic/structured sum up of how I got into this mess and when which problems arose
- I started out with the original GingerBread 2.3.3 (Phone was working fine)
- following this guide step by step ( http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide ) and using the files linked there, I
- successfully flashed the SpeedMod Kernel and ClockWorkMod to get root access using Heimdall
- successfully installed CM 9.1 via CWM Recovery (from internal SD)
- now the phone worked fine with CM 9.1
BUT
- GPS wasn't working and I didn't have FM radio
- so I got myself the JP5 radio zip from here (http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Support_Downloads)
and a GPS fix from here (http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s/250698-fix-gps-fix.html)
- and installed them both at the same time via CWM Recoevry the same way I did with the CM 9.1 zip file
This was probably the first big mistake I made, because
- now I had GPS working again, but from now on
- the phone wouldn't ask for the PIN after booting
- I didn't have service anymore
- the phone failed to scan for networks
- but it wasn't showing the "no sim card" icon in the task bar
I tried rebooting the phone and when that didn't help I started messing around in CWMR
- wipe data/factory reset
- wipe cache partition
- wipe Dalvik cache
When that didn't help either, I
- tried to re-install cm9.1, getting the abort with code 7 error
- then tried to recover the original rom from my backup folder
- that looked promising in CWM as it didn't abort like cm9.1, but when rebooting once it was done in CWM the phone got stuck on the logo screen immediately and won't boot since.
- I retried wiping user data and caches and installing cm9.1, to no effect.
Then I started digging into the forums here and elsewhere but couldn't find specific advice aseful to me in this situation.
Now I'm sitting here with my fubar phone and don't know what to do next -_- crying for help
Please excuse this wall of text, I tried to give as much useful info un my problems as possible.
Any help is greatly appreciated.
Cheers,
Jules

JulesBell said:
Any help is greatly appreciated.
Click to expand...
Click to collapse
you keep mentioning 2.3.3 as your base, as such I am assuming you have an i9000M ...so confirm what is your phone model as upgrade ROMS will vary .
The easiest way to solve this is to start from the beginning ( assuming you have moved all your important files to your PC) If not just mount USB storage using CWM and copy your entire Internal SD card to PC...for salvaging later and you can format your Internal SD card and partitions without worries to start afresh.
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
1) you can download an upgrade ROM, JVU for i9000 or UJKG3 for i9000M or even a rescue kit, which ever suits you and flash back to stock 2.3.6 for i9000 or 2,3.3 for i9000M from My Android Collections
2) After this you can root and get CWM by flashing a semaphore GB kernel for i9000 or UGKG3 root + CWM for i9000M
3) here is where you make an EFS backup to keep for life in your PC
4) after this you can flash the CM 9.1, you can either follow the developers guide or chose one from My Guides and Manuals

Sounds like you're not more of a noob than I am
From what I learned from my battle the assert(...) failures indicate that that the device type cannot be read anymore which in turn indicates that the filesystem storing that information is corrupted (and/or the partition table defining your filesystem). Btw. if you extract the .zip file containing the cm mod and do a "grep -r assert" you can find the installation script (don't remember exactly where it's located right now). It's not very helpful but informative...
The filesystem mess can be fixed with flashing a new pit file (I recommend this post on pit files which seems to be a phenomena specific to Samsung phones), then installing one of the stock ROMs in the post I linked and finally reinstalling CM (which I believe repartitions your internal sdcard again). I think you want to do both the PIT and the stock ROM in the same go with Odin. Of course this is pretty much the same as I said in the post above and therefore probably isn't helpful to you, but it worked for me
Good luck!
JulesBell said:
Hi Gardar, hi xsenman,
I stumbled upon this thread by googling the same error message that Gardar initially posted (The error code 7 on attemping to flash CM 9.1).
Unfortunately, being a somewhat naive noob, I feel I am not proficient/confident enough to try the solution that Gardar found for himself just yet.
My problem is that by some dumb attempt to restore to the original GingerBread 2.3.3 after initially successfully installing CM9.1 and then some time later facing some problems concerning the phone not recognizing the SIM card anymore (it said "no service" and couldn't scan for networks and wouldn't ask for the PIN after rebooting the phone), I now seem to have completely messed up the phone's system. The phone won't boot and when I try to flash it to CM9.1 again from CWMR, it aborts, giving me the code 7 error message that Gardar posted.
I was browsing through the forums here, following the links given in this thread, trying to find some answers by myself and stumbled upon this:
" Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and
replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong
Radio etc "
in xsenman's "Android Solutions for Galaxy Phones" thread
( http://forum.xda-developers.com/showthread.php?p=30415128#post30415128 )
This seems applicable but I have no idea what to make of it. I am really lost now, so some dumbed down step-by-step guide of what to do now would be really appreciated.
A quick sum up of what state my SGS i9000 is in right now:
- The phone doesn't boot into operating system (gets stuck on the first Samsung Galaxy S logo screen)
- I can start download mode
- I can access CWM Recovery (v2.5.1.0 SpeedMod Kernel)
- through that I can mount the usb storage to connect it to my Windows PC and access the internal SD card
that is (from my noobish point of view) about all i can do.
What backup I have available:
- NANDroid backup from earlier this day, including
- cache.img (23 KB)
- data.img (51,503 KB)
- dbdata.img (17,016 KB)
- nandroid.md5 checksum file (1 KB)
%note: from what I read somewhere (and tried out), this backup seems useless for recovering to the stock android, because the sys.img is missing. Am I right about that?
- unfortunately, I have NO "EFS"-folder backup. Yes, xsenman will hate me but I can't help it now :'(
%note: I think this might be relevant concerning my phone not getting service and not asking for the PIN after booting.
A chronologic/structured sum up of how I got into this mess and when which problems arose
- I started out with the original GingerBread 2.3.3 (Phone was working fine)
- following this guide step by step ( http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide ) and using the files linked there, I
- successfully flashed the SpeedMod Kernel and ClockWorkMod to get root access using Heimdall
- successfully installed CM 9.1 via CWM Recovery (from internal SD)
- now the phone worked fine with CM 9.1
BUT
- GPS wasn't working and I didn't have FM radio
- so I got myself the JP5 radio zip from here (http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Support_Downloads)
and a GPS fix from here (http://www.android-hilfe.de/root-hacking-modding-fuer-samsung-galaxy-s/250698-fix-gps-fix.html)
- and installed them both at the same time via CWM Recoevry the same way I did with the CM 9.1 zip file
This was probably the first big mistake I made, because
- now I had GPS working again, but from now on
- the phone wouldn't ask for the PIN after booting
- I didn't have service anymore
- the phone failed to scan for networks
- but it wasn't showing the "no sim card" icon in the task bar
I tried rebooting the phone and when that didn't help I started messing around in CWMR
- wipe data/factory reset
- wipe cache partition
- wipe Dalvik cache
When that didn't help either, I
- tried to re-install cm9.1, getting the abort with code 7 error
- then tried to recover the original rom from my backup folder
- that looked promising in CWM as it didn't abort like cm9.1, but when rebooting once it was done in CWM the phone got stuck on the logo screen immediately and won't boot since.
- I retried wiping user data and caches and installing cm9.1, to no effect.
Then I started digging into the forums here and elsewhere but couldn't find specific advice aseful to me in this situation.
Now I'm sitting here with my fubar phone and don't know what to do next -_- crying for help
Please excuse this wall of text, I tried to give as much useful info un my problems as possible.
Any help is greatly appreciated.
Cheers,
Jules
Click to expand...
Click to collapse

-
xsenman said:
you keep mentioning 2.3.3 as your base, as such I am assuming you have an i9000M ...so confirm what is your phone model as upgrade ROMS will vary .
The easiest way to solve this is to start from the beginning ( assuming you have moved all your important files to your PC) If not just mount USB storage using CWM and copy your entire Internal SD card to PC...for salvaging later and you can format your Internal SD card and partitions without worries to start afresh.
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
1) you can download an upgrade ROM, JVU for i9000 or UJKG3 for i9000M or even a rescue kit, which ever suits you and flash back to stock 2.3.6 for i9000 or 2,3.3 for i9000M from My Android Collections
2) After this you can root and get CWM by flashing a semaphore GB kernel for i9000 or UGKG3 root + CWM for i9000M
3) here is where you make an EFS backup to keep for life in your PC
4) after this you can flash the CM 9.1, you can either follow the developers guide or chose one from My Guides and Manuals
Click to expand...
Click to collapse
Hey again, xsenman and gardarh,
thanks a lot for the quick replies.
I want to go and try to follow the directions you guys gave me, but first of all some additional info and corrections that I forgot or stated wrong after a long night of browsing this and other forums and desperately trying to get my phone working again.
- regarding the model and original firmware: I'm pretty sure it's just the plain sgs gt-i9000 (without the "M"). The latter version seems to be specific for the Canadian/North American market, and my phone (like me ) is from Germany. Also, in the phone status info menu it just said "i9000" when the phone was still working. And I may have been mistaken about the version number 2.3.3, it might as well have been 2.3.6.
I only recently (this week) bought this phone used from a friend. I'm not sure which firmware version the phone was originally shipped with, but since my friend is not a tech geek, I think it is safe to assume she only installed SAMSUNG-official updates.
- then, I think THIS IS IMPORTANT, I think the EFS files may have been corrupted and the IMEI may have been lost when flashing the radio module and the GPS fix, which I guess may have caused the phone to lose network service and not be able to scan for networks.
Will this be miraculously restored when flashing to stock 2.3.6 from an original ROM or do I need to extract the IMEI some way BEFORE I go ahead and re-partition the internal SD card?
- do I need to re-partition anyways? I tried to mount "/system" in CWM and it failed.
- also, I forgot to mention that after the failes recovery from my backup, I couldn't even get to CWM Recovery anymore. I flashed the hardcore kernel onto the phone again via USB using Heimdall, so now I can access CWMR again.
Thanks a lot!
Cheers
Jules
---------- Post added at 04:20 PM ---------- Previous post was at 03:35 PM ----------
I just discovered that there seems to be a backup of my EFS folder after all, which was created at the same time as the nandroid backup. I copied the backed-up "efs" folder to the root directory as well as my PC just to be sure. Copying the folder to root doesn't seem to have any effect on the bootability of my phone though.
However, finding this backup gives me some confidence regarding acomplete reset to stock with an original ROM and PIT-file, so I'll go for that now and update you on the results.
Cheers,
Jules

phone restored
Thanks a lot guys, with your help I was able to restore my phone to a stock GB 2.3.6, using
i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq
Right now I m just happy it's working again and not in the mood to flash to cm9.1 again, fearing i might hit the problems with GPS and fm radio not functioning again... any suggestions?
Best wishes
Jules

In my limited experience, if you cannot mount /system your filesystem is probably corrupted (at least that was the conclusion I came to).
You should not be worried about which android version the device was running (e.g. 2.3.3) but you do have to be careful about choosing which region the firmware was designed for. See if you can find your device type here:
http://www.sammobile.com/firmware/?page=3
Take note of the code under the PDA column.
The download from that site didn't help me though, but should hopefully help you in finding the correct stock firmware (from my link above).
Chainfire posted some info about stock rom names (See http://forum.xda-developers.com/showthread.php?t=1103399 undir the section "Help! Which file do I use ?". It's for Galaxy S2 but I believe the idea behing the naming is mostly the same.

problem solved
Hey gardarh,
thanks for your reply. I got the phone working again by completely resetting it to a stock 2.3.6 gingerbread firmware, using a rescue kit. What in detail was wrong, I wil never know

salival eedfie
JulesBell said:
Hey gardarh,
thanks for your reply. I got the phone working again by completely resetting it to a stock 2.3.6 gingerbread firmware, using a rescue kit. What in detail was wrong, I wil never know
Click to expand...
Click to collapse
Good to hear! Which rescue kit (for future reference)?

abc
gardarh said:
Good to hear! Which rescue kit (for future reference)?
Click to expand...
Click to collapse
>>> i9000 Rescue Rescue Kit for i9000 using heimdall packed by ldq <<<
from xsenman's list.
Cheers,
Jules

[Q] internal SD corrupt, how to install ROM on ExtSD?

hi guys....
i have a i9000.......... with soft-brick, i use a jig (301k whit miniusb ), and access to download mode and flashed a stock rom......
but the internal memory, keeps previous programs and gives me FC, ​​with CWM recovery after doing full wipe, and format the internal memory, restarting the computer maintains all, do not delete anything ........
now get a message that the internal sd is damaged, but not allow me to enter mode debbug because the phone is freeze ... I also recognize the pc to format the external memory .........
as I can do to install a ROM CM-10, in the external memory?
thanks for the help.
sorry for my eng.

You say the message says your internal SD is damaged. What EXACTLY does the message say?
Sent from my GT-I9000 using Tapatalk 2

try this! http://forum.xda-developers.com/showthread.php?t=1906089 i don't have an sgs, so i can't tell you if it works and i can't help you, but in that thread you can find someone to help you

I was having the same problem and found the solution here
I was having the same problem and found the solution here http://forum.xda-developers.com/showpost.php?p=35585404&postcount=8
this is my post to thanks for the kernel
http://forum.xda-developers.com/showpost.php?p=38210629&postcount=12
look for a sd fast I have a class 4 and was too slow and buy a class 10 and now works just like new.

far2 said:
I was having the same problem and found the solution here http://forum.xda-developers.com/showpost.php?p=35585404&postcount=8
this is my post to thanks for the kernel
http://forum.xda-developers.com/showpost.php?p=38210629&postcount=12
look for a sd fast I have a class 4 and was too slow and buy a class 10 and now works just like new.
Click to expand...
Click to collapse
Thank you.
I flash the kernel but got a boot loop.
I have the firmware JW4 not get the JVU ... my model is i9000t, could you help me get the firmware that worked with your phone.
Thanks in advance.
sorry for my English.

solved!!!
Downloading the ROM file: I9000XXJVU_I9000OXAJVU_OXA.rar
Downloading the ODIN & PIT files: Flashprogram_Samsung_I9000__Pits.rar
Downloading the Drivers for the PC: SAMSUNG_USB_Driver_for_Mobile_Phones_v1_3_2300_0.zip
Most importantly: KEEP YOUR PHONE FULL CHARGED OR AT-LEAST ABOVE 50% CHARGING LEVEL.
Once you are done with the prerequisites, you can move down to the installation procedure as below:
1. Unzip the ROM, ODIN and Drivers to their respective folders in case it requires any password, it will be “samfirmware.com”
2.Now, the first thing to be done is install the phone drivers on the PC which you are to use for flashing the ROM. To do this, navigate to SAMSUNG_USB_Driver_for_Mobile_Phones_v1_3_2300_0 folder and select the appropriate setup x86 or x64 based on the type of OS you are using on your PC.
Once this one has been installed, get your GT I9000 in the download mode by using the 3-Button combo. For that, first switch off the phone and wait for it to vibrate a little just to confirm that it is completely switched off. Then, press the three buttons: Power Key, Volume Down and Home Key and hold until you see a green android saying “Downloading”
3. Next, goto Flashprogram_Samsung_I9000__Pits folder and open I9003_Odin3 v1.82.exe (Don’t bother the I9003 in the file name. It is compatible for I9000 also)
4.Once ODIN has be opened, connect your phone to the PC while it is in download mode. Once connected, an “Added” remark will appear on the message window.
5. Next, click on the PIT button, navigate to the Flashprogram_Samsung_I9000__Pits folder and select s1_odin_20100512.pit
6. Then, click on the PDA button, navigate to the I9000XXJVU_I9000OXAJVU_OXA folder and select the CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5 file.
7. Then, click on the PHONE button, navigate to the I9000XXJVU_I9000OXAJVU_OXA folder and select the MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5 file.
8. Then, click on the CSC button, navigate to the I9000XXJVU_I9000OXAJVU_OXA folder and select the GT-I9000-CSC-MULTI-OXAJVU.tar.md5 file.
PLEASE MAKE SURE TO SELECT THE FILE PROPERLY AS ABOVE AND DOUBLE CHECK BEFORE CONTINUING FURTHER.
9. Next, make sure that Re-Partition, Auto Reboot and F. Reset Time have been check marked.
Once all the above steps are done, click on Start button and wait for the message window to show “All threads completed” and “Pass” displayed on the top left box.
10. Then, click on PDA button, navigate to Kernel_JVU_Fix_sdcard file, and clic on Start!
and viola!!!
thanx far2

I glad this Solve the SGS problem for you
gerickt said:
solved!!!
and viola!!!
thanx far2
Click to expand...
Click to collapse
I glad this Solve the SGS problem for you, and all the people in the forum, hope some developer can make a kernel like this but for the new jw4+ or even better for the cm9 or cm10
I know some people has install the cm9 and cm10 do but they have a total sd failure, our sd is still readable and is even worse.
Gerickt yesterday I write to you a PM in Spanish wit more indication to you did you receive?
PD: nice you made a detail description for the procedure :good:

the developer answer to my
rxxxni was the developer to post the kernel here and he just answer the place to look for more info in his kernel here
htcmania.com/showthread.php?t=520348
I don't know if this is bad to post other links outside the xda but he made the kernel and there is more info