Database Users

Any fix for this? (Picture attached)

I'm out of ideas. I've asked before but got no where. I figured a picture may help. I can root and get all the way to cm 7.0.3 but anything 1.2 update related fails. I've tried using the cwm flashable update but that fails too.
The pic is from a fresh 1.0. (I've tried 1.1 also.)
Sent from my DROIDX using XDA Premium App

USE THIS http://forum.xda-developers.com/showthread.php?t=1000957 with a sandisk 8 gb class 4 chip.....
Call it a day.... use CM7.1 RC, its very stable.... if you need to update to nightlies, its simple as just copy the downloaded file onto the external memory card.

Yeah that is a last resort. I plan on giving that nook to my brother who is android illiterate. How did everything get borked anyway?
I bypassed the registration and my nook info looks like this
Sent from my DROIDX using XDA Premium App

OH CRAP.... looks like some sort of internal corruption....
Do a complete wipe......
THEN Do the SDCard install...
It's seemless to the user... THere is no bootup screen or anything... The nook will automatically boot to the sd first.... so he won't need to know anything...
if he is REALLY not too literate, then he can just pull the sd, and it boots into the nook.

Ok....I'm not sure what kind of SD card I have... it just says micro SD hc 4gb with a circle with a 4 in it.
So I'm assuming its a class 4 SD card...not sure the brand though
Sent from my DROIDX using XDA Premium App

oman0123 said:
Ok....I'm not sure what kind of SD card I have... it just says micro SD hc 4gb with a circle with a 4 in it.
So I'm assuming its a class 4 SD card...not sure the brand though
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
It will work fine..... class 4 is good enough

Also if anybody knows a fix for whatever happened I would much rather do that than running off of sd
Also Thanks for the help slider. At least I know he will at least have the current cm if I can't find a fix
Sent from my DROIDX using XDA Premium App

oman0123 said:
Also if anybody knows a fix for whatever happened I would much rather do that than running off of sd
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
Did you try to wipe it? under settings?

slider2828 said:
Did you try to wipe it? under settings?
Click to expand...
Click to collapse
Yup wont let me. Says: deregister device failed with error: user not registered (E_NOT_REGISTERED)
Sent from my DROIDX using XDA Premium App

Looks like your "ROM" got corrupted... it is a partition (/dev/mmcblk0p2) that is mounted r/w as /rom
Check and see if you have partition mmcblk0p3 and if rombackup.zip is in there...
Boot off CWM bootable uSD... then try the following:
adb shell mkdir /tmp
adb shell mount /dev/block/mmcblk0p3 /tmp
adb shell ls /tmp
if rombackup.zip is there... you're fine... we can fix it.

Wow I've been rooting for about 3 years and have never ever used adb. Crazy right? Can anybody point me in the right direction ?
Sent from my DROIDX using XDA Premium App

can that be done in terminal emulator or do I gotta go and install adb and whatever else on my computer?

term emulator would work.

DizzyDen said:
Looks like your "ROM" got corrupted... it is a partition (/dev/mmcblk0p2) that is mounted r/w as /rom
Check and see if you have partition mmcblk0p3 and if rombackup.zip is in there...
Boot off CWM bootable uSD... then try the following:
adb shell mkdir /tmp
adb shell mount /dev/block/mmcblk0p3 /tmp
adb shell ls /tmp
if rombackup.zip is there... you're fine... we can fix it.
Click to expand...
Click to collapse
Ok I tried adb shell mkdir /tmp and i get mkdir: cant create directory /tmp: read only file system.
Tried adb shell mount /dev/block/mmcblk0p3 /tmp, it fails and says no such file or directory.
does this mean if I want the newest versions of cm7 I gotta do it off sd?

Arrrgh been trying all night. I hope there's still a way and its not completely borked
Sent from my DROIDX using XDA Premium App

oman0123 said:
Ok I tried adb shell mkdir /tmp and i get mkdir: cant create directory /tmp: read only file system.
Tried adb shell mount /dev/block/mmcblk0p3 /tmp, it fails and says no such file or directory.
does this mean if I want the newest versions of cm7 I gotta do it off sd?
Click to expand...
Click to collapse
You could still run CM7 off of EMMC... we're just trying to salvage your device specific information if there's any hope... which I truly think there is.
oman0123 said:
Arrrgh been trying all night. I hope there's still a way and its not completely borked
Click to expand...
Click to collapse
Sorry... was at work... didn't have a chance to reply...
try adb remount
before the other steps above... if you get an error then you will need to
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
One of those two should work from CWM bootable uSD... then the steps I listed above will work... IF you have the rombackup.zip file... we'll help you through fixing your issues.

DizzyDen said:
You could still run CM7 off of EMMC... we're just trying to salvage your device specific information if there's any hope... which I truly think there is.
Sorry... was at work... didn't have a chance to reply...
try adb remount
before the other steps above... if you get an error then you will need to
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
One of those two should work from CWM bootable uSD... then the steps I listed above will work... IF you have the rombackup.zip file... we'll help you through fixing your issues.
Click to expand...
Click to collapse
I got the same error messages after the remount but the "adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system" seemed liked it work. it didnt say anything though

It won't give you a message saying it was successful... just try the other commands to see if you have backuprom.zip on partition 3. If its there... we can fix the issues... if not.. we have to make stuff up to fix it
You can do the same thing for partition 2 (where the device specific stuff is stored unzipped) by creating directory called tmp2 and mounting /dev/block/mmcblk0p2 to it... in that one 3 specific files you're looking for are:
DeviceID
MACAddress
SerialNumber
Those are plain text type files (but not DOS or windows formatted.. so you can view them, but don't edit them in notepad)

DizzyDen said:
It won't give you a message saying it was successful... just try the other commands to see if you have backuprom.zip on partition 3. If its there... we can fix the issues... if not.. we have to make stuff up to fix it
You can do the same thing for partition 2 (where the device specific stuff is stored unzipped) by creating directory called tmp2 and mounting /dev/block/mmcblk0p2 to it... in that one 3 specific files you're looking for are:
DeviceID
MACAddress
SerialNumber
Those are plain text type files (but not DOS or windows formatted.. so you can view them, but don't edit them in notepad)
Click to expand...
Click to collapse
Ok you are gonna have to help me with that. I wouldnt even know where to begin. We all gotta push our limits right? haha

Check your PM... give me a call if you want.
I gave you some bad commands.... this should work:
adb shell mount -O remount /remount, rw /dev/block/mmcblk0p5 /system
adb shell mkdir /system/tmp
adb shell mount /dev/block/mmcblk0p3 /system/tmp
adb shell ls -l /system/tmp
then
adb shell mkdir /system/tmp2
adb shell mount /dev/block/mmcblk0p2 /system/tmp2
adb shell ls -l /system/tmp2
OR
adb shell
mkdir /system/tmp
etc.
etc.
Since you have the rombackup.zip on mmcblk0p3 try this...
extract attached file... then run the resettofactory.cmd file... it will copy the BootCnt file to /rom and make it think its on 8th failed boot.

[SOLVED] Using Terminal Emulator to write to system

Not sure if this will help anyone else, but I searched forever trying to figure out how to write into the system folder using Terminal Emulator on the Note 3 to no avail. I found a slew of posts that said to type "mount -o rw,remount /system" to achieve this. When I used this command it didn't return any errors so I assumed it worked, however no files ended up being copied and pasted to the location I wanted. I found numerous other examples that were supposed to enable writing to the system as well, but none of them worked. I finally figured out how to get it to work on my Note 3 by typing "mount" in terminal emulator and noticing that at the very beginning of the string that was returned was "rootfs". So if you are wanting write to your system using Terminal Emulator on the VZW Note 3 here is what ended up working for me:
Code:
mount -o remount,rw rootfs
to return to read only enter:
Code:
mount -o remount,ro rootfs
I wanted to figure this out because a bug in TWRP v2.6.3.0 maimed my efs partition and bricklooped my phone. Even flashing the Stock Developer tar by Beans wouldn't bring it out of the brickloop. I was able to get out of the brickloop by following this thread, but even though my phone booted up and the IMEI # was correct, my /efs folder was missing in action. This caused odd things to happen like my lock screen not functioning and the power button instantly turning the phone off instead of bringing up the power menu. I discovered this was because the phone was placed into something called "factory mode" and that to fix it you needed to edit some files in the efs folder, which were completely missing on my device. Member js0uth graciously sent me his efs folder from his Developer Note 3 and when I copied it to my phone it began to function normally again (big shout out to js0uth!). However, this folder was completely deleted once again after a reboot. So now you can see why I was looking for a way to copy these files using Terminal Emulator. I ended up making a Tasker profile with the Secure Settings plugin that automatically copies the files from my ext SD card to my system folder on boot of the device. In order to mount, copy/paste the files while retaining the correct permissions from the folder that js0uth sent me, and unmount the system I had the set up my Secure Settings command as follows:
Code:
mount -o remount,rw rootfs;cp -Rpf /storage/extSdCard/efs/* /efs/;mount -o remount,ro rootfs
So now I have a livable workaround for my problem until I can discover a way for the phone to rebuild my own /efs folder.
Edit: See radionerd's post for a permanent fix to this issue and be sure to hit thanks under his name if it helps you.

I did the same to my DE. Corrupted EFS about a month ago after a few flashes using TWRP 2.6.3.0. Boot loops for 28 hours of hell until I followed your tracks to the trick that deleted my corrupted EFS folder, and created a new empty folder. I guess this would wipe out IMEI, Mac, and more in models that store phone specific data in EFS. We lucked out I've read that our phones have that info in a few other folder not EFS
Since wiping EFS I have run stock ROM, CM11, and now bean V6. I didn't see the factory mode popup until recently. I noticed that the screen will flash when leaving or entering cell service.
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Thanks for documenting your steps to recovery.
radionerd

radionerd said:
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Click to expand...
Click to collapse
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
radionerd said:
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Click to expand...
Click to collapse
Setting the Factorymode folder to ON is actually what disables that mode. Seems backwards I know, but when it's set to OFF (or if the folder is completely missing as in my case) that warning message will display. If that folder is intact on your phone then you should be able to use a string to disable or enable Factorymode.

It got worse before it got better
bodieism said:
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
No worries, I went from an annoyance of no lock screen to bricked for over 6 weeks. This happened after trying to do an EFS backup.
I've learned a lot since back then, My DE is back 100%, EFS is repaired. I think we ran the same script which actually points to the wrong mount in our phones. It brought us out of bootloops, but efs was pointed to block12. Qualcom snapdragon Note-3's use mmblk0p11 to load /efs.
If you still have to load the tasker script, I think I figured out an easy fix to rebuild your original efs folder.
I would backup mounts first, delete /efs folder. Then run the original script, but this time change from 12 to 11.
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p11
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs
Bet that would do the trick
Here is my thread
Click to expand...
Click to collapse

^ That did do the trick! :good:
Phone is back to 100% working order :highfive:

[Q] efs folder empty, 'E: unable to mount /efs' error (still have IMEI)

Hi all
I still have IMEI, I'm able to make phone calls and everything else. But my phone is in this Factory Mode and my EFS folder can not be mounted and it empty.
I have EFS back up.
when i flash somthing i see 'E: unable to mount /efs' error'
I have tried to search for sulotion without succes and i tried to flash stock rom and other roms and still same problem.
what sould i do?

up

eden66 said:
Hi all
I still have IMEI, I'm able to make phone calls and everything else. But my phone is in this Factory Mode and my EFS folder can not be mounted and it empty.
I have EFS back up.
when i flash somthing i see 'E: unable to mount /efs' error'
I have tried to search for sulotion without succes and i tried to flash stock rom and other roms and still same problem.
what sould i do?
Click to expand...
Click to collapse
That's a weird problem.
It sounds like the EFS is working properly but the phone can't mount the partition properly. (Which is weird by itself)
You might try using Odin to flash back to bone stock to see if that repairs the partition. But that might be risky if the EFS is damaged because any further damage might totally kill the EFS.
When you say you have the IMEI do you know that because you can make calls? Or do you know that because you have looked in settings and it tells you what your IMEI is?

Skipjacks said:
That's a weird problem.
It sounds like the EFS is working properly but the phone can't mount the partition properly. (Which is weird by itself)
You might try using Odin to flash back to bone stock to see if that repairs the partition. But that might be risky if the EFS is damaged because any further damage might totally kill the EFS.
When you say you have the IMEI do you know that because you can make calls? Or do you know that because you have looked in settings and it tells you what your IMEI is?
Click to expand...
Click to collapse
I tired back to stock but same probelm.
And i see the IMEI in the settings and when I dail *#06#. The IMEI is ok like it As appears behind the battery.
its very wierd

eden66 said:
Hi all
I still have IMEI, I'm able to make phone calls and everything else. But my phone is in this Factory Mode and my EFS folder can not be mounted and it empty.
I have EFS back up.
when i flash somthing i see 'E: unable to mount /efs' error'
I have tried to search for sulotion without succes and i tried to flash stock rom and other roms and still same problem.
what sould i do?
Click to expand...
Click to collapse
Hi mate ,
try this maybe folder are not mounted correctly
1- Install / use Terminal Emulator
2- mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
3- mke2fs /dev/block/mmcblk0p10
4- mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
5- Reboot
Anyhow check this thread also
http://forum.xda-developers.com/showthread.php?t=2392632

[Q] HELP... NOTHING will work

so i have an S4 GT-I9505 originally on H3G. i live in the UK
i was given the phone as a non starter, i have managed to flash Cyanomodgen 11.0 however ....
it has a sim card in yet it states:
Network - Unknown
Signal Strength - 0
Mobile Network Type - Unknown
Service status - Out of Service
Roaming - Not roaming
Mobile Network State - disconnected
My Phone number - unknown
IMEI - Unknown
IMEI SV - Unknown
Baseband version - Unknown
i have tried using Odin to flash the original O/S but odin gets stuck on 'getting PIT'
i have tried using Odin to flash a new radio again it sticks at 'getting pit'
I have tried EFS recovery but the EFS file is practically empty and wont restore and doesn't have the relevant files in for a restore...
really really stuck with this, at this moment in time i have a tablet not a phone.
I just want this back to stock working as a phone....
HELP

piratesteve84 said:
so i have an S4 GT-I9505 originally on H3G. i live in the UK
i was given the phone as a non starter, i have managed to flash Cyanomodgen 11.0 however ....
it has a sim card in yet it states:
Network - Unknown
Signal Strength - 0
Mobile Network Type - Unknown
Service status - Out of Service
Roaming - Not roaming
Mobile Network State - disconnected
My Phone number - unknown
IMEI - Unknown
IMEI SV - Unknown
Baseband version - Unknown
i have tried using Odin to flash the original O/S but odin gets stuck on 'getting PIT'
i have tried using Odin to flash a new radio again it sticks at 'getting pit'
I have tried EFS recovery but the EFS file is practically empty and wont restore and doesn't have the relevant files in for a restore...
really really stuck with this, at this moment in time i have a tablet not a phone.
I just want this back to stock working as a phone....
HELP
Click to expand...
Click to collapse
Hi mate ,
Do you have an EFS backup? restore it
Check if the EFS folder is mounted correctly
Install / use Terminal Emulator
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Reboot
After that check :
With a root explorer go to EFS/factoryApp/factorymode and open it if it says off change it to on
If you decide to go back to stoc check here , great thread , it shows you how to use the PIT file

EFS and Terminal
Thanks for your reply,
since my post i have managed to flash a stock rom (4.4.2), however when i use root browser to look in the EFS folder it is empty
so i downloaded terminal emulater.. when i opened terminal it went like this
[email protected]:/ $
i then typed in what you said...
[email protected]:/ $ mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
it then read
mount: invalid option -- -
mount: invalid option --
so i tried
mke2fs /dev/block/mmcblk0p10
nothing happened
so then i tried
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
it then showed
mount[ -r option] [ -w option] [-o option] remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
so i reset the device and went looking for the EFS file..... again empty.
sorry for the long winded reply but its all about the detail.

piratesteve84 said:
so i have an S4 GT-I9505 originally on H3G. i live in the UK
i was given the phone as a non starter, i have managed to flash Cyanomodgen 11.0 however ....
it has a sim card in yet it states:
Network - Unknown
Signal Strength - 0
Mobile Network Type - Unknown
Service status - Out of Service
Roaming - Not roaming
Mobile Network State - disconnected
My Phone number - unknown
IMEI - Unknown
IMEI SV - Unknown
Baseband version - Unknown
i have tried using Odin to flash the original O/S but odin gets stuck on 'getting PIT'
i have tried using Odin to flash a new radio again it sticks at 'getting pit'
I have tried EFS recovery but the EFS file is practically empty and wont restore and doesn't have the relevant files in for a restore...
really really stuck with this, at this moment in time i have a tablet not a phone.
I just want this back to stock working as a phone....
HELP
Click to expand...
Click to collapse
It looks to me like You have lost Your EFS partition data.
This is bad if You don't have EFS backup done.
Only way to restore Your EFS data without backup is either returning to return to full stock plus Triangle Away wipe flash counter and sending phone to warranty repair.
Or if You are not under warranty, find someone with Z3X box.

[Q] i337m Null imei and unknown baseband help

Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.

Twisteddd said:
Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.
Click to expand...
Click to collapse
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.

Asadullah said:
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.
Click to expand...
Click to collapse
Thanks for replay
But that is a way to explore the phone files?
I did a lot of research to find out if the efs file on this model s4 actually contains the .nv_data.bin at all? or it is somewhere else?
Do you know if these files are actually missing from efs folder on i337m? or they are stored somewhere else?
Thanks.

Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255

Twisteddd said:
Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255
Click to expand...
Click to collapse
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.

NighthawkXL said:
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.
Click to expand...
Click to collapse
Tried and gave me the following error in shell
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell
[email protected]:/ $ su
su
root[email protected]:/ # mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs: invalid option -- t
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_
PERCENT] [-L LABEL] BLOCKDEV [KBYTES]
-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run
1|[email protected]:/ #

Twisteddd said:
Thanks for replay
But that is a way to explore the phone files?
Thanks.
Click to expand...
Click to collapse
Thats how people were re-writing / repairing their meids

Asadullah said:
Thats how people were re-writing / repairing their meids
Click to expand...
Click to collapse
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.

Twisteddd said:
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.
Click to expand...
Click to collapse
Yeah its a rough road ahead of you. I know it can be done because people advertise it on craigslist. But I don't know exactly how.
get on stock nb1 and dial *#0808# change usb settings to dm+modem+adb might get you on the right road.

Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services

Twisteddd said:
Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services
Click to expand...
Click to collapse
There's definitely a different way z3x is such a rip off. I don't know it but as I get time I'm looking around. I'm wondering if you can locate all of the spots that carry the imei if you can change them to something else.

Can some one tell me if the following z3x box sold on ebay enough for repairing baseband on my phone i337m? Or do I need to buy the smart card with it also?
http://m.ebay.ca/itm/151500466184?nav=SEARCH
I know i will need the uart micro usb.
Thanks.

Does null IMEI cause unknown baseband or unknown baseband causes null IMEI?
Which one should be fixed first?
Also the service mode (*#0011#) being blank is it because of the modem is not working?
Thatnks.

When I try qpst in windows 7 to connect to the phone in order to rewrite IMEI;
I can change usb setting to RMNET by dialling *#0808#, the device manager it installs two usb ports under ports. Com6 and com7
RMNET SAMSUNG network driver installs but cant be started. it shows a yellow caution sign on the driver. Restarting windows and phone does not fix it.
When I enter the com ports to qpst configuration, it says active but says no phone.
Any help is appreciated.