[IMPORTANT] Backup your EFS IMMEDIATELY. [Backup and Restore Guides]

[IMPORTANT] Backup your EFS IMMEDIATELY. [Backup and Restore Guides] - Samsung Galaxy SL i9003

~~~~~~~~~ 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...

Related

[GUIDE]Full ROM backup/dump for MTK6573 & MTK6516 phones !!![NOT nandroid backup]

Hi all MTK6573/MTK6516 users !!!!
SEE SECOND POST FOR MTK6516 phones.
THIS POST IS FOR MTK6573 phones.
This is for all MTK6573 users with Android 2.3(.x). Also for all B63M phones !!
Follow this guide to backup your FULL ROM !! You can even flash your phone through FlashTools with this COMPLETE backup !!!
ROOT IS REQUIRED !!
Here is the guide:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'MTK-6573-BackUpTools.rar' from attachments and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
NOTE: The backup script is not created by me. Gathered all information from the web !!
Hit THANKS if you find this useful !!

For MTK6516 !!
THIS POST IS FOR MTK6516 phones.
This is for all MTK6516 users with Android 2.2(.x).
Follow this guide to backup your FULL ROM !! You can even flash your phone through FlashTools with this COMPLETE backup !!!
ROOT IS REQUIRED !!
Here is the guide:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'MTK-6516-BackUpTools.rar' from attachments and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
NOTE: The backup script is not created by me. Gathered all information from the web !!
Hit THANKS if you find this useful !!

A few questions!
Hello!
Thank you for this software, it worked with making a dump of my rom. How do you create a scatter file to use in SP Flash Tool? Or do you have another program that I can use to flash these files back onto the phone?
The SP Flash Tool I am using V2.1129.00 does not show as many partitions as what was backed up by my phone with the default MT6573 scatter file that it comes with.
I keep getting errors trying to load/burn the files to my phone.
PLEASE HELP!!

LeStonga said:
Hello!
Thank you for this software, it worked with making a dump of my rom. How do you create a scatter file to use in SP Flash Tool? Or do you have another program that I can use to flash these files back onto the phone?
The SP Flash Tool I am using V2.1129.00 does not show as many partitions as what was backed up by my phone with the default MT6573 scatter file that it comes with.
I keep getting errors trying to load/burn the files to my phone.
PLEASE HELP!!
Click to expand...
Click to collapse
You can try this:
Copy the backup_ folder from your sd card to your computer. Now place a copy of a the scatter file.txt in that folder.
Now in SP Flash tool, browse to the folder and select the scatter file that you placed.....all files will be loaded automatically......

It didnt work . . .
Hello!
I took your advice and attempted to load the scatter file from the same folder that the backup partitions are in.
A few of they files loaded on their own, not all of them, and their are still partitions missing.
When I open the scatter file in txt editor it shows all partitions.
When I open the scatter file in smart phone flash tool i only show
preloader
dsp
uboot*
bootimg*
recovery*
secro
logo*
android*
usrdata
The files above are what shows in sp flash tool program and the ones with the * are the files that load automatically.
I did try a smart phone flash tool version 5.1140 and the scatter file did load correctly with all the partitions, but again not all load and I get an error when I try to load them manually. In addition, I have never been able to successfully use version 5.1140 to flash.
I was able to flash in version 2.1129, but as I said I couldnt load every partition so I am missing my nvram and other partitions.
Can you recommend anything else?
Maybe a different version of sp flash tool that you know works? Maybe a different program all together?
THANKS!

@Bala
Yo, bro, its been awhile since our last chat ! You have been like an android modding/ hacking teacher/ guru & i'm sure alot of users will benefit from all of it...
@LeStonga
Yes, in fact your are correct, there is a software by linerty(these russians are so 'terror', not only hacking but coming out with tools to make it easier) that converts the extracted firmware.info back into scatter.txt...You can find the tuts & tools here.
The tuts even show you ways to upload with FlashTool too ! i know there is an upload function but never knew the way to use it though...

