Database Develop

[Q] Nandroid Restore = "Error mounting DATA:!"

Long story short: When restoring via Nandroid it hangs, when using advanced restore the data portion says
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Error mounting DATA:!
Click to expand...
Click to collapse
This afternoon I tried running the Voodoo zip, but the one I downloaded from their site isn't for the Captivate. I ended up with a phone that was constantly displaying 90 degrees off from what it should have been (holding it straight up had the phone thinking I had it on its side).
I decided to uninstall voodoo by creating the "disable lagfix" folder on my card. I rebooted and the phone hung and remained hung at the spinning progress wheel for an hour. I pulled the battery since I couldn't get out of that screen. Rebooting after that had me in what appeared to be the stock version and showed a few of my non-stock apps as "com.etc..." apps.
More reading on here and I found the Captivate-specific version of Voodoo. I figured I'd try to install that before restoring from the Nandroid backup I ran before installing the Voodoo. However, when in recovery mode I couldn't "click" anything with the power button. I tried using adb reboot recovery which didn't fix the problem and instead put me into a non-stop cycle of non-functioning recovery modes after boots.
So I used Odin to get back to stock. Now I'm trying to restore back to where I was before Voodoo. I tried to just run a simple Restore but it hung and after 90 minutes it hadn't completed. So I tried to run an advanced restore and all sections restored except for Data. When I try to restore Data i get the error at the top of this post. I've googled for an answer and everything I've read so far is Cyanogen specific and appears to require Cyanogen to fully fix it. Anyone know how to fix this on a Captivate? Anyone have a link that I'm missing?
Thanks!

If you can boot the phone, then go into android terminal emulator (you may have to download it from the market first) and type mount in the terminal. See what type of partition /data is. If it's ext 4, the disable lagfix was not finished before you pulled the battery. Your best bet then is to download the Captivate voodoo beta 4 kernel version 1.6, which is sticky post in the Captivate development forum here, remove the disable lagfix folder/file from /sdcard/Voodoo/ and let it boot. It will then get you to the point where you should have been at first without having rotation issues and with a kernel that understand ext4. After that, restore your phone to the way it needs to be with Titanium, or by manually downloading and reinstalling any apps that got deleted by your premature battery pull. When ready to do a nandroid backup, do a disable lagfix and let it fully reboot to convert the ext4 to RFS. Then you can do a nandroid backup of restore, as clockwork recovery does not understand ext4 (yet).

Thanks Rajendra! I'll try that and follow up with the results.

I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.

Duplicate post (no way to delete I guess?)

RobertDeBord said:
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Click to expand...
Click to collapse
Try this - once the phone boots - then go to internal sd card and see if there is a Voodoo folder (which there still should be) inside the Voodoo folder make a folder called disable-lagfix - reboot and it should go through the reverse process of creating the lagfix (robot voice). After it finishes reboot go to rom manager and restore.
Hope This Helps....

I can tell you, I've never had a successful restore from rom manager/clockwork recovery. Not once! The only thing that program is good for is as a replacement recovery reboot, it lets you select which zip you want to install from, rather than having to manually name everything to "update.zip". I can't honestly think of anything else its good for. I've tried literally dozens of restores on my captivate and everyone of them has crashed or frozen at some point during the restore. Worthless!!

[ROM] STOCK - FULL ICS IMM76D.LP10 for Verizon i815 LTE Tab (only!) *UPDATE 10/16*

UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated

Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?

johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium

johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.

Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney

Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.

rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.

electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium

bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem

Awesome!

ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.

boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?

rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?

electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)

I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?

almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP

bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c

Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium

chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294

electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?

[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] No network, no IMEI, unknown Baseband, SIM not recognized,

Hi,
After trying to install an home-made CyanogenMod ROM, I can't connect anymore to the network.
When I type *#06#, it says "null / null"
*#1234# says "AP : I8190XXALL2" (the original ROM I just flashed) "CP : Unknown" and "CSC : Unknown"
Baseband version says Unknown too.
When I try to go to mobile network configuration, it says I've to put a SIM card.
Unfortunately, I've no backup of EFS or ModemFS, if the issue comes from here.
Already tried to flash stock ROMs like the I8190XXALL2_I8190OXXALL1, I8190XXAMA1_I8190OXAAMA1, or I8190XXAMA2_I8190XEFAMA1_XEF, or restoring a few old backups of the whole system. Still nothing.
I've heard I could've corrupted the EFS and lost the .nv_data file, but AFAIK it's not on the EFS partition on the I8190.
I can successfully make a backup of the EFS with EFSPro and it contains several files :
Code:
11/04/2013 19:28 <REP> .files
11/04/2013 19:28 <REP> bluetooth
11/04/2013 19:28 <REP> FactoryApp
26/11/2012 15:43 0 GUARDFIL
01/01/2012 02:15 12 gyro_cal_data
11/04/2013 19:28 <REP> imei
01/01/2012 02:02 222 pre_recovery.log
11/04/2013 19:28 <REP> RFHAL
11/04/2013 19:28 <REP> RFHAL.DEF
11/04/2013 19:28 <REP> wifi
If someone has an idea it'd be great, thanks in advance.

