Ok so I'm trying to sideload the new update to my watch because I'm impatient. I can get the adb reboot to send to the watch but I can not get past the android with stomach open image. I can't get the menu so that I can choose to sideload update can anyone help. I searched but may have missed a previous thread to this. I seen that you should swipe down to pull up the menu but I can't get this menu to show ... Any help would be appreciated.
Never mind I finally got it to recognize my swipe... frome left to right... it is real slow about reacting....
Related
So I decided to try to apply a hide bar/status bar toggle i found online which required replacing the services.jar found in system/framework with a custom services.jar. Unfortunately, after rebooting, I'm stuck at the asus logo boot loop and if I try to recover it just goes to an Android on it's back with an exclamation mark. Any help would be appreciated!
setup adb and see if you can get the device to be recognized by doing adb devices
Yeah, adb isn't recognizing it
That's why I never do mods like that, too risky.
GOOD LUCK ln getting it back running.
songmeesay said:
So I decided to try to apply a hide bar/status bar toggle i found online which required replacing the services.jar found in system/framework with a custom services.jar. Unfortunately, after rebooting, I'm stuck at the asus logo boot loop and if I try to recover it just goes to an Android on it's back with an exclamation mark. Any help would be appreciated!
Click to expand...
Click to collapse
First of all: If it's turning on and the screens showing the ASUS logo and the Android on its back its NOT BRICKED! Brick = Paperweight which yours is not.
If you can get ADB working then pushing out the replacement files again should be fairly simple. Got into the same issue when I was trying to find a way to root mine - would bootloop and ADB was only available for 5-10 seconds before it would reboot again. Eventually made a .bat file to perform the remounting of /system and copying of files.
"Adb wait-for-device" is a handy command to use - it'll pause until it sees a device connect. If it's at the start of a script it'll wait till it sees the device before it runs anything else.
If this still fails you could try googling for a way to manually update? Not sure how lucky you'll be.
If this fails then the only way is to re-flash it. Unfortunately we don't yet have a way of doing this (and won't have until ASUS unlocks the bootloader) so your only option is to wait around hoping it's sooner rather than later, or send it back to ASUS and pay to have it repaired.
Hope you get it fixed.
Cool, I'll try the above and if it fails I don't mind waiting around to re-flash. Kept my GT 10.1 for situations like this. Thanks.
hartej said:
First of all: If it's turning on and the screens showing the ASUS logo and the Android on its back its NOT BRICKED! Brick = Paperweight which yours is not.
If you can get ADB working then pushing out the replacement files again should be fairly simple. Got into the same issue when I was trying to find a way to root mine - would bootloop and ADB was only available for 5-10 seconds before it would reboot again. Eventually made a .bat file to perform the remounting of /system and copying of files.
"Adb wait-for-device" is a handy command to use - it'll pause until it sees a device connect. If it's at the start of a script it'll wait till it sees the device before it runs anything else.
If this still fails you could try googling for a way to manually update? Not sure how lucky you'll be.
If this fails then the only way is to re-flash it. Unfortunately we don't yet have a way of doing this (and won't have until ASUS unlocks the bootloader) so your only option is to wait around hoping it's sooner rather than later, or send it back to ASUS and pay to have it repaired.
Hope you get it fixed.
Click to expand...
Click to collapse
Thank you!
I gotta try this
Could you post your bat file or contents
Sent from my PC36100 using XDA App
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
Ok first of all Im sticking this question in general android Q&A because there in no XDA Forum for this phone. It is a Straight Talk LG Optimus Q 55c, this is my girlfriends phone its basically an optimus p500/v with a sliding keyboard Overclocked too 800mhz. I own a virgin optimus V so I have a lot of experience with this platform but Im stumped maybe im just neglecting to see something, Im hoping "another set of eyes" will help turn on a light and get my girlfriends phone working again as she cant afford another :/!
So here is what Im dealing with. I had rooted the phone for her and installed clockwork mod recovery & fastboot. Since she got the thing its had problems freezing (probably because it stock overclocked), and occasionally pulls a random reset. She asked me If I could install another ROM on it to see if it may help make the phone more stable. I went a searching and found that the Optimus Q community is very small almost nothing and her only real choice was a port of the Area51 Rom. So Installed the rom.... A few days later she had told me her phone was mega slow now and acting up way more, so I told her I would flash back to stock.
I rebooted the phone and found to my surprise CWM and fastboot seemed to be gone... what the h*ll? Im assuming when I flashed AreaRom it installed the stock Recovery and removed fastboot, I cant figure out any reason why the stock recovery would be back on the phone. Anyways I didnt feel like flashing a new recovery at the time. Well 3 days go by and her phone crashes and gets stuck in a boot loop. So she went in to recovery and wiped it. The phone then went through the process of collecting e-mail and password, asking about backing up, then asking whether or not to turn the location services on. Once you hit next Android throws an exception and says setupwizard.apk failed to initialize or something along those line. So after that the launcher does not load only the task bar at the top. When rebooted the phone enters a boot loop againg until wiped.
So heres the deal I can use adb, but when I try to get into an adb shell the prompt says error: closed. I have been able to use adb to push and pull files that is all. I tried to push setupwizard.apk to the system/apps directory but of coures it needs to be remounted to read write and I dont have any shell access to do that. So basically adb sees the phone but the shell doesnt work, when i type adb root it reports adbd is running as root on the phone, so I guess the shell service just never loads.... I do have stock recovery but the problem with that is there is no update.zip files it will except I have tried a myraid of methods to sign an update.zip but every time I try to run the update the stock recovery says verification failed. Of course LG has no official updates for this phone using there signature that I can use.
So basically my phone works recovery works android starts but cant finish setting up and never starts the adb shell service. If anyone knows how I can push setupwizard to /system/app, get adbd to initialize, or sign a 3rd party rom and have the stock recovery use it I would be very gratefull! Maybe there is a way to get fastboot back on there or enabled or something? adb reboot-fastboot just reboots like normal. I am at the point where I going to take the phone apart to find a serial uart connection and pray I can get a shell that way!!
Ive looked into a few programs like kdz update and lgmdp but they dont seem to work with this phone and I cant get into any emergency mode, maybe Im doing it wrong this is the first ive heard of emergeny mode.
Pls help me root my zte obsidian running android 5.1 Model NO. Z820
I need help too
I also have ZTE obsidian tmobile and really want to root it i cant do much because it only comes with 4gb of space and i cant move apps to the SD card till i root Please help find a root
yeah same issue here all say that it cant after like 10-15 mins its just like nope sry
have you used this
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Yes, I tried. Its not working.
Is there any other way. I am desperate. It doesnt allow to move the Apps to SD card. There is no way. Locked in 4GB
I have a z820 in need of root as well. I've tried everything, including the link up there, and so far.....nope. Nothing. No apps to SD for me either.
Zte can't root for ****!!!!
I'm so mad because I really tried everything even a computer won't let me tried everything there to like why would the make a zte that can't even move your games or pictures or music to your SD card knowing danm well everybody gone need like we only got 4g that's nothing so what are we so posted to do delete stuff that we like.to trade for the other that we really don't need **** I'm pissed right now I know y'all are to but if anybody finds something please send me the info or con me by [email protected] thank you:good:
Needs update
This Phone really needs an update, it reboots and sucks, we can't even get into fastboot or anything to try to unlock the bootloader someone needs to make this possible because who in the hell uses only 4gb of storage, apps are so big and you can only download like 3 apps then you have to get rid of something if you want another app and its dumb so please someone..HELP US :crying:
Throwing my post up here so I can follow. Need root bad on this thing. I am using lite versions of every app. Lol
Same problem w/ ZTE obsidian..tCan't move to SD card. Anybody figure somethcing out yet?
I've gotten Kingroot to attempt to root it once and the results varied. Usually got 16% but the highest was almost 30% but I can't even get kingroot to even root it anymore.
The phone is not going into fastboot at all. I think the bootloader is locked. The phone will never be rooted.
I might of found a way, but it's untested so, proceed at your own risk, I am not responsible if your phone becomes bricked.
Enable developer mode and tick "OEM Unlocking" in the developer menu
Download SuperSU update zip from Chainfire's site and put it on your sdcard (internal won't work)
Power off your phone and hold power and volume up
Select recovery, wait for the android with the lid open to show up
Hold power and volume up for a couple seconds and let go
A menu should pop up, if not try again until it does
Select "update from sdcard"
Select the SuperSU zip
Let it flash the zip (shouldn't take long)
Choose reboot
See if SuperSU is installed and test that it works
Again, this is untested and would need a couple of people testing it to make sure it works flawlessly, so if this worked, please post that it did.
Nope. Thank you though.
picsles said:
Nope. Thank you though.
Click to expand...
Click to collapse
Any type of error happen or did it not allow it to flash at all?
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Musicmanmike said:
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Click to expand...
Click to collapse
You have to hold down power and vol up for like 2 seconds when you get to the dead android, then you'll get the recovery menu.
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Kurrelgyre said:
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Click to expand...
Click to collapse
OEM Unlocking is always on for me even after restarts but I haven't tried to flash SuperSU yet. You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
EDIT: Also every new Kingroot build allows you to attempt to root it for like 2 days and then it just can't for some reason but the thing with 18% still happens.
LUModder said:
You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
Click to expand...
Click to collapse
The logcat I am familiar with is in ADB. The only way I can find to access the phone from recovery with ADB is to select the flash from ADB option, which puts the phone in sideload mode where you can't pull data off. I was unsure if trying to load the ZIP that way would brick the phone so I haven't tried it.
I also tried using Fastboot and it doesn't recognize the phone at any time.
Is there another way to capture what is happening with the update?
I tried selecting restart in bootloader from the recovery menu with the phone connected to the PC. It stayed at the ZTE splash screen for over 10 minutes but neither fastboot nor ADB was able to communicate with it. I tried various key combinations without effect and finally ended up pulling the battery. Maybe it just froze up during boot for some reason.
I have tried every one-touch root I can find, none of them work. All the manual guides start with unlocking the bootloader - which I can't find any info on for this model. Based on the partition info, it's definitely locked: it has 27 (!) partitions including names like seccfg and oemkeystore. Is this normal for a lollipop device?
hi all been a while since i been on here but find myself in bit of a pickle.
my dad gave me his old android tablet for my son to play but its not working like the os has gone from it all it does is stay on the main screen with the android or i have been able to get into the tablets default recovery mode where it asks things like apply update from zip or apply update by adb etc etc. the tablet in question is an avaco stb7012 v1 and i know its a cheap ebay china knock off just looking to flash it but cant seem to get anything to work in order to flash anything on there anybody have an idea ive tried using commands like fastboot and adb but says device null on adb and fastboot it says waiting for device and nothing happens. am i doing something wrong is there a guide i can follow to do it or is it naff coz i thought as long as it does boot into recovery then there is some glimmer of hope i dont no what else to do spent hours researching any roms for this tablet but nothing. hope someone can help all i want to do is be able to install a new os of android onto it and get it running again.
thanks