Hello balamu96m!
Thank you for your suggestions, that was the website which I first followed instructions for.
As you can see however, even when Bruno (administrator of the tutorial you provided in the link) opened his scatter file, nvram partition is not shown. I was able to use the program balamu96m pointed me to and it made perfect backups of all my partitions.
My problem is that sp flash tool loads my scatter file and it is the same as Bruno's which is lacking several partitions, especially the nvram partition.
If i use an updated sp flash tool (v5), when I load my scatter file all of my partitions are shown, including nvram, but I have never had any success flashing my phone with that version.
Maybe I can use that version but someone has to help me set up the configurations to flash . .. i.e. download with or without battery, com, baud rate, etc.
Sp flash tool V2.11 was easy to use and straight forward, but even though my scatter lists all my partitions (when i open in a text editor), it only loads the partitions shown in bruno's tutorial, not including nvram.

yuweng said:
@Bala
Yo, bro, its been awhile since our last chat ! You have been like an android modding/ hacking teacher/ guru & i'm sure alot of users will benefit from all of it...
@LeStonga
Yes, in fact your are correct, there is a software by linerty(these russians are so 'terror', not only hacking but coming out with tools to make it easier) that converts the extracted firmware.info back into scatter.txt...You can find the tuts & tools here.
The tuts even show you ways to upload with FlashTool too ! i know there is an upload function but never knew the way to use it though...
Click to expand...
Click to collapse
Hi yuweng bro!
It seems miui is going to release their source code........i read in the russian forum at 4pda that one mtk6573 was running miui 4 (ics).......is that true??
So when miui sources are out, can we build one for our mi-357/350n??
Waiting for your reply

