Related
Having a crazy day. Got the new ChevronWP7 unlock last night. Did the internet sharing interop combo. Now get error trying to reload xap files. Trying to put on accentchanger file.
Error - failed to connect to the device. Ensure that the device is connected..
The xap app is not supported
You have to deploy supported xap only
Ex:
Screen cupturer
Nokia maps
Battery status
Tango, but it is now in marketplace
Some other apps like Native keyboard are not working.
Good luck.
Sent from my 7 Mozart
@verynuclear: Not sure what you think you're trying to say, but it's totally possible to use high-privilege apps like Advanced Config (which does custom accent colors, among other things). You just need Interop Unlock, which is easy on LG, possible (via an app) on Samsung, and difficult but not impossible on HTC (I have it on my HD7).
The problem is that after using the Interop-unlock app on his or her Samsung phone, the OP seems to be having trouble with the XAP deployment tools. @jgibo, I suggest you read and then post in the relevant threads for those apps, rather than starting a new thread.
The main reason for asking question is if the deployment tool stopped working for anyone else. After I got Chevron on there I was able to install screen capture, accent changer. Screen capture worked. So I removed accent changer and followed instructions for interop unlock install. Then saw the thread for internet sharing and interop in one. Installed that to phone. Got internet sharing Then tried a few different xap files and couldn't install any. So did that xap mess something up? Guess I will look elsewhere for answers.
This is all they have on MSDN site.
--------------------------------------------------------------------------------
This can be caused by several reasons, including if the device is off. If the device is already connected, sometimes disconnecting and then reconnecting the device may fix the problem. Rebooting the device may also fix this problem
You do have internet sharing OFF right? You can not deploy XAP's with ICS on. I don't mean to be rude but it really does pay to read the whole post when someone gives instructions on how to do something before saying it messed up your whatever.
voluptuary said:
As long as your device is unlocked in some way (Developer/Chevron/Other) you can get internet sharing on your Samsung phone.
1.) First install the WP Dev Tools and unlock your Samsung phone.
2.) Use the Application Deployment tool to send THIS to your phone. You do not need to run it and you can delete it after it has been deployed.
3.) Install the Diagnosis app by typing ##634#
4.) After the Diagnosis app starts type *#9908# and select 'System Tweaks' press 'Save' then 'Close' and RESTART your phone.
5.) Your phone now has internet sharing and as a bonus is interop unlocked!
PS: You need to have a recent firmware on your phone or your diagnosis app and drivers will not be new enough to work.
EDIT: I built the file depoyer app using the tools provided by Heathcliff74 so many thanks to him! Also ADC is built in as well so no need to worry about that and I also upped the max number of connections from 3 to 5 devices.
NOTE: If you have internet sharing turned on (active hotspot) you will not be able to deploy XAP's untill it is turned off. Also, as with any xap, you need to have your screen unlocked to deploy.
Click to expand...
Click to collapse
Of course if you have ICS off then I'm sorry for this little rant and all I can suggest is restarting your phone and PC and trying again.
ICS is and was off. Found other posts with same message. Currently reinstalling dev tools. I do IT support for a living and hate havinng to do troubleshooting on my own stuff From past experience with computers it is either a coincidence or cause when a new problem occurs. Hence the questions asked. I do remember seeing an odd usb error in system try when I was doing step 4. Did a troubleshoot on my Focus connection but that didn't help. Also tried all usb connections. If the reinstall doesn't work will have to get my htpc out and try on it.
Reinstall didn't work. Since it stopped after running system tweaks I am trying again. Wish the instructions had a note on how long after hitting the save button before it was done. Has the Loading GPRS Profile for System Tweaks on screen. I think I may have hit the close button yesterday while is was still showing Loading. Right now I am not touching phone till I see it go away. Unless you are supposed to hit close right after hitting save.
The settings are applied almost instantly, as soon as it says loaded after you hit save then you can hit close and restart. Another user stated they had to turn ICS on then off again before he could deploy XAPs. Another question, you haven't turned on wired tethering have you? I ask because if you don't set your phone back to Zune sync you also will get the error you are getting.
EDIT: Main question, does Zune see your phone when you plug it in at all? Can you sync media? Cause if you can't you have another issue that is beyond anything my XAP could have done.
That kind of worked. Turned on ICS then back off. Got Advanced Config to install. Now get UnauthorizedAcessException. Click ok and app closes. Go from one issue to another.
ATTENTION / WARNING / ACHTUNG!!!!!!!
Efun (distributor of what we know as the "Nextbook Premium 8SE") in fact sells two different tablets marketed under the same name. This rooting method will ONLY work with a Nextbook Premium 8SE running a Rockchip processor.
**Am very sorry if this has already been posted, searched and did not find anything.**
Soon after purchasing my Nextbook Premium 8 se I learned that many Roms, apks, etc. that I couldn't find via Google (in English, anyhow) are easily found in Italian.
Which brings me to what I found today
androidworldDOTit/forum/mediacom-smartpad-810c-381/%5Brom%5D%5Bics-4-1-1%5D%5Bxteam-4-0-jellybean%5D%5Bmediacom-810c%5D-67171/
Run that through Google Translate if like me you don't speak a word of Italian.
All right, time to sit down and write a guide to doing this. First things first: I didn't do any of this work! People like Devmonkey, Sunnyboy167, deeno33, and FinlessBob, (over at Freaktab) and Xteam at Android World Italy are the ones who've put in the legwork and hours to make this stuff possible. I'm just gathering their work in to one place.
Before you begin: Back up all your things if you want to keep them!
Also, remove your micro sd card from the Nextbook. I darn near fried mine because I didn't.
Next: You know the drill. You're a big boy, (or girl, or whatever. I'm not here to judge) I, nor anyone else is responsible if anything bad happens to your device, to you, your happiness, or your hard earned money or your time. YOU are choosing to root your device and install Jellybean on to it and YOU assume all responsibility. Cool? Also, this will probably void your warranty. But let's face it, if you're here, you probably don't care too much about your warranty anyway. Let's get rocking.
STEP 1: Make sure you have the device drivers installed for your Nextbook on your computer. I'm using a Windows 7 64 bit desktop. I imagine that other Windows desktops pre Win 8 will be similar. If you're using Linux, I believe that drivers aren't necessary. But hey, if you've installed Ubuntu, Arch Bang, Puppy, etc, you've probably got this figured out anyway.
Turn off your Nextbook Tablet Connect the micro usb cord to it, then hold in the volume up and down keys while plugging it in to your computer.
"NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 2: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 3: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 4: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine." ~Sunnyboy167
Ok, now that the device drivers are installed you'll want to download the file linked from here: zippyshareDOTcom/v/60864398/fileDOThtml
Sorry, I have less than 10 posts, so you'll need to convert the dots to, you know, dots. I get why the site does that.
Scan that thing for any nasties, and then unzip it wherever you'd like. (I used my desktop) Open it and click on the folder "Mediacom 810c" Inside you'll find a file named "Rk29update.exe." Open it. You'll see a box like this:
See attached picture
That is what it will look like if your tablet is not hooked up to your computer. So if it isn't (which it should be, since I never told you to disconnect it) reconnect it now.
Click the box that says "loader," then click "Formatta!!" Which, as you might have guessed is Italian for "Format." No going back now, kid.
Let the thing run its course, it'll take a couple of minutes. Once it's done, click the box that says "Aggiorna!!" This will install Jellybean on to your Nextbook. Be patient, as this will take a few minutes. You'll hear your computer make the "device disconnected" sound, and you'll be all set. You can unplug your Nextbook from your computer now.
First boot up of the device on Jellybean was a touch slow for me, but don't panic. Once you've gotten through set up the Rom runs incredibly smooth and fast. The first screen you'll see will be the welcome (benvenuto) screen. You can select English (or your preferred language) from the drop down menu. From this point on it should be smooth sailing. Google Now works like a charm, Project Butter seems to really make a difference on this tablet, camera works, notifications work, everything seems good. There are minor bugs here and there, but nothing Earth shattering.
One last thing: for a $99 budget "craplet" from Big Lots, you could do a lot worse than this tablet. I've found it pretty sturdy, highly customizable, and generally responsive and fun to use. I also own a Nexus 7, and while this clearly can't touch it spec wise, it's definitely a fun second device to keep around.
ok, so far so good. The Rom is very responsive, Google Now is working well. Only thing to note, which I should have known: Take out your micro sd card first! I ended up corrupting mine when I flashed the Rom. (And guess where I had everything backed up too? = fail)
But again, other than that, this Rom is awesome
Request for Bug List
Thanks for posting about this Italian Rom for the Nextbook 8. I am thinking about installing it. Can you provide a list of bugs that you've noticed?
Thanks again!
Shaun
shaunmt said:
Thanks for posting about this Italian Rom for the Nextbook 8. I am thinking about installing it. Can you provide a list of bugs that you've noticed?
Thanks again!
Shaun
Click to expand...
Click to collapse
of course!
As mentioned in the install guide, take out any MicroSD card, as you might damage it. That said, however, upon another reading of the original Italian install guide, apparently the "data system corrupted" bug that I took for being my MSD card being screwed up is in fact a known bug that is actually affecting internal memory, but only temporarily. The solution is to simply format it on device, and everything will work fine. The option to format is given as a push notification immediately upon getting through the sign in process, and nothing in actuality appears to be damaged, but until I did the format I could not access anything on my MSD card.
The big recurring one I've noticed may or may not be unique to this Rom, as my device had it before on a gingerbread Rom; namely, the battery charge level never seems to change. It always seems to be at 100% right up until it drops dead, no warning. Actually, that's not entirely accurate, because if it runs out, and I charge it and unplug while the charge shows a number less than 100% the battery icon will continue to show "charging" until 100% (even though unplugged) and then stay there.
When waking the tablet up it takes a couple of seconds to reconnect to wifi. Any notifications coming in will slow it down for up to a couple of minutes. I've noticed that if I try and use it during this time I occasionally "overload" the device, and end up with it rebooting. My best advice: wake it, give it a second to go from "no internet connection" to having found wifi, unlock the screen, and then wait about 1 minute before doing any heavy use until any notifications pop up; once you do that you're good to go.
If I think of or notice anything else hopefully I'll remember to edit this post.
2 Problems I found
Conect11 said:
of course!
As mentioned in the install guide, take out any MicroSD card, as you might damage it. That said, however, upon another reading of the original Italian install guide, apparently the "data system corrupted" bug that I took for being my MSD card being screwed up is in fact a known bug that is actually affecting internal memory, but only temporarily. The solution is to simply format it on device, and everything will work fine. The option to format is given as a push notification immediately upon getting through the sign in process, and nothing in actuality appears to be damaged, but until I did the format I could not access anything on my MSD card.
The big recurring one I've noticed may or may not be unique to this Rom, as my device had it before on a gingerbread Rom; namely, the battery charge level never seems to change. It always seems to be at 100% right up until it drops dead, no warning. Actually, that's not entirely accurate, because if it runs out, and I charge it and unplug while the charge shows a number less than 100% the battery icon will continue to show "charging" until 100% (even though unplugged) and then stay there.
When waking the tablet up it takes a couple of seconds to reconnect to wifi. Any notifications coming in will slow it down for up to a couple of minutes. I've noticed that if I try and use it during this time I occasionally "overload" the device, and end up with it rebooting. My best advice: wake it, give it a second to go from "no internet connection" to having found wifi, unlock the screen, and then wait about 1 minute before doing any heavy use until any notifications pop up; once you do that you're good to go.
If I think of or notice anything else hopefully I'll remember to edit this post.
Click to expand...
Click to collapse
After I leave it charging, it goes into the sleep of death I guess? I don't know if this is because I had some apps downloading in the background. Also, my auto rotate doesn't work. I don't know if there's a fix for it, but so far, I havent found any
but besides those 2 things, the rom works great!
I'm having a hell of a time getting drivers for Windows 7 installed. Can someone point me in the direction to the drivers and possibly driver install instructions? .
I have tried with and without USB debugging turned on. In device manager I see M3-chip with USB debugging on. The only thing I can figure is I have the wrong drivers.
I have a Nextbook Premium 8 SE.
TIA
need new drivers
ardy said:
I'm having a hell of a time getting drivers for Windows 7 installed. Can someone point me in the direction to the drivers and possibly driver install instructions? .
I have tried with and without USB debugging turned on. In device manager I see M3-chip with USB debugging on. The only thing I can figure is I have the wrong drivers.
I have a Nextbook Premium 8 SE.
TIA
Click to expand...
Click to collapse
Im having the same problem need help here guys i just got mine yesterday it looks like the newer ones has different software in them or are updated.in drivers it only shows m3-chip and will not in stall on window 7 or xp.
Link is broken
Conect11 said:
ok, so far so good. The Rom is very responsive, Google Now is working well. Only thing to note, which I should have known: Take out your micro sd card first! I ended up corrupting mine when I flashed the Rom. (And guess where I had everything backed up too? = fail)
But again, other than that, this Rom is awesome
Click to expand...
Click to collapse
Hi Connect11 great job and thanks for collecting the information for us, can you please provide a new link because the current link is broken, I want to test on my Nextbook 8SE.
arnelpabustan said:
Hi Connect11 great job and thanks for collecting the information for us, can you please provide a new link because the current link is broken, I want to test on my Nextbook 8SE.
Click to expand...
Click to collapse
Good job gettin stuff together...i been trying to make it easier for folks to understand all this in the official nextbook 8se root thread. Info is so jumbled and most people dont read through the thread far enough to make sense of what they've just downloaded...lolz. anyways good work and heres a link to another great JB rom for this tab....big props to OMA for his work on this. I been runnin it for a 2 months now and i love it!! http://forum.xda-developers.com/showthread.php?t=1903745 This one can be tricky with the kernel and the system image so please follow directions carefully if you decide to try this rom...i had issues with bricks (my fault of course) but nothing the rk flasher tool cant fix. And of course backup, backup, backup, nuff said:laugh:
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
A bit off topic but im curious as to what recovery other nextbook 8se owners are using?? Any input would be greatly appreciated.
How to root my Xperia u st25i?? Pls help me
Sent from my ST25i using xda app-developers app
Help!
"STEP 1: Make sure you have the device drivers installed for your Nextbook on your computer.[/B] I'm using a Windows 7 64 bit desktop. I imagine that other Windows desktops pre Win 8 will be similar. If you're using Linux, I believe that drivers aren't necessary. But hey, if you've installed Ubuntu, Arch Bang, Puppy, etc, you've probably got this figured out anyway."
I'm stuck on this step! How do I find and install the drivers for the Nextbook 8? I went to the Device Manager already, I found my "Unknown Device", and I picked "browse my computer for driver software", but every time I pick the file to update it from, it says "windows could not find driver software for your device". Please help me!
thank you for the rom I'll give it a try
Nextbook Premium 7
Do they have jelly bean on Nextbook Premium 7.
cant turn on
hey, i turned my tablet off, and now it wont turn on :crying: I dont know if I'm doing something wrong, but it just wont power on... any help would be great!
deanfranks21 said:
hey, i turned my tablet off, and now it wont turn on :crying: I dont know if I'm doing something wrong, but it just wont power on... any help would be great!
Click to expand...
Click to collapse
Same thing happened to me, you'll just have to wait a day or two for the battery to completely die, then hold the power, and as soon as the screen comes on, plug it in, hope this helps! :good:
so far so good, g-sensor wouldnt work with both included kernels so i flashed the kernel from Finless Bob's ICS Rom for NEXT8P12 and it's working again except i cant use the OC settings that kernel from this ROM has.
Only issues:
Wifi is a bit inconsistent
Apps can't download to system memory, there has to be an sd card present
G-Sensor isnt working (have to use kernel from Finless Bob's Next8P12 ROM)
Nothing else yet
is there anyway i could use the g-sensor driver from the other kernel while still using the kernel from this rom, if that makes sense.
Thanx.
going great untill
cant find subfoldr NXTBOOK8ROOT in my computer aso the zippyshare file in the link doesnt work pleaase help
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
deanfranks21 said:
hey, i turned my tablet off, and now it wont turn on :crying: I dont know if I'm doing something wrong, but it just wont power on... any help would be great!
Click to expand...
Click to collapse
there shul be a reset button in the back of the device if not you can boot it into recovery mode by holding the power key and voulme down key AT THE SAME TIME then u can wipe everythng and reboot your device:good:
midnite48161 said:
Im having the same problem need help here guys i just got mine yesterday it looks like the newer ones has different software in them or are updated.in drivers it only shows m3-chip and will not in stall on window 7 or xp.
Click to expand...
Click to collapse
Same here
Sent from my Next8P12 using XDA Premium HD app
swordjamie said:
Same here
Sent from my Next8P12 using XDA Premium HD app
Click to expand...
Click to collapse
Same for me as well... and it's really annoying me... I can't root it... so until someone finds a fix... I guess we're going to have to wait, also every time I go the whole driver thing, it says it can't find the drivers too. I don't really care to root it... but... I just wanted to try it.
Conect11 said:
ATTENTION / WARNING / ACHTUNG!!!!!!!
Efun (distributor of what we know as the "Nextbook Premium 8SE") in fact sells two different tablets marketed under the same name. This rooting method will ONLY work with a Nextbook Premium 8SE running a Rockchip processor.
**Am very sorry if this has already been posted, searched and did not find anything.**
Soon after purchasing my Nextbook Premium 8 se I learned that many Roms, apks, etc. that I couldn't find via Google (in English, anyhow) are easily found in Italian.
Which brings me to what I found today
androidworldDOTit/forum/mediacom-smartpad-810c-381/%5Brom%5D%5Bics-4-1-1%5D%5Bxteam-4-0-jellybean%5D%5Bmediacom-810c%5D-67171/
Run that through Google Translate if like me you don't speak a word of Italian.
All right, time to sit down and write a guide to doing this. First things first: I didn't do any of this work! People like Devmonkey, Sunnyboy167, deeno33, and FinlessBob, (over at Freaktab) and Xteam at Android World Italy are the ones who've put in the legwork and hours to make this stuff possible. I'm just gathering their work in to one place.
Before you begin: Back up all your things if you want to keep them!
Also, remove your micro sd card from the Nextbook. I darn near fried mine because I didn't.
Next: You know the drill. You're a big boy, (or girl, or whatever. I'm not here to judge) I, nor anyone else is responsible if anything bad happens to your device, to you, your happiness, or your hard earned money or your time. YOU are choosing to root your device and install Jellybean on to it and YOU assume all responsibility. Cool? Also, this will probably void your warranty. But let's face it, if you're here, you probably don't care too much about your warranty anyway. Let's get rocking.
STEP 1: Make sure you have the device drivers installed for your Nextbook on your computer. I'm using a Windows 7 64 bit desktop. I imagine that other Windows desktops pre Win 8 will be similar. If you're using Linux, I believe that drivers aren't necessary. But hey, if you've installed Ubuntu, Arch Bang, Puppy, etc, you've probably got this figured out anyway.
Turn off your Nextbook Tablet Connect the micro usb cord to it, then hold in the volume up and down keys while plugging it in to your computer.
"NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 2: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 3: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 4: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine." ~Sunnyboy167
Ok, now that the device drivers are installed you'll want to download the file linked from here: zippyshareDOTcom/v/60864398/fileDOThtml
Sorry, I have less than 10 posts, so you'll need to convert the dots to, you know, dots. I get why the site does that.
Scan that thing for any nasties, and then unzip it wherever you'd like. (I used my desktop) Open it and click on the folder "Mediacom 810c" Inside you'll find a file named "Rk29update.exe." Open it. You'll see a box like this:
See attached picture
That is what it will look like if your tablet is not hooked up to your computer. So if it isn't (which it should be, since I never told you to disconnect it) reconnect it now.
Click the box that says "loader," then click "Formatta!!" Which, as you might have guessed is Italian for "Format." No going back now, kid.
Let the thing run its course, it'll take a couple of minutes. Once it's done, click the box that says "Aggiorna!!" This will install Jellybean on to your Nextbook. Be patient, as this will take a few minutes. You'll hear your computer make the "device disconnected" sound, and you'll be all set. You can unplug your Nextbook from your computer now.
First boot up of the device on Jellybean was a touch slow for me, but don't panic. Once you've gotten through set up the Rom runs incredibly smooth and fast. The first screen you'll see will be the welcome (benvenuto) screen. You can select English (or your preferred language) from the drop down menu. From this point on it should be smooth sailing. Google Now works like a charm, Project Butter seems to really make a difference on this tablet, camera works, notifications work, everything seems good. There are minor bugs here and there, but nothing Earth shattering.
One last thing: for a $99 budget "craplet" from Big Lots, you could do a lot worse than this tablet. I've found it pretty sturdy, highly customizable, and generally responsive and fun to use. I also own a Nexus 7, and while this clearly can't touch it spec wise, it's definitely a fun second device to keep around.
Click to expand...
Click to collapse
can you post a different link it says file dows not exist on this server
---------- Post added at 06:01 PM ---------- Previous post was at 05:51 PM ----------
imthatkiid said:
Same for me as well... and it's really annoying me... I can't root it... so until someone finds a fix... I guess we're going to have to wait, also every time I go the whole driver thing, it says it can't find the drivers too. I don't really care to root it... but... I just wanted to try it.
Click to expand...
Click to collapse
I foiund a way around it you click start go into ur control panel and click system then to the side it should say device manger at the very top click it find where it says m3-chip left click on it chose update driver software click browse my computer click let me chose from a list of my drivers click show all devices click next click have disc then browse then chose the rk29 driver/win/64/rockusb click ok there u go
---------- Post added at 06:37 PM ---------- Previous post was at 06:01 PM ----------
I got my device to be an rk29 device but its not coming up on the screen when the device is connected please help me
I'm trying to root my tf700, and although I have Unknown Sources checked, and the USB debugging checked, I still get the error that it needs to be turned on. And then I get the daemon is not running message. Is there another way to root my Infinity?
Also, my Build is 9.4.5.21, so I'm thinking of nvflash. The problem is that although I've unlocked the bootloader, I still see I have a firmware update pending. I'm afraid to install the upgrade, lest it moves me to the later build, and thus prevents me from using nvflash.
Can anyone offer some help on my inability to root? And advice on the firmware/nvflash situation? Thanks...
Which root process are you trying to use?
1click root or debugfs?
Coming from the ground up
Thanks for the reply. I'm using the dbugfs.
Reggie777 said:
Thanks for the reply. I'm using the dbugfs.
Click to expand...
Click to collapse
Sometimes switching usb plugs on the PC works.
I know a lot of folks in the forum have said that trying on a different PC also works.
Are you working with Win7 or XP or something different?
It says Daemon isn't running. And then next screen it says Rooting failed. System partition was not found
I'm using Windows 7.
Please excuse the stupid question.. but should the tablet be on a certain screen while this is going on? Or should it be off?
Reggie777 said:
It says Daemon isn't running. And then next screen it says Rooting failed. System partition was not found
I'm using Windows 7.
Please excuse the stupid question.. but should the tablet be on a certain screen while this is going on? Or should it be off?
Click to expand...
Click to collapse
I suggest you re install android SDK. Download from here. Only install packages with android in it (should be 2)
http://developer.android.com/sdk/index.html
Reggie777 said:
It says Daemon isn't running. And then next screen it says Rooting failed. System partition was not found
I'm using Windows 7.
Please excuse the stupid question.. but should the tablet be on a certain screen while this is going on? Or should it be off?
Click to expand...
Click to collapse
Hmmm,
The tab should be on and connected as MTP I believe.
Is the tablet seen when clicking on the computer icon or in explorer?
Also check device manager to see if the tab shows up in there.
If the tab is plugged into a front USB (if using a Desktop PC) try a port on the back if available.
Oops edit!
Did you try downloading and installing the PCSuite from the Asus website?
Thats OK said:
Hmmm,
The tab should be on and connected as MTP I believe.
Is the tablet seen when clicking on the computer icon or in explorer?
Also check device manager to see if the tab shows up in there.
If the tab is plugged into a front USB (if using a Desktop PC) try a port on the back if available.
Oops edit!
Did you try downloading and installing the PCSuite from the Asus website?
Click to expand...
Click to collapse
I did the SDK install.... no difference. It is showing up on the PC. But I have not downloaded the PCSuite from Asus, since I've been afraid of going there, and getting tied up with the Sync issue. I had read that if I had the sync on, they can track the tablet along with reading the info, and even doing some extreme things if they felt I deserved it. I didn't know if I was supposed to register it before I unlocked it. or what. The odd thing is that I have unlocked it successfully.
i've also moved the usb connector to different ports but with the same result. I do notice, that now, it says after saying daemon is not running, that daemon started successfully. But then, it says Rooting Failed.... System Partition could not be found.
Is it possible to install nvFlash on an unlocked device, but one that is not rooted?
Lemme see here...
Ur right clicking the .bat file then running as admin then?
http://androidroot.mobi/t3_nvflash/
...on the mobi blog it just says to be unlocked and have nerves of steel.
I had a nightmare getting the Win 7 drivers to install.
I eventually gave up and used Linux...
Nerves of steel is right. I'm about to try the procedure on another computer. Hmmmm. Is the sync app from Asus relatively safe to use? someone said it worked for them after they installed it.
If I'm sweatin' it now,... can you imagine how I'm a tremblin' with the nvFlash install ahead of me?
My ol' gTablet never gave me this much stress. :highfive:
Reggie777 said:
Nerves of steel is right. I'm about to try the procedure on another computer. Hmmmm. Is the sync app from Asus relatively safe to use? someone said it worked for them after they installed it.
If I'm sweatin' it now,... can you imagine how I'm a tremblin' with the nvFlash install ahead of me?
My ol' gTablet never gave me this much stress. :highfive:
Click to expand...
Click to collapse
Man I know...I was always afraid to do anything at first.
I was pretty afraid of a 500 dollar lesson gone wrong...then one day I said "what the hell man up"
So here I am today a satisfied customer!
I have PC Suite installed, I had registered and unlocked so Big brother Asus had my number from the beginning.
Seems like PC Suite is the only way in certain cases.
Coming from the ground up
Well, it did not work on the second computer... And now, what I get is, daemon does start, and the cursor moves to a new line, and just blinks back at me ... ouch. Didn't I just feel silly waiting for 30 minutes, and nothing happened? Reminded me of the cat that just sits and watches the curtains move. Ah well. So, I am unlocked, but also unrooted. Does anyone happen to know if the one click app works with our Infinity? I getting desperate enough to pay. :crying:
HTTP://forum.xda-developers.com/showthread.php?t=1824713
Was wondering if you had seen this thread...
I was reading thru the debugfs thread and there it was.
Forgot all about it...there's got 2 be an answer.
We need to get you fixed up!
Coming from the ground up
I'm Rooted!
Whew!... Thanks to all who responded and pointed me in the right direction. It was not pretty. I encountered a number of errors. I'll list them below, in case anyone else is having the same problem/s I had.
1. After you choose "1" from the debugfs menu, it ends up saying "Rooting failed. System partition was not found." Check to see if the device is being seen. How you do this is go to the same directory you unzipped the files you downloaded, and start a command line from this directory. The question was how? Press the Shift key, while right clicking on the directory where adb.exe is, and you will get a window with a prompt. This is a very useful window. type "adb devices", and you should see some datafline" and then a code number followed by "device". Naturally, mine was not there. If this is not there, type " adb kill-server" Then "adb device", and hopefully, if the stars align correctly. You will see your device there with it's code. If not, then you have to check the device manager, and check the drivers. To do this... Go to the start box in lower left of window bar, and type "device manager". The file will be listed, click on it. and you should see your device listed. I found it twice.. once by itself using, and again under Portable Devices. I clicked on these, and updated the drivers to the ones in the same directory with the files you unzipped. Hopefully that will work. If it doesn't you might have to uninstall them, and reinstall them.
2. After all that, you still might not get past option 1 in the menu. Possible error, "more than one device found". So, you have to check if anything else is interfering. [I'm not sure if this was the culprit but as soon as I removed my Zunes, I was good to go].
3. And then option 1 gets a little further along and goes off to never never land. So... I moved to option 2, Manual entry of the partition. It warns you to not go into this section if you are not sure. Naturally, I shook off my cold sweat and plunged ahead. The address I used, from another post was "/dev/block/mmcblk0p1", and that seemed to work.
4. Then.... the app got stuck trying to reboot the device. You can check if it is seeing the tablet by the "adb devices" check. If is not, you have to fiddle with the drivers again.
5. Finally, after a number of tries, and a lot of colorful venting... it went through... and I was rooted.
Whew! It was ugly... But finally. :fingers-crossed:
I relate my story to encourage anyone who might be discouraged by the roadblocks. Hang in there, and as they say... "Never Give Up. Never Surrender!"
Now to tackle installing nvFlash. I have my blankie all ready.
AWESOME!
Way to go slugger!
So was another media device "Zunes" plugged up in another port?
You have done well!
It's pretty fulfilling to wind thru all this and come out with a desired result.
Thanx for the low down.
It will mean a lot to others having trouble.
Thumbs raised kiddo!
nvFlash adventures...
Again, thanks to the wonderful support from the wonderful folks here.:highfive:
Just to end on an even higher note, I wanted to add that I was able to install nvFlash, and generate my "Resurrection Files". I don't know if this is allowed on this forum to include a link, but I followed this video
http://www.youtube.com/watch?v=J3ypzUaKxvo&feature=colike
which seemed to anticipate some of the very same roadblocks I encountered. So, now, I can look about that "firmware update" notification that keeps flashing in my bar.
My Infinity adventure continues...
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Original link: I don't have rights to place URLs in as I haven't posted enough here. If a moderator can add the link here, I would appreciate it.
Original text (from Google Translate):
Code:
All along, only heard Surface Pro can run Ubuntu and Android. But never seen someone real up and running, often took a running Live CD boot to coax interface, now Rerede.com released China's first support for Surface Pro Android system. Support the Android installed on your machine up. And it can coexist with your Windows!
Working conditions:
· Touch
· Keyboard
· Camera
· Gravity sensor · WIFI
· Other
Not supported:
· Bluetooth
Compatibility:
· Support and native dual-boot Windows 8
• The need to disable Secure Boot
Data is priceless! Please make the necessary data backup before installing! We do not assume any responsibility for loss of data!
Unzip password: rerede.com
Copy the code
Preparation:
In a hard disk to free up more than 1G unallocated space, 4GB recommended
Installation:
1, decompress, burn to use UltraISO to live.img U disk
2, disable SecureBoot
3, the use of U disk boot, select the third item, manually install Android4, tips Choose disk to install Android, select the disk you want to install, I chose Surface of SSD (1),
Tips Do you want to preserve Windows and dual boot (if dual boot Windows), press Y
5 Tips Do you want to resize Windows to make more space (whether android resized), press N
6 Tips Install GummiBoot BootLoader (using gummiboot), press Y
7, when prompted Enter boot menu timeout (boot menu wait time), I chose 5
8, press Enter to install, the installation process approximately less than 1 minute.
9 After the installation is complete, unplug the U disk, enter the restart to complete the installation reproduced or quoted, please indicate from the hot community , Rerede.com
Pictures attached
That looks really nice. Hope they figure out the bluetooth as well.
JLIT99 said:
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Click to expand...
Click to collapse
Thanks for this, it's really working, although far from perfect. Fastest touch response on android =))
Here's the direct link to download: http://rerede.com/surface.android-ia.rerede.com.vPRC2.zip
Could you get the front Cam working?
Turns out that front cam doesn't run by default. I fixed it along with some other things like youtube playback, play store etc. It's almost perfect now
Surface 2 Pro
Has someone tested these instructions on a Surface 2 Pro ? Working ?
Unfortunatly, I have a Surface 1 Pro and encounter the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
Gummiboot the EFI bootmgr does not install. Maybe it would be possible to install it manually.
Secure Boot is disabled, and I also tried different USB sticks and the original unmodifed Android-IA image. No success.
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
ToniSoft said:
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
Click to expand...
Click to collapse
What do you mean by using Refined?
how do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
zcrugby,
How do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
Click to expand...
Click to collapse
You need to use a USB hub, so that you can have you USB stick and USB keyboard attached simultaneously. This installation program does not recognize the Surface keyboard, but it does recognize a standard USB keyboard.
I, however am having a different problem. I get (almost) to the end of the whole process, after it says press enter to continue with the installation and does a bunch of stuff, but then give the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
It was mentioned earlier in this thread, but no one seemed to shed any light on the subject. In other forums some have suggested that it was just an incompatible memory stick, but I have not tried multiple memory stick by different manufactures...
Others have suggested that you need to disable AHCI and instead run in IDE mode, but with the Surface Pro 2's woefully underwhelming BIOS, I haven't yet figured out how to disable AHCI. There's some that say that simply changing some registry keys will do the trick, but I haven't gotten that to work yet, and I don't have extremely high hope for it when I do.
Does anyone here have any thoughts about this error??? Anyone run into it who has successfully gotten it working after seeing this error? If so, how?
Thanks!
please help: Fatal Asertion Failed... (status 100)
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Quixtrike said:
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Click to expand...
Click to collapse
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
ozkaya said:
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
Click to expand...
Click to collapse
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Quixtrike said:
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Click to expand...
Click to collapse
1- No I'm not using grub, in fact I also tried to daisy chain grub booting gummiboot booting Android and it doesn't work. I'm using native EFI entry.
2- I don't have it written up somewhere, I did it as I was reading and trying. But basically, you first need to install Ubuntu with dual boot with Windows. Have a look at the /boot partition, you will see the gummiboot files and config files there. Then research command line parameters for efimootmgr program and create the entry for the gummiboot file in /boot partition.
3- Just use google for this one, you can select advanced startup options somewhere from the settings in Windows 8 fancy menu. You can also create desktop shortcut for this. Once you completed Step 2, you will see Windows, Ubuntu and Android entries there. Since, Windows will be default, when you would like to switch to Android, you just double tap the shortcut and select Android. In Android you just power off and next restart will be Windows again. No keyboards, mouse etc needed. I also got the front cam and youtube playback working. Only bluetooth doesn't work.
Surface Pro 2
Anyone got this to work with Surface Pro 2? I am thinking of getting one, and if it could run android, im definitely getting one!
(I don't really see the point of getting Surface 1 when the 2 is out now)
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
when turning trusted platform module on and off it works sometimes
Jacob.Halsey1 said:
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
Click to expand...
Click to collapse
I'm having the same problem over and over .. still no luck
Greetings to all the developers and registered users on this site... Yes, this is my first post, but I read here pretty often and I used the search function, trust me! Seriously, I've tried all I could and I am at my wits end, but this is technology, we can't let it own us, we gotta continue owning it and that's what online communities like xda help us do, so thanks for all your past, present, and future contributions here. So I got this Metro PCS Kyocera Hydro Wave (C6740N) that I can't factory reset for a number of reasons, but mainly because I believe that there is either no boot-loader or no recovery partition as a result of Metro PCS flashing the ROM...
Anyway, lets get to the juice:
- Device powers on/off, but no combo of Vol -/+ and Power buttons bring up a recovery menu or anything (holding any combo down just boot-loops)
- Device has no SIM and no micro SD card, and the battery is not removable
- Device is locked... Like, pattern-locked/google account info/too many attempts/yada yada yada
- Device has no data and no WiFi connection active, so I could not use the google account to get past the lockscreen
- Device does not have USB debugging enabled/Google drivers for ADB do not work (Windows 7 auto-detects when I plug in the phone and installs a generic Microsoft driver which cannot be removed even after uninstalling the device, and also I pointed the Device Manager to the correct Google drivers I installed with the Android SDK Tools, as well as the Samsung Naked Universal Drivers I found on this forum, and Kyocera ADB drivers I found through Google which all failed, Windows returned a message stating that the most up-to-date or best driver for this device is already installed)
What I've tried (everything possible really):
- Hard reset/Recovery from phone: FAILED
- Connect to Linux and install ADB, then tried running the adb shell, adb devices, fastboot devices, etc but phone not detected: FAILED
- Connect to Windows 7 and install ADB (Android SDK Tools), I literally checked every single box and installed Platform-tools, google drivers, everything, got to the command prompt as admin, cd to the ADB directory, ran same commands as in linux, also tried commands on several forums and posts like adb shell rm /data/system/gesture.key to remove the lock but everything: FAILED
- Connect to Windows 7 and attempt to install proper drivers using RootGenius, MoboRobo, PDAnet, and several other suggestions which all were oblivious/unable to detect the device despite Windows recognizing it, so they all: FAILED
- Connect to Windows 7 and attempt running ADB through a Cygwin terminal, but the command "sudo" was not recognized/not valid, so: FAILED
- Connect to Windows 7 and use XRYViewer to extract data from the phone, possibly to see the system files and get an actual understanding of what everybody is saying you need to mount from the recovery partition, but no clue how to use this, since I can't find an XRY file in the internal storage, so: FAILED
- Connect to Windows 7 and access data/recover data from device using "Wondershare Dr.Fone for Android" and "iLike Android Data Recovery Pro" but both programs instructed me to enable USB Debugging, which is not possible, so the both also: FAILED
Despite this being my first post, I have scoured the forums here in addition to every other forum and webpage regarding this issue as well... There just isn't much about this phone except negative reviews, and I have come to the conclusion that on this particular model phone, I am out of options... I have a paperweight... I'm not very familiar with Android... So please correct me if I'm wrong...
Any input?
I'm curious if there are any options at this point, I have been trying to get through to this phone on several computers for the past couple days and it is frustrating me... Any input from the community would be much appreciated...
Mojo2XL, I guess you did not find an answer?
Mojo2XL said:
I'm curious if there are any options at this point, I have been trying to get through to this phone on several computers for the past couple days and it is frustrating me... Any input from the community would be much appreciated...
Click to expand...
Click to collapse
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
eenuckols said:
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
Click to expand...
Click to collapse
may be this:
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I found code in internet, but may be it works? can't check, my "wave" comes to me from USA by post for a few weeks..
barabeka said:
may be this:
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I found code in internet, but may be it works? can't check, my "wave" comes to me from USA by post for a few weeks..
Click to expand...
Click to collapse
doesnt work.. you can only get to emergency dialer which can only b used to make emergency calls
elliwigy said:
doesnt work.. you can only get to emergency dialer which can only b used to make emergency calls
Click to expand...
Click to collapse
okay. i will try something, when my phone will come. is your Wave locked?
barabeka said:
okay. i will try something, when my phone will come. is your Wave locked?
Click to expand...
Click to collapse
i bought another phone and they threw it in free but it has a pin code lock so i cant even get to google screen to bypass frp as im stuck at pin lockscreen and these darnphones have no recovery..
i doubt ull figure out a way as im real savvy with this stuff lol theres no recovery to boot into in order to reset and no way to update tje phone wothout knowing the pin code
any luck? i cant believe this thing is this locked down. makes apple look like chils play
warriorpluto said:
any luck? i cant believe this thing is this locked down. makes apple look like chils play
Click to expand...
Click to collapse
i believe it can be done with a pc
Did you happen to get the files the other member posted that was only available for eight days?
Mojo2XL - Sort of.
I saw a youtub video (sorry no link) that says there was a OTA update that changed the phone's firmware that solved all the problems mentioned here. Thing is I have no carrier and cannot find this new firmware, but, I am still hunting....
eenuckols said:
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
Click to expand...
Click to collapse
I'm having the same problem, I have been trying to get this thing to hard reset for a week now. There has to be a way to reset this Hydro Wave.. Has anyone dealt with this thing?
Hey hold the buttons as follows volume- & power at the exact same time while your phone is off be warned if you phone was preowned you need the goole account originally activeated with that phone if you do not have that then your in the same vote as me i cant remember any of my gmail account info to my wave from when i had it active I have litterally tried every thing to recover the info and i still can't recover it
WhiteWolf77 said:
Hey hold the buttons as follows volume- & power at the exact same time while your phone is off be warned if you phone was preowned you need the goole account originally activeated with that phone if you do not have that then your in the same vote as me i cant remember any of my gmail account info to my wave from when i had it active I have litterally tried every thing to recover the info and i still can't recover it
Click to expand...
Click to collapse
That doesn't work on this phone the hydro wave from AT&T has factory reset protection so it cannot be reset using the volume down and power button reset
Any update?
dannybz said:
Any update?
Click to expand...
Click to collapse
let me work on this, been trying to master as many FRP bypasses as i can. I don't have the device but a client is in the same boat
I accidentally stumbled upon a something weird. I've managed to make the camera crash to the home screen somehow. I believe this was a result of holding both volume buttons and opening numerous menus while using the camera. My guess is that it overloads it after a certain amount of times and causes it to crash. I've gotten the android UI to crash like this before. I will try to recreate the scenario and update you guys on this. it's on a Kyocera Hydro Wave. Running android 5.0 I believe. Try going wild until the phone starts to lag. eventually stuff will crash and the lock screen may go with it. use this to your advantage and enable USB debugging as quickly as possible because it will reset itself after about 30 seconds. Someone else on YouTube has recently told me that it worked for them. I would look into doing that.
PhoneScrambler said:
I accidentally stumbled upon a something weird. I've managed to make the camera crash to the home screen somehow. I believe this was a result of holding both volume buttons and opening numerous menus while using the camera. My guess is that it overloads it after a certain amount of times and causes it to crash. I've gotten the android UI to crash like this before. I will try to recreate the scenario and update you guys on this. it's on a Kyocera Hydro Wave. Running android 5.0 I believe. Try going wild until the phone starts to lag. eventually stuff will crash and the lock screen may go with it. use this to your advantage and enable USB debugging as quickly as possible because it will reset itself after about 30 seconds. Someone else on YouTube has recently told me that it worked for them. I would look into doing that.
Click to expand...
Click to collapse
Is there anything a little more realistic possible? Lol, I can see an update available, can't connect to WiFi to update haha. The stuff they lock these phones with anymore i swear
I'm new to this forum, but NOT new to this site . I have visited here on numerous occasions seeking the help that needed . With that being said, I would like to offer a Bonafide, Tried and True way to factory reset the Kyocera Hydrowave . I KNOW that this work's for I have done in on numerous occasions for a friend of mine that works for Metro PCS ....
Step One: Completely power off the phone .
Step Two: Hold the Power AND Volume DOWN Buttons SIMULTANEOUSLY .
Step Three: DO NOT release any buttons, even when you get to the Boot Menu . (Very Important, If you don't do it right, you have to start all over lol ) .
Step Four: Once inside the Boot Menu, ONLY release the Power Button; or the Boot Menu will close and you have to start all over again .
Step Five: Use the Volume Down Button to Highlight the Wipe/Factory Reset Option .
Step Six: Use the Power Button to Select the option .
Step Seven: Watch the bottom of the screen for the progress, and then use the Volume Up Button to restart .
And there you have it . I hope that this helps out SOMEONE out there, because I feel good giving back for the help that I have received on here .
PS.( If you would like for me to post a Video Tutorial on this, can someone please tell me how to post the Video; I guess by me being a Newbie on here, I'm not allowed to do as of yet ) . If Anyone needs to contact me, as I'm not on here very often, my email is [email protected] .
LilAnt530 said:
Is there anything a little more realistic possible? Lol, I can see an update available, can't connect to WiFi to update haha. The stuff they lock these phones with anymore i swear
Click to expand...
Click to collapse
As unrealistic as it may sound it actually works Trust me on this. its similar to the LG attack which... is nothing but entering a long password.
betanews.com/2015/09/16/bypass-the-android-lollipop-lockscreen-by-entering-a-really-long-password
Just give it a go. it already worked for one dude on youtube. it takes a while but it honestly works. If you can get it, update the phone as soon as possible turn the screen timeout off and let it update. when the phone resets the update will install and you will be able to factory reset.
I mean it couldn't hurt. if you're locked out with no factory reset and ADB tools won't work what else can you do?