Hi all.
I have got my SGS II for 4 months and i was running it with stock rom and CF kernel. Yesterday, I was comming home from chrismas and was asked - as usual - to turn off my phone on the plane. Put it in plane mode and shut down.
Turned on for some series watching, turned off for arrival.
After that, my phone quit working: no SIM could be detected. After some research, I realized that my IMEI was set to 0 and Phone: unknown. I went back right away to stock, but it did not help.
By the time I flashed, i had no idea that efs folder did not came with cwm backup, so i have no backup of working efs folder.
I have some files on EFS folder, but i have no idea of what is "good" folder.
Can somebody point me to some direction?
I heard about some miracles perfomed by ODIA user, hehehe.
Thanks in advance.
Try this thread.
I did...
But I still cannot have access to change the efs files/dir. And still didn't figured how to have write access for these. Could you enlighten me?
Thanks!
To get write access you need to use a file explorer like Root Explorer (or similar) from the Market.
PauloSherring said:
But I still cannot have access to change the efs files/dir. And still didn't figured how to have write access for these. Could you enlighten me?
Thanks!
Click to expand...
Click to collapse
Are you getting "permission denied" and/or "read only filesystem" errors?
I take it you ARE running all commands with root priviledges?
It is working!
Thanks people! I've been struggling with this problem for only two days, but it feels like months! I needed to umount the /efs unit and mount again with other accesses priorities (r/w, i.e.).
In fact, this thread: http://forum.xda-developers.com/showthread.php?t=1261948&page=5 was the reason for me achieving this.
i had the same issue with my galaxy,
https://market.android.com/details?...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
this utility helped me to fix it.
Thanks to Helroz
Glad you got it working Paulo I can imagine it would be pretty stressy to have a working phone one minute and a reboot later no IMEI.
PauloSherring said:
Thanks people! I've been struggling with this problem for only two days, but it feels like months! I needed to umount the /efs unit and mount again with other accesses priorities (r/w, i.e.).
In fact, this thread: http://forum.xda-developers.com/showthread.php?t=1261948&page=5 was the reason for me achieving this.
Click to expand...
Click to collapse
Related
Hi, guys.
I just updated my phone with ICS and after that my lock screen settings don't work (slide,facial, pattenr), is this a common issue on this update? should i flash again to stock and upate again trough the phone?
Betornillo said:
Hi, guys.
I just updated my phone with ICS and after that my lock screen settings don't work (slide,facial, pattenr), is this a common issue on this update? should i flash again to stock and upate again trough the phone?
Click to expand...
Click to collapse
Check for /efs/imei/keystr. Should contain "ON". If it doesn't exist, you'll need to create it. You need root to accomplish any of this.
ctomgee said:
Check for /efs/imei/keystr. Should contain "ON". If it doesn't exist, you'll need to create it. You need root to accomplish any of this.
Click to expand...
Click to collapse
Thanks friend. Just one more question. Is this dangerous to the EFS folder, i just got back my phone after 18 days on the warranty service since it lost it's IMEI and i don't want to pass trough that 18 days again, should i root the phone, back up the EFS folder and then try your solution.
What do you think friend?
Can i use thi solution i found on this post
http://forum.xda-developers.com/showthread.php?t=1648026
"- Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
Go to home, force close your terminal app, shut your screen off, and when your turn it back on your lock screen should be there."
Betornillo said:
Thanks friend. Just one more question. Is this dangerous to the EFS folder, i just got back my phone after 18 days on the warranty service since it lost it's IMEI and i don't want to pass trough that 18 days again, should i root the phone, back up the EFS folder and then try your solution.
What do you think friend?
Can i use thi solution i found on this post
http://forum.xda-developers.com/showthread.php?t=1648026
"- Download "Terminal Emulator" app from market
- open it
- type into the command:
su
echo -n ON > /efs/imei/keystr
sync
Go to home, force close your terminal app, shut your screen off, and when your turn it back on your lock screen should be there."
Click to expand...
Click to collapse
You should always back up your efs folder.
And yes, that will work. Also check to make sure the file has at least read permissions for all groups once it's created.
ctomgee said:
You should always back up your efs folder.
And yes, that will work. Also check to make sure the file has at least read permissions for all groups once it's created.
Click to expand...
Click to collapse
Well the thing i did not want to do i already did, my phone is stuck on the boot screen afteri tried to downgrade from ics to GB using this rom
I9100UMKG4_I9100UMKG2_I9100TCEKG4_HOME (wich is correct because i used it before three weeks ago in order to restore my phone and make work the warranty)
after the flash the phone showed me several red letters with the E: cant mount file *****
OMG What should i do. i'm in panic again cause i just got it back after 18 days :'(
I can acces to download mode, is this thing good. should i stop flashing and flshing the same rom?
Pls help
i made some research about the e: can't mount trouble and looks like i need to install the i9100XXKH3 with the re-pratition field checked, so i'll try that. Wish me luck :'(
Meanwhile i'll search some clean underwear cause those red letters scared me.
Hi anyone and everyone,
So let me start by saying I am really in need of help two months ago i had a flawless CM7 Nook Tablet 16GB that worked like a dream and now i have a useless brick and im about to through it away the problem i have can be viewed here............ http://www.youtube.com/watch?v=0BAZ...&playnext=1&list=PL05B917C134DF82A7........It gets stuck on the white screen everytime i was able to boot into CWM with a bootable sd card and I have tried to flash many roms from there and yet every time i get stuck at white screen please help help help help!
WOW!!!!!!!!!!!!!!!!!
Thanks in advance to all that reply!
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
ShinnAsuka said:
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
Click to expand...
Click to collapse
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
and as to where I am now......everytime I turn on my nook it gets stuck at the white screen with the cardboard box.....unless I use a bootable sd card which then I have tried to flash old roms new roms and I get nothing
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
Your partitions are : shot / corrupt / messed up. They "really" gotta be working okay . . . Will the near by B&N store put them back in good working order for you ?
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
With a bootable SD card are you able to.use ADB? If you are you might be able to push a normal build.prop to /system and be able to boot back into your rom. If not then like old fart said you may have messed up your partitions.
Sent from my Nook Tablet CM7 BETA using xda premium app
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Clksk8 said:
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Click to expand...
Click to collapse
assuming you have adb setup correctly the commands aren't too difficult. i believe the following should suffice. i only know windows commands so yeah..
open your start menu, type in cmd and then enter.
navigate to directory where you have adb installed. in my case it was -> cd C:/ntroot
then connect your NT to your computer, make sure usb debugging is enabled which it most likely is if you can get into cwm.
use adb devices, and there should a string of numbers which is your serial number. if you see it then that is a good sign.
then adb remount, which makes the file system writable.
next make sure you have the normal build.prop in that directory that you have adb installed in.
then do adb push build.prop /system
should be very quick, if all goes well you should be able to boot back into your rom. otherwise, your partitions are likely screwed up...
if your partitions are screwed up, there should be a couple of links in the android development section that tell you how to repartition so you can start anew.
good luck.
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
that serial number is normal, you should really learn to use the search function provided by this forum but here are two that i found...
http://forum.xda-developers.com/showthread.php?t=1562130
http://forum.xda-developers.com/showthread.php?t=1605664
those two are assuming you screwed up your partitions.
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
adb is hooked up correctly but when i put adb devices i get
0000000000 recovery instead of a serial number?
So I have bricked my Nook dozens of time but when I do I just download the acclaim_update.zip from one of these threads and go to a file in it.
Go to /META-INF/com/google/android/updater-script and then I just edit the first two lines. Edit both parts where it says "blaze" and change it to "acclaim". If you're on ubuntu then all you have to do is press saveand it will ask if you want to update the file (or something like that) and click yes. Then just make a CWM bootable sd card and flash that file Hope it helps!
Please could somebody tell me if there is any known method for backing up efs/IMEI data that works for the S5830i and if anybody has ever actually successfully restored their IMEI number for this model of phone?
I've read alot of information about differrent methods, although most of them are in the Galaxy S forums and I've seen one post in the Galaxy Ace S5830 forum stating there is currently no known working restore method for the S5830 (but not the S5830i).
Also, apparently (see http://forum.xda-developers.com/showpost.php?p=25718433&postcount=8) you can actually corrupt the /efs partition when backing it up if you are not carefull as it is a hidden partition that is not mounted by default when the phone boots. Apparently, if you don't unmount it after you've backed it up, goodbye /efs partition.
Even if there is no current working restore technique, I would rather backup now to be on the safe side and hope a restore method becomes apparrent in the future as I've already lost my IMEI information once (and managed to get a phone replacement under warranty luckily). I would however prefer to know how I can safely do so first.
Ok, so I've been looking into how to do this for a couple of weeks now and still nothing. Surely somebody must know some information regarding /efs or IMEI data on the s5830i?
I'm in an ADB shell at the moment and I've got an /efs folder in my root directory, but I've looked in this directory and it's currently completely empty (including hidden files). The only thing I can presume is that on my phone /efs is merely a directory that has been created for the specific purpose of acting as a mount point for the actual 'efs partition', which is not actually mounted at the moment for whatever reason.
Issuing the mount command confirms nothing along the lines of an efs partition is mounted. I've had a look in /dev and from searching this forum a bit more, I understand, efs is likely to be /dev/stl# (where # is a digit). So does anybody know which one it is?
I'm not going to do anything silly and start dd'ing it straight off but there must be some way of backing it up safely seeing as it has been done on many other phones. Also any information on when and how it is mounted (by Android OS) and how to mount it safely would be much appreciated even if this is more Android general than my specific model of phone.
I may be speaking to myself in this thread but in case anybody else needs an answer, it looks like Galaxy Toolbox can do an /efs backup and is compatible with the S5830i. See:
http://forum.xda-developers.com/showthread.php?p=25949902
https://play.google.com/store/apps/details?id=com.doky.sgtoolbox
Incidentally, that information seems to imply that the /efs device file is at /dev/bml15, which does exist on my phone, not that I plan on manually interacting with it!
I know this is an old topic and no one showed up here.
But I wanted to come to say to you THANKS! because you really helped me
kitsune0 said:
I know this is an old topic and no one showed up here.
But I wanted to come to say to you THANKS! because you really helped me
Click to expand...
Click to collapse
galaxy toolbox is the solution :good: i already try it ... work fine in restore and backup
terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
angel.sea said:
terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
Click to expand...
Click to collapse
1. Use SGY Toolbox
2. Use this .
http://forum.xda-developers.com/showthread.php?p=38823212
3. Then at last resort
Use the command given by above person
AW: Is efs/IMEI Backup Possible for S5830i
Yeah thats work for me too :thumbup:
Gesendet von meinem GT-S5830i
Ok so I'm what you guys would call a newbie with Android, I've been an iPhone user for years (switched from Verizon to AT&T to get the iPhone because at the time it was an AT&T exclusive). However I'm a really big Google enthusiasts so I have followed Android from inception. Growing tired of how bad AT&T's reception was in my house I recently switched back to Verizon and I purchased the GS4. I'm very happy that I can make calls without the use of a Micro Cell, truthfully reliable coverage was the biggest reason why I switched carriers. Else I would probably got the GS4 or HTC 1 on AT&T.
Being a newbie I made some noob mistakes, however I'm glad to report non of my mistakes bricked my phone. My phone works flawless it's only the stock recovery that is jacked up. So to start off I naively though all S4's were 100% open when rooted, by that I thought I could simply install any ROM I wanted to as long as I was rooted. However it appears that Verizon made Samsung lock the firmware with the OTA updates, from what I gather now after reading is the initial firmware was ok but the subsequent OTA downloads introduced the locked boot. Which sucks for me because I willingly took both updates which put the ME7 and now the MI1 builds on my device.
When I started to root process I had the MI1 build and I performed the De LaVega root method (thank you Tomsgt for your videos)! At the time of root and right after the root I was still not aware of the difference with builds. At that point I attempted to install TWRP via GooManager, since I had the MI1 build it did not work. GooManager kept telling me there was no file for my phone or something similar.
Now this should have been huge red flag for me but I was persistent and I looked on TWRP's website and found the file for my phone along with the manual install instructions. I'm familiar with using a Linux command line so followed the instructions to write TWRP into /dev/block/mmcblk0p21 on my device.
After reboot my device failed to get into stock recovery mode, instead it goes back into download mode but has an extra line of text that says "Could not do normal boot". Since I originally hosed my stock recovery I have read up on the different builds and I have also successfully installed the clockmod recovery option. That all works fine it's just factory recovery is still hosed up and it's annoying me!
I know that was a bit long winded but wanted to give a little background. Now I hope I'm not the only guy/girl who has jacked up the stock recovery section. I was hoping someone had some instructions to fix. Heck I think (but I'm not 100% sure) that if I can get someone who still has stock recovery to copy/export what they have in /dev/block/mmcblk0p21, then I can download that file put on my sd card and then write that back into my system using the same dd input/output command I did before.
May not be that easy but that's what I'm hoping for, or maybe some suggestions. :fingers-crossed:
Thx,
Joe
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
kennyglass123 said:
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
Click to expand...
Click to collapse
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
garzjoe said:
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
Click to expand...
Click to collapse
Bump....
Still hoping there is someone out there who can help me out.
garzjoe said:
Bump....
Still hoping there is someone out there who can help me out.
Click to expand...
Click to collapse
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
southpaw5271 said:
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
Click to expand...
Click to collapse
Hmm I can investigate that but my phone is not bricked. I'm using it now to reply to you. Stock recovery is hosed...so when I power off and then hold Vol+, Power, Home key and then let go of power and keep holding the other two buttons. That key sequence gets my phone into recovery mode. However I can't get into that with my phone anymore.
Thx,
Joe
Hello everyone, i recently purchased one of these from newegg at a reasonable price, but I can't seem to find rom's for them anywhere. Does anyone have any ideas on where to look, i've been hunting on google for hours. It's currently running 4.2.2
Kernel 3.0.36+
Firmware: CT9706_RK610
Im not sure what else to do. I would hate to have to stick with stock considering it's a little laggy with the junk that they piled onto it. Not to mention i know it has the chinese OS installed on it. Luckily i WAS able to root it, and even get cwm installed on it, but i have no rom to flash to it as of yet. Any help is appreciated, thanks!
Soft Bricked Taipad 10s
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Adulator12 said:
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Click to expand...
Click to collapse
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
MAXIMAURO said:
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
Click to expand...
Click to collapse
Do either of you still have the original firmware for the Taipad 9X? I've essentially bricked mine by loading an incompatible firmware and would love to get back to the original.
I'd be willing to pay a small fee to get it.