Related
I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
I wouldn't completely advise removing it - maybe rename it so it's still there, but just hidden, in case you have to return to it with WebOS Doctor or anything. Especially since it's the only way to go about using ACMEUninstaller / ACMEInstaller2 / WebOS Doctor / Recovery images and the like.
Then again, I just did some looking in the /boot, and can't see anything about that recovery, unless it's tied into the WebOS one.
UnderZone7 said:
I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
Click to expand...
Click to collapse
I wouldn't remove webOS, not only for the reasons ve6ay stated above, but because I find webOS very useful. It is a useful and elegant os, battery life is much better, and that's the beauty of the TP, the ability to dual boot.
The nice thing is, if you remove the Moboot entry for WebOS, you don't actually remove WebOS - you just remove the option to boot from it. BUT you also can bring it back with just a quick terminal command (I noticed this during my poke-around of /boot as I stated earlier).
Besides, if you want to skip it entirely, you can create two file in your /boot directory directly from your CM install.
I used Terminal Emulator, but you can from Root Explorer, too. Browse to /boot, mount it (hit the mount r/w button up top), hit Menu => Create New File. Call it "moboot.timeout" (without quotes). Long-press it, click Open With, choose Text Editor. In there, as the only line there, type in your timeout - (if you want it to be always super-fast, chose 1), then hit enter, back, then save.
Second file to create is one called moboot.next - which basically says "On next reboot, always choose <selection>" To use this, again, Menu => Create New File => Long-press it => Open With => Text Editor. In here, type in CyanogenMod, hit enter, back, save, and then reboot. On reboot, you should automatically go straight into Android, no options to go anywhere else.
Or, if you can stomach booting into WebOS long enough, install Cyboot from Preware, and use it to make your changes to the timeout and default boot options. I just did this, and can tell you, if you do set Next to Android, and timeout to something abysmally small, you automatically will boot into Android, no choice of anything else.
Hope that helps you, mate.
You REALLY don't want to do this, as stated above if something goes terribly wrong it's the only way to use ACMEInstaller and stuff. Even WebOS takes not much space and pretty cool, so i choose to leave it, but recovery is a must..
I've had a Droid 3 for a little under a year now. For the past few months I was having an 'issue' where the phone would not vibrate when I got an SMS message. Apparently this is a known issue caused by installing a non-stock SMS app from the app-store. I took it to the Verizon store and the guy put in a request for a replacement phone. He knew I'd rooted it and just said to make sure I unroot it, uninstall the bootloader, and factory reset before sending it in. I did all 3 things however the reset didn't reset my custom boot animation so I figured I'd activate the phone real quick, reroot, change that, and unroot. I started the activation process and I get to the "Add Accounts" screen, added my Google account, and hit Done. It asks about location services, I hit "Next" and then com.motorola.setup crashes and I have to force close. If I hit the Home button it takes me right back to the "add accounts" screen and I'm stuck in that infinite loop. I can still receive texts and reply to them from the notifications menu, I can send and receive phone calls with voice commands, I can access the browser, but that's about it. I cannot get to the home screen and I cannot open the settings 'app'.
I brought it back to the Verizon store and they were baffled, told me that Verizon would probably charge me full retail for the replacement if I sent this once back, so I sent back the replacement phone and am stuck with this one now.
I think what caused this is that I had the 'Bloat Freezer' app installed and I had frozen a bunch of the default Verizon apps. I didn't unfreeze them before the factory reset and I have a feeling that's what's causing the issue. I had the idea to re-root the phone and install Bloat Freezer again from the Play store but the Play store isn't recognizing my Droid 3 anymore.
Any suggestions?
Factory reset is a deceiving term. It resets it to factory user data (none) and settings. It doesn't restore the system. What you need is an SBF to flash the entire phone to factory software, overwriting all partitions. First though, you must find which system you had. Since you didn't recently get this phone, did you accept an OTA update within the last month or so? If so, head over to the Dev area and download the stickied SBF file to return you from .906 to .890. If not, there is an SBF in the General area called Quick Unbrick or something like that.
http://www.youtube.com/watch?v=pcne9tFtBxY
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
If you've had your D3 for over a year and have not updated to .906, then you'll need .890. The .906 update is fairly recent (a couple months old I think?) so if you don't explicitly remember taking it, use .890.
Side note, check the rom you used before this happened. Check if it's based on .906 or .890.
Sent from my DROID3 using xda premium
JDiPierro said:
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
Click to expand...
Click to collapse
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
Anyway, if you did, you can install the Android SDK's adb app and, from a command prompt, you can try to type the following command (with the phone on and cabled to the computer)
adb shell cat /system/build.prop | grep "version"
This should show you a bunch of lines, one of which will be "ro.build.version.full". The system version follows that text on the line - I have last month's OTA, so mine is Blur_Version.5.7.906.XT862.Verizon.en.US (so I have 5.7.906).
You can most easily get adb (for Windows) with instructions from here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
After you get those files unzipped in c:\android, you can start a command prompt by hitting start, type "cmd" and enter in the search box - this will start a black command prompt window. From there, enter the command cd \android and then enter the adb command I put up above.
I'm not sure it will work, but it should.
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
doogald said:
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
...
adb shell cat /system/build.prop | grep "version"
Click to expand...
Click to collapse
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
eww245 said:
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
Click to expand...
Click to collapse
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
Click to expand...
Click to collapse
Needs to be I. Charge only mode. On stock rom I believe its called none
Sent from my XT860 using xda premium
JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
Click to expand...
Click to collapse
You can grep: because you are running a shell command, I believe it is running on the phone, not on the windows computer.
(The grep is not all that critical, though, as I believe the version number line is one of the last lines displayed by that command.)
You can do an:
adb devices
before you run the shell command to verify that the computer and phone are communicating; it should return a line of characters that represents your phone, if it is connected.
I switch to unother SIM card and i get "SIM network unlock PIN".
I search the forums and i read:
http://forum.xda-developers.com/showthread.php?t=1064978&highlight=sim+network+unlock+pin
http://forum.xda-developers.com/showthread.php?t=1846451&highlight=sim+network+unlock+pin
GalaxSim Unlock says "Device model not supported at this time"
http://forum.xda-developers.com/showthread.php?t=1715149
I'm rooted with Busybox and in EFS folder I don't have "nv_data.bin"
should I try on stock :
make sure no sim card inside the phone yet, if there is, just take it out
Dial *#197328640#
Main Menu > [1] UMTS > [1] Debug Screen > [8] Phone Control > [6] Network Lock > Options [3]Perso SHA256 OFF > (after choosing this option, wait about 30 seconds, then go back one step by pressing the Menu button then select Back, now you are in [6] Network Lock then choose [4] NW Lock NV Data INITIALLIZ ..... wait for a minute then reboot your phone...
there won't be any confirmation just reboot your phone, put your sim back in, wait for about 10-30 seconds for your phone to pick up the network and kabaaam it is unlocked, the timing is important btw
Baseband I8190XXALK6, 4.1.1
Please help!
unfortunately doesn;t work for me. Says NOT ACTIVE... and phone is still sim locked. Any workaround for this?
ktcomgrup said:
I switch to unother SIM card and i get "SIM network unlock PIN".
I search the forums and i read:
http://forum.xda-developers.com/showthread.php?t=1064978&highlight=sim+network+unlock+pin
http://forum.xda-developers.com/showthread.php?t=1846451&highlight=sim+network+unlock+pin
GalaxSim Unlock says "Device model not supported at this time"
http://forum.xda-developers.com/showthread.php?t=1715149
I'm rooted with Busybox and in EFS folder I don't have "nv_data.bin"
should I try on stock :
make sure no sim card inside the phone yet, if there is, just take it out
Dial *#197328640#
Main Menu > [1] UMTS > [1] Debug Screen > [8] Phone Control > [6] Network Lock > Options [3]Perso SHA256 OFF > (after choosing this option, wait about 30 seconds, then go back one step by pressing the Menu button then select Back, now you are in [6] Network Lock then choose [4] NW Lock NV Data INITIALLIZ ..... wait for a minute then reboot your phone...
there won't be any confirmation just reboot your phone, put your sim back in, wait for about 10-30 seconds for your phone to pick up the network and kabaaam it is unlocked, the timing is important btw
Baseband I8190XXALK6, 4.1.1
Please help!
Click to expand...
Click to collapse
see http://forum.xda-developers.com/showpost.php?p=64512412&postcount=85
or read here:
Do this:
radool said:
Because the OP didn't post too many details, most people couldn't perform all the operations through to the end...
Here goes:
Dial *#197328640#, it will take you to the service menu
Choose UMTS, or, if UMTS is missing, choose [1]Debug Screen directly
Choose [8] Phone Control
Choose [6] Network Lock
You will see "Not Active", you need to press the Settings/Options soft button (button on the left), and you will get a list of options
From the list choose the third [3] line, and enter the following text: SHA256 OFF
After 10-20 seconds you will see a returned value, I had 6
I saw most people stopped at step 5 above, before getting this far because they haven't pressed the left Options button to enable them to enter SHA256 OFF command.
Unfortunately, I couldn't figure where to enter the NW lock NV Data INITIALLIZ text... but maybe someone else can now pick it from here.
Click to expand...
Click to collapse
and then:
I typed the "NW Local NV Data INITIALIZE" exactly the way I typed your "SHA256 OFF". After that, I waited a minute and rebooted phone.
So once again: do the SHA256 OFF and then instead of SHA256 OFF, type "NW Local NV Data INITIALIZE", wait a minute and reboot.
See linked post to thank people who worked this out.
http://forum.xda-developers.com/showpost.php?p=64512412&postcount=85
Sister says she was driving and phone suddenly factory reset (android recovery icon with text saying erasing, or something along those lines). After the process completes you are greeted with the setup screen to select your language and continue setup. Took a while to get past this since this process somehow also turned on voice assistant. If anyone else experiences this, you need to use two fingers to scroll and tap the item you want, then double tap it to select. (Ex: when you get to a keyboard, to type the letter "a" you need to tap a to highlight it, then double tap "a" to actually send the letter to the textbox. Powered off and jumped into recovery menu which showed a system update progress bar then displayed the following:
LMY47X.G920TUVU3DOJ7
....
(Recovery Menu Options)
....
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I found a post elsewhere about CSC which indicated it had to do with regional codes which will identify the firmware to issue to the device. The post also said after updating the code your device will reset. So, any thoughts on why this would randomly happen? Phone lock screen was secure so accidental taps/presses seems unlikely. I wasn't present at the time of the incident so I cant be certain of each step that took place before it randomly factory reset.
NOTE: Device is fully stock, never rooted or attempted to root. The phone is up an running so this is not a post requesting help for that, just to share experience with others that may run into this issue and possibly find out what caused it.
Hello,
I would like to disable the Dual boot menu option of Teclast x98 plus, do you knwo how to do it?
or at least change the timing out option from 10s to 1s?
I have tried though the standard windows booth option but it is not the same booth menu...
thanks
I own a Teclast X80 Pro, problaby it's the same option. From what I've read, there's a little box in the upper left corner you can tick when you start the device and got the option to choose betwen Windows and Android. Remove the tick and only one OS should boot (but don't know which one). Under Android settings (scroll to the end) there's a Boot option where you can choose Dual OS or not (and a third option). Hope this helps a bit.
metalaxi said:
I own a Teclast X80 Pro, problaby it's the same option. From what I've read, there's a little box in the upper left corner you can tick when you start the device and got the option to choose betwen Windows and Android. Remove the tick and only one OS should boot (but don't know which one). Under Android settings (scroll to the end) there's a Boot option where you can choose Dual OS or not (and a third option). Hope this helps a bit.
Click to expand...
Click to collapse
thanks,
unfortunately I do not have the little box when I start the device., and I have already removed android... what I need to remove now is the selection menu at the start.
Any other ideas?
thanks
tuleggi said:
thanks,
unfortunately I do not have the little box when I start the device., and I have already removed android... what I need to remove now is the selection menu at the start.
Any other ideas?
thanks
Click to expand...
Click to collapse
Maybe change the boot sequence in UEFI / BIOS? There are some options on my device like Android, Windows Boot Manager and so on.