My Device IS IN The Factory Mode And I Cant Exit From It - Galaxy Note 10.1 Q&A, Help & Troubleshooting

hello guyz i am having a big problem that is my device in in factory mode and there isnt power menu and there isnot a lock screen i tried a lot of solutions but the big problem that my efs folder is empty and i havent any backup cause my device was bootlop on samsung screen so i flashed a ics rom via odin and all the backups i have it to jb i tried to restore a one and its the same please help me I tried To Flash A New frimware and the same

Search via Google >>> Note 10.1 factory mode xda

bilal.23 said:
hello guyz i am having a big problem that is my device in in factory mode and there isnt power menu and there isnot a lock screen i tried a lot of solutions but the big problem that my efs folder is empty and i havent any backup cause my device was bootlop on samsung screen so i flashed a ics rom via odin and all the backups i have it to jb i tried to restore a one and its the same please help me I tried To Flash A New frimware and the same
Click to expand...
Click to collapse
If you don`t have an efs backup, then unfortunately there is nothing you can do except sending it to a service center, happened to me almost 6 months ago, tried all options , nothing was successful, had to send it for repair.:crying:

bilal.23 said:
hello guyz i am having a big problem that is my device in in factory mode and there isnt power menu and there isnot a lock screen i tried a lot of solutions but the big problem that my efs folder is empty and i havent any backup cause my device was bootlop on samsung screen so i flashed a ics rom via odin and all the backups i have it to jb i tried to restore a one and its the same please help me I tried To Flash A New frimware and the same
Click to expand...
Click to collapse
Here is the exact solution for this problem which i have recently had!
You have to root your phone and install Terminal Emulator from Google Play.
Open terminal emulator and type as ;
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
You now should not see the that message anymore. Its because of an EFS corruption.
Hope it helps!!!

Related

note 2 clone

hi...i'm searching on how to fix booting problem on my note 2 clone??? i think i have brick my phone when i trying to chnage font using font installer....now it stuck on android logo...does anyone know how to fix the problem??? thanks in advance
Anyone??
Sent from my R800i using Tapatalk 2
Bump!!! Help plss...
Sent from my R800i using Tapatalk 2
spec
spec
Why did you post 4 times?
sent from my minecraft world
CasTTeLLo said:
hi...i'm searching on how to fix booting problem on my note 2 clone??? i think i have brick my phone when i trying to chnage font using font installer....now it stuck on android logo...does anyone know how to fix the problem??? thanks in advance
Click to expand...
Click to collapse
turn off your phone, press volume up +home key + Power on. you are on 3e screen. then "wipe data / factory reset" then reboot.
*Note: that this will format your phone to factory default. and delete all your data.
still not working
ronnylaborada said:
turn off your phone, press volume up +home key + Power on. you are on 3e screen. then "wipe data / factory reset" then reboot.
*Note: that this will format your phone to factory default. and delete all your data.
Click to expand...
Click to collapse
i try to enter recovery sytem but still no luck....still stuck @ android logo after reboot...
note2 clone
CasTTeLLo said:
i try to enter recovery sytem but still no luck....still stuck @ android logo after reboot...[/QUOTE
u have test to volume up hole+back button hole+power button hole...
Click to expand...
Click to collapse
I have same problem with my friends note 2 clone.. Can't fix yet... Bookmarking this page...
same problem
i have also the same problem, please help me if you get rid of it
CasTTeLLo said:
hi...i'm searching on how to fix booting problem on my note 2 clone??? i think i have brick my phone when i trying to chnage font using font installer....now it stuck on android logo...does anyone know how to fix the problem??? thanks in advance
Click to expand...
Click to collapse
try this service code :-
*#*#10086#*#*
if its ok let me know.
regards
If you have busybox installed on your android and adb shell on your pc try this script
Code:
echo " "
echo "Waiting for device..."
adb wait-for-device
echo " "
adb -d shell su -c "mount -o rw,remount /system"
adb -d shell su -c "ls /system/fonts"
adb -d shell su -c "mv /system/fonts/FONT_NAME.EXTENSION /system/fonts/NEW_FONT_NAME.EXTENSION"
The ls command lists the names of the fonts in /system/fonts directory and now try renaming them one by one using the script. You must replace "FONT_NAME.EXTENSION" with the one find after ls command. If after renaming the first file doesn't work run the script again with the following font name and so on.
Take out the battery and put it in and quickly hold the buttons that put you into stock recovery
Sent from my SGH-T959V using xda app-developers app

[Q] GS III Debrick Escapade

So, I mistakenly used Ez-Unlocker with 4.4.2 and bricked my GS III. Based on various posts found around here I was able to get it running again. However, no matter how many times I try to reset the phone, either through Odin or the Verizon repair utility, this is what I get:
[[http]] [[://]] www [[dot]] ledzilla [[dot]] us/images/Screenshot_2014-07-19-14-13-55.png
I've tried various methods I've found to resolve this, but the best I've managed was to delete a trio of apps from the phone with the name "Factory Mode" and "Factory Test", but all that accomplished was getting rid of the yellow text that persists across the home screen. I still got the the warning box at the bottom of the screen.
So, is there a way to completely fix this with the phone being on the latest firmware and OS?
Also, on a side note, I received a warranty replacement because I didn't realize it was EZ-Unlocker that caused the problem until I did it on the replacement, too. I was able to restore it back to working condition, too, and without the factory mode issue, except the same exact process caused the EFS data to get corrupted so now there's no IMEI. Here's a screen shot of the system data (there's no SIM card installed, so I don't know if that affects some of these values):
[[http]] [[://]] www [[dot]] ledzilla [[dot]] us/images/Screenshot_2014-07-19-19-37-44.png
Is there any way to fix this issue, too?
And sorry about the links, but I'm assuming most here would know why it's all chunked up like that.
I should also mention that in order to resolve the issue I have rooted using Towleroot, and I installed Superuser for, well, super user rights. In conjunction with this, I also accessed the phone using the ADB shell and entered the following:
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
I was able to confirm changes to the files, but it effected no change on the situation. The yellow text did not go away and the "Factory Mode" message still appeared at reboot and shut off the WiFi.

[Q] ADB SHELL CHMOD 644 ,nothing is working anymore...

Hello everybody
I needed to push a file to /system/app but since I was on stock rom & kernel, that didnt support adb root.
I needed to be able to push the backup file after restart but ADBD Insecure couldn't patch after restart.
my phone is optimus G E975 , fully stock 4.1.2
I found this command which could do the thing BUT :
adb shell
su
chmod 777 /system
since it didnt restore to default after restarted I tried to restore it myself(didn't work) with:
adb shell
su
chmod 644 /system
but after that every thing force stopped & after restart, phone can't boot anymore,just when want t start boot animation, it just cant & goes to recovery every time!
even Hard reset didnt work, but as stock recovery supports adb, I wish you guys can help me. but It seems adb shell gives permission denied(13) in recovery. please someone help...
Anyway am I able to flash in download mode????? (for the last solution)
any help to change that CHMOD to 777 in recovery or something else?
any help appreciated so much!
After using this command, it seems the /system directory became unreadable,
FIX: after flashing e975tot rom through LGNPST in DW mode, the phone booted up normally & problem fixed.

samsung J5 stuck in Custom recovery (twrp)

Hello
I am a newbie to the forum but I used to visit and check stuffs here in india
I own j5
Model : J500f
I rooted it with kingroot and then changed to su with steps given in one of a thread in xda
then for xposed I set my SElinux premmisive with terminal emulator with this code
Code:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "echo 0 > /sys/fs/selinux/enforce" >> /system/su.d/permissive.sh
chmod 755 > /system/su.d/permissive.sh
and it worked well tooo but after sometimes notification came
SElinux was disabled .unauthorised system changes
Click to expand...
Click to collapse
I clicked on it then it gone to the security area with one big red shield saying restart to revert changes I clicked it and then my phone restarted and then I am always booting imto recovery I tried restoring with my back up it was succesfull but it still boots into recovery, tested my buttons they are alsooo fine
please helppp meee
therikz2 said:
Hello
I am a newbie to the forum but I used to visit and check stuffs here in india
I own j5
Model : J500f
I rooted it with kingroot and then changed to su with steps given in one of a thread in xda
then for xposed I set my SElinux premmisive with terminal emulator with this code
and it worked well tooo but after sometimes notification came SElinux was disabled .unauthorised system changes I clicked on it then it gone to the security area with one big red shield saying restart to revert changes I clicked it and then my phone restarted and then I am always booting imto recovery I tried restoring with my back up it was succesfull but it still boots into recovery, tested my buttons they are alsooo fine
please helppp meee
Click to expand...
Click to collapse
Next time you'll need to delete security log agent apk in system/app.
Now to unbrick you'll have to reflash stock, go to sammobile and find your firmware there.
Thankk you alot i tried it and it worked
Sent from my SM-J500F using Tapatalk

Boot starting TWRP instead of System

I recently chose, through the internal options of the cell phone, to restore the factory mode. After performing the procedure, the cell phone restarted directly to the TWRP screen. It turns out that now it has a default boot for TWRP and not for the system. I can still access my system, just as it was before, if I used the Factory Mode option in Bootloader. But in Factory Mode the cell phone has some limitations, such as not working the cellular network.
To simplify:
Reboot -> TWRP
Bootloader -> Start System -> TWRP
Bootloader -> Factory Mode -> System in Factory Mode
Is there any way to restore the boot to start the system instead of starting TWRP? Is this a possible solution?
I'm using a custom ROM Ressurection Remix v5.8.5 - Android 7.1 for XT1225, if it is necessary to change some internal configuration by Factory Mode.
I tried the solution below, which tries to fool the system and quit Factory Mode, but FactoryApp does not exist in the list of system applications.
Code:
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
You need to install the latest modded TWRP from @bhb27.
https://androidfilehost.com/?w=files&flid=39562
Install, reboot twice, solved.
Other people have had that problem over the past year or so, and it's always because they are using older TWRP or "official" TWRP and not the latest @bhb27 modded TWRP.
Sent via open market LG US998 V30/V30+

Categories

Resources