Database Info

[Q] Problem with EFS Pro & GT-i9300

Hello,
i've tried to backup the EFS Partition of my new Galaxy S3 with EFS Pro v1.8.3. My Busybox version is 1.20.2.
While trying to backup I get the following error:
Code:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'mountpoint:'
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!
Device-Info:
Code:
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
ROM Build: m0xx-user 4.0.4 IMM76D I9300XXALE8 release-keys
Android Version: 4.0.4
BusyBox Version: 1.20.2-Stericson
SU Binary Version: 0.91:SUPERSU
I tried to post in the EFS Pro Thread, but I don't have ther permission to.
So maybe you can help me here?
Yours
Cryptomaniac

I also get this too!

I have the same problem:
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
ROM Build: m0xx-user 4.0.4 IMM76D I9300XXALE8 release-keys
Android Version: 4.0.4
BusyBox Version: 1.20.2-Stericson
SU Binary Version: 0.93:SUPERSU
This error shows up when I choose the img format: (on local and device backup path)
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Verifying MD5 Checksum... Failed!
Device MD5 Hash: md5sum: can't open 'mountpoint:'
Backup Data MD5 Hash: md5sum: can't open '/sdcard/EFSP
Error: MD5 Checksum Mismatch!!!
DO NOT USE THIS BACKUP!!!
Operation Finished!
When I choose the tar format or disable the MD5 check the procedure runs through but only creates a faulty file with about 4k size:
Checking Device Connection... Device Connected!
Checking ROOT Access... Okay.
Backing Up Device's '/efs' Folder, Please Wait...
Detected '/efs' Partition Location: mountpoint: /factory: Not a
Creating EFS Backup Partition Image...
Copying EFS Backup To PC Storage... Okay.
Copied: remote object '/sdcard/EFSProBackup/EFS_201275_185620.img' does not exist
Deleting Temporary EFS Backup From Device... Okay!
Operation Finished!
any help is much appreciated

the new version fixed the problem for me
EFS Pro v1.8.6 has now been released!
Improved Nexus S / Galaxy Nexus Support and fixed the bug that caused the detection of the partition location to fail for some devices
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1308546

I am facing some issues with my Galaxy Note, I can't write in EFS Pro thread too. I backup my efs with EFS Pro. Now my imei become null and baseband unknown because of flashing roms. I can't restore backup, it show mount point error. Someone help me.

EFS Pro 2.0.12: Unable to Create Archive
I am a new user to EFS Pro, and am using v2.0.12. I tried other older versions, and am getting the same error, and that is when I start the backup, I get an error that it cannot create the archive.
My S3 Tmobile (SGH-T999) is rooted and currently running CM10.1 1/24 nightly. I also enabled USB & ADB debugging. The program accesses the phone OK, it seems that the problem is just in the final saving of the file.
I thought perhaps it was a permission issue with the program not being able to write to my disk, however I have it running with Administrator privileges. I'm stumped. Oh and my O/S is Windows 7 Pro, 64-bit.

grogargh said:
I am a new user to EFS Pro, and am using v2.0.12. I tried other older versions, and am getting the same error, and that is when I start the backup, I get an error that it cannot create the archive.
My S3 Tmobile (SGH-T999) is rooted and currently running CM10.1 1/24 nightly. I also enabled USB & ADB debugging. The program accesses the phone OK, it seems that the problem is just in the final saving of the file.
I thought perhaps it was a permission issue with the program not being able to write to my disk, however I have it running with Administrator privileges. I'm stumped. Oh and my O/S is Windows 7 Pro, 64-bit.
Click to expand...
Click to collapse
I have the same problem. Help please. Thanks!
Edit: solved the problem downgrading busybox to the latest stable version.

