Database Users

[REQ] Need someone to check something for me on a STOCK Vibrant

Anyone out there willing to help me out?
I just someone to run this command with their phone hooked up, USB Debugging ENABLED:
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
This will output a text file in whichever directory you run the command from, that will list the hardware capabilities of the phone for me - this would help me IMMENSELY from a development standpoint!
Check out the text file - zero personal / private information will be in there!
Thanks!

I have a samsung that is ROOT, has the gps-fix for ROOT users, the custom recovery image.
Is that good for you?

abcdavidefg said:
I have a samsung that is ROOT, has the gps-fix for ROOT users, the custom recovery image.
Is that good for you?
Click to expand...
Click to collapse
That would be a start - I'd like to find one that is non-root, though!

Doward said:
That would be a start - I'd like to find one that is non-root, though!
Click to expand...
Click to collapse
http://www.4shared.com/document/7F2UoKt-/class_structure_VIBRANT.html
This is from an un-rooted Vibrant bone stock Rom just after flashing it with ODIN!

mp2ning said:
http://www.4shared.com/document/7F2UoKt-/class_structure_VIBRANT.html
This is from an un-rooted Vibrant bone stock Rom just after flashing it with ODIN!
Click to expand...
Click to collapse
Great, thank you!
*edit*
Oh wow... oddball structure there!!
Can I get these as well?
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
and
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt

adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
http://www.4shared.com/document/ouZxt2TF/_2__platform_structure_VIBRANT.html
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
http://www.4shared.com/document/Vnvz-oEQ/virtual_structure_VIBRANT.html
I had already rooted after I posted the first file so I unrooted to get these last 2 files in case it matters!

mp2ning said:
adb shell ls -l -R /sys/devices/platform > platform_structure_VIBRANT.txt
http://www.4shared.com/document/ouZxt2TF/_2__platform_structure_VIBRANT.html
adb shell ls -l -R /sys/devices/virtual > virtual_structure_VIBRANT.txt
http://www.4shared.com/document/Vnvz-oEQ/virtual_structure_VIBRANT.html
I had already rooted after I posted the first file so I unrooted to get these last 2 files in case it matters!
Click to expand...
Click to collapse
LOL awesome, thanks!!

I connect my phone, open the cmd and then I type this
cd\
cd AndroidSDK\tools\
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
I dont get error, but i dont get any text.
I am just trying to help

abcdavidefg said:
I connect my phone, open the cmd and then I type this
cd\
cd AndroidSDK\tools\
adb shell ls -l -R /sys/class > class_structure_VIBRANT.txt
I dont get error, but i dont get any text.
I am just trying to help
Click to expand...
Click to collapse
What do you get?
If the file completes, then you should be able to type in 'dir' and see class_structure_VIBRANT.txt in there

Doward said:
What do you get?
If the file completes, then you should be able to type in 'dir' and see class_structure_VIBRANT.txt in there
Click to expand...
Click to collapse
I attach the files that you asked for it

[Q] Understanding GladRoot Root script for 1.26-1.83

