Hi! I have a question... How i can relock the bootloader of ze500kl? I use the unofficial unlock, i never use the unlock app for ze500kl.
There is a method for do this?
Thanks in anvance
I am italian.. i can't speak english... Sorry...
Flash this .zip file on TWRP and flash stock recovery on fastboot
*Mod edit: attachment is removed. Please do not provide false solution.
This script below only does a print job, nothing related to relock, I suppose.
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print "Relock Bootloader..."
dd if=/dev/block/bootdevice/by-name/abootbak of=/dev/block/bootdevice/by-name/aboot
ui_print "Done!"
Click to expand...
Click to collapse
Thanks
Does this work even when you use the official bootloader unlocker from Asus?
EDIT: the answer is yes.
Related
I just had to unroot my transformer so I could RMA it (it didn't want to charge anymore) and I noticed that a lot of the actions could be scripted so it would be quicker and people couldn't screw the process up since it's automated.
I based my script off of [GUIDE] Official [unroot] guide here
Code:
#!/bin/bash
echo "Script by Brando56894 from XDA Developers"
directory=`pwd`
echo "Checking for necessary files...."
if [[ -e blob && EP101_SDUPDATE.zip ]]
then
echo "The necessary files are present, continuing process"
else
echo "One or more of the necessary files is missing."
echo "Would you like me to get the files for you? (y or n)"
read answer
if [[ $answer == 'y' ]]
then
wget http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
unzip -n UpdateLauncher_US_epad_user_8239.zip
cd ASUS/Update
unzip US_epad-user-8.2.3.9.zip
mv blob $directory
mv US_epad-user-8.2.3.9.zip $directory/EP101_SDUPDATE.zip
else
read -p "Please acquire the needed files. Press enter to exit"
exit
fi
fi
echo
adb devices
echo
read -p "If device is listed, press enter to continue unrooting"
adb push blob /data/local/
adb push EP101_SDUPDATE.zip /Removable/MicroSD/
adb shell dd if=/data/local/blob of=/dev/block/mmcblk0p4
adb reboot recovery
echo "It should now be flashing the stock update, unrooting the TF in the process"
echo
read -p "Press enter to exit"
exit
This is for 3.2 ?
It worked for me on 3.2 but I believe it should work for any version since it wipes everything out by reflashing the blob via nvflash. Make sure you have everything backed up to your sdcard because it wipes everything, including the internal memory.
This would also work if you were, for example, on 3.2 and wanted to go back to 3.1, wouldn't it?
Edit. Do you have the filenames to be downloaded for the WW version?
hi,
By mistake I flash a i9500 recovery on a 9505 and it installed (see picture) and erased my EFS.
I flash a stock with spit, then replaced the EFS (which I had saved on the PC), but each reboot EFS disappears! and the image returns.
Each solution??? I do not know what to do
Alan-B said:
hi,
By mistake I flash a i9500 recovery on a 9505 and it installed (see picture) and erased my EFS.
I flash a stock with spit, then replaced the EFS (which I had saved on the PC), but each reboot EFS disappears! and the image returns.
Each solution??? I do not know what to do
Click to expand...
Click to collapse
you must be rooted, type the following commands in terminal emulator:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
samersh72 said:
you must be rooted, type the following commands in terminal emulator:
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
Hi,
Thanks
I'll test
But t'is Flash had to add items to the root? but what to delete?
Alan-B said:
Hi,
Thanks
I'll test
But t'is Flash had to add items to the root? but what to delete?
Click to expand...
Click to collapse
rm >> will remove old "keystr" file (if existed, responsible of power menu and lockscreen) and old "factorymode" (responsible of this yellow window)
echo >> will make new two mentioned files with a "on" in it
chown >> will change file owner and group information of these two files to the right one.
chmod 744 >> will set the right permission for the two files rwxr--r--
reboot :good:
you can also use "adb shell" to execute those commands.
samersh72 said:
rm >> will remove old "keystr" file (if existed, responsible of power menu and lockscreen) and old "factorymode" (responsible of this yellow window)
echo >> will make new two mentioned files with a "on" in it
chown >> will change file owner and group information of these two files to the right one.
chmod 744 >> will set the right permission for the two files rwxr--r--
reboot :good:
you can also use "adb shell" to execute those commands.
Click to expand...
Click to collapse
Sorry but the command does not pass error file read-only '
How to use ADB Shell? never used!
NB:
I do not understand why if I replace the EFS it fades to reboot?
And delete any file to remove this yellow page (which directory and file?)
Sorry but this is not easy!
Alan-B said:
Sorry but the command does not pass error file read-only '
How to use ADB Shell? never used!
NB:
I do not understand why if I replace the EFS it fades to reboot?
And delete any file to remove this yellow page (which directory and file?)
Sorry but this is not easy!
Click to expand...
Click to collapse
be sure you have busybox installed
hmmm you need to mount efs folder as write
with root explorer (enable mount in its setting) long press on efs folder and choose permission and tell me what is the permission and if you can set it to: owner: rwx group: rwx others: r-x
samersh72 said:
be sure you have busybox installed
hmmm you need to mount efs folder as write
with root explorer (enable mount in its setting) long press on efs folder and choose permission and tell me what is the permission and if you can set it to: owner: rwx group: rwx others: r-x
Click to expand...
Click to collapse
Ok is solved...
Re Hi,
My EFS is a copy pasted on the PC, is there a solution for the flash via a zip? in a command line?
Or create a tar. To restore
please help me
please help me[/QUOTE]
i have the same , yellow screen , and NO power menu
what too do ?
su
rm /efs/FactoryApp/keystr (NOT FOUND)
rm /efs/FactoryApp/factorymode (NOT FOUND)
echo -n ON >> /efs/FactoryApp/keystr (No Such File Or Directory)
echo -n ON >> /efs/FactoryApp/factorymode (No Such File Or Directory)
chown 1000.1000 /efs/FactoryApp/keystr (NOT FOUND)
chown 1000.1000 /efs/FactoryApp/factorymode (NOT FOUND)
chmod 0744 /efs/FactoryApp/keystr (NOT FOUND)
chmod 0744 /efs/FactoryApp/factorymode (No Such File Or Directory)
reboot
Please Help me ??
-=Ghostface=- said:
please help me
i have the same , yellow screen , and NO power menu
what too do ?
su
rm /efs/FactoryApp/keystr (NOT FOUND)
rm /efs/FactoryApp/factorymode (NOT FOUND)
echo -n ON >> /efs/FactoryApp/keystr (No Such File Or Directory)
echo -n ON >> /efs/FactoryApp/factorymode (No Such File Or Directory)
chown 1000.1000 /efs/FactoryApp/keystr (NOT FOUND)
chown 1000.1000 /efs/FactoryApp/factorymode (NOT FOUND)
chmod 744 /efs/FactoryApp/keystr (NOT FOUND)
chmod 744 /efs/FactoryApp/factorymode (No Such File Or Directory)
reboot
Please Help me ??
Click to expand...
Click to collapse
if you have the I9505 variant, do this with terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
for I9500:
Code:
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
then do the previous posted line commands
What about s3 code?
samersh72 said:
if you have the I9505 variant, do this with terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
for I9500:
Code:
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
then do the previous posted line commands
Click to expand...
Click to collapse
same problem i am having,, what is code for s3 I9300 ?
Please help me..
m.htc said:
same problem i am having,, what is code for s3 I9300 ?
Please help me..
Click to expand...
Click to collapse
for S3 I9300 efs is in block 3 (like I9500)
Can't open error
samersh72 said:
for S3 I9300 efs is in block 3 (like I9500)
Click to expand...
Click to collapse
can't open '/dev/block/mmcb1k0p3' : no such file or directory error..
What to do ?
m.htc said:
can't open '/dev/block/mmcb1k0p3' : no such file or directory error..
What to do ?
Click to expand...
Click to collapse
It is not b1k but blk (l like lemon)
Sent from my Galaxy Nexus using xda premium
ya did same later
samersh72 said:
It is not b1k but blk (l like lemon)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
still error,, see attached image...
m.htc said:
still error,, see attached image...
Click to expand...
Click to collapse
see here, it may help http://forum.gsmhosting.com/vbb/f777/how-fix-samsung-gt-i9300-yellow-text-overlay-factory-mode-1660813/
I'm with 9505 internation HK unlocked handset, and i mis flash recovery without making EFS folder backup. Now i'm in factory mode with yellow text and no lock screen and power menu. Try several ways from other thread, seem this following thread is quite similar problem as mine http://forum.xda-developers.com/showthread.php?t=2395210 but i cant solve my problem with the solution in the thread.
su
rm /efs/FactoryApp/keystr (no such file or directory)
rm /efs/FactoryApp/factorymode (no such file or directory)
echo -n ON >> /efs/FactoryApp/keystr (no such file or directory)
echo -n ON >> /efs/FactoryApp/factorymode (no such file or directory)
chown 1000.1000 /efs/FactoryApp/keystr (usage: chown <user>[:group] <file1> [file2] ...)
chown 1000.1000 /efs/FactoryApp/factorymode (usage: chown <user>[:group] <file1> [file2] ...)
chmod 0744 /efs/FactoryApp/keystr (usage: chmod [OPTION] <MODE> <FILE> -R, --recursive change files and directories recursively --help display this help and exit)
chmod 0744 /efs/FactoryApp/factorymode (usage: chmod [OPTION] <MODE> <FILE> -R, --recursive change files and directories recursively --help display this help and exit)
reboot
I think the way samersh72 method is come close to fix mine but i dont know what i'm wrong in this please see if can help on it
I'm on rooted Stock German firmware phone with Super Su BusyBox installed PhilZ recovery and Mounted efs folder and set persission as samersh72 mentioned
Anybody help, Samsung said i need to replace new mainboard. But i think it should have the way to solve this from you guys
already solved my problem thank you
tanipat said:
already solved my problem thank you
Click to expand...
Click to collapse
can you tell how did you solve it for others benefit
samersh72 said:
can you tell how did you solve it for others benefit
Click to expand...
Click to collapse
Surety, because actually i'm one by one benefit from few post as well (you too, Big thanks to you as well). But i'm new here and not much knowledge about these things much and nor developer, just try to make it most understandable as possible per below
As i said i cant mount EFS folder so i need to know first where is it contains, you need root, busy box and android terminal installed.
1.check folder efs by enter into recover and try mount your EFS, it should be fail. Then you check the LOG and you will see the folder that make it error note it because you need to use it
2. reboot and enter android terminal and type below (in my case i note the folder that error is "mmcblk0p10" without quote (credited to this post http://forum.xda-developers.com/showthread.php?t=2389962)
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
Once the device reboot then
At this stage your EFS folder will not gonna be empty no more. I do copy the whole folder to the safe place (i think this is not required but i did)
3. enter in to android terminal again and type (Credited from you samersh72)
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
And then the magic done it's wok and my device reboot with no more factory mode and yellow tex, as well my power menu and lock screen comes back. Thank you all you guys and XDA that revive my device for good. I would ever never do anything rather than backup my EFS folder right after everytime. I spent 1 month on this and finally get it done. Thank you again you guys. If any help needed from anyone on this i'm glad to help as much as i can.
tanipat said:
And then the magic done it's wok and my device reboot with no more factory mode and yellow tex, as well my power menu and lock screen comes back. Thank you all you guys and XDA that revive my device for good. I would ever never do anything rather than backup my EFS folder right after everytime. I spent 1 month on this and finally get it done. Thank you again you guys. If any help needed from anyone on this i'm glad to help as much as i can.
Click to expand...
Click to collapse
glad that you fixed your issue, please add [solved] to the title of this thread :good:
samersh72 said:
glad that you fixed your issue, please add [solved] to the title of this thread :good:
Click to expand...
Click to collapse
I dont know how to add "solve":crying:
tanipat said:
I dont know how to add "solve":crying:
Click to expand...
Click to collapse
just press on edit in the first post, then add "solved" in his title where you typed : [Q] Please help misflash Recovery, in factory mode with empty EFS file and no backup
How to fix this factory mode problem.
please see the attached image & help me.
Mobile model - Samsung Galaxy S4 I9505
sumonfd said:
How to fix this factory mode problem.
please see the attached image & help me.
Mobile model - Samsung Galaxy S4 I9505
Click to expand...
Click to collapse
in terminal emulator, tyoe
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
with search button you could find the answer...
samersh72 said:
in terminal emulator, tyoe
Code:
su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
with search button you could find the answer...
Click to expand...
Click to collapse
I tried with that but not working. Please help me.
sumonfd said:
I tried with that but not working. Please help me.
Click to expand...
Click to collapse
what it gave you? i think you need to mount the partition before:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
samersh72 said:
what it gave you? i think you need to mount the partition before:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
Click to expand...
Click to collapse
Showing mke2fs not found after giving the below command
mke2fs /dev/block/mmcblk0p10
sumonfd said:
Showing mke2fs not found after giving the below command
mke2fs /dev/block/mmcblk0p10
Click to expand...
Click to collapse
P.S. you must be rooted
samersh72 said:
P.S. you must be rooted
Click to expand...
Click to collapse
my phone is already rooted & also installed root browser MORE OVER IT'S IMEI CORRUPTED & DON'T HAVE WARRANTY.
i Have z3x box & NS pro. please guide me.
Open "Root Explorer" App
efs/FactoryApp/
Open "factorymode" file with text editor
Change OFF to ON
Reboot
Mr.W0lf said:
Open "Root Explorer" App
efs/FactoryApp/
Open "factorymode" file with text editor
Change OFF to ON
Reboot
Click to expand...
Click to collapse
already tried this but not working.
sumonfd said:
already tried this but not working.
Click to expand...
Click to collapse
Tried to do the same for "keystr" file?
Mr.W0lf said:
Tried to do the same for "keystr" file?
Click to expand...
Click to collapse
both file are edited to "ON" but was not working then delete these file & restart after that edited then reboot, now working.
But IMEI problem, please advise me how to fix that.
Hello,
I have a verizon note 3 with mi9
I rooted via kingo and tried to back up my efs via:
http://forum.xda-developers.com/showthread.php?t=2447342
basically I forgot to install busybox, the process did not work, the script modified my phone's files but i'm not exactly sure which ones
for example in the phone directory i dont have files in /efs (http://www.note2forum.com/forum/gal...dden-menu-dialer-verizon-galaxy-note-3-a.html)
i wanted to enable the Hidden Menu (Dialer) on Verizon Galaxy Note 3.
So I have unrooted via Kingo app now. And I did a factory reset. I still do not see any files in the /efs folder on the phone
I want to know what I should do to fix the EFS files.
My phone still works to make calls and have internet, but I'm afraid to do anything further.
Thank you in advanced
You can't see efs without a root browser. Unlikely there ever was an issue.
Sent from my SM-N900V using xda app-developers app
akellar said:
You can't see efs without a root browser. Unlikely there ever was an issue.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Thanks, okay I rerooted the phone. I am using ES file explorer and I can see alot of files in the folder efs/ now. I'm guessing they are all there since my phone seems to still work.
anyways below is what the script I was using was doing, maybe someone can explain whats going on, and confirm stuff didn't get deleted. I have no idea whats going on there.
:BACKUP
CLS
@ECHO *****************************************
@ECHO * BACKUP EFS *
@ECHO *****************************************
CHOICE /C YN /M "WARNING: Do you wish to Continue? (This will make EFS BACKUP)"
IF ERRORLEVEL 2 GOTO MENU
@ECHO --- STARTING ----
@ECHO --- WAITING FOR DEVICE
bin\adb wait-for-device
@ECHO --- Backup efs image ---
bin\adb shell "echo | getprop > /sdcard/getprop.txt"
bin\adb pull /storage/sdcard0/getprop.txt
bin\adb shell "echo | getprop ril.product_code > /sdcard/version.txt ; getprop gsm.version.baseband >> /sdcard/version.txt ; getprop ril.serialnumber >> /sdcard/version.txt"
bin\adb pull /sdcard/version.txt
setlocal enabledelayedexpansion
for /f "tokens=*" %%a in (version.txt) do set "var=!var!%%a_"
echo %var%
bin\adb shell su -c "make_ext4fs -s -l 20M /sdcard/efs.img /efs"
bin\adb shell su -c "dd if=dev/block/mmcblk0p3 of=/sdcard/%var%EFS.raw.img"
bin\adb shell su -c "busybox tar cZvf /sdcard/%var%EFS.tar.gz /efs"
bin\adb pull /sdcard/efs.img
bin\adb pull /sdcard/%var%EFS.raw.img
bin\adb pull /sdcard/%var%EFS.tar.gz
bin\tar.exe -c efs.img >> %var%EFS.tar
bin\md5sum.exe -t %var%EFS.tar >> %var%EFS.tar 2>nul
REN %var%EFS.tar %var%EFS.tar.md5
bin\7za.exe a %var%EFS.zip %var%EFS.tar.md5 %var%EFS.raw.img %var%EFS.tar.gz getprop.txt
del *.img *.txt *.gz *.md5
@ECHO -
@ECHO -
@ECHO Finished. Output file is %var%EFS BACKUP
) ELSE ( @ECHO "ERROR: PACKAGING does not exist" )
pause
goto MENU