@Bala
AFAIK, Miui public part of their source code before the launch of their first android phone, Xiaomi M1 & now launching their next version M2 which is based on ARM Cortex-A8 & coincidentally, its just been launch today ! Its fully supported by the Miui team & it has two ROM, one ROM for daily use & the other one for you to flash their 'nightly' built. Best is that you can switch over to either one of them at any time ! Great for android enthusiastic...
However, of all hundreds over MT65xx android phone manufacturer all over the world, non of them actually ported it to Miui ! There is only one answer to this, it will be copied over to all other MT65xx ! Thats what Chinese are best at...(Oopps, i'm a Chinese too...)
So, i think you won't see an official Miui phone on MT65xx platform... Currently, official Miui ROM is for single SIM... You can check out Miui sources here & here
If its really true that the russian has ported Miui to MT65xx, very soon we'll have Miui running on every MT65xx...
What you said on the other thread is true, if Mediatek keep on keeping their source code, i think very soon they can keep it to themself forever.... No android enthusiastic will ever buy their phone ever... Even HTC has released the source code for a whole bunch of devices recently after been pressured by android enthusiastic...
@LeStonga
AFAIK, FlashTool is not for flashing NVRam(IMEI). However, you can use it to backup NVRam then restore it. Typically, you only need to download boot, recovery, logo, android, usrdata. Normally, i just download 'android' partition only(system.img) I normally put a 'tick' at 'No Action' for NVRam...
{
"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"
}
There is a thread on how to backup & restoring your MT65xx IMEI by cybermaus just over a week ago...

help help
I have android phone china H4300. mediatek mtk6573. yesterday , i deleted stock launcher and format factory the phone. so i don't use it.
please help me up rom (i haved rom) or install the Launcher ,...
thank you

vanlaosonya said:
I have android phone china H4300. mediatek mtk6573. yesterday , i deleted stock launcher and format factory the phone. so i don't use it.
please help me up rom (i haved rom) or install the Launcher ,...
thank you
Click to expand...
Click to collapse
Do you have modded recovery??

balamu96m said:
Do you have modded recovery??
Click to expand...
Click to collapse
i only have stock recovery

Thanks it works on my MT6573 phone

Hey balamu....
Can you please tell me how to restore this backup...???

maitreyapatni said:
Hey balamu....
Can you please tell me how to restore this backup...???
Click to expand...
Click to collapse
Allow me to answer ...
To restore this backup, 1st you need to convert the firmware.info into your own scatter.txt file. Read here : http://bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
Then you run SPflash tool, choose your scatter file and the appropriate area to flash. You don't need to flash all area. Just boot+system (android) to restore is sufficient. You can change the file by double-click at the appropriate row. Untick to deselect, tick to select which area to flash.
Again, no need to flash the whole thing ... some file contains private info such as nvram/userdata. I've read that many device already bricked by flashing wrong file (specially uboot) unless it's from your own backup.

no cache.img, system.img, data.img
hi balamu, i need some help.
i have an mt6516 phone. i followed every step, but 3 files didn't show up i.e cache.img, system.img, data.img
in the end of running script, gscript show "no such files". my question are: is that normal? are those file important? any ideas to get these files?
i really need any help here.
so thx in advance

hisoka8888 said:
hi balamu, i need some help.
i have an mt6516 phone. i followed every step, but 3 files didn't show up i.e cache.img, system.img, data.img
in the end of running script, gscript show "no such files". my question are: is that normal? are those file important? any ideas to get these files?
i really need any help here.
so thx in advance
Click to expand...
Click to collapse
they are really important...................you can retry the process again.......it should work.....!

silly me
found out the problem. looks like i didn't do exactly one of your step "extract into sd card". i actually extract the content into a folder inside the sd card, so gscript can't find the "Install" folder. I copied the folder into sd card and redo the process then those file showed up. LOL.
anyway, nice share... :good::good:

n7000 note copy rom file i loss it help
n7000 note copy rom file i loss it help
mtk 6573
plz send rom file
mail id [email protected]
thanks in adwance

Hi,Thanks for tutorial,I backup my phone,create scatter file and all goes ok but now i have 1 litl problem,my phone is mobiwire aquila mt6573 platform, he got factory recovery e3 and i wanna change to cwm and Bruno say that cwm must be specific for phone so is any chance to find cwm for my phone or any hack/swap from backup recovery or any other method?
Sorry guys on bad english or wrong section
Thanks

[ROM][7/25] Stock Android 4.3 for Nexus 7 (3G) / No Root / Flashable ZIP

This is a flashable ZIP, containing the latest kernel and build of Android 4.3 by Google. It is made for the Google Nexus 7 3G, and is flashable through TWRP. I did not test it since I don't have a 3G model of the Nexus 7.
Download link: https://mega.co.nz/#!xskHxaRb!ZP3kYCk66VinJc70TswVBSAv8yZ3QoKKgUCtzVe66lY
Odexed, and no superuser management tool. Chainfire released an experimental version supporting Android 4.3 on his Google+. so I'll add that to the OP later.
Enjoy!

Anybody tested?
Also, will there be radio and bootlosder in flashable form?

Fatal1ty_18_RUS said:
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Click to expand...
Click to collapse
From what i can see, there is no bootloader and radio in it, so anyone has to flash it by himself.
EDIT: The ZIP works fine, i just flashed bootloader and radio through fastboot prior to installing it over TWRP. Haven't tested any root zips, yet.

i got 4.3
{
"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"
}

Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
biggoldring said:
Click to expand...
Click to collapse
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?

stadicon said:
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
Click to expand...
Click to collapse
you mean you flash the zip in stock recovery??

Gabrieltan said:
you mean you flash the zip in stock recovery??
Click to expand...
Click to collapse
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..

stadicon said:
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
Click to expand...
Click to collapse
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?

Gabrieltan said:
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Click to expand...
Click to collapse
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.

stadicon said:
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
Click to expand...
Click to collapse
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx

Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta

zard said:
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?

Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta

zard said:
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
that is what i did just now... and it cause i lost my root for tb.. now trying clear data, forget root and rerun the application

Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
Yeah, i forgot to say that i full wiped first, of course (not sure if it's mandatory, though). Bootloader and radio may not be so important, as after i flashed them 4.2.2 booted successfully (before installing 4.3) which might be a sign that not much of a difference was made.
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.

stadicon said:
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
Click to expand...
Click to collapse
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??

There should be no way to lose your backups unless you have chosen purposely to do so. Check that your Titanium Backups folder is still there in SDCARD.
If I weren't on vacation using only Chromebook I'd have upped this this morning with root; I managed via ARM Chromebook dev mode with adb and fastboot to backup data from my N4 and N7 3G and then install stock, flash recovery and make root, followed by restoring my titanium data. Both devices were as they were in 4.2.2 but in 4.3 within the hour.
Furthermore I had the ability to flash Franco r170 on the N4

Gabrieltan said:
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
Click to expand...
Click to collapse
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
BTW, i think the battery drain issue is now fixed.

stadicon said:
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
Click to expand...
Click to collapse
i also dont know why.. but i can backup... ya, only can use root explorer to delete, i tried few apps, all cant delete..

gapps hosted here works: http://forum.xda-developers.com/showthread.php?t=2248654

Clean Flashed 5.0.1 from website, Flashed newest TWRP, but it won't start TWRP.

Basically just as the title says, I can't reboot into TWRP. It shows TWRP, then boots regularly.
Is this a 5.0.1 compatibility issue with TWRP or what?
I can't get root without TWRP and I can't get into TWRP.
Thanks for help.

scottocs said:
Basically just as the title says, I can't reboot into TWRP. It shows TWRP, then boots regularly.
Is this a 5.0.1 compatibility issue with TWRP or what?
I can't get root without TWRP and I can't get into TWRP.
Thanks for help.
Click to expand...
Click to collapse
TWRP 2.8.1.0 boots fine, 2.8.2.0 causes issues atm so flash 2.8.1.0.

gee2012 said:
TWRP 2.8.1.0 boots fine, 2.8.2.0 causes issues atm so flash 2.8.1.0.
Click to expand...
Click to collapse
Ahhhh, great! Thanks

scottocs said:
Ahhhh, great! Thanks
Click to expand...
Click to collapse
You`re welcome

Just as a follow up:
I am on 5.0 and in Android my new TWRP Backups (2.8.1.0) are not shown as a file but rather as a (useless) 0 byte file. Help?
EDIT: Seems like TWRP puts my backups into some other location on my storage so that Lollipop does not see them.
Alright. 2.8.2.0 is broken and 2.8.1.0 puts my backup where I can't reach them conveniently... What now?

Go to the twrp thread and search restorecon. It's a well covered issue

slater_g said:
Just as a follow up:
I am on 5.0 and in Android my new TWRP Backups (2.8.1.0) are not shown as a file but rather as a (useless) 0 byte file. Help?
EDIT: Seems like TWRP puts my backups into some other location on my storage so that Lollipop does not see them.
Alright. 2.8.2.0 is broken and 2.8.1.0 puts my backup where I can't reach them conveniently... What now?
Click to expand...
Click to collapse
I noticed same thing yesterday, and I could not found any solution, so I flashed 5.0.1 again and i´m now comlpetely stock and shearching solution
Wakamatsu said:
Go to the twrp thread and search restorecon. It's a well covered issue
Click to expand...
Click to collapse
Never heard of it, but I shearch now. When I use TWRP filemanager under recovery then this file is correct location (data/media/0/TWRP... ) But under my mixplorer I saw only some TWRP file 0 byt. And after some reboots I even did not saw any filer /root folder. ( it looks like same problem as 5.0 and then permissev boot.img fixed this )

Wakamatsu said:
Go to the twrp thread and search restorecon. It's a well covered issue
Click to expand...
Click to collapse
Thanks. Looked it up but figured that TWRP itself is capable of mounting the device as MTP on my computer and listing the folders correctly. So accessed my backup from there.

slater_g said:
Thanks. Looked it up but figured that TWRP itself is capable of mounting the device as MTP on my computer and listing the folders correctly. So accessed my backup from there.
Click to expand...
Click to collapse
so ..solution was.....?

Mairo said:
so ..solution was.....?
Click to expand...
Click to collapse
Terminal
su
restorecon -FR /data/media/0/*

Aerowinder said:
Terminal
su
restorecon -FR /data/media/0/*
Click to expand...
Click to collapse
thanks this almost helped me.
now when I open Mixplorer then I see SD card/TWRP folder, but still not Backup folder.
But when I go trough /root/data/media/0/TWRP/ then I can see Backups/05c847******/my backup.
can I run some other command in terminal to activate SD card/TWRP location also? ( this location should be /root/storage/emulated/0/TWRP....or.... /root/storage/emulated/legasy/TWRP).
This didnt helped me, I just give up and wait. I dont like if something don't work properly.

Mairo said:
thanks this almost helped me.
now when I open Mixplorer then I see SD card/TWRP folder, but still not Backup folder.
But when I go trough /root/data/media/0/TWRP/ then I can see Backups/05c847******/my backup.
can I run some other command in terminal to activate SD card/TWRP location also? ( this location should be /root/storage/emulated/0/TWRP....or.... /root/storage/emulated/legasy/TWRP).
This didnt helped me, I just give up and wait. I dont like if something don't work properly.
Click to expand...
Click to collapse
It should fix it.

rootSU said:
It should fix it.
Click to expand...
Click to collapse
To I leave this "*", end of this :::restorecon -FR /data/media/0/* :::: or do I add TWRP instead? If so, then I know what I did wrong

You leave the star

ok.. then I did everything correctly. after that I manage to see TWRP folder and inside this same 0 bit BACKUP folder.

Mairo said:
ok.. then I did everything correctly. after that I manage to see TWRP folder and inside this same 0 bit BACKUP folder.
Click to expand...
Click to collapse
Not sure what you're saying. Screenshot?

rootSU said:
Not sure what you're saying. Screenshot?
Click to expand...
Click to collapse
I try tomorrow again, I made a clean install and I have stock right now. ( I flashtomorrow twrp 2.8.1.0 ( 2.8.2.0 seems to be buggy right now), then supersu2.40 and then try " su (enter) restorecon -FR /data/media/0/*" again and let You know.

rootSU said:
Not sure what you're saying. Screenshot?
Click to expand...
Click to collapse
Hi. So I flashed TWRP 2.8.1.0, then flashed superSU 2.40. Then run in Terminal this su restorecon -FR /data/media/0/* command. Then I rebooted in recovery (twrp) and made a nandroid backup.
Then I rebooted and opened my file manager MiXplorer. Under SD I see TWRP foledr but inside this there is unknown BACKUP file (location: /storage/emulated/0/TWRP/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"
}
But when I go /data/media/0/TWRP/Backup then I see this file
problem is that Windows sees /storage/emulated/0/TWRP location and I can´t get access to this backup file.

You need to delete the unknown backups file then run the command. If that still gives you issues, do a titanium backup, nandroid backup, move the nandroid backup anywhere on your sdcard using a root explorer, copy the data back to your computer and factory reset including wiping sdcard / storage... Maybe even flash factory userdata.img using fastboot.
Then boot into your wiped device, go through initial setup and copy your sdcard contents back and put your nandroid in the correct place. Restore it.

rootSU said:
You need to delete the unknown backups file then run the command. If that still gives you issues, do a titanium backup, nandroid backup, move the nandroid backup anywhere on your sdcard using a root explorer, copy the data back to your computer and factory reset including wiping sdcard / storage... Maybe even flash factory userdata.img using fastboot.
Then boot into your wiped device, go through initial setup and copy your sdcard contents back and put your nandroid in the correct place. Restore it.
Click to expand...
Click to collapse
I ran this command before I made a nandroid backup. And I tried delete this unkonown backup file and now I can't see under /root any files ( No Items ).
I had wiped sd card, userdata. I made flashall.bat with factory image.
I had almost same problem with 5.0 and then this LRX21O-permissive-boot file helped me? are this bootimage same as 5.0.1?
EDIT: Soo strage..
I flashed francos r69 kernel and then I went in to recovery and I restored everything from this backup what I made to testing this problem. And now looks like everything is working. I see now TWRP folder and inside backup file and I also see now files under /root. ( now after restore with stock boot/kernel and no problems ).
looks like somehow flashing francos kernel fixed my problem.
EDIT2: after restoring sms with titanium I can't see again any files under /root folder. But everything is ok with this TWRP folder under sdcard/twrp.

[RECOVERY][ROOT][TWRP-3.2.1] Vernee M5

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.

[ROM][BETA] OFFICIAL PIE from ASUS

I am not responsible if you brick your device.
UPDATE BETA PIE ROM
Direct link Download- https://drive.google.com/uc?id=1_r6zxR34q5aN72SPhAjMLkV4GxQcD4ff&export=download
Flash procedure for pie- https://www.asuswebstorage.com/navigate/a/#/s/A9A029F390A34806BED2A412E194C44D4
For BL unlocked phones
Recommended PBRP
PBRP has function to fix the encryption after flashing the ROM. You may choose to flash decrypt.zip for your own satisfaction.
PBRP worked like a charm for me.
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Stock FULL ROM OREO 8.1
Stock Recovery & TWRP Flash-able
You have to flash full ROM if magisk is installed. Take backup & be very careful if device get encrypted after installing the ROM. (Flash decryption file- https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/mod-decrypt-data-t3787311 )
* Use 7zip/WinRAR- Extract / Open Archive by right clicking the firmware zip and go to > META-INF > com > google > android
*open updater-script with a note editor
* Remove all the lines above the code
ui_print("Target: Android/sdm660_64/sdm660_64:X.X.X/XXXX/XX.20XX.XXXX.XXX-20XXXXXX:user/release-keys");
*Save it/rezip the firmware and copy it to sdcard
*Wipe System, data, cache / format DATA.
*Flash the ROM
Official ROM link- https://www.asus.com/Phone/ZenFone-Max-Pro-M2/HelpDesk_BIOS/
One click Download - https://dlcdnets.asus.com/pub/ASUS/...995.844210030.1548823414-323285766.1546595187

so after installing latest 186 ROM continue installing decrypt.zip right?

rycroot96 said:
so after installing latest 186 ROM continue installing decrypt.zip right?
Click to expand...
Click to collapse
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.

Ajeyvm said:
when i had installed December update (unlocked bootloader & magisk installed) i flashed the new rom, installed decrypt.zip yet the phone got encrypted on boot. Later i formatted data and flashed decrypt.zip and the phone booted normally.
Its kind of two way procedure. Try it. There is nothing wrong in experiment unless you haven't taken backup.
I'll flash as soon as i go home & let you know the status.
Click to expand...
Click to collapse
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro

rycroot96 said:
but when encrypted twrp doesn't disappear right? ok I am waiting I haven't updated since ubl + magisk. what is meant by twrp backup right? I have a system backup and booted. thanks a lot for the info bro
Click to expand...
Click to collapse
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.

Ajeyvm said:
backup means your personal data, apps, contacts, internal storage.
TWRP wont be gone after flashing. The phone works fine even after its encrypted. You need to flash decrypt.zip to get internal storage access in TWRP . And for overall smoothness of the device.
Click to expand...
Click to collapse
thank you very much for the info

Guys ... Use PBRP Recovery.. It is based on TWRP...
It automatically patches forced encryption, after flashing the firmware file...
But just to make sure flash decrypt.zip too ...

So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
{
"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"
}

watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
and my nandroid backup that I just make is on internal storage... so now it's already encrypted(or it isn't?) and no longer be able to use...
Is there any way I can decrypt back my phone?
my custom recovery/twrp encrypted as well
I got my nandroid backup few days ago on my computer
Click to expand...
Click to collapse
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
watatara.102 said:
So I did really dumb error... I flashed OTA(edited updater-script), then flashed decrypt.zip and flashed Magisk-v18.0.zip(this is what I shouldn't do)... and now my phone is encrypted
Click to expand...
Click to collapse
I did exactly the same... But using PBRP recovery... Faced no issue at all...

Tyakrish said:
I don't think there is a way to decrypt your phone without losing data...
Best way is restore from your nandroid backup...
I did exactly the same... But using PBRP recovery... Faced no issue at all...
Click to expand...
Click to collapse
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?

error displayed 7 in twrp.
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution

shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Do not unzip the file.
Right click on the file, open archive. Edit the updater script. Save it. Better to use 7Zip.

watatara.102 said:
uh, the one that is encrypted is on /data I'm right?
my internal storage/internal SD which is on /data/media is not encrypted right? then I still can copy my NANDroid backup?
Click to expand...
Click to collapse
I am not sure exactly, which partitions are encrypted. But yes I think internal storage on /data/media is not encrypted...
But if you open TWRP then you will get a message to decrypt your device... DONT do this ! It will wipe your internal storage too, even if it is not encrypted...
If you want to copy your nandroid backup, then boot up your ROM and then transfer files using MTP to your computer..
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
shivrajmalani said:
When edit the script and rezip firmware then go to twrp then error 7 displayed that the zip file is crupted.so get me solution
Click to expand...
Click to collapse
Did you use WinRAR ? Do one thing...
After extracting zip, and editing the script, go to the root of your firmware folder, select all files then add to archive. Select archive format as zip and keep the lowest compression possible...
While flashing, disable zip verification. This should work... Otherwise try the method by @Ajeyvm

I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT

watatara.102 said:
I got this weird bug and it's will keep creating new log everytime reboot
here log file https://pastebin.com/wXHvcbDT
Click to expand...
Click to collapse
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Whenever i restart my phone i get that bug report. I clear it & use the device as usual. Evrything else is working fine. No need to revert back unless u r facing some major issue.

Zahirpro2 said:
i think im the only one getting for this bug......lets rollback old version haha...i see asus official website....that they have rollback the latest version
Click to expand...
Click to collapse
Oh so its not just me then, good to know

It looks good.
Edit, someone posted a review - https://youtu.be/_wli8M-71yI

Someone should really post a mirror of the official link

Official link is down does anyone has any other mirror link?

Database Info

welcome