Related
~~~~~~~~~ WARNING ~~~~~~~~~
PLEASE BACKUP YOUR EFS BEFORE YOU ATTEMPT TO FLASH OR MODIFY YOUR PHONE. EFS CONTAINS YOUR DEVICE IMEI WHICH IS VERY IMPORTANT.
You could use the following backup methods to backup your IMEI.
1. Archive Backup [Recommended]
This will create a compressed archive and copies it to your SD Card
* Root your phone.
* Install Terminal Emulator use ADB from your Computer.
* Type the following commands
Code:
su
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
* This will create a compressed archive efs-backup.tar.gz in your SD Card.
* Copy this archive to your system and save it in several places.
2. Individual Files
This will just copy the files from your efs partition to your sdcard.
* Root your phone.
* Install Terminal Emulator use ADB from your Computer.
* Type the following commands
Code:
su
cp -a /efs/. /sdcard/i9003_efs/
* This will create a folder i9003_efs in your sd card containing your EFS partition files.
* Copy this folder to your system and save it in several places.
3. Automatic Backups with CyanogenMod
* Whenever you are flashing from Stock to CyanogenMod, the EFS is copied to a different partition. In this process, a backup of the efs is created in /sdcard/backup/efs.
* You could copy the efs backup files to your system and save them for later.
Note that EFS is unique for device and if you loose your EFS without having a backup, you couldn't restore it and you will have to visit the Samsung Service and get your motherboard replaced.
A Little Background
IMEI is stored in the EFS partition of your device and it is unique for each and every device. IMEI is important and so is the EFS partition on your phone. Whenever you flash any custom rom, the efs partition is never touched and is always present on the device unlike the SYSTEM and KERNEL partition which vary with firmwares.
IMEI in a Stock rom is stored in the STL3 (/dev/block/stl3) partition and the filesystem is RFS. This is the primary and the most important partition and this data is shipped with the device and is unique for each and every phone.
Starting from Cyanogenmod 10 Alpha 4, the filesystem has been changed to facilitate bigger partitions. The RFS filesystem is no longer used since it is proprietary to Samsung. Instead, we are using YAFFS. For this reason, we wont be able to read the RFS partition which contains the EFS since the RFS support was removed from the kernel. To overcome this problem, we create a mirror partition for EFS and we copy the data from the original EFS partition to the newly created partition during when the ROM is being flashed. This creates 2 copies of the EFS in the device and also each time CyanogenMod is flashed, a backup of the EFS is created in the sdcard which could be very useful.
Hence, if you are having issues with lost IMEI on Cyanogenmod 10 or 10.1 releases, it would mean that maybe the mirror partition is improper but the original partition is still intact, which could be checked by returning back to stock. If you are still not having your IMEI on the Stock rom also, that is when you would be needing to restore using this guide.
*** RESTORING YOUR EFS ***
FOLLOW THIS GUIDE ONLY IF YOU ARE ON A STOCK ROM AND THE ABOUT PHONE DOESNT SHOW THE BASEBAND AS WELL AS THE IMEI NUMBER.
IF YOU ARE ON ANY CUSTOM ROM, FIRST FLASH THE STOCK ROM AND CHECK TO SEE IF YOU HAVE YOUR IMEI BACK.
PLEASE READ THE ENTIRE TOPIC BEFORE ATTEMPTING TO DO ANYTHING. IF YOU ARE HAVING ANY CONCERNS OR NEED TO ASK ANY QUESTIONS, FEEL FREE TO MAKE A POST IN THIS TOPIC AND I WILL DEFINITELY REPLY. PLEASE DON'T HURRY AND SCREW UP THINGS EVEN BAD. MESSING AROUND WITH SUCH THINGS COULD PROVE COSTLY SINCE THE ONLY ALTERNATIVE REPAIR IS BY GETTING THE MOTHERBOARD CHANGED BY SAMSUNG.
FOR THIS GUIDE, YOU WILL BE REQUIRED TO HAVE AN EFS BACKUP WITH YOU. YOU CANNOT RECOVER YOUR EFS WITHOUT IT (Atleast for now). NEVER SHARE YOUR EFS BACKUPS WITH OTHER MEBERS, SINCE THE NETWORK CARRIER MAY BLACKLIST YOUR IMEI IF THERE ARE MORE THAN ONE DEVICE BEING USED WITH THE SAME IMEI ON THE SAME CARRIER.
Click to expand...
Click to collapse
What is Required
* Any Stock Rooted ROM with CWM Recovery [DDFL2 Recommended]
* Odin or Hemidall
* Odin EFS Template for Galaxy SL I9003 [I9003_EFS_ODIN_BLANK_TEMPLATE.tar]
* CWM EFS Restore Script [I9003_EFS_CWM_RESTORE.zip]
* Backup of EFS
* External SD Card
* Some Brains.
Check the Extent of Damage / Create Backups
* If you are having issues with IMEI, first flash back to the Stock ROM
* Once on a Stock ROM, Check the contents of /efs with a File Manager and see if there are any files.
* If there are no files, you could directly perform the restore using the next step.
* If there are some files and you are having a fake IMEI, it would be better to backup the current EFS just in case.
** From the ADB Shell, type
Code:
su
dd if=/dev/block/stl3 of=/sdcard/efs.rfs
This will create a efs.rfs raw backup for your device, which could be used later on whenever you need it. You could flash the efs.rfs file from Odin. Keep it somewhere safely.
Recovery Procedure if you have Archive Backup or the Individual Files.
* Flash the Stock ROM and make sure that you are able to boot into the recovery and everything works fine. [ I am not going to cover flashing instructions since they are everywhere in the forum]
* Create a folder in your External SD Card named "efsbackup" and copy all the files and folders from the EFS backup that you have directly inside the folder. If you are having a tar.gz archive, extract all of the files into the folder directly.
* Power down the device and press Volume Up + Home + Power Combination to get into the Recovery Mode.
* Select Install ZIP from SDCard and then select the I9003_EFS_CWM_RESTORE.zip from the SDCard. Wait for few seconds to complete the restore.
* Once done, boot the phone and check to see if you are getting your Baseband, Network Signal and IMEI.
* If you still are not able to get your IMEI, make sure that you are using the proper backup. Try another backup if you have it.
Recovery Procedure if you have RAW Partition Image
* Copy the Partition Image to SD Card and name it efsbackup.rfs
* Connect the phone to ADB or use Terminal Emulator for the following commands
Code:
su
dd if=/sdcard/efsbackup.rfs of=/dev/block/stl3
This will restore the partition to your backup and you should be having a working IMEI now.
Formatting your EFS Partition
DO THIS ONLY IF YOU ARE HAVING ISSUES WITH MOUNTING /efs WHILE FLASHING NEW ROM OR IF YOU HAVE USED EFS CLEAR IN ODIN OR IF YOU EFS GET CLEARED EVERY BOOT.
* Download the I9003_EFS_ODIN_BLANK_TEMPLATE.tar file from the attachment.
* Power off the phone and boot into the Download mode by using the Volume Down + Home + Power Combination.
* Connect your phone to the PC, Start up Odin and select the I9003_EFS_ODIN_BLANK_TEMPLATE.tar in PDA and press Start.
* Once done, your EFS will be blank and you could use the 1st Method to restore your EFS backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very nice info dhiru
Sent from my GT-I9003
Dhiru is there terminal emulator command to create efs.rfs backup???
This thread should be stickied
I have the fake imei. I try many method but still 0049xxx. Any solutions? Thank you
ndttung8487 said:
I have the fake imei. I try many method but still 0049xxx. Any solutions? Thank you
Click to expand...
Click to collapse
Yeah. You could try this method but you need a backup first.
Sent from my GT-I9300 using xda premium
dhiru1602 said:
Yeah. You could try this method but you need a backup first.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Can I use backup IMEI from the same SL i9003 device to mine? as it have huge problem with hardware but still have correct IMEI and all informations? Thank you.
ndttung8487 said:
Can I use backup IMEI from the same SL i9003 device to mine? as it have huge problem with hardware but still have correct IMEI and all informations? Thank you.
Click to expand...
Click to collapse
Yes. But be advised that 2 phones with same IMEI could cause legal problems. IMEI spoofing is illegal in several countries.
You could use the EFS backup (nv_data.bin) from any I9003, I9000 or Nexus S devices.
dhiru1602 said:
Yes. But be advised that 2 phones with same IMEI could cause legal problems. IMEI spoofing is illegal in several countries.
You could use the EFS backup (nv_data.bin) from any I9003, I9000 or Nexus S devices.
Click to expand...
Click to collapse
Oh thank you, because that phone my dad had bought some years ago but hardly damage, he bought a new one and leave it to me! I won't fix that phone as i very expensive to recover, so I use your steps as above? Thanks alot dhiru!
ndttung8487 said:
Oh thank you, because that phone my dad had bought some years ago but hardly damage, he bought a new one and leave it to me! I won't fix that phone as i very expensive to recover, so I use your steps as above? Thanks alot dhiru!
Click to expand...
Click to collapse
If you already have some files in the /efs partition, maybe your permissions are messed up. Get me an output for ls -l /efs/
dhiru1602 said:
If you already have some files in the /efs partition, maybe your permissions are messed up. Get me an output for ls -l /efs/
Click to expand...
Click to collapse
So I use this command in my phone or broken phone? before or after i copy?
ndttung8487 said:
So I use this command in my phone or broken phone? before or after i copy?
Click to expand...
Click to collapse
that is for check your efs folder permission, which is your good phone with imei problem.
Sent from my Galaxy Nexus
I try every steps many times but still 0049xx.
I got backup file from broken phone which the same as mine (SL i9003) efs folder and everything too
Can you help? thanks alot!
i have unknown baseband and blank imei...can this fix it?...and i dont backup my efs folder before my samsung galaxy Sl i9003 lost imei and unknown baseband ...any solution for my problem?...
sorry for my poor english
ndttung8487 said:
I try every steps many times but still 0049xx.
I got backup file from broken phone which the same as mine (SL i9003) efs folder and everything too
Can you help? thanks alot!
Click to expand...
Click to collapse
That's strange. Maybe there is some kind of verification if the IMEI belongs to the device or not and that is why it is failing. I honestly don't know.
karlcaks said:
i have unknown baseband and blank imei...can this fix it?...and i dont backup my efs folder before my samsung galaxy Sl i9003 lost imei and unknown baseband ...any solution for my problem?...
sorry for my poor english
Click to expand...
Click to collapse
Are you on stock rom?
dhiru1602 said:
That's strange. Maybe there is some kind of verification if the IMEI belongs to the device or not and that is why it is failing. I honestly don't know.
Are you on stock rom?
Click to expand...
Click to collapse
Thank you alot for your hard work Dhiru! I'll try again but if no luck than it's fine! Because I love to use SL and still able to use in my country!! Exept I didn't know can I use it in India if I have a chance to visit!!!! Very happy if able to use it in your country too.
ndttung8487 said:
Thank you alot for your hard work Dhiru! I'll try again but if no luck than it's fine! Because I love to use SL and still able to use in my country!! Exept I didn't know can I use it in India if I have a chance to visit!!!! Very happy if able to use it in your country too.
Click to expand...
Click to collapse
Try removing nv_data.bin.md5 and see if it does any good.
rm -rf /efs/nv_data.bin.md5
dhiru1602 said:
Try removing nv_data.bin.md5 and see if it does any good.
rm -rf /efs/nv_data.bin.md5
Click to expand...
Click to collapse
It said "read only file system", can you pm your skype or yahoo? thank you
Are you on stock rom?[/QUOTE]
yes now im on DDLF2 now...
Hi everyone, I've been using twrp since I first rooted my nexus 5 but using the recovery tools app I flashed philz recovery and I like it but what are the differences and are there key features I should know about?
Nexus 5, CM11, Franco kernel and Xposed framework
I listed the key features in post 1 of the philz recovery thread.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
TheAlliedFleet said:
Hi everyone, I've been using twrp since I first rooted my nexus 5 but using the recovery tools app I flashed philz recovery and I like it but what are the differences and are there key features I should know about?
Nexus 5, CM11, Franco kernel and Xposed framework
Click to expand...
Click to collapse
Backing up what rootSU mentioned below is the list of features in his Philz Recovery thread:
Features:
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
optional reboot after custom backups/restores
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
you can cancel any nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
USB mount in recovery
adb root in recovery: just wait about a minute to activate
Overall, Philz Recovery has a lot more features then the standard touch CWMR, such as built in terminal, gui file manger, ability to flash multiple zips and many more (Which are listed above).
Basically, PhilZ is the best of both worlds (TWRP and CWM)
Hi there. I'm currently using the "official" CWM v6.0.4.5, and I do find it quite annoying that it now creates its backups under data/media/clockworkmod instead of the easily accessible .../0 sd partition. I'd love to switch to Philz if only for the theming and OTG support. It looks like it's as simple to use as your standard CWM. So I have two questions: 1) I can just flash the Philz Recovery zip using my current CWM, then just delete the Clockworkmod folder under the data/media folder since I would no longer need it? and 2) Is there an option to backup EFS like in TWRP? Because after reading some of the horror stories on these forums about restoring the EFS partition (granted on a different device), this is definitely something I don't want/need to be able to backup for fear of the possibility of messing anything up.
Thanks for taking the time to help out!
charesa39 said:
Hi there. I'm currently using the "official" CWM v6.0.4.5, and I do find it quite annoying that it now creates its backups under data/media/clockworkmod instead of the easily accessible .../0 sd partition. I'd love to switch to Philz if only for the theming and OTG support. It looks like it's as simple to use as your standard CWM. So I have two questions: 1) I can just flash the Philz Recovery zip using my current CWM, then just delete the Clockworkmod folder under the data/media folder since I would no longer need it? and 2) Is there an option to backup EFS like in TWRP? Because after reading some of the horror stories on these forums about restoring the EFS partition (granted on a different device), this is definitely something I don't want/need to be able to backup for fear of the possibility of messing anything up.
Thanks for taking the time to help out!
Click to expand...
Click to collapse
1. Yes
2. Yes but you can disable it.
BirchBarlow said:
1. Yes
2. Yes but you can disable it.
Click to expand...
Click to collapse
Great. I've always preferred CWM over TWRP for some reason, but now this gives me the best of both like you said. Thanks!
This is a small utility to create flashing via Odin backup EFS or FULL ROM including: bootloader, system and modem.
Usage:
+ Get the root
+ Extract archive
+ On the device to enable debugging of USB and wired to the PC
+ Enter the folder SAMSUNG_SM-N900_FULL_BACKUP_RESTORE_UTILS, run FULL_BACKUP.bat
+ On the device to allow root access adb
+ Select the desired option
* BACKUP ODIN ROM - about 20 minutes.
* When ODIN RESTORE phone automatically switches to the ODIN MODE and extract files for firmware from * .zip archives
A.S._id said:
This is a small utility to create flashing via Odin backup EFS or FULL ROM including: bootloader, system and modem.
Usage:
+ Get the root
+ Extract archive
+ On the device to enable debugging of USB and wired to the PC
+ Enter the folder SAMSUNG_SM-N900_FULL_BACKUP_RESTORE_UTILS, run FULL_BACKUP.bat
+ On the device to allow root access adb
+ Select the desired option
* BACKUP ODIN ROM - about 20 minutes.
* When ODIN RESTORE phone automatically switches to the ODIN MODE and extract files for firmware from * .zip archives
Click to expand...
Click to collapse
Can it backup data partition too?I mean all installed apps with all the settings....just like a nandroid.
Can u direct us to a method by which we can convert nandroid backup into odin flashable archive?
Thanks a lot.
Sent from my beloved Galaxy Note 3
unisol107 said:
Can it backup data partition too?I mean all installed apps with all the settings....just like a nandroid.
Can u direct us to a method by which we can convert nandroid backup into odin flashable archive?
Thanks a lot.
Sent from my beloved Galaxy Note 3
Click to expand...
Click to collapse
It is theoretically possible. But I not implement this feature, from the need to perform a variety of conditions: 1. The need to in the device external microsd not smaller internal memory free space 30Gb. 2. The creation of the backup would take more than an hour. I pursued the goal is to make utility to obtain the firmware from the device when it is impossible to get it by another method, such as when she flew through the air or for create custom Odin ROM. But and for everything else, there Titanium backup
But if you very needs this you can make it into terminal:
Code:
su
make_ext4fs -s -l 27044M /mnt/exSdCard/userdata.img /data
A.S._id said:
It is theoretically possible. But I not implement this feature, from the need to perform a variety of conditions: 1. The need to in the device external microsd not smaller internal memory free space 30Gb. 2. The creation of the backup would take more than an hour. I pursued the goal is to make utility to obtain the firmware from the device when it is impossible to get it by another method, such as when she flew through the air or for create custom Odin ROM. But and for everything else, there Titanium backup
But if you very needs this you can make it into terminal:
Code:
su
make_ext4fs -s -l 27044M /mnt/exSdCard/userdata.img /data
Click to expand...
Click to collapse
Thanks a lot for clearing up things...great tool.
Very nice!!
will check and report !
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hi everyone, I made this tutorial because I did not find anything on the internet related and I believe that this information will help.
Requirements:
Unlocked bootloader
//
How to flash TWRP:
First grab this TWRP (TWRP 3.1.0.0):
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-0-0-xiaomi-redmi-4a-t3576024
Install with fastboot with these commands:
Code:
fastboot flash recovery twrp-3.1.0-0-20170318-UNOFFICIAL-rolex.img
fastboot boot twrp-3.1.0-0-20170318-UNOFFICIAL-rolex.img
It will boot TWRP then flash this zip (It will remove forced encryption on MIUI, if not flashed you will bootloop):
http://en.miui.com/thread-310923-1-1.html
//
//
How to Magisk/Root:
Thats is simple just grab the latest zip and apk from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Go to TWRP and flash after reboot install the apk and you're good to go!
//
//
How to Xposed System/less:
Go to this thread and grab the apk and install (Xposed Material):
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Open it and go to MIUI based roms and select if you want system one (our arch is arm64 so xposed-v87-sdk23-arm64...), or if you want systemless root select Magisk (xposed-v87-sdk23-Magisk...) it will download and ask for SU to reboot and install on TWRP.
//
//
How to move apps to sdcard on MIUI (App2SD:
To move apps to SD first make sure you have a good SD card (Class 10 for example) because if not things will lag a lot, then download App2SD (the blue one), now you need to partition you SD card you can do that by three ways in the app itself, on Gparted for linux or in MiniTool Partition Wizard for Windows, (ALL YOUR DATA ON SD WILL BE ERASED!) you will make two partitions one for your things like photos and music and the other one for apps the first will be VFAT and the second EXT4,
after that go to the app give superuser and select link apps to sd card, it will ask the partition and type then ask wich method will be using, i have used all methods, i'm using magisk and the magisk method leave me in bootloops, the normal method and init.d method works but i need to do a soft reboot after I start the phone to mount the sd, the only works after reboot for me its advanced method. now you're good to go, move your apps to your SD!
App2SD link: https://play.google.com/store/apps/details?id=in.co.pricealert.apps2sd&hl=pt_BR
//
Comming soon: Unlock your bootloader from Linux with help of virtualization.
Thanks mate for the guide. It's work on MIUI Global ROM. Is there any way to browse 2nd Partition when i need to edit some file manually on 2nd Partition? :good:
BryanByteZ said:
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hi everyone, I made this tutorial because I did not find anything on the internet related and I believe that this information will help.
Requirements:
Unlocked bootloader
//
How to flash TWRP:
First grab this TWRP (TWRP 3.1.0.0):
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-0-0-xiaomi-redmi-4a-t3576024
Install with fastboot with these commands:
Code:
fastboot flash recovery twrp-3.1.0-0-20170318-UNOFFICIAL-rolex.img
fastboot boot twrp-3.1.0-0-20170318-UNOFFICIAL-rolex.img
It will boot TWRP then flash this zip (It will remove forced encryption on MIUI, if not flashed you will bootloop):
http://en.miui.com/thread-310923-1-1.html
//
//
How to Magisk/Root:
Thats is simple just grab the latest zip and apk from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Go to TWRP and flash after reboot install the apk and you're good to go!
//
//
How to Xposed System/less:
Go to this thread and grab the apk and install (Xposed Material):
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Open it and go to MIUI based roms and select if you want system one (our arch is arm64 so xposed-v87-sdk23-arm64...), or if you want systemless root select Magisk (xposed-v87-sdk23-Magisk...) it will download and ask for SU to reboot and install on TWRP.
//
//
How to move apps to sdcard on MIUI (App2SD:
To move apps to SD first make sure you have a good SD card (Class 10 for example) because if not things will lag a lot, then download App2SD (the blue one), now you need to partition you SD card you can do that by three ways in the app itself, on Gparted for linux or in MiniTool Partition Wizard for Windows, (ALL YOUR DATA ON SD WILL BE ERASED!) you will make two partitions one for your things like photos and music and the other one for apps the first will be VFAT and the second EXT4,
after that go to the app give superuser and select link apps to sd card, it will ask the partition and type then ask wich method will be using, i have used all methods, i'm using magisk and the magisk method leave me in bootloops, the normal method and init.d method works but i need to do a soft reboot after I start the phone to mount the sd, the only works after reboot for me its advanced method. now you're good to go, move your apps to your SD!
App2SD link: https://play.google.com/store/apps/details?id=in.co.pricealert.apps2sd&hl=pt_BR
//
Comming soon: Unlock your bootloader from Linux with help of virtualization.
Click to expand...
Click to collapse
Hello!
Could you explain in detail how to use magisk to transfer the data to the SD? because I don't understand the method, thanks!
DISCLAIMER
Code:
Your warranty is now void.
I'm not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired, because the alarm app failed. Please
do some research if you have any concerns about features included
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
This is made for Vernee M5 only. Do not use on other devices!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prerequisites:
Way 1: Backup your M5 with MTK flashtool (readback function). You can find the scatter loading file in the attachment. You can also use @77777777777777's unbrick.img, but it does not contain all partitions (e.g. NVRAM/NVDATA, because the information stored there differs on every device and should be kept private (IMEI)).
Way 2: Backup your M5 as written here. This only works if your device is already rooted.
Unlock your bootloader. You can find @77777777777777 's guide here
ADB and fastboot tools
An external sd card
Test TWRP before flashing
adb reboot bootloader
fastboot boot recovery.img
There is a little bug in the recovery that does not turn the screen on. After one to two minutes you can press the power button and it will turn on.
Do not decrypt the data partition or delete it if you don't flash a custom rom. If TWRP works for you and you plan to flash it, allow system modifications. This will prevent android from restoring the stock recovery.
Flash TWRP
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot continue
Booting into TWRP
adb reboot recovery
Using 'reboot to recovery' button in magisk
Hold power + volume up if the device is powered off and select recovery
Installing magisk
Download magisk and copy it to an external sdcard
Once the card is in your device, reboot into recovery. Do not decrypt the data partition! This will cause bootloops. Allow to make system modifications if you haven't done this before because otherwise you will not be able to flash magisk.
Flash the zip
Credits:
@77777777777777
Everyone who contributed to this
TeamWin
Magisk developers
Downloads:
scatter file: see attachment
twrp: https://github.com/ngc4622/android_device_nb_vernee_M5/releases
reserved
reserved (2)
Im tester
I would like test TWRP, but i cant flash it Always start stock recovery ?
Is your bootloader unlocked?
Can you boot it ('Test TWRP before flashing'), or does this fail as well?
If you can boot it, mount the system partition and use the file explorer to find out if there is a file in the system folder called recovery-from-boot.bak
If it is called recovery-from-boot.p, retest twrp but allow system modification. Then twrp will rename this file. After that you should be able to flash and use TWRP.
ResurrectedRobot said:
Is your bootloader unlocked?
Can you boot it ('Test TWRP before flashing'), or does this fail as well?
If you can boot it, mount the system partition and use the file explorer to find out if there is a file in the system folder called recovery-from-boot.bak
If it is called recovery-from-boot.p, retest twrp but allow system modification. Then twrp will rename this file. After that you should be able to flash and use TWRP.
Click to expand...
Click to collapse
It works already! :good:
Need help
Hi, i'm don't understand how to make the root on vernee m5 with texts.. Sorry for bad english, i'm a newbee in the questions.
But any people can make a movie tutorial for root the vernne m5?
Thanks.
sergiokdc said:
Hi, i'm don't understand how to make the root on vernee m5 with texts.. Sorry for bad english, i'm a newbee in the questions.
But any people can make a movie tutorial for root the vernne m5?
Thanks.
Click to expand...
Click to collapse
Look any video about flashing twrp any android.
factory reset
Hi all!
Factory reset doesnt work after flashing recovery.
(need back original)
Hi,
@sergiokdc: could you find out what you need to do? If so, did it work?
@triumfanto: As said above, please do not do a factory reset with this recovery if you do not flash a custom rom.
However, it now happened . Please try to restore your device with MTK flashtool using @77777777777777's unbrick.img. You can find it here. Please let me know if it worked for you. If you need further help, do not hesitate to ask for it.
Yours,
ResurrectedRobot
The solution is back the original recovery and device boot again.
Thanks for your favor!
Looking forward into this, thanks for the hard work bro.
If you need any help, I can try to help, just send a pm
I have a question
can you help me please before unlocking the bootloader how can I make a backup of the imei
RenoRex said:
can you help me please before unlocking the bootloader how can I make a backup of the imei
Click to expand...
Click to collapse
For backuping IMEI you need the scatter file and MTK flashtool.
You start flashtool and select the scatter file.
Then you go to the readback option and add entries for the nvdata and nvram partitions.
You can find the values for size etc in the scatter file.
Then you turn your phone off and start the readback.
Connect the powered off phone to your computer and wait until it finishes.
Yours,
ResurrectedRobot
ResurrectedRobot said:
For backuping IMEI you need the scatter file and MTK flashtool.
You start flashtool and select the scatter file.
Then you go to the readback option and add entries for the nvdata and nvram partitions.
You can find the values for size etc in the scatter file.
Then you turn your phone off and start the readback.
Connect the powered off phone to your computer and wait until it finishes.
Yours,
ResurrectedRobot
Click to expand...
Click to collapse
ResurrectedRobot thank you very much for the response with this version of SPFlash Tool v5.1744 I can use the scatter file
ResurrectedRobot said:
DISCLAIMER
Code:
Your warranty is now void.
I'm not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired, because the alarm app failed. Please
do some research if you have any concerns about features included
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
This is made for Vernee M5 only. Do not use on other devices!
Prerequisites:
Way 1: Backup your M5 with MTK flashtool (readback function). You can find the scatter loading file in the attachment. You can also use @77777777777777's unbrick.img, but it does not contain all partitions (e.g. NVRAM/NVDATA, because the information stored there differs on every device and should be kept private (IMEI)).
Way 2: Backup your M5 as written here. This only works if your device is already rooted.
Unlock your bootloader. You can find @77777777777777 's guide here
ADB and fastboot tools
An external sd card
Test TWRP before flashing
adb reboot bootloader
fastboot boot recovery.img
There is a little bug in the recovery that does not turn the screen on. After one to two minutes you can press the power button and it will turn on.
Do not decrypt the data partition or delete it if you don't flash a custom rom. Only allow system modifications on a flashed TWRP!
Flash TWRP
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot continue
Booting into TWRP
adb reboot recovery
Using 'reboot to recovery' button in magisk
Hold power + volume up if the device is powered off and select recovery
Installing magisk
Download magisk and copy it to an external sdcard
Once the card is in your device, reboot into recovery
Flash the zip
Credits:
@77777777777777
Everyone who contributed to this
TeamWin
Magisk developers
Downloads:
scatter file: see attachment
twrp: https://github.com/ngc4622/android_device_nb_vernee_M5/releases
Click to expand...
Click to collapse
BAD TUTORIAL!
Following the exact steps mentioned got my device in a loop after flashing recovery. TWRP kept asking for a decryption password and the device wouldn't boot in system mode. Basic wiping or system formatting wouldn't work within TWRP since it could not mount the partitions. I ended up using fastboot to try and format what I could, which didn't fix anything (might have been stupid, but this shouldn't be happening anyway).
FORTUNATELY, at least the unbrick tutorial (https://forum.xda-developers.com/showpost.php?p=75570725&postcount=94) works, and I had created a backup for nvdata and nvram before attempting all of this. So, right now, at least I have a working phone again (google service keeps crashing, but that's not as much of an issue).
So, summarizing, if you are reading this thread and thinking about installing TWRP on your M5, thing again and perhaps wait until there's a custom ROM available, so more people will attempt and report these issues.
20180503 said:
BAD TUTORIAL!
Following the exact steps mentioned got my device in a loop after flashing recovery. TWRP kept asking for a decryption password and the device wouldn't boot in system mode. Basic wiping or system formatting wouldn't work within TWRP since it could not mount the partitions. I ended up using fastboot to try and format what I could, which didn't fix anything (might have been stupid, but this shouldn't be happening anyway).
FORTUNATELY, at least the unbrick tutorial (https://forum.xda-developers.com/showpost.php?p=75570725&postcount=94) works, and I had created a backup for nvdata and nvram before attempting all of this. So, right now, at least I have a working phone again (google service keeps crashing, but that's not as much of an issue).
So, summarizing, if you are reading this thread and thinking about installing TWRP on your M5, thing again and perhaps wait until there's a custom ROM available, so more people will attempt and report these issues.
Click to expand...
Click to collapse
Hi,
I'm sorry to hear it did not work for you.
I admit some parts in the tutorial are ambiguous making it possible to run into your issue.
I'll update the tutorial in order to prevent this during the next hours. I hope it will work four you then.
Yours,
ResurrectedRobot
ResurrectedRobot said:
Hi,
I'm sorry to hear it did not work for you.
I admit some parts in the tutorial are ambiguous making it possible to run into your issue.
I'll update the tutorial in order to prevent this during the next hours. I hope it will work four you then.
Yours,
ResurrectedRobot
Click to expand...
Click to collapse
Sorry for being a little heated, I felt like my device was lost at some points.
Now I see you mentioning that system modification should be allowed (and sure, at first I dismissed it, just like the decryption), but isn't the entire point of Magisk the fact that it is systemless? Why does keeping it read-only cause problems?
I think I'll be keeping my phone stock for now (well, aside from the bootloader), until there's a good custom ROM available at least. Coming from another phone that ran Lineage causes some disappointments, but the only big issue with stock Vernee is the shutter sound.
20180503 said:
FORTUNATELY, at least the unbrick tutorial (https://forum.xda-developers.com/showpost.php?p=75570725&postcount=94) works, and I had created a backup for nvdata and nvram before attempting all of this. So, right now, at least I have a working phone again (google service keeps crashing, but that's not as much of an issue).
Click to expand...
Click to collapse
In case anyone else is in this same situation, installing the update given by the manufacturer (http://www.vernee.cc/products/m5/rom/) restored Google functionality. It's mind-boggling how much functionality is broken when Google is not working.
20180503 said:
Now I see you mentioning that system modification should be allowed (and sure, at first I dismissed it, just like the decryption), but isn't the entire point of Magisk the fact that it is systemless? Why does keeping it read-only cause problems?
Click to expand...
Click to collapse
To be honest, I do not know much about magisk except a few basics.
If you allow system modifications in TWRP a file that automatically restores the stock recovery after reboot is being renamed in order to keep TWRP.
However, this does not refer to the magisk installation issue. In some special cases the system partition is being changed when installing magisk (e. g. addon.d support) but this should
only happen when using custom roms. So I can not really tell you why you ran into this issue because is should, as you said, not happen.
If somebody knows more about magisk, please tell us.