BrMBr said:
I have the same problem. Help please. Thanks!
Edit: solved the problem downgrading busybox to the latest stable version.
Click to expand...
Click to collapse
I have the same issue, but the busybox change didn't help
Device Info:
---------- Hardware Information ----------
Connected Device SN.: 3832E63FECEC00EC
Device Manufacturer: SAMSUNG
Device Model: GT-I9000
Product Code: GT-I9000HKDKOR
Hardware Version: MP 0.800
---------- Firmware Information ----------
PDA Version: I9000XXJVQ
Baseband Version: I9000XXJVQ
CSC Version: I9000OXAJVQ
---------- Software Information ----------
Kernel Release: 2.6.35.7-I9000XXJVQ-CL281085
Kernel Version: #DarkCore_2.9.2_JVQ PREEMPT Sat Jul 23 19:19:57 EEST 2011
ROM Build: GT-I9000-user 2.3.4 GINGERBREAD XXJVQ release-keys
Android Version: 2.3.4
BusyBox Version: 1.20.0-Stericson
SU Binary Version: 2.3.1-ef
LOG
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Okay.
Checking backup folder location... Okay.
Backing up selected partition(s)...
Creating archive: GT-I9000_201366_154523.tar.gz...
Operation failed!
Any Idea ?

[Q&A] [P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permis

[Q&A] [P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permis
Q&A for [P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permissive !
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permissive !. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

signature verification issues
When I attempt to flash this rom onto my p905v using any version of odin (I have tried 3.04, 3.07, and 3.09) I am getting this error:
secure magiccode check fail.
I also tried install this using adb sideload and I am getting a signature verification error when I do that. Did anyone run into a similar issue with this device? Thanks I really appreciate any help.

Update Kernel to Latest Firmware
Hello esgie, thank you for the kernel
but will you kindly update it to the latest firmware P905XXUANH3
Thank you

Update Kernel to Latest Firmware
Can you Kindly update it to latest Firmware

MD5 Error
I have attached a screenshot of the error i received, can you help please
its showing
MD5 hash value is invalid
P905BootReloaded1Fix1.tar.md5 is invalid.

gee22 said:
I have attached a screenshot of the error i received, can you help please
its showing
MD5 hash value is invalid
P905BootReloaded1Fix1.tar.md5 is invalid.
Click to expand...
Click to collapse
It seems like you're using a different Odin than the one that made the hash, most likely older. However, just take the .md5 string away from the filename and flash it as .tar instead. Unlress, of course, your file is from an obscure source.

Thank you
I am using Odin 3.09
arcadia2uk said:
It seems like you're using a different Odin than the one that made the hash, most likely older. However, just take the .md5 string away from the filename and flash it as .tar instead. Unlress, of course, your file is from an obscure source.
Click to expand...
Click to collapse

anyone else receiving complete write failed? I get this when I flash after removing the md5 extension as suggested above..

[Q&A] [ROM] [5.0.2] [NIGHTLY] CyanogenMod 12 for Nexus 5

Q&A for [ROM] [5.0.2] [NIGHTLY] CyanogenMod 12 for Nexus 5
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.0.2] [NIGHTLY] CyanogenMod 12 for Nexus 5. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

ramon
Any bugs?

RamonEdnei said:
Any bugs?
Click to expand...
Click to collapse
One or two.

zagorteney said:
One or two.
Click to expand...
Click to collapse
Even With 5.0.2 i am still having old issue of streaming music in the car. The audio still skips. Any suggestion for that ? Expect that Cm12 5.0.2 is running smother than before.

Like entering a rainforest!

galaxys said:
Like entering a rainforest!
Click to expand...
Click to collapse
Its scary yet the thrill and dopamine rush is like nothing else...:laugh::laugh:

I can't flash the zip on my friend's nexus. He's on TWRP 2.8.5.2
Anyone have any ideas?
A bit from the log underneath.
Installing '/sdcard/Download/cm-12-20150304-NIGHTLY-hammerhead.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against RSA key 0
Zip signature verified successfully.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package supports bootloader(s): HHZ12d; this device has bootloader HHZ11k.
This package supports bootloader(s): HHZ12d; this device has bootloader HHZ11k.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/cm-12-20150304-NIGHTLY-hammerhead.zip'
Error flashing zip '/sdcard/Download/cm-12-20150304-NIGHTLY-hammerhead.zip'
Updating partition details...

bomzje said:
I can't flash the zip on my friend's nexus. He's on TWRP 2.8.5.2
Anyone have any ideas?
A bit from the log underneath.
Installing '/sdcard/Download/cm-12-20150304-NIGHTLY-hammerhead.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against RSA key 0
Zip signature verified successfully.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package supports bootloader(s): HHZ12d; this device has bootloader HHZ11k.
This package supports bootloader(s): HHZ12d; this device has bootloader HHZ11k.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/cm-12-20150304-NIGHTLY-hammerhead.zip'
Error flashing zip '/sdcard/Download/cm-12-20150304-NIGHTLY-hammerhead.zip'
Updating partition details...
Click to expand...
Click to collapse
Upgrade your bootloader to HHZ12d.

Primokorn said:
Upgrade your bootloader to HHZ12d.
Click to expand...
Click to collapse
Thanks man, that was it.
Looking over the log again, I guess I should've seen that.
Thanks nonetheless

Any other has real problem with performance and stability? I get really hogging experience sometimes like all ram is used and device is struggling to do anything ... Known memory leak or something?
My autorotation also seems to disable itself sometimes and my WIFI keeps disconnecting from time to time..

How can i disable speed indicators on data icons in status bar? Like stock?
Sent from my Nexus 5 using XDA Free mobile app

Can you update using CM updater?
I can't, every time I update, it does reboot, but the version of the rom is the same. I have to manually install downloaded zip using recovery.

biowep said:
Can you update using CM updater?
I can't, every time I update, it does reboot, but the version of the rom is the same. I have to manually install downloaded zip using recovery.
Click to expand...
Click to collapse
With CM recovery?

Primokorn said:
With CM recovery?
Click to expand...
Click to collapse
clockworkmod recovery, yes

biowep said:
clockworkmod recovery, yes
Click to expand...
Click to collapse
CWM is not the same. CM Recovery is the new recovery developed by Cyanogen.
More details: http://forum.xda-developers.com/google-nexus-5/general/recovery-cyanogen-recovery-nexus-5-t3042595

Primokorn said:
CWM is not the same. CM Recovery is the new recovery developed by Cyanogen.
More details: http://forum.xda-developers.com/google-nexus-5/general/recovery-cyanogen-recovery-nexus-5-t3042595
Click to expand...
Click to collapse
It works with CM recovery and also with TWRP. Is CM12 no more compatible with CWM or there is just a problem with my device?
On their wiki page the CWM recovery is still the reccomended one: http://wiki.cyanogenmod.org/w/Install_CM_for_hammerhead

biowep said:
It works with CM recovery and also with TWRP. Is CM12 no more compatible with CWM or there is just a problem with my device?
On their wiki page the CWM recovery is still the reccomended one: http://wiki.cyanogenmod.org/w/Install_CM_for_hammerhead
Click to expand...
Click to collapse
CWM is outdated since Jelly Bean and this wiki page too
TWRP remains the more powerful and updated recovery for Android.

Sounds are very low with the last update. Notifications, messaging and charging sound, very very low. Nightly 10/02

I can not install CM12 after upgrading to 5.1 ???
Please help me?
Sent from my Nexus 5 using XDA mobile app

datagubben said:
I can not install CM12 after upgrading to 5.1
Please help me?
Sent from my Nexus 5 using XDA mobile app
Click to expand...
Click to collapse
Give more details... Maybe it's caused by the new bootloader.

error 7 on Twrp

When i try to flash a ROM on my leeco, appears in twrp the error 7 what means???
Have a solution for this error??
And custom ROM android 7 or lineage os, aosp, resurrection remix ROMs
for leeco le s3

A some GuY said:
When i try to flash a ROM on my leeco, appears in twrp the error 7 what means???
Have a solution for this error??
And custom ROM android 7 or lineage os, aosp, resurrection remix ROMs
for leeco le s3
Click to expand...
Click to collapse
My dear Friend
Do not put everything here on XDA, do some exercise and search on google, you will get your answer. i request you to please close this thread.:good:

Error 7 in TWRP-Recovery means that the ROM-Image (zip file) doesn't match your phone. In our case there exist several models for the S2 (SD652): X520, X522, X526 and X527.
If you want to avoid Error 7, you need to open the zip-file (maybe 7zip):
- go to directory META-INF \ com \ google \ android
- open the file "updater-script" with an editor like notepad++
- place a # at the beginning of the first two lines, looks like this:
# (!less_than_int(....
# get_device_compatible...
- save the modifications in the zip-file and put it into the phone
- now update your phone via twrp

A some GuY said:
When i try to flash a ROM on my leeco, appears in twrp the error 7 what means???
Have a solution for this error??
And custom ROM android 7 or lineage os, aosp, resurrection remix ROMs for leeco le s3
Click to expand...
Click to collapse
It is possible to make a screen shot of the whole error message in TWRP.
There is more than one Error 7.
Provide the screen shot, to be sure you'll get the correct answer.

JamBax said:
It is possible to make a screen shot of the whole error message in TWRP.
There is more than one Error 7.
Provide the screen shot, to be sure you'll get the correct answer.
Click to expand...
Click to collapse
Ok i send a print and thx to try to help me

Andy_04 said:
Error 7 in TWRP-Recovery means that the ROM-Image (zip file) doesn't match your phone. In our case there exist several models for the S2 (SD652): X520, X522, X526 and X527.
If you want to avoid Error 7, you need to open the zip-file (maybe 7zip):
- go to directory META-INF \ com \ google \ android
- open the file "updater-script" with an editor like notepad++
- place a # at the beginning of the first two lines, looks like this:
# (!less_than_int(....
# get_device_compatible...
- save the modifications in the zip-file and put it into the phone
- now update your phone via twrp
Click to expand...
Click to collapse
Ok dude, i can try do this your help, thx man

Andy_04 said:
Error 7 in TWRP-Recovery means that the ROM-Image (zip file) doesn't match your phone. In our case there exist several models for the S2 (SD652): X520, X522, X526 and X527.
If you want to avoid Error 7, you need to open the zip-file (maybe 7zip):
- go to directory META-INF \ com \ google \ android
- open the file "updater-script" with an editor like notepad++
- place a # at the beginning of the first two lines, looks like this:
# (!less_than_int(....
# get_device_compatible...
- save the modifications in the zip-file and put it into the phone
- now update your phone via twrp
Click to expand...
Click to collapse
Thanks....
Do I have to add space after the #?
# (!less_than_int(1513360281, getprop("ro.build.date.utc"))) || abort("Can't install this package (Sat Dec 16 01:51:21 CST 2017) over newer build (" + getprop("ro.build.date") + ").");
# getprop("ro.product.device") == "le_x6" || abort("This package is for "le_x6" devices; this is a "" + getprop("ro.product.device") + "".");

[GUIDE] [VIDEO] Properly Install Custom ROMs on Mi A1 !!

I've seen lot's of folks getting messed up while flashing ROMs on the Mi A1, probably because of the A/B partitioning system (maybe) so, I've made a video on how to flash custom ROMs on Mi A1!! You can watch it here! :good:
Direct Link:https://youtu.be/Ufdn8ql5Lso
​

Thank you!
Works fine if you have TWRP already installed ...
But coming from Stock there is no TWRP.
Maybe you can add the missing parts (unlock bootloader, install TWRP ...)

good day.
I think i need a little help. I tried to Install 4 different ROMs (Resurrection remix, dotOS, Aospextended, BootleggersROM) through the methods described here.
i always get the following error message.
Skiping digest check:no digest file found
step1/2
error applying update: 7 (errorcode::kInstallDeviceOpenError)
Updater proceess enden with ERROR: 1
Error Installinga zip file '/sdcardTWRP/ROMs/AospExtended-v5.3-tissot-2018-0325-0858-OFFICIAL.zip'
updating partition details...
...done
I do know what to do, I cant find any information about the error on the web.
can you please help me?