did u flashed stock roms with custom recovery?

I'm flashing it using Odin3 v3.07 with the phone in download mode. But I've TWRP 2.5.0.0 on it. Should I flash stock recovery and re-flash a stock ROM ?

Take it to Samsung's service center, but first make sure you flash Samsung's stock ROM and a stock recovery. I had this problem too and they've fixed it.

Is it really the only solution ? Because it's not easy for me to contact Samsung and go to a repairer.
And since this type of problems should never happens and might happen only when you're tweaking your device, can't they refuse to repair it ?
Someone working on smartphones at Intel can't fix it ?
And if I got it fixed, how should I prevent from further problems ?
Many questions, sorry… Thanks anyway.

I had this problem to and i flashed ot trough odin with a stock rom and a pit file and checked re-par. Square helped for me
Sent from my GT-I8190 using xda premium

piernov said:
Is it really the only solution ? Because it's not easy for me to contact Samsung and go to a repairer.
And since this type of problems should never happens and might happen only when you're tweaking your device, can't they refuse to repair it ?
Someone working on smartphones at Intel can't fix it ?
And if I got it fixed, how should I prevent from further problems ?
Many questions, sorry… Thanks anyway.
Click to expand...
Click to collapse
Well if you get a sloppy serviceman he won't see what you did with a device, so it all depends on him. And yes they can refuse a warranty repair, in which case you're screwed.
I recommend that you backup your partitions in the future. All of them to prevent it from happening again.
You can try repartitioning but I'm 80% sure it won't work.

Yes man, you've lost most of your efs datas.. if you don't have a backup of efs, take it to the service center

Hey, finally corrupted all my modem partition while trying a few things to get back my IMEI, none of them worked. After having it corrupted, it put me in Factory mode and I wasn't able to do anything (only system, cache and efs partitions were mounted AFAIK). Took me some time to find I had to format my modem partition (/dev/block/mmcblk0p12 if I remember correctly), but I still don't have an IMEI. Now I think all the "important" datas were stored in this partition, for exemple in the file named NV.dat (which I don't have any copy). So is a backup of this partition enough to prevent this type of problems ? And since this file might be similar with the EFS file called .nv_data.bin in other Samsung phones, interverting them might make it work ? Or am I totally wrong ? I didn't find any information related to what this file contains in reality, how it is encoded… no one tried to hack it already ?
PS: Now before sending my phone to the service center, I tried to run CM10.1 on it, but it's stuck on the boot animation and I can't connect with adb (that's not the whole story, but it's the last thing I get). Does anyone have an idea ? (I know it's a separate topic and it requires much more informations and we can't make a "working" ROM until we have source code for the NovaThor, but it may interest someone) (you can contact me by IM on the IRC Freenode network for exemple)

i dont know if this will help http://forum.xda-developers.com/showthread.php?t=1264021

Will not work since we don't have a .nv_data file or something similar, I think…

do u have efs back up?

No, that's the main problem, but event with an EFS backup, if the efs datas aren't all stored in the EFS partition, I'd have lost them, no ? (but no one confirms that they are stored in the EFS partition or elsewhere)

Main mistake was to use EFSPro. This program doesn't work correctly with i8190.
Code:
[b]GT-I8190 Partiotions layout. Названия разделов для GT-I8190.[/b]
mmcblk0p1=MBR,GPT
mmcblk0p2=MasterTOC
mmcblk0p3=PIT
mmcblk0p4=MD5HDR
mmcblk0p5=STEboot1
mmcblk0p6=STEboot2
mmcblk0p7=Dnt
mmcblk0p8=reserved
mmcblk0p9=CSPSAFS
mmcblk0p10=CSPSAFS2
mmcblk0p11=EFS
mmcblk0p12=ModemFS
mmcblk0p13=ModemFS2
mmcblk0p14=Fota
mmcblk0p15=IPL Modem
mmcblk0p16=Modem
mmcblk0p17=Loke4
mmcblk0p18=2ndLoke4
mmcblk0p19=PARAM
mmcblk0p20=Kernel
mmcblk0p21=Kernel2
mmcblk0p22=SYSTEM
mmcblk0p23E=CACHEFS
mmcblk0p24=HIDDEN
mmcblk0p25=DATAFS

[Q] Help! HTC One M7 TWRP update problem, can't access storage??

Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan

ImMrBS said:
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
Click to expand...
Click to collapse
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that

Danny201281 said:
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.

ImMrBS said:
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
Click to expand...
Click to collapse
Yep that's about right. Running the script shouldn't do any harm but since you already experienced the Factory reset. The command should no longer be in your bcb anyway. As far as I'm aware this only happens once after a new flash and shouldn't repeat every time you use recovery.
But using the zip to clear your bcb is not a bad idea for piece of mind.