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+
Related
HII GUYS THIS THREAD IS ALL ABOUT LG P690:-
FIRST
/////////////////////////////ROOTING:-/////////////////////////////
Code:
http://forum.xda-developers.com/showthread.php?p=21348926
2)Custom Recovery for LG Optimus Net - Clockwork 5.0.2.7
DOWNLOAD ALL THESE FILES:-REQUIREMENTSFLASH_IMAGE
RECOVERY IMAGE
ADB RUNNING
http://developer.android.com/sdk/index.html
The Recovery can be installed as follow:
•Download recovery.img from the link attachment
•IMPORTANT: Check MD5SUM - This is to ensure that during the download / copy the file is not corrupted
•Copy recovery.img to the SD
•download Flash_image, unzip and copy it to SD
Now you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Code:
$ adb shell
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image> /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Note: the command
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.
WILL GIVE YOU SOME ERROR IGNORE IT
If all goes well, the menu with a cheerful hat ClockworkMod background confirms that the boot recovery occurred in CW.
Also ignore the error below: "E: bad boot message" is not a real error.
The recovery functionality is simple:
- The volume keys to scroll
- The back button to go back
- The power button to select a menu item.
If you have problems, you can select Advanced / Error Reporting. This will generate a log into SD (recovery.log). You can use it to understand the problem.
/////////////////////////////
[HOWTO] Flash original firmware on P690
http://forum.xda-developers.com/showthread.php?t=1483192
[HOWTO] Flash DOWNLOAD firmware on P690
http://forum.xda-developers.com/showthread.php?t=1483180
/////////////////////////////
///////////////////////////////
[ROM] DarDroidXD_0.3 [LGP690]
http://forum.xda-developers.com/showthread.php?t=1483206
//////////////////////////////
This guide works 100% , just used it now waiting for custom recovery to download.
Majestic36 said:
This guide works 100% , just used it now waiting for custom recovery to download.
Click to expand...
Click to collapse
Doesnt work for me, recovery just freezes at the LG screen
Need to understand what is recovery and custom installation
May I know what is Custom Recovery for LG Optimus Net - Clockwork 5.0.2.7 and what it do?
and what is installing cyanogenmod 7.0 is it a custom rom and is it better then stock rom?
Hi guys,
I have problem. I rooted my LG P690 and installed CWM bootloader. During installing custom ROM my phone bricked and rebooted after LG initial picture. I was able to enter only RECOVERY MODE by pressing PWR+BACKARROW+VOL_UP. But that was all, I couldn't also repair phone through HDZ_FW_UPD.exe , because problem with USB drivers. I tried everything, but without success. But I was able to connect to phone via ADB commands, downloaded update.zip, added it near fastboot.exe file, run fastboot and install that update.zip. I removed SD card to other phone, connected, uploaded some CyanogenMod 9 and moved SD card back to LG P690. Now I was able to enter BOOTLOADER (BUT I DON'T REMEMBER COMBINATION OF BUTTONS DURING SWITCHING PHONE !!!), and installed CyanogenMod9. Everything looks OK, but after rebbot and entering new Android OS my touch screen isn't working. I don't know why, but I think that problem is in that CyanogenMod9 version - it doesn't recognize touching screen. It reacts to pressing Vol UP/DOWN buttons (setting volume), pressing BACK button or long pressing PWR button. But that's all. I can turn off the phone by remobing battery. When it's ON and I connect it via USB, I cannot use ADB.exe or FASTBOOT.exe commands because PC donesn't recognise device
So now the question - how to enter bootloader during power ON sequence? I tried all combinations:
- pressing and holding PWR+VOL UP
- PWR+VOL DOWN
- quick pressing of VOL UP
- quick pressing VOL DOWN
- pressing PWR+BACK+VOL UP
- pressing.....and so on and so on
I don't know why I cannot access bootloader becasue before I did it without any problem....Can you please write me detailed "butto n sequence" for entering bootloader on LG P690 Optimus Net? Or am I LOL?
Thank you very much
Rado
SOLVED -> entering bootloader works with pressing HOME+VOL_DOWN+PWR_ON
I have used CyanagenMod 10.0 STABLE ROM without any issue for several days until this Morning where my Google Play kept giving error "insufficient storage space" for some reason. I read from several discussions abt this as none of them fix my problem so I decided to do followings:
Using ClockModRecovery 6.0.2.3:
1. wipe data/ factory reset
2. wipe cache
3. wipe dalvik cache
test: still got same problem
4. wipe data from the last option where there are four icons shown (Recovery, Android, USB/fast boot/ Wipe Data icons)
5. access recovery mode again and do followings
6. format system success
7. format /staging - success
8. format /data - ERROR mounting /data!
9 reboot device and still stuck at booting (THE CyangenMod logo kept showing)
10. access recovery mode again -> mount /data and /emmc FAIL
When I click the USB icon duriing initial boot, my PC (Win 7) could not detect my tablet device but when I chose Recovery mode, my PC was able to detect the device with some errors. The folder structure is shown below.
H:\Downloads\Android\TF700 Rooting>adb shell
~ # ls
ls
btmac init sys
cache init.rc system
data proc tmp
default.prop res ueventd.cardhu.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
etc sdcard
fstab.cardhu staging
When I access the system folder, there is nothing there/ I tried using below config to flash the CM10.0 ROM again and wish to fix my problem:
H:\TF700 Rooting>adb push update.zip /root/update.zip
1333 KB/s (169361362 bytes in 124.049s)
It seemed the file had been transferred but the issue remains.
I have two questions:
1. Is there anyone who knows how to enable USB debugging from clockmode recovery? I might not enabled this earlier. I s there a way to check from ADB command?
2. Any suggestion to help me recover my OS? The bad thing is that I backup my ROM to internal EMMC and now it is not mountable for some reason
Further the ADB outputs are below:
H:\Downloads\Android\TF700 Rooting>adb devices
List of devices attached
015d2XDXXXXXXXXXX device -> serialno is hidden purposely
H:\Downloads\Android\TF700 Rooting>adb get-state
device
H:\Downloads\Android\TF700 Rooting>adb get-serialno
015d2XDXXXXXXXXXX -> hidden purposely
H:\Downloads\Android\TF700 Rooting>adb root
H:\Downloads\Android\TF700 Rooting>adb shell
[email protected]:/ $ su
su
Permission denied
1|[email protected]:/ $ superuser
superuser
/system/bin/sh: superuser: not found
127|[email protected]:/ $
I hope I did not brick my tablet since I am still able to view the root folders and access the clockMod Recovery consistently. please correct me if I am wrong "whew".
PLZ HELP..
Problem Fixed. I managed to fixed my own problme by flashing with Stock ROM.
Managed to fix my own problem eventually by Flashing to Stock ROM.
Hopefully this helps whoever gets same problem as mine.
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!!!
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.
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.