Sorry guys, I have searched through, tried all possible things... but cannot get things working... here's my story (long, but gives the whole picture)
1. Was on CM 6.0 (stable) and Amon RA 1.7 recovery
2. Got a new SD card (8gb class 6)
3. Had Nand backups, so just removed the old card and inserted the new
4. Booted into recovery, partitioned SD card, copied CM 6.1.0 RC and gapps onto the SDCard
5. Performed Wipe Data/Factory reset, Wipe cache, Wipe Dalvik-cache and flashed CM 6.1.0 rc and gapps
6. Booted into the ROM, signed into my account, got all my apps from market
7. Everything was running fine
8. Booted into recovery, made a Nand backup and installed Steel my Elegance
9. Booted into the ROM and realized something was not correct, so decided to restore from the Nand backup
10. Booted into recovery and tried to restore - failure, asked me to run nand backup from adb
11. Did that but that did not resolve the situation
12. Performed step #5 (above) again and got it to the original state
13. Did not login into my account, as I wanted to get a backup of a fresh install
14. Booted into recovery made a Nand backup successfully
15. Just to be on the safer side, tried restoring... did not work. Same error - run SH from adb - tried that, but did not work
16. Read somewhere on the forums to wipe cache before backup and try, did that backed up and tried restoring - no go
17. Decided to flash ClockWork recovery - did that through terminal (ROM booting properly)
18. Booted into recovery - successfull
19. Tried creating Nand backup - failed at Cache - cannot image cache error message or something
20. Performed format SD card, cache, system and all other formats available from the recovery (ClockWork mod)
21. Tried performing nand backup - created some folders/files under the clockwork mod folder with junk characters
22. Performed a SD card format from computer (FAT32)
23. Booted into recovery and tried nand backup - no go
24. Decided to revert back to Amon RA 1.7 - flashed through terminal and rebooted into recovery - phone won't go to recovery
25. Though there might be some problem with the img file, so downloaded from multiple locations and tried it - still no go
26. Followed all sorts of instructions - mount/remount, flash_image - no go. When I do flash_image recovery <image name>, the command exits without any errors, but still can't boot into recovery
27. Installed ROM manager and flashed clockworkmod recovery from within, still no go.
28. Performed "Fix permissions" - ended with "Could not run some privileged commands"
29. I can still boot into the ROM and when I go to terminal can do SU - takes me to "#" from "$" - so I am guessing I still have root
It just doesn't add up... and I feel very lost, right now. I guess the only thing remaining to do is go back to 2.1 RUU, reroot and go from there. Is there any other way? Or did I do something wrong?
Can someone please help?
Edit: I had enough battery juice or wall power plugged into the phone while trying the backups and restores...
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
go to impalers cyanogen mod q&a, ask there, impaler is really knowlegable and helpful, you should get some concrete help.
I don't think this has anything to do with CM, else would have posted there.
Thanks anyways.
cordell12 said:
Do you still have the super user app? Check the permissions in the app, maybe one couldve gotten declined???
Click to expand...
Click to collapse
Checked that, everything that needs access seems to have it.
Any other ideas? I am so close to going RUU route......
Maybe this can help? I dont know never had this happen?
http://forum.xda-developers.com/showthread.php?t=845069
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
andythegreenguy said:
Thanks everyone... I ended up going the RUU way. Got my recovery back, backup/restore and CM6.1.0 RC up & running. Loooonnnnggg night .
Click to expand...
Click to collapse
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
cordell12 said:
I hate that you had to go that route, but atleast all is well now. It couldve been worse and not even let you RUU Thats a Scary thought!
Click to expand...
Click to collapse
No kidding... . It was so frustrating, just going through it all.
Originally, I had rooted my phone that had 2.31.651.7 on it. So, I applied that RUU and went through the root. It seemed to have rooted fine, but then it won't allow me to flash recovery - did the same steps as I had performed during my first rooting process, but didn't work. Then went through all possible ideas suggested on the forums... still no luck. So, finally put the 2.27.651.5 RUU, followed regaw_leinad's rooting method and everything worked out.
All-in-all a good learning experience .
BTW, for anyone that is reading, I think the issue was a corrupted SD card. I might have pulled it while the phone was running and then applied a corrupted recovery image.
Hi All
I looked around and didnt see anyone with my problem, I installed Rom Manager on my NC and when i went into recovery my NC just started boot looping. Does anyone have any suggestions on how i can fix this?
Same Problem....
Sorry I can't help I'm having the same problem I installed ROM Manager, tapped Backup Current Rom, clicked Ok and now it just keeps booting until it displays "Touch the Future of Reading" then turns off and does it all over again, I have tried interrupting the boot 8 times unfortunately I don't really think there is anything I'm interrupting as not only did that not work if I let it just sit it does the exact same thing without reverting to its non-rooted state. Please anyone help!!!
When in the loop...wait Dorothy to turn off... then just as it starts up hold power and n button for 4-5 seconds and release...should boot you into CWM. Then either try clearing cache and dalvik cache then reboot. What where you doing when it happened? Installing kernel? Making backup? Do you have the newest version of cwm?
Sent from my LogicPD Zoom2 using XDA App
If you look in the nook color development subforum right now there is a thread called how to boot into recovery and it explains and shows exactly what I mean... check it.out.
Sent from my LogicPD Zoom2 using XDA App
I already looked at a couple including one with a video showing you exactly how to do it (power/n buttons) it just keeps restarting like I'm not doing anything. I was trying to make a backup and ya i downloaded it yesterday
help plz. samsung galaxy s - after install ROM MANAGER click backup after - you have to install clockworkmod - i clicked YES - and problem - all the time my phone is restart in clockworkmod and and cant choose any option - apply sd card e.t.c. please help me what can i do for get my phone alive. step by step please my mates. thank you in advance. [email protected]
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
Worked PERFECTLY!!! Thank you!!! I thought i was screwed! CWR screwed this thing into a loop! YOU ARE A SAVIOR!
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
STICKY PLEASE!!!!! This is amazing and it freakin buried!
I found that if you install cwr from rom manager that if you reboot before rebooting into cwr, you will avoid the cwr boot loop.
I think this is a problem with any nook waswith 1.1 and rooted with AN3.0
Sent from my LogicPD Zoom2 using XDA App
I don't see the need of removing CWR. Setting BootCnt to 0 should be enough..
Use:
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
And you can also make a flashable zip of it if people are adb-phobic..
Sam
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
You, sir, saved me from tossing my NC in a fit of frustration. CWR had me in Nook purgatory for 6 hours... Thank you kindly!
samuelhalff said:
I don't see the need of removing CWR. Setting BootCnt to 0 should be enough..
Use:
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
And you can also make a flashable zip of it if people are adb-phobic..
Sam
Click to expand...
Click to collapse
Sam, what you have will actually keep it in recovery - you're setting it to a count of 8.
However, this should *really* fix it (from adb shell):
mount /dev/block/mmcblk0p2 /rom
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
dd if=/dev/zero of=/rom/bcb bs=1 count=1088
umount /rom
The above fix is apparently in an upcoming CWR release (in git now). The /rom/bcb bit is apparently what causes the "Installation Failed" message, too.
As I mentioned, the zip I posted above will uninstall CWR. The bit above will fix the boot loop, but it will most likely reappear the next time you boot into recovery.
This worked perfect. Saved my CM7 install.
You're right sorry. Read the thread a bit quickly. Thaught it was standard bootlooping..
Sent from my NookColor using Tapatalk
damned that i didnt see that thread.. i passed 3 hours before testing this solution..
I don't know if its related but from now i can't install from market, it just download app and say "download successfull" . No installation..
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
I am having exactly the same problem. But this solution isn't working for me. When I install the attachemnt I get an error:
--Installing: /sdcard/uninstall-CWR.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/uninstall-CWR.zip
(Status 0)
Installation aborted.
I didn't know if that was the error referred to above, but I reboot multiple times after this and it continues to boot into recovery mode. I've downloaded and transferred the file to the g tablet twice.
Please help.
Thanks
A clear flag on CWR would sure be nice. Here I am at work and have no way of removing it.
To give some background, I was booted, and in ROM manager, I clicked reboot to recovery - didn't work, so I figure "what the hell, let's kill it and try again." Wrong... So then I manage to get it rebooted into recovery, I do a factory reset (thinking everything's hosed at this point), then try to reboot, and what do you know? Yep, recovery again.
My guess is all this started after I updated SuperUser ... things started going weird after that.
Ah yes, and after a restore, I click on reboot system now - and it turns the device off??? Wonky...
edit: OMG... now the damn thing won't turn on at all... This is beautiful crap here...
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
Thanks, Edison. This solution worked perfectly.
This is a rundown of restoring your IMEI and /efs partition. A lot of people lose their IMEI and have no problem restoring it a variety of ways. But if your restored IMEI disappears on next reboot, your problem is something else. I had this, and I believe it was a corrupted /efs partition.
solution, short answer: flash a good efs.rfs file. I did it in Heimdall; I assume it'll also work in Odin. The one I found online (see attachment) restored my efs to the dummy IMEI of 004999010640000. Where I live and on my provider, this gives me network access. From there I could restore my backup nv_data.bin file to /efs. And then my proper IMEI sticks across reboots.
also: kitch posts another way to fix this, here and here.
NOTE: Messing with IMEI has potential legal problems. The attached file restores IMEI to a fairly common dummy number, so I assume it's not a problem. (mods, please delete if this is a problem). The dummy IMEI could work in your area, but that still could pose legal problems. Check in your area, and see the next paragraph.
WARNING/DISCLAIMER: I found this file on Rapidshare. I don't know who made it, put it there, where it might have been linked from, or what exactly is in it. All I had was a filename and I googled it. And all I know about it is that if you have the problems described above and below, then this may work for you. It did for me. If anyone can "see" inside the file to check that it doesn't contain anything malicious, please comment. All I can say is that ClamXav found nothing wrong with BML3_RESTORE.tar.md5 or the efs.rfs contained within it. And that I'm not responsible for what you do to your own phone.
More ways to check if this is your problem:
- You have no signal. In System Settings > About phone, Baseband says Unknown, even if you know you have a modem in there. Also, them going to Status, your IMEI and IMEI SV also say "Unknown". Other people posting about lost IMEI say they have either all zeroes there, or the dummy IMEI 004999010640000.
The rest of this is what I did in GB. I assume if you have this problem, you tried other solutions that got you here too.
- Flashing stock Samsung ROM with repartition doesn't restore IMEI (at least in Heimdall; I can't check Odin). Flashing EZbase Recovery in Heimdall doesn't do it either. They flash, but afterward boots to recovery mode and shows errors about not being able to apply Multi-CSC.
- in Terminal Emulator or adb, running 'mount /efs' returns: 'mount: can't read 'etc/fstab/': no such file or directory'.
- From here, you can still flash a rooted kernel and flash GB ROMs in CWM recovery mode. After each flash, recovery mode shows errors about not being able to mount /efs and/or /dbdata, and not being able to apply CSC.
- From here, if you try flashing to CM7 or CM9, installation aborts. Onscreen error message shows problems with /tmp/updater.sh.
- If you tried to flash a recent kernel with Heimdall, you can get in its recovery mode. I did this trying to get to a known working JB nandroid. I flashed the JB rom again, and it completes. Rebooting sent me back to recovery mode. Repeat rebooting until fed up. Restoring nandroid completes. Rebooting sent me back to recovery mode. Repeat rebooting until fed up.
solution, long answer:
For me, this was from GB.
- Flash the attached file. For Heimdall, untar it (in command line, run 'tar -xvf /path/to/BML3_RESTORE.tar' without quotes, and replacing /path/to/ with the proper filesystem path. If you don't know what this is, try dragging and dropping the file into your terminal window on your computer.)
Then run: 'heimdall flash --efs /path/to/efs.rfs' (without quotes, again replacing path, or drag-and-drop the file into your terminal window)
On first attempt (second was other human error), I did not flash a whole package with PIT file, or repartition. I did later, and that worked fine, too.
- It automatically reboots (unless you told Heimdall not to). You may go to recovery mode and see a bunch of errors about mounting, but applying Multi-CSC is a success. Reboot, and the phone starts normally. You may momentarily see the circle-and-slash no-signal icon in the upper left corner, but soon after it should show signal bars. Your homescreen may show your network somewhere.
- Check IMEI. It should be the dummy number. You can do this with the phone's number keypad (typing *#06#). I prefer to go to System Settings > About phone > Status. This way you can see the dummy IMEI, and IMEI SV should now also show a number. Go back up one level and also check Baseband; that should now show your modem.
- Restore actual IMEI. This requires that you previously backed up your /efs folder. Restoring this is documented better and more thoroughly elsewhere. I went into my /efs backup folder and copied nv_data.bin to /efs. This is easy with Root Explorer. Press the filename, select copy, navigate back up and to /efs. At the top of the screen, click Mount R/W. Delete everything in there (menu, multi-select, select all, delete). Paste the file. Long press the file, change permissions. Make it 644 (Owner is Read+Write, others are Read), save. Long press again, scroll toward bottom of menu and Change Ownership. Make it Radio (1001) and Radio (1001), save. Click to Mount R/O and exit.
- Check it. Go back and check your IMEI and it should be your real one. IMEI SV should probably change, too. (For me, it was 01 in GB, but now it's 03 in ICS). Reboot, and it should remain. Baseband is also filled in.
From here you can flash up to ICS, or whatever, and your IMEI should remain.
note on attachment: The original filename I searched for and found on Rapidshare was BML3_RESTORE.tar.md5. I've changed the extension to be *.tar, so it can upload to XDA. I think Odin users need to add the .md5 extension.
md5 checksum for BML3_RESTORE.tar: f5ab4c90ed60105c8b50e4e9b112e50b
Credit: XDA user magarto is the one whose post led me to this file and fix, from his post here.
errata: This was originally a [Q]-tagged Question thread. I overwrote the OP with this guide and changed the thread title. Hence, the next several posts may seem out of context.
Still unsolved huh? Khmers do have limited access, due to what happened in their country, anyway you can get a better idea here http://forum.gsmhosting.com/vbb/f258/ how efs problems are solved by various box. Just search this forum about efs or post, many Filipinos there .
Having said that, the version of Galaxy S I am using is Korean (has DMB TV, so hardware differences), and to solve this in our version , we simply flash the beginning ROM (with MOVI Files) Its like the Installation Files of Windows, which does a complete setup . This is the last resort for the Korean Galaxy S, solves any and every problems, always wondered why the Galaxy S, does not have this compilation or its only with samsung service centers. anyway
If you have an efs backup, you should try using Root explorer to overwrite (copy paste) the the current efs folder, fix chmod 644 and EXIT using the menu of root explorer and reboot phone to see if it sticks.
thanks for the forum link. yeah, the phone shop nerd was stuck, too. and they did have a box, several that sounded like the octopus box you said.
i've been doing some looking, too, and wondering if it's corrupted file system. i saw several posts about corrupted internal SD, and I don't know if that could be related. my internal SD mounts fine when I boot up, and all my files are there and working. nonetheless, this post seemed interesting, about reformatting in adb with parted:
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
but i still have yet to find out if it's related. flashing anything in recovery, i see this:
E:failed to mount /efs /dbdata your storage not prepared yet please use UI menu for format and reboot actions
ehhh... i'd put off learning more about adb on the backburner. looks like i'm diving in.
Two different issues, internal SD get corrupted when one fails to UNDO lag fix, since samsung uses rfs and lag fixing changes it to ext 4, internal SD will fail to be recognized and needs to be formated to rfs by any Rom using rfs ( mostly stock Roms (to solve that flashing a speedmod kernel, does the trick) But your problem is efs folder
and i came across one person, who had both because he had made a onenand mode lagfix and failed to undo before flashing and was pretty impossible to get over
xsenman said:
and i came across one person, who had both because he had made a onenand mode lagfix and failed to undo before flashing and was pretty impossible to get over
Click to expand...
Click to collapse
ugh ... that does not sound promising.
and i'm not even fully aware yet what lagfix is or does. it had never been an option on any kernel i used since i started flashing roms, only early this year from stock to CM7 and soon after to CM9 and other ICSes. Well, until yesterday, when i tried flashing a supercurio kernel on a GB rom, and that failed. But I did see lagfix options under recovery>advanced. at any rate, i hope i'm not in the same boat.
is there any way in adb to find out if i am?
groksteady said:
ugh ... that does not sound promising.
and i'm not even fully aware yet what lagfix is or does. it had never been an option on any kernel i used since i started flashing roms, only early this year from stock to CM7 and soon after to CM9 and other ICSes. Well, until yesterday, when i tried flashing a supercurio kernel on a GB rom, and that failed. But I did see lagfix options under recovery>advanced. at any rate, i hope i'm not in the same boat.
is there any way in adb to find out if i am?
Click to expand...
Click to collapse
what I am saying is that, you do not have this problem, cause If you had, your internal SD will become unavailable and cannot be used and cannot be formated either ...so just solve the efs problem , thats what you need to concentrate on.
xsenman said:
what I am saying is that, you do not have this problem, cause If you had, your internal SD will become unavailable and cannot be used and cannot be formated either ...so just solve the efs problem , thats what you need to concentrate on.
Click to expand...
Click to collapse
thanks, man. i just did try this, simply taking a Camera photo and opening it in Gallery. also, ran mount in terminal to see, and yeah, saw rfs not ext.
when i try to mount /efs, i get an error:
moutn: can't read '/etc/fstab/': no such file or directory. there's a vold.fstab in there, with paths for mounting the internal and external sdcards. ehhhh... still learning what all this is about.
groksteady said:
thanks, man. i just did try this, simply taking a Camera photo and opening it in Gallery. also, ran mount in terminal to see, and yeah, saw rfs not ext.
when i try to mount /efs, i get an error:
moutn: can't read '/etc/fstab/': no such file or directory. there's a vold.fstab in there, with paths for mounting the internal and external sdcards. ehhhh... still learning what all this is about.
Click to expand...
Click to collapse
efs folder has read only permission, so you cannot do anything you like...don't mess with vold.fstab...you will have problems with your SD cards .
The only thing I can suggest is to go back to th earliest eclair or froyo to recover.
you may need to unarchive the downloaded file and then unarchive the resulting TAR files too
Hence in heimdall you should have
PIT file (s1_odin_20100512.pit), CHECK repartition
IBL+PBL = boot.bin
SBL = Sbl.bin
MODEM = modem.bin
PARAM = param.lfs
CACHE = cache.rfs
DBDATAFS = dbdata.rfs
FACTORYFS = factoryfs.rfs
KERNEL = zImage
But First, try to delete the EFS Folder (using root explorer) shut down, Go into recovery and wipe everything than battery pull to shut down and go onto download mode after that Flash
just a suggestion
xsenman said:
Hence in heimdall you should have
PIT file (s1_odin_20100512.pit), CHECK repartition
Click to expand...
Click to collapse
thanks ... this is where I get hung up. Anytime I check repartition, I get libusb End of Pit errors. It runs fine without repartition. This is Heimdall 1.3.1 and 1.3.2 on a Mac 10.5.8.
I'm going to make an Ubuntu Live CD and see if I can get it that way. I used to have an old Lubuntu laptop, and I remember Heimdall working to flash a kernel when the Mac didn't. It'd be great if the repartitioning is what's holding me back.
aargh. didn't work. Heimdall on Linux does let me repartition, but on the reboot I still get errors that /efs can't be mounted, multi-CSC can't be applied, etc. I tried ezbase recovery and the full stock setup for the original provider from sammobile. I tried deleting /efs, full wiping and pulling the battery like you suggested. I tried separately flashing a dbdata.rfs in heimdall, which was suggested for someone else with mount problems. but, it seems like all the other mount problems people have are with sdcard, and not /efs.
If I restore /efs, is it supposed to write data to /dev/block/stl3? because that file is always 0kb. But I could try the dd command to restore that way... maybe later tonight. it's been a long afternoon working through this.
I also don't know what is the deal with not being able to find /etc/fstab. I saw in some other places that Android doesn't use it, so I don't know what's calling it, and why. Or if that's tied to why I can't flash anything beyond a GB rom; I get errors about /tmp/updater.sh.
EDIT: OK, so at some point with ezbase recovery and manually restoring nv_data.bin to /efs, after a little while I saw that my /sys/block/stl3 (and so /dev/block/stl3) were looking normal. I successfully restored the file, plus the IMEI folder, which has bluetooth info. I did this with flight mode on, toggled it off and connected to my network. About Phone was showing my real IMEI, plus BT and wifi MAC addresses. And I had /sys/block/stl3 looking normal. So I ran the dd if=/sys/block/stl3 of=/sdcard/efs.rfs, and used that efs.rfs file to flash full roms in heimdall, repartitioned. I used ezbase recovery and the stock firmware from sammobile.com for the original mobile provider. Neither worked. On first boot both times, I got errors about not being able to mount /efs or apply multi-CSC. My IMEI on reboot is always "unknown", not even all zeroes, until I fix it. And CWM won't flash any CM7 or CM9 zips, giving status 7 errors that it couldn't mount. I also tried flashing the efs.rfs file alone in heimdall command line, and that didn't work. Ezbase is 2.3.3 and my stock is 2.3.5, and serial number info indicates it was made in 2011 or really late 2010 (i'm loathe to pull the battery off these days), so I wouldn't think Froyo could help out. I've reached out to a few people here who had the same problem, but never posted about a fix, or finally giving up. I'm almost at my wit's end. There must be a solution, some way to reformat or push back /efs data to /stl3.
BTW, can anyone post the filenames of what is in /sys/data/stl3 for their i9000? I'd like to know if I'm missing something in there, at least when it does fill up. Right now, I'm thinking it's gotta be a bad partition.
weird..just can't help wondering why it seems so difficult, I assume you are always practicing standard requirements before and after flashing like
1. Using CWM, make sure to wipe data/factory reset,
2. Then wipe cache, and then go into advanced, and wipe the dalvik cache too.
3. From there, flash the ROM
4. Afterwards, repeat the wipe step as in step #1
5. Continuing on, go into advanced and fix permissions.
6. Finally, reboot the device.
In my version its even more stricter, take a look this is required for an uncomplicated Flash
Hm, I've always done 1-3, as that's what's prescribed in most installation instructions, and still Dalvik even if it's not specified. I've only ever wiped post-flash a couple times, and only because it was mentioned in some threads, plus a whole re-flash of the rom. And I'd never heard of fixing permissions after flashing until HellyBean, but I always did with that.
This problem came up coming off of HellyBean with the test idle2 kernel, to AOKP JB, which apparently boots after a status 7 error and abort, but I only knew that later and didn't try that. I then flashed Semaphore to get to the working CWM 6 backups, and ended up in a loop of recovery modes. In hindsight I should have flashed a whole rom -- I went from a datadata rom to one without that I never booted, then to a kernel without datadata just to get the recovery and nandroid.
Rats, I didn't even think about that.until just now typing this out.
sent from a telephonic device
IMEI BACK.
There was a link in a post here that got me there -- basically, someone uploaded an efs.rfs file. Mods, flag me if this is illegal/against rules, but I'd guess it's not because the file gives you the 0049 IMEI.
But for me that didn't matter -- my partition or the linking was screwed up somehow, and I needed a proper one to flash in Heimdall. I couldn't simply correct my nv_data.bin backup and then export bml3.
The Spanish forum link goes to a dead upload, but I was able to find the file BML3_RESTORE.tar.md5 on Rapidshare. If you need this, it was a rollercoaster. At this point I didn't expect anything to work, and I'm still suspicious of finding a file on the web and flashing it without at least some community I can "talk" to about it.
What happened with the file: I flashed it in heimdall, onto a pretty overloaded and laggy JW5. Rebooted, and immediately saw the circle-and-slash no signal logo, so thought it didn't work -- then it pops up to four bars. I swipe to unlock the screen and it completely freezes. So I went back to ezbase recovery kit and flashed the whole thing (with the CF-root kernel, not stock) plus the efs.rfs file. I didn't repartition because I'm on a Mac, and that doesn't work for some reason, and the linux live CD is painfully slow. It flashes, and after completion, I still get a bunch of errors about mounting, but i get a success message about applying multi-CSC. I reboot, and About Phone shows the fake IMEI, but the homescreen is showing my provider. Also, the file explorer showed my internal and external sdcards.
I reinstalled Root Explorer with Titanium Backup, deleted all in /efs and dropped in my backed up nv_data.bin, changed perms and ownership to radio and radio. Exited folder and reopened, and it was all repopulated. Then I dropped in my backup of the /efs/IMEI folder, only because that has a file with BT info and that didn't regenerate. Rebooted, and all was still there! Finally getting out of this weeklong rabbit hole, and able to come back up to ICS with my real IMEI.
Word of caution, though, if going back up from there to one of the latest ICSes. There's people saying to take the latest CM9 nightly -- if you do that, you're flashing up to CWM 6. If you want to go from there to any of several other ICS roms, you might run into a problem because they might be CWM 5.*. After I had CM9 booted, I went into recovery to flash AOKP M6, lost recovery and ended up having to go *back again* to heimdall. Then onto Team Hacksung's CM9 build 16, then finally to AOKP. Done. And I think at this point I'll lay off the Jellybeans for a little while.
groksteady said:
IMEI BACK.
Click to expand...
Click to collapse
This is great, Now in order to get others who may get into this situation, out of this mess, can you post a step by step guide ( simplified as much as possible)
such that I can link your post to my EFS problems and solutions post, already downloaded Bml3 and will upload to another , so a step by step guide to resolve this will be helpful to others.
xsenman said:
This is great, Now in order to get others who may get into this situation, out of this mess, can you post a step by step guide ( simplified as much as possible)
such that I can link your post to my EFS problems and solutions post, already downloaded Bml3 and will upload to another , so a step by step guide to resolve this will be helpful to others.
Click to expand...
Click to collapse
Sure thing... I'll amend the OP later today. So glad to be out of this mess. I seriously thought I'd be manually restoring my imei on every reboot until I get a new phone.
sent from a telephonic device
xsenman, I changed the OP to a guide, hopefully the symptoms and instructions are clear enough. and thanks for talking me through this; I was losing my mind, and so close to throwing my phone in the river.
for anyone else: xsenman was helping me in another thread too. There, I mention how the official Samsung Service Center here said I had a memory board problem, can't recover IMEI without replacing that, for US$150. I went to one of the many phone seller shops with decent hackers/tinkerers, and they couldn't do it either, and they had Octopus Boxes, or at least a box for Samsung.
anyway. HTH others.
and a tinfoil-hat request: anyone who is able to look at the file attached in the OP, can you see if there's anything troubling or 'weird' in it. I just found the damn thing and tried it. It wasn't the most security-conscious step, but I was in a pinch.
so i had this same problem flashing hellybean 20120820 and used one of the guides here to return to stock then copied my good efs off to my computer flashed all the way back then restored the efs folder but it wouldnt stick. I tried several times fixing permissions and a few other suggestions on this forum but nothing worked. Finally i read somewhere that the cache would restore the efs folder if it wasnt cleared, so i restored my efs thru root explorer to the good one from gingerbread rebooted to recovery, wiped cache, and rebooted. Voila it finally stuck, i dont know exactly why it worked or where i heard clear the cache but it did. Maybe it will work for oyu
Psykologikal said:
Finally i read somewhere that the cache would restore the efs folder if it wasnt cleared, so i restored my efs thru root explorer to the good one from gingerbread rebooted to recovery, wiped cache, and rebooted. Voila it finally stuck, i dont know exactly why it worked or where i heard clear the cache but it did. Maybe it will work for oyu
Click to expand...
Click to collapse
Huh, that's cool. I hadn't read that anywhere before. I'm not in that jam anymore, but its good to know.
I do wonder if I all the other 'normal' methods never worked for me because I was using Heimdall. It shouldn't make a difference, but I did run into basic common problems, like repartitioning not working on Macs.
Thanks for the tip. I hope I won't need to try it.
sent from a telephonic device
I have SC-01C docom tab. during unlocking its imei became null and baseband became unknow. I try this tutorial and result in imei 0000946xxxxx.
But when I restart tab. Imei again null.
Note: there is no option of 644 in Permission.
Please help me to solve this.
nsnobel2 said:
I have SC-01C docom tab. during unlocking its imei became null and baseband became unknow. I try this tutorial and result in imei 0000946xxxxx.
But when I restart tab. Imei again null.
Note: there is no option of 644 in Permission.
Please help me to solve this.
Click to expand...
Click to collapse
Sorry to get to this reply so late. And, that I'm not sure I can help you -- I don't know anything about this tablet. This guide helped me with a Samsung Galaxy S i9000. From a quick search online, the PIT file you'd use is different. I don't know for sure, but I would guess it's possible that your EFS partition is different from the i9000, and this method would not work for you.
For permissions, you should be able to change them by long-pressing a file in Root Explorer, Root Browser or similar apps; it's not an option you choose, you manually toggle r/w, r and r for owner, group and others, respectively. Or you can use the chmod command in Terminal to set to 644, same thing.
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.