Related
This will officially not work for 1.1
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox
Installs Button Savior
Installs Go Launcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
June 24, 2011 -
Removed: Multitouch Permission
Added: Modified framework.jar
June 22, 2011 - Fixed: Script not running at boot.
June 20, 2011 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch.
You must have enough intelligence to follow instructions.
Let's get started:
Download TouchNooter from here: touchnooter-1-6-24.zip
Linux: Unzip and use dd if=touchnooter-1-6-24.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
You should see the screen "Rooted Forever".
It will boot like normal and you should be asked to select a launcher now. (If not use Button Savior to go home. This will bring up the launcher chooser.)
That was the hard part, now to the simple stuff.
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from Go Launcher's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from "Extras".
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
Arnold Snarb - modified framework.jar
nemith - helping me figure out getting it to run at boot.
JesusFreke - For getting root.
MrMuffin - For the original Market Hack that we're using.
Currently Working On: TouchNooter 1.11.x
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
An .img file is being uploaded for TouchNooter 1.6.20 It'll do all the copy and edit stuff, the only thing it can't do is create an android ID.
In the "GappsAndMore" there was some keyboards which were from the NC it was just a raw pull from AN. This is more refined with things that could cause issues removed. (Like Keyboards, Framework.jars from the NC, etc.)
william1853 said:
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
Click to expand...
Click to collapse
I'd suggest a wipe and running TouchNooter... GappsAndMore had Keyboards and stuff in it and removed the stock keyboard =\
is a wipe in the nook touch holding down the power for 20 seconds?
No you need to do a complete wipe by triggering recovery, but I don't know how to trigger recovery yet.
oh well the perils of early adoption. I'll follow the thread with anticipation!
william1853 said:
oh well the perils of early adoption. I'll follow the thread with anticipation!
Click to expand...
Click to collapse
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Confirmed this works great. I'm going to find a fix for the calendar.
GabrialDestruir said:
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Click to expand...
Click to collapse
Recovery is holding the power button for 20+ seconds it will trigger recovery
xboxexpert said:
Recovery is holding the power button for 20+ seconds it will trigger recovery
Click to expand...
Click to collapse
Really? Is that from when it's off?
GabrialDestruir said:
Really? Is that from when it's off?
Click to expand...
Click to collapse
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
xboxexpert said:
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
Click to expand...
Click to collapse
I tried it and all I could get was it turning on and off
TouchNooter 1.6.20
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
MystaWright said:
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
Click to expand...
Click to collapse
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
GabrialDestruir said:
I tried it and all I could get was it turning on and off
Click to expand...
Click to collapse
Didn't work for me either. 8 interrupted boots did.
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
GabrialDestruir said:
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
Click to expand...
Click to collapse
Same problem here... tried to return EVERYTHING to stock too.
yugoliang said:
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
Click to expand...
Click to collapse
I did a reset of the device back to the out of the box experience, registered with my BN account, shut down and followed the directions to the letter. I had no luck at all. It just shows the Rooted Forever screen, then boots normally is if nothing happened.
Sorry Guys and Gals. Entirely my fault. It seems a combination of my own forgetfulness and bad scripting (I forgot proper codes and methods used in AN) caused this just to do nothing. I'm uploading a version as I'm typing this and will remove "BROKEN" from the title when it's up.
Still broken. init.rc isn't running it's script properly.
Script can be ran manually with:
Code:
adb shell sh /sdcard/nooter/tmp/scripts/Nooter
Will be working on getting it to trigger properly
So guys i just installed LBE Privacy guard it asked me for root permission and it automatically rebooted my phone it starts up fine then but whenever LBE launches (on boot) the phone starts looping again...what can i do?
Delete it very quickly before the next boot. And yes it isn't working on jb. Success!
The fix
Austin3161337 said:
So guys i just installed LBE Privacy guard it asked me for root permission and it automatically rebooted my phone it starts up fine then but whenever LBE launches (on boot) the phone starts looping again...what can i do?
Click to expand...
Click to collapse
Use TWRP recovery rather than cwm for its file manager.
In recovery, tap advanced -> file manager -> navigate to data/app.
Find the lbe entry (can't remember the exact title, but includes lbe in it) and delete it.
Reboot.
Breath a sigh of relief...
Twrp doesn't show files.
Download aroma file manager and push it to your phone. Then just use it as you would install any mod. It is a full fleshed file manager for recovery.
this is XXXDDDAAA
easy and safe way to remove any app that causes bootloop is to boot into safe mode. You don't need custom recovery or root to boot into that mode
1. Power the Galaxy Note off.
2. Press and hold the Power button to turn the device on.
3. Once you see the animation on the screen, continuously tap the Menu button. (Button with 3 lines below the screen)
promi said:
easy and safe way to remove any app that causes bootloop is to boot into safe mode. You don't need custom recovery or root to boot into that mode
1. Power the Galaxy Note off.
2. Press and hold the Power button to turn the device on.
3. Once you see the animation on the screen, continuously tap the Menu button. (Button with 3 lines below the screen)
Click to expand...
Click to collapse
Just had to force safemode from boot because of LBE. I suggest tapping the menu button repeatedly the second it starts up (before boot animation). I tried when I saw the animation and it didn't boot into safe mode.
I just had LBE cause my phone to crash loop constantly. By booting into safe mode, I was able to uninstall the app! Thanks to those above who helped us with this tip about how to boot into safe mode.
If you look at the Play Storage page for LBE, you will notice it's rating has really crashed, and it currently has over 1900 complaints regarding this issue...
https://play.google.com/store/apps/details?id=com.lbe.security.lite
The publisher of LBE is nowhere to be found and has not updated the app in over 16 months. I am guessing it has been abandoned.
I am just putting the following keywords here to help others find this page:
LBE privary guard crash loop fix
LBE privacy guard boot loop fix
fix for LBE crash
lbe boot loop
lbe crash loop
how to uninstall lbe privacy guard
I AM NOT RESPONSIBLE FOR ANYTHING NEGATIVE THAT HAPPENS TO YOUR PHONE!!
ALSO WORKS FOR T-MOBILE DART!!
Never Hurts to Thank or GIFT to all that help you!
NO PC NEEDED!!!!!!!!:highfive:
Necessary downloads from the Play Store
SuperUser or SuperSU -- One will work, the other won't -- [/COLOR][/SIZE] --A MUST HAVE for any rooted phone! Superuser/SuperSU is the app that manages what apps on your rooted device have access to su. Apps that are granted su have elevated permissions and can modify just about any part of the system. The app consists of two parts, Superuser.apk and the su binary.
Superuser.apk runs as any other app and gives you, the user, a place to see what apps you have allowed or denied, as well as view a log of what apps have used su when.
Link2SD-- DO NOT USE until rooted.--Link2SD is an application that makes it easy for Android 1.6+ users with root privileges on their phone to move applications to the SD card.
The idea behind is same with apps2sd scripts, linking applications to SD card's second partition but differs in two ways.
One, instead of linking /data/app folder (that means moving all applications), you can select applications that you want to move.
Two, it's an application which means has a user interface. You can manage your applications with few clicks.
It also provides native apps2sd features on Android 2.2 and higher. It can move any non-protected user apps to SD card (force move), with batch moving capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).
BusyBox--DO NOT USE until rooted. --A MUST HAVE for any rooted phone! Almost EVERY rooted applications needs BusyBox to perform their magic, if you have a rooted phone then you NEED BusyBox.
Pro version contains Backup feature (for safer installs), uninstall feature, Advance Smart install feature, the ability to hand pick the applets you want, safety check for missing applets on start, and better overall support. The pro version will receive more frequent updates than the free version will.
Root Checker (optional)--Checks for ROOT -- Use AFTER Installing a Superuser app.
BOOT-LOOP FIX
1.) Power off the phone by removing the battery.
2.) Replace battery.
3.) Boot into recovery by holding Volume DOWN and power button until the android with the triangle appears. This will appear AFTER the android that is by himself!! (about 30 seconds)
4.) Press the home button
5.) Navigate to the 3rd choice - " wipe data/factory reset". Select by pressing the menu button
6.) Navigate to YES and select by pressing the menu button.
7.) When the wipe is complete, navigate to and select - "reboot system", again with the menu button.
ROOTING
2.3.7 BUILD V768V1.0.0B08 = NO FACTORY RESET NEEDED???Maybe
2.3.7 BUILD V768V1.0.0B19 = FACTORY RESET NEEDED???Maybe.
2.3.7 BUILD V768V1.0.0B20 = FACTORY RESET NEEDED
1.)Using your PHONE or computer - Download attached update.zip file.
2.) copy/move update.zip to root of sdcard
3.) Power off the phone
4.) reboot into recovery by holding Volume DOWN and power button until the android with the triangle appears . This will appear AFTER the android that is by himself!!(about 30 seconds)
If for some reason, you CANNOT boot into recovery try to FACTORY RESET.
5.) At this screen, Press the HOME button.
6.) scroll to your second option, navigating with the volume buttons - "Apply update from sdcard" and press the Menu key
7.) select UPDATE.ZIP to install
8.) Navigate to YES, if asked, and press the menu key.
9.) Navigate to - "reboot system now" and select by pressing the menu key.
10.) Install SuperUser. I installed SuperUser and Root Checker before installing the update.
11.) Install Busybox - Using the SMART INSTALL feature. Get it from the play store.
12.) Follow this guide - if you are going to partition an SD Card - It will show you how to partition the SD Card and install Link2SD :
Partition you SD Card To Acquire more "Internal Memory"
Congratulations!! You are now ROOTED and have more "Internal Memory"!!
Special THANKS to JCASE for his CREATION of the ZTE MERIT UPDATE.ZIP
I did the boot-loop process and then the root process. I had no errors and was rooted on the first try. You should not need to factory reset. This is only the boot- loop fix and root. No new recovery or roms.
Anyone else try this?
Liquidsmooth GSII
Hi fathertomany,
Thank You, it worked, root granted and superuser installed.
Wow, I may be only the second person in the world after you to get one rooted
So to confirm and Thank, Yes, this rooted it easy and quick, can't believe it but awesome!
Thanks!
b7
Wow 230 views and only 1 other person telling me it worked for them? I would like to keep up with this and maybe figure out some way to get roms and such, like twrp, themes, etc... But I need to know if there are any bugs or not by following these instructions. I am not a DEV but am willing to try to accomplish things people want. Currently trying to get twrp ported by someone for this phone. Whoever is willing to work on the port should pm me.
Hey I'm new to posting but I've been on android for a few years. I'm having troubles with booting into recovery mode. Whenever I try it shows some yellow text at the bottom. Something about the data directory. Think u can help me fix this please? Thank u
[Edit] My phone has been doing that since way before I downloaded the zip file. So just to clarify it has nothing to do with the file
Sent from my ZTE V768 using xda app-developers app
need help booting into recovery
fathertomany said:
I AM NOT RESPONSIBLE FOR ANYTHING NEGATIVE THAT HAPPENS TO YOUR PHONE!!
Never Hurts to Thank or Donate to all that help you!
I have boldly went where no one has gone before. After much soul searching about bricking my son's phone because I have only followed guides, I decided that this phone was so similar to the AVAIL/MERIT that I would use that method to root his Concord. I did this because his phone ran out of memory and subsequently got stuck on boot-loop. Because this worked, I wrote this tutorial.
NO PC NEEDED!!!!!!!!
This quick tutorial will help you get into recovery and root.
What files are needed are not my work! I only decided to use the ZTE MERIT GUIDE AND ZIP for my son's T-mobile Concord(V768).
To get out of the BOOT-LOOP
1.) Power off the phone by removing the battery.
2.) Replace battery.
3.) Boot into recovery by holding Volume- and power button until the android with the triangle appears. this will appear AFTER the android that is by himself!!
4.) Press the home button
5.) Navigate to the 3rd choice - " wipe data/factory reset"
6.) Select by pressing the menu button
7.) When the wipe is complete, navigate to and select - "reboot system"
To Root
1.) Download attached update.zip file
2.) copy/move update.zip to root of sdcard
3.) Power off the phone
4.) reboot into recovery by holding Volume- and power button until the android with the triangle appears.
5.) At this screen, Press the HOME button.
6.) scroll to your second option, navigating with the volume buttons - "Apply update from sdcard" and press the Menu key
7.) Navigate to YES and press the menu key (no data will be wiped but the update will be installed and you will be rooted)
8.) Navigate to - "reboot system now" and select by pressing the menu key.
9.) Install superuser or equivalent. I installed Superuser and root checker before installing the update.
If for some reason, you get an error, try to factory reset first.
Congratulations!!! You are now Rooted!!
Special THANKS to JCASE for his work on the ZTE MERIT UPDATE.ZIP mentioned above. The UPDATE.ZIP file was downloaded from Stayboogy's tutorial.
Click to expand...
Click to collapse
What carrier and version and build number are you on? You can find that under settings--> about phone. My carrier is Family Mobile (which runs on T-Mobile) and I'm running Android 2.3.7 and Build number V768V1.0.0B20.
I am having trouble getting the Concord to boot into recovery. I can't seem to get to a screen with a triangle. Can you walk through the steps to get it into recovery again or possibly post a video?
The video stayboogy supplied in the link you posted for the Avail/Merit said to put the phone into recovery mode by holding the volume up key and the menu key while pressing the power button. When I do that the concord freezes at the green android logo and does not go into recovery mode and does not boot normally. I have to pull the battery. Same thing if I hold both of the volume buttons and the menu key.
If I hold the volume down and the menu key (or just the volume down key or just the menu key) and turn on the power button I get the green android startup screen followed by a screen with a white box and an orange arrow coming out of the box pointing to a small green android. When I get to this screen pressing home or the volume up or down buttons just cause it to reboot.
bkool96 said:
Hey I'm new to posting but I've been on android for a few years. I'm having troubles with booting into recovery mode. Whenever I try it shows some yellow text at the bottom. Something about the data directory. Think u can help me fix this please? Thank u
Sent from my ZTE V768 using xda app-developers app
Click to expand...
Click to collapse
I personally have not noticed this. make sure your phone is off. make sure you press the volume down button first. while still holding the volume down button press and hold the power button. DO NOT let go of either button until the android with the triangle appears. you will see the android by himself first, CONTINUE HOLDING THE BUTTONS FOR ABOUT 30 SECONDS. When the android with the triangle appears, you can let go of both buttons. Then press your home button. this should bring up your recovery menu.
USE THE VOLUME BUTTONS TO NAVIGATE UP AND DOWN.
USE THE MENU BUTTON TO SELECT YOUR CHOICES. I
BELIEVE, THE POWER BUTTON ACTS AS THE BACK BUTTON? (MAYBE JUST USE THE BACK BUTTON.) I will check this when my son gets home from school. he is the one with the phone.
remember there is NO factory wipe necessary, unless you are trying to get out of the boot-loop.
iamhdr said:
What carrier and version and build number are you on? You can find that under settings--> about phone. My carrier is Family Mobile (which runs on T-Mobile) and I'm running Android 2.3.7 and Build number V768V1.0.0B20.
I am having trouble getting the Concord to boot into recovery. I can't seem to get to a screen with a triangle. Can you walk through the steps to get it into recovery again or possibly post a video?
The video stayboogy supplied in the link you posted for the Avail/Merit said to put the phone into recovery mode by holding the volume up key and the menu key while pressing the power button. When I do that the concord freezes at the green android logo and does not go into recovery mode and does not boot normally. I have to pull the battery. Same thing if I hold both of the volume buttons and the menu key.
If I hold the volume down and the menu key (or just the volume down key or just the menu key) and turn on the power button I get the green android startup screen followed by a screen with a white box and an orange arrow coming out of the box pointing to a small green android. When I get to this screen pressing home or the volume up or down buttons just cause it to reboot.
Click to expand...
Click to collapse
You can find most of that in the title "Confirmed!! T-Mobile Concord (V768) ROOT and BOOT-LOOP fix!!"
My Android BUILD will be posted when my son gets home. he has the phone. It should be the same. I am using the same carrier with the same version of android. Android 2.3.7
I am also on the family mobile plan.
fathertomany said:
I personally have not noticed this. make sure your phone is off. make sure you press the volume down button first. while still holding the volume down button press and hold the power button. DO NOT let go of either button until the android with the triangle appears. you will see the android by himself first, CONTINUE HOLDING THE BUTTONS FOR ABOUT 30 SECONDS. When the android with the triangle appears, you can let go of both buttons. Then press your home button. this should bring up your recovery menu.
USE THE VOLUME BUTTONS TO NAVIGATE UP AND DOWN.
USE THE MENU BUTTON TO SELECT YOUR CHOICES. I
BELIEVE, THE POWER BUTTON ACTS AS THE BACK BUTTON? (MAYBE JUST USE THE BACK BUTTON.) I will check this when my son gets home from school. he is the one with the phone.
remember there is NO factory wipe necessary, unless you are trying to get out of the boot-loop.
Click to expand...
Click to collapse
I tried again with no luck. In the Root ZTE Concord thread a few of us tried and were never able to get into recovery mode.
I just tried the steps you listed but I get the same screen with the white box and arrow and if I continue to hold the power and volume down button it causes the phone to reboot. If I keep holding down the power and volume down even after it reboots it just repeats, green android screen, white box screen, reboot, green android screen, white box, reboot, etc. I can record a video of the screen later today if you are interested.
Did you ever install an over the air update? I did months ago and I wonder if that update changes or removes how to get into recovery mode.
I have T-Mobile android 2.3.7 build number V768V1.0.0B19
Sent from my ZTE V768 using xda app-developers app
iamhdr said:
I tried again with no luck. In the Root ZTE Concord thread a few of us tried and were never able to get into recovery mode.
I just tried the steps you listed but I get the same screen with the white box and arrow and if I continue to hold the power and volume down button it causes the phone to reboot. If I keep holding down the power and volume down even after it reboots it just repeats, green android screen, white box screen, reboot, green android screen, white box, reboot, etc. I can record a video of the screen later today if you are interested.
Did you ever install an over the air update? I did months ago and I wonder if that update changes or removes how to get into recovery mode.
Click to expand...
Click to collapse
I will attempt to find this screen later when my son gets home. 3:30pm central.I have only owned the phone for about 1 1/2 months. I do not believe that I have received any update OTA or any other way. my son downloads a lot of CRAP. He eventually got stuck in the pink logo boot-loop. I proceeded to do the boot-loop fix that I listed and after the factory reset to get out of it, I confirmed that it booted normally, turned the phone off and went back into recovery.
One thing I did notice about this phone is the power button. It is "weird". I am one of those that mash the buttons EXTRA hard to insure that they are being pressed. I make sure that I use both hands, one finger on each hand for each button and I hold as still as possible. Making sure that I don't toggle any buttons. at first, my phone would some how be stuck on the green android that is by himself. What your are saying sounds similar but I never noticed the white box. I think that this might be the download mode. if you have some kind of case on the phone, try removing it.
OTA update?
bkool96 said:
I have T-Mobile android 2.3.7 build number V768V1.0.0B19
Sent from my ZTE V768 using xda app-developers app
Click to expand...
Click to collapse
Have you ever applied the over the air update? I have and I wonder if that has eliminated the ability to get into recovery mode.
I stated in my previous post that I have not noticed one. I bought the phone at the end of February. I rooted the phone the night before I posted this tutorial. I will check the build version as soon as my son gets home. FYI, The rom is totally stock as no one has had this rooted, unlocked bootloader or otherwise, that I know of.
Sent from my LIQUIDSMOOTH SGH-T989
fathertomany said:
I will attempt to find this screen later when my son gets home. 3:30pm central.I have only owned the phone for about 1 1/2 months. I do not believe that I have received any update OTA or any other way. my son downloads a lot of CRAP. He eventually got stuck in the pink logo boot-loop. I proceeded to do the boot-loop fix that I listed and after the factory reset to get out of it, I confirmed that it booted normally, turned the phone off and went back into recovery.
One thing I did notice about this phone is the power button. It is "weird". I am one of those that mash the buttons EXTRA hard to insure that they are being pressed. I make sure that I use both hands, one finger on each hand for each button and I hold as still as possible. Making sure that I don't toggle any buttons. at first, my phone would some how be stuck on the green android that is by himself. What your are saying sounds similar but I never noticed the white box. I think that this might be the download mode. if you have some kind of case on the phone, try removing it.
Click to expand...
Click to collapse
I tried again and made sure to hold the buttons firmly without moving but have the same result. Maybe your son never applied the OTA update and that's why you can get in recovery mode.
---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------
fathertomany said:
I stated in my previous post that I have not noticed one. I bought the phone at the end of February. I rooted the phone the night before I posted this tutorial. I will check the build version as soon as my son gets home. FYI, The rom is totally stock as no one has had this rooted, unlocked bootloader or otherwise, that I know of.
Sent from my LIQUIDSMOOTH SGH-T989
Click to expand...
Click to collapse
I was just wondering if the OTA update was applied by bkool96 and maybe that's why we both can't get recovery mode to boot.
If you are willing to back up what you can and then do a factory restore. You might have luck that way. I will try to get into recovery later today since my son has been using the phone but I may still be able to seeing as how I am already rooted.
Sent from my LIQUIDSMOOTH SGH-T989
Also, googling it, I noticed that I may be A** backwards. Meaning, Try Volume UP and the power button. If that works then I will edit the tutorial.
Sent from my LIQUIDSMOOTH SGH-T989
fathertomany said:
Also, googling it, I noticed that I may be A** backwards. Meaning, Try Volume UP and the power button. If that works then I will edit the tutorial.
Sent from my LIQUIDSMOOTH SGH-T989
Click to expand...
Click to collapse
I'm pretty sure its volume down+power button. Im stuck at the green android with volume up and I get into recovery with volume down for like 3 seconds then it reboots with a yellow error message mentioning something about the /data directory
Sent from my ZTE V768 using xda app-developers app
When you press the volume up and power buttons, DO NOT let them go until the Android with the triangle appears. Then follow the rest of the guide. I remember getting frozen at the green Android by himself.:banghead:
Sent from my LIQUIDSMOOTH SGH-T989
fathertomany said:
When you press the volume up and power buttons, DO NOT let them go until the Android with the triangle appears. Then follow the rest of the guide. I remember getting frozen at the green Android by himself.:banghead:
Sent from my LIQUIDSMOOTH SGH-T989
Click to expand...
Click to collapse
I tried it again and its still a no go. Maybe its my phones build number that the recovery mode doesn't like?
Sent from my ZTE V768 using xda app-developers app
---------- Post added at 01:32 PM ---------- Previous post was at 01:25 PM ----------
iamhdr said:
Have you ever applied the over the air update? I have and I wonder if that has eliminated the ability to get into recovery mode.
Click to expand...
Click to collapse
I updated back at the end of December which fixed problems I had with mounting the USB storage on my Mac
Sent from my ZTE V768 using xda app-developers app
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
Please ensure you REALLY use the correct key combo! Just saying bla does not tell us what exactly you tried.
If you really can't get in you can try to Boot into download mode
https://m.youtube.com/watch?v=0cbLhpWq5C8
Then use lgup to reinstall stock ROM and do all the stuff again to get twrp, root and a custom ROM.
Naerade said:
Hi everybody !
I usually (always normally) succeed myself at resolve my phone problems, but this time I can't do anything.
My problem :
I have a LG G4 ; I saw an update of Imperium Rom (v8) this morning, so I installed it, everything worked well until I decided to install a, apparently, ****ed mod on xposed ; and since I have rebooted I can't do anything ; the LG logo shows and just after "UI system as stopped", just one time but, then I can't do anything, screens over screens, can't access parameters, password required, "flex mode" (never saw this before), re-password, system UI restart, loading background, restart system UI; and this in a infinite loop SOOOOO
I decided to reset it, yeah... But I can't access my recovery, wow o/
I followed the step to access it by switch it off and press volume down etc --> It just boot normally, or best in safe mode by magic but same problem ; via parameters but I can't access parameters ; and via ADB buuut my phone isn't recognized even with the complete sdk, drivers, everything you want, there's nothing to do because --> while restarting system UI it deconnects so of course it can be recognized
I removed xposed (while I could still access recovery, as I was thinking it was coming from the xposed module) and so now I can't even access recovery via shutdown menu (as I had put "reboot to recovery" in via Xblast, a xposed module) ; and of course it doesn't change anything
I neeeeed your help so much, I don't mind losing what's on it :crying:
Click to expand...
Click to collapse
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
raptorddd said:
can it enter download mode.. if so use LGUP and KDZ file.
to enter download mode press vol key up connect usb. youll see it on screen. then flash it using KDZ
Click to expand...
Click to collapse
Thank for your answer ! No it couldn't even boot in download mode
I resolved my problem by forcing again the buttons to reset completely, it finally showed me after about 30 boots or more the reset screen, I said "ok" ; and in fact it just rebooted saying "updating Android", I did not lost anything.
I still don't understand how it happened but anyway !
I don't know if it's possible to set the topic as resolved ? I don't find it
So hello there!
I'm having the following issue and I'm kinda out of ideas.
I was running a (KingRoot) rooted fireOS 4.6.6.1 (420) if I'm not mistaken.
So this is what happened:
Phone was running just fine, but I wanted to get rid of the facebook background services which kept running without the actual app installed. Also a friend proposed to run the 'fstrim' command. So reading through xda I found an app called 3C Toolbox (http://www.3c71.com/android/?q=node/916) which seemed to be safe to use. Installed it and still didn't change a thing except for the three 'fstrim' actions to perform. After that I restarted my phone.
Powered off just fine, but at the start only the 'Amazon' logo comes up and vanishes into a black screen with the backlight still on. Even after waiting several hours nothing changes.
So what did I attempt to get it wirking again?
At first I tried to simply restart it. --> Nothing changed.
Tried to get into recovery and clean the cache. --> Nothing changed except the 'Amazon' being on for a bit longer
Get into ADB and try pull/uninstall... --> Guess due to the locked bootloader I'm not allowed to issue any command other than 'adb sideload [packagename]' for system updates. As for ADB itself I can only get it to recognize on the PC when I get into recovery and choose the 'apply update from ADB' option.
Get into fastboot according to this tutorial (https://forum.xda-developers.com/showthread.php?t=1668159) --> doesn't work.
Get into 'Safe Mode' with this tutorial (https://forum.xda-developers.com/fire-phone/help/how-to-fire-phone-to-boot-safe-mode-t2828240) --> doesn't work either.
So does anybody has another idea I could give a try or should I just abondon all my data and flash a new clean image?
Also I'm not sure if updating from ADB will erase all personal data too. Guess so, but maybe I can get a clearification in here too.