I was looking at the code for GladRoot (http://forum.xda-developers.com/showthread.php?t=1016060) and I had a couple of questions I was hoping someone could answer.
First of all, does anyone have the code for psneuter?
Secondly, if the goal of rooting is to Superuser.apk, why is temporary root access necessary? I've never used adb before this, but isn't the point that developers can easily do things like install applications using it? The superuser apk might grant super user access after it's installed, but before that it's just like any other apk.
I'd appreciate it if someone could answer these questions. Thanks.

Anyone want to help me out? Doesn't seem like too hard of a question...

Id take a look at What is root access on google. It sounds like you have no idea about the basics. There is a ton of info for beginners even on this site. If I misunderstood you I apologize but your question would only leave me to believe you need to learn the basics. Good luck
Sent using the phone with the biggest balls....Atrix 4G

Gladroot doesn't give temporary root access either unless it changed.
Sent using the phone with the biggest balls....Atrix 4G

dupreeks said:
Id take a look at What is root access on google. It sounds like you have no idea about the basics. There is a ton of info for beginners even on this site. If I misunderstood you I apologize but your question would only leave me to believe you need to learn the basics. Good luck
Sent using the phone with the biggest balls....Atrix 4G
Click to expand...
Click to collapse
Well I'm definitely a beginner, but not that beginner. I'll show you what I'm talking about:
Code:
rem If we do, since we need to run several commands as root, use psneuter to
rem temporarily root the device.
echo.
echo Obtaining temporary root access...
%~dp0adb push %~dp0bin\psneuter /tmp/psneuter > NUL 2>&1
if not errorlevel 0 set message=Unable to send psneuter. && goto abort
set retval=
for /f "tokens=*" %%l in ('%~dp0adb.exe shell "/bin/chmod 6755 /tmp/psneuter > /dev/null 2>&1 && echo PASS"') do set retval=%%l
if "%retval%" neq "PASS" set message=Unable to chmod psneuter. && goto abort
set retval=
for /f "tokens=*" %%l in ('%~dp0adb.exe shell "/tmp/psneuter > /dev/null 2>&1"') do set retval=%%l
if "%retval%" neq "" set message=Unable to execute psneuter. && goto abort
echo.
echo Waiting for root access to kick in...
timeout /t 5 /nobreak > NUL 2>&1
So what I said was correct. GladRoot definitely get's temp root access. After it does that, it changes some settings and installs superuser.apk:
Code:
rem Remount the /system read/write.
echo.
echo Mounting /system as read/write...
%~dp0adb.exe shell mount -o rw,remount /dev/block/mmcblk0p12 /system > NUL 2>&1
rem Install sqlite3 for additional system changes required later in the script.
rem This is silent because it shouldn't interfere with anything even if it's
rem not used.
%~dp0adb.exe push %~dp0bin\sqlite3 /system/bin > NUL 2>&1
%~dp0adb.exe shell chmod 6755 /system/bin/sqlite3 > NUL 2>&1
echo.
echo Ready to root.
echo.
pause
rem Let's root!
rem Check for duplicate busybox installation and remove it.
echo.
echo Cleaning up SuperOneClick mess...
%~dp0adb.exe shell "find /system/xbin -type l | xargs rm" > NUL 2>&1
%~dp0adb.exe shell rm /system/xbin/busybox > NUL 2>&1
rem Copy su over and set permissions for use.
echo.
echo Rooting your device ...
%~dp0adb.exe push %~dp0bin\su /system/bin > NUL 2>&1
%~dp0adb.exe shell chmod 6755 /system/bin/su > NUL 2>&1
rem Install the Superuser app for allowing other apps root access.
echo.
echo Installing Superuser app...
%~dp0adb.exe install -r %~dp0bin\Superuser.apk > NUL 2>&1
echo.
echo Root complete.
echo.
So again my question is why do you need temp root access to install superuser.apk?

Temp root access is needed because superuser is installed in system/apps in the system partition. Without root a user does not have read write permissions in the system partition. This means a user cannot uninstall apps or install apps with out root permission. Temp access allows a script or person to modify the system partition, in this case it gives apps access to permanent root. The source code for psneuter is here.

on21st said:
Temp root access is needed because superuser is installed in system/apps in the system partition. Without root a user does not have read write permissions in the system partition. This means a user cannot uninstall apps or install apps with out root permission. Temp access allows a script or person to modify the system partition, in this case it gives apps access to permanent root. The source code for psneuter is here.
Click to expand...
Click to collapse
Yeah that pretty much sums it up. Gladroot was and still is my method of root. I wish I could unlock the boot loader with my current 1.8.3 setup I have and not lose anything. If anyone has a solution I would really appreciate it. I like my phone how it is but want to be able to make nand backups basically. I am not huge on CM7 and it doesn't seem like there are many stable roms for the Atrix right now.

You can there should be a pudding for 1.8.3. I remember using it. It wipes data and allows you to unlock the boot loader if you choose. HERE
Just choose the correct sbf to download and then follow instructions in thread.

Need nudge in right direction. Un-rooting Droid X

Guys, need a nudge in right direction.
EDIT: I am running stock ROM
I have a rooted DroidX. Will be getting RAZR MAXX next month and want to sell my DX. So i want to take it back to stock to sell.
I have searched but couldn't find anything close to my situation.
Any ideas would be appreciated or can I just do a factory reset?
Here are the specifics.......
Had DX running .605.
I rooted using this video http://www.youtube.com/watch?v=Pxks-o2cd7E&feature=plcp
This is the version of the script I used.. I still have the script but there is not an "unroot" option in it.
Code:
echo ***************************************************************************
echo * *
echo * DROID 3 Easy Root script v7 *
echo * *
echo ***************************************************************************
echo *
I can post entire code if needed.
Here is where I am running into my specific problem.
When .621 OTA update was coming down, I installed OTA rootkeeper.
I took the OTA update and was able to retain root and be on .621
Only other mods done were supercharger (which I reversed to stock) and a mod to get wifi hotspot going.
The hotspot mod I did was a complicated one. Downloaded some program from Motorola and went in and edited some values in a database in the phone.
Where can I go to figure out how to reverse this back to stock so I can sell it in good faith?
Unfortunately I was extremely new to all of this when I rooted it and didn't think about going back.
I have a full Titanium Backup of the system after root and before .621 update.
Heck, here is the entire rooting code if it helps.
Code:
@echo off
cls
adb kill-server > NUL
COLOR B0
TITLE DROID 3 Easy Root Script
cls
echo ***************************************************************************
echo * *
echo * DROID 3 Easy Root script v7 *
echo * *
echo ***************************************************************************
echo *
echo * Please make sure you meet these pre-requisites:
echo *
echo * (a) install the correct driver
echo * (b) turn on USB debugging (on your phone under Settings -^> Applications)
echo * (c) plug in your phone and set your USB mode to 'charging only'
echo *
echo * Note: your phone will reboot twice during this procedure. This is normal.
echo *
echo * READY TO ROOT YOUR DROID 3 WHEN YOU ARE!
echo *
COLOR E0
pause
echo *
echo * Waiting for your phone to be connected...
echo *
adb wait-for-device > NUL
COLOR B0
echo * Running exploit [part 1 of 3]...
adb kill-server > NUL
adb shell rm /data/local/12m.bak > NUL
adb shell mv /data/local/12m /data/local/12m.bak > NUL
adb shell ln -s /data /data/local/12m
adb reboot
echo *
echo * Rebooting the phone... please wait.
adb kill-server > NUL
COLOR E0
adb wait-for-device > NUL
adb wait-for-device > NUL
COLOR B0
echo *
echo * Running exploit [part 2 of 3]...
adb shell rm /data/local/12m
adb shell mv /data/local/12m.bak /data/local/12m
adb shell rm /data/local.prop.bak > NUL
adb shell mv /data/local.prop /data/local.prop.bak
adb shell echo "ro.sys.atvc_allow_netmon_usb=0" ^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_netmon_ih=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_res_core=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_res_panic=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_all_adb=1" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_all_core=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_efem=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_bp_log=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_ap_mot_log=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_gki_log=0" ^>^> /data/local.prop
adb reboot
echo *
echo * Rebooting the phone... please wait.
adb kill-server > NUL
COLOR E0
adb wait-for-device > NUL
adb wait-for-device > NUL
COLOR B0
echo *
echo * Running exploit [part 3 of 3]...
adb remount
adb push busybox /system/xbin/busybox
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
adb shell chown system.system /data
echo *
echo * ALL DONE! YOUR PHONE SHOULD BE ROOTED!
echo *
echo ******************************************************************************
echo.
echo You may now close this window...
echo.
COLOR A0
adb kill-server > NUL
pause
TITLE Command Prompt
COLOR 07

Just simply try a factory reset
Sent from my shiny new white LOCKED SCH-I535 using xda app-developers app

If that didn't work just sbf back to stock. That will work for sure and gives the buyer the new phone experience
Sent from my SCH-I535 using xda app-developers app

dbett4 said:
Just simply try a factory reset
Sent from my shiny new white LOCKED SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Lol didnt mean to thank you but oh well...
Any ways lol to OP you can factory reset a hundred times and you still won't remove root.
Why remove root anyways you'll sell the phone faster and save someone the hassle of rooting again
As for the regs who don't know that root is... meh. Again won't hurt the phone in any way.
You will have to sbf back to what ever firmware you want. Afaik it's the only way to remove root. I'm not experienced enough for manual removal, and sbf is so simple and hassle free...when done right.
Easy to f-up if not lol.
Gl
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

I just checked ebay completed autions. Rooted phones do sell fast and are selling for more!! Great. Thanks for the tip.
If I do a factory reset, then it will go back to stock except it will leave root?? The main thing I was worried about was with the OTA upgrade.
If all else fails I will sbf with version .621 (afaik you can't go back further once you have .621 OTA) then re-root.

I did the same I had a deal and bought two DROIDX and rooted both then upgraded but kept root same way you did but my brother got a new phone so I went to market and downloaded an app called ginger unroot and bam full unroot. I even downloaded su and a root checker but no root. Hope this helps
Sent from my DROIDX using xda premium

Instead of SBF'ing I just did a factory reset. And it did in fact keep root.
Thanks guys.

Here's what ya do:
Factory reset
You will still have root.
Inform prospective buyer about rootkeeper.
Instruct them exactly what to do (don't make this part of your auction, just offer the advice after the sale;
make sure they know:
ota update =by by root)
Once buyer sets up their Google act and installs rootkeeper buyr can now ota with out worries of loosing root.
I just sold my dx and did this exact same thing.
Buyer was more than happy.
Hope that helps and glws
Sent from my DROID X2 using Tapatalk 2

How much did you get for it?
Sent from my Kindle Fire using xda app-developers app

[Solved] Help error flash recovery !!

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/

[Solved] Please help misflash Recovery, factorymode with empty EFS file and no backup

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