Database Develop

[Q] Can't remove install-recovery.sh

Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.

Xenobio said:
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Click to expand...
Click to collapse
Can you describe in detail what you did?

Method 1: command line
1. Booted into recovery
2. Installed GOT Open Recovery
3. Immediately after that (without rebooting, as it would have caused the stock recovery to be reinstalled) went into console and typed "rm -f /system/etc/install-recovery.sh"
4. Nothing happens, the command line # symbol just appears on the next line
5. Went back to main menu and rebooted, stock recovery came back
Method 2: script
1. Downloaded the "Disable_recovery_check_by_OTA.zip" file from the page mentioned previously
2. Unzipped and copied the .sh file to my sdcard in the OpenRecovery scripts folder
3. Step 1 and 2 like above
4. Went to the "Miscellaneous > Run script" menu
5. Ran "Disable_recovery_check_by_OTA.sh"
6. It says "-- Shell script..." then the path and filename of the script, then it says "Done" on the next line
7. Went back to main menu and rebooted, stock recovery came back
I also tried something after removing the install-recovery.sh...if I reboot into recovery (press and hold X immediately after selecting "Reboot" from the GOT main menu), I get Open Recovery back. But, if I reboot into Android and then turn it off and then boot into recovery, it's the stock recovery.

But every time you can use openrecovery right? If so, that's normal behavior. We can't replace recovery.

did you try to put the script into the init folder? I'm not sure anymore if its that one, but one of these folders contains a bunch of script that will be executed on boot up.. it worked for me (once) before i bricked my phone.. lol

Xenobio said:
Hello all,
I'm having a problem with the stock recovery. I have tried installing G.O.T. Open Recovery 2.01 and the install is OK, and I can do stuff in the menus, but every time I reboot, the stock recovery comes back. I followed the instructions by nadlabak on how to remove the script that reinstalls the stock recovery (android.doshaska.net/rootable, sorry the forum isn't allowing me to post the actual link as I'm a new user), but it doesn't work. There is no error message, just nothing happens. Can someone help? Thanks.
Click to expand...
Click to collapse
I am sure there is a way. OpenRecovery from G.O.T is slightly differrent, try to use the one from nadlabak and see what happens....?

[Q] Restoring apps gone wrong - now rebooting constantly? plz help

Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot... [Bricked?]
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help

djkoch said:
Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot...
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
Click to expand...
Click to collapse
Try to hard reset, turn off your phone press volume - and power.

Thanks for the response... When I press power+volume down, the "unpacking box with android person" appears for a 20 seconds or so... the reboots and I'm back to rebooting constantly
When I try pressing volume down and home key/returnkey I can get in to S/W update mode, but I cant get the ADB to work?
Other suggestions?

That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.

gensplejs said:
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
Click to expand...
Click to collapse
It wasnt a problem when deleting them, and the phone was alright... it was when restoring through ADB it went wrong... I need a suggestion to get it fixed not an "I-told-you-so"

Yeah... sorry... i was kinda an ass.
But sadly I'm all out of ideas.
Maybe if we had a service manual (not user manual)
Sent from my LG-P990 using XDA Premium App

Can you connect to phone by adb?
You need to clear dalvik cache.

Hi Doc
No... unfortunately I cant get ADB to work....
I can get into S/W update mode, but ADB doesnt work. I can get the Factory reset to begin too, but it just gets into the reboot circle again.
If there was just a way to get into ADB mode I could push every single file again
Damn... I hope it isn't bricked for good

If HR doesn't work. Just return for warrenty.
Cause if it reboots that a corrupted boot.img
Try to see if you can get alist of apps installed on phone.
If superuser.apk is not in there, return it for warrenty.

In one of the reboots I think I had a glimse of a connection thru ADB acouple of times. I had approx. 10 seconds before rebooting again.
Did a list... and guess I saw a dir called "root" but didnt have time to get into the system/app directory...
If we can't find a solution I think I'll try to return the phone and hope for a new one without any question asked

Have you tried putting it in sw update mode and running the LG update tool?
http://www.lg.com/dk/support/mc-support/mobile-phone-support.jsp?countryCd=dk
Might do the trick

Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."

djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
There in no way to restore you phone now because we don't have any tools that's work with optimus 2x.
Bring it back to retailer and say that phone is just not booting and you want a replacement.

Edit: Well... discount the advice below for the time being... I've found myself in the same position and the commands below don't work.
My phone is also now useless...
I replied to your thread over at MoDoCo, and although the thread has gone off track it does have Paul's attention.
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
Oh dear.
I tend to agree, whilst it will be recoverable it could be very time consuming.
A factory reset will wipe cache and dalvik cache, so that's not your problem.
Neither is boot.img your problem, that will be intact.
However, if you can't get a console (via adb or terminal) you're in a difficult position.
Try issuing the 'stop' command in your brief adb window to see if you can preserve the shell.
Code:
$ su
# stop
If you can then try and mount /system rw
If you can do that then you can possibly self recover... by carefully and selectively adding files to /system/app/, rebooting and trying, again and again.

[Q] Tough time going back to stock

I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.

I am not sure if it would make a difference in your situation but I do everything for my phone on an x86 system. I have had issues with LG and Samsung phones in the past when trying things on an x64 computer.

ifixgse said:
I've been running CM 11 for a little more than a month and have been really enjoying it. So, I have no idea why I decided to download the MythTools and revert back to stock At&t. Doing so, I messed something up on my phone.
To start, I'm using Windows 7 64bit and when selecting option 1 (install ADB-fastboot-apkTools) I get the new cmd window that states "please select install button after new window is opened press any key to continue...." when I press any key the cmd window would just close. Hoping it would help, I then chose option 6 to update my Motorola drivers. When my browser window opened I got the ADB installer window and clicked install. It seemed to have installed fine. I then updated my moto drivers. Thinking I was all set I went for option 2 to flash the stock firmware which I had put in the firmware folder. With my phone in fastboot I started the process and it failed. Reading through the cmd prompts I had noticed it said something like 'you selected 2- instal cwm.img cannot load cwm.img' . I unplugged my phone and tried to restart it and it was stuck on the bootloader screen. I then restarted into recovery and my PhilZ recovery did start up. However it displays "E: could not mount /data to setup /data/media path!" . I was still able to go through the process of a clean re-install of CM 11 but am stuck on the startup splash screen for CM.
I definitely got myself in way too deep and am clueless on how to fix this. Would someone mind instructing me on what to try next? Many thanks in advance.
Click to expand...
Click to collapse
you said you are stuck on startup splash meaning bootloop? if it is you should try again with rsd lite.
else you may lose all your data in the memory but do a format media/data and sdcard, so that it can mount /data, it worked for me. then format system mount everyting and do a fresh install of any rom you can sideload or just have it in the sdcard.

I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.

ifixgse said:
I'm pretty sure I am doing something wrong with MythTools. When I select option 2 in the tool to install stock firmware the following happens,
- asks for fimware folder example and I select "N"
- asks if firmware files are finished copying.. I press enter and continue
-then it says "the system cannot find the path specified
the system cannot find the path specified
the system cannot find the path specified
'7z' is not recognized as an internal or external command
operable program or batch file
Are you ready to flash stock fimware...
at this point i stupidly hit enter and that was it with my phone. I'm guessing the tool could not locate the firmware .xml file for extracting and I have no idea why. The compressed folder is IN the firmware folder.
One other question with Mythtools, when installing the tools what path do you want them installed in? I did them in the same file the Myth tools are in.
Click to expand...
Click to collapse
Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock. Any questions don't hesitate to ask.
If this helps you hit that thanks button!

I made a mistake in the flashing Cyanogen mode htc one x+

Hallo…I used the nice:
HOX+ Tutorial for Unlocking, Rooting & installing a custom ROM [BEGINNERS FRIENDLY ]
-Installing HTC's Drivers … was ok
-The use of the AndroidSDK\platform-tools … was ok
-Unlocking the Bootloader .. was ok
-Recovery installation and a backup …. was ok
-install the root the SuperSU.zip ….
i could see the app after installing … hope it was ok
--By mistake I tried to install: cm-13.0-20160916-SNAPSHOT-ZNH5YAO1AN-find7.zip
After selecting the ROM.zip it hangs, stuck or so. I don’t exactly remember.
Now it starts only in boodloader mode.
I read and search a lot to find solution, but I am a German and it is difficult for me to find the right English words to search.
I tried the restore in recovery Mode. It is wiping, formatting and restoring successfully
But nothing changed. It is still only starting in boodloader mode.
I try to copy the rom: cm-11-20160815-NIGHTLY-enrc2b.zip via PC-terminal “adb sideload.
Sometimes it shows on the terminal window: Devise offline
Next it shows: more than one device/emulator.
And sometimes the terminal window it shows 100% compleate,but on the mobile it shows failed
I tried factory rest too. But still the same.
Can someone please point me to a link to find solution to get my mobile starting again so that I can flash the cyanogenMode ?
Thanks Heinz
3 Pics of the boodleader Mode

Google Apps disappeared after rooting

Hello,
I followed a tutorial yesterday to get root access to get rid of some of the pre-installed apps on my newly bought P8 Lite 2017.
I made sure the operation would work on my phone before starting : PRA-LX1 (C432B170), EMUI 5.0, Android 7.0
I supposedly managed to get root access, but somehow without me doing anything for it, all of the Google Apps (including Play Store) have totally disappeared within the phone.
I'll describe below my yesterday's doings. To precise, I'm a novice in this and never rooted any phone before.
- Downloaded ADB, Fastboot & Drivers (adb-setup-1.4.3.exe) and installed it.
Got an adb directory created in my C:\ afterwards containing adb.exe, fastboot.exe and two AdbWin .dll .
- Unlocked bootloader doing so : plugged my phone with USB, opened cmd (win+r), went to my C:\adb folder (cd command) and typed adb reboot bootloader; the phone rebooted in bootloader mode. Typed then fastboot oem unlock [code_ive_been_given_on_huawei_website]. Operation was successful.
- Downloaded TWRP (twrp-3.1.1-2-v1-prague.img), renamed it recovery.img and put it in my C:\adb directory.
Opened the cmd (win+r) and rebooted into bootloader mode (adb reboot bootloader). (NB : I tried using the PowerShell cmd but it said "adb isn't recognized as command [...]" "The command adb is nowhere to be found but exists in current spot, PowerShell doesn't load commands from current spot [...]")
Once my phone rebooted in bootloader, I typed in the cmd prompt : fastboot flash recovery recovery.img and operation was successful (two lines of "OKAY" or something similar iirc).
- Downloaded SuperSU (v2.79-201612051815-EMUI5.0.zip), rebooted my phone to put it in.
To mention it, since bootloader unlock the first screen I see is "your device has been unlocked and can't be trusted" with three operations "1. Power up to boot, 2. Vol up to enter erecovery, 3. After 5sec it'll boot automatically". Getting this screen is normal to my understanding.
I moved SuperSU.zip into an external SD once rebooted and plugged via USB.
Then I entered TWRP Recovery Menu, Install-ed the SuperSU.zip, and then Wipe-d Dalvik/Cache and rebooted afterwards.
Phone rebooted once, twice, and ended up booting normally.
Google Apps disappeared since then (no appearance in Settings>Apps), this including Chrome (which was seemingly the sole browser) and PlayStore (rest of Google Apps being what I wanted to erase).
I'm fairly sure that those disappeared after I unlocked the bootloader, but can't be certain of it (operations to get root access took me some time and reboots and the Chrome widget on the main screen has been gone since then iirc).
NB : I see the SuperSU app and when I go to Settings>Google Play "All my applications - See all my applications on the shop" and click on that, nothing happens (I assume it should redirect me to something like the SuperSU dev PlayStore page with his/her developed apps).
I've tried to find out what to do reading some forum posts and the sole post I found that's alike is the following : https://forum.xda-developers.com/mate-9/help/missing-playstore-unlocking-bootloader-t3551269/page2, which end up with a user telling to factory reset, but I read on other posts (not necessarily on xda) that may/might brick and as a novice I would like to get clues on what to do next before going all in on it and bricking it.
Note, I stupidly didn't Backup before doing the operations to get root ... I didn't think of it and the tutorial I followed forgot to mention it.
Thanks in advance for the time spent reading and the help given.

Use the unbrick part of the rooting tutorial. You will get latest stock firmware
---------- Post added at 23:20 ---------- Previous post was at 23:20 ----------
Aftereards root with magisk v14 or supersu

After unlocking the bootloader you must do a factory reset before installing twrp and super su..
Unroot then try to factory reset then re-root you device..
hope it works