Related
Alright, So I recently just moved from an Evo to the epic. And I'm glad I did. The evo was great, But I missed having a keyboard and the epic hasn't dissapointed.
I have a couple questions though,
Rooting on the evo was super easy, I'm still confused on how to use the one click root for epic. People are saying it doesn't work? And I read on some website if you just want to change roms and change kernals just to flash a custom recovery onto it and don't root, because rooting will only let you get root-only apps.
Please? Explain on how to root with the one click root method because I'm Completely lost on how to do this for the epic 0_o
The one click root does work. I followed the instructions and my phone is rooted. I'm new to android and to rooting but not new to modding phones/computers/software. After rooting you can still download none root apps in addition to root apps. From what I've seen most of the rooting issues come from people not following the instructions or not truely understanding them. I haven't flashed to a new rom yet. I'm waiting on froyo. So I can't say for sure but its my understanding that you have to have root premissions to flash a custom rom.
Sent from my SPH-D700 using XDA App
As far as how to root with the one click root I installed the samsung usb drivers for my operating system (win 7 64bit) Note: after reading several posts the driver installation takes a little bit. Click on the installing drivers message to bring up the install window. I let the installtion run for almost 15 minuted and it still gave me an error but after turning on usb debbuging on phone connecting with usb, mounting sd card, and running the one click root my phone restarted and I was rooted. If you search other posts you'll find more detailed instructions.
Sent from my SPH-D700 using XDA App
Correction. You don't have to root to flash a rom I don't know what I was thinking when I typed that. All you need is clockwork recovery.
Sent from my SPH-D700 using XDA App
The only problem you'll encounter, if any at all, with rooting is with driver installation. If u follow the guides tho and don't try to experiment, u shud be good to go. These roots are one click as well as it involves running a simple bat file. Some phones are more finnicky than others, but they shud give u no trouble if u know what ur doing. Good luck.
And yes, the keyboard on this rules
Sent from my SPH-D700 using Tapatalk
I don't know how it got updated, but it did. I wasn't running a custom rom or kernel or anything. It was just a stock a500.
Well now most of my apps force close, can't connect to Xda forums, wallpapers don't work, wifi barely works, etc.
Should I go back to bestbuy and exchange it? I've had it for less than a week. I just want one that works! I love this tablet though.
Fyi, order and chaos is pretty damn fun on our big screens, as is Contract killer zombies I miss playing them lol.
Any helpful advice is welcomed and thanked!
Sent from my SAMSUNG-SGH-I997 using xda premium
Was it running 3.0 or 3.1 when you got it? If so it should have prompted you and asked you if you wanted to update.
The easiest thing, especially if you are new to the world of android, would be to exchange it at Best Buy. There are ways of fixing it, but that would involve reverting back to an older honeycomb version, rooting it and possibly installing a custom ROM.
Edit - It appears you are not new the the Android world. My bad...... You probably know a lot more than I do!
Was it always giving you errors, or did they all of a sudden just pop up?
It never promoted anything, it just asked me to update acer drivers or whatever so I did. Next thing I know I'm on 3.2
I never got errors until 2 or 3 days ago. I can't even post on the Xda app now!
I'll probably just exchange it. Ducks about my ghost armor though
Sent from my SAMSUNG-SGH-I997 using xda premium
Why not just factory reset it?
Sent from my GT-I9100 using xda premium
Would that take it back to 3.1?
Sent from my A500 using xda premium
skatin707 said:
Would that take it back to 3.1?
Sent from my A500 using xda premium
Click to expand...
Click to collapse
No it wouldn't!
Please ignore the man behind the curtain!
I think you got the new magicaly updating Iconia feature I heard about.
You'll have to downgrade before you can do anything.
http://forum.xda-developers.com/showthread.php?t=1276227
kjy2010 said:
No it wouldn't!
Please ignore the man behind the curtain!
I think you got the new magicaly updating Iconia feature I heard about.
You'll have to downgrade before you can do anything.
http://forum.xda-developers.com/showthread.php?t=1276227
Click to expand...
Click to collapse
Wonderfully useful post.
I was never promoted for an Android update, just acer updates. I've only had this thing for a week, not to mention i've never "officially" updated an Android devices.
I'm aware I would have to downgrade. How difficult is it? It seems pretty simple, but I've never done it before. Is all data wiped when you downgrade?
Sent from my SAMSUNG-SGH-I997 using xda premium
The acer update was the android update.that is how it works with embedded devices.
Ooops.
Downgrade then wipe and install a rooted 3.2 you will be all happy again I promiss
skatin707 said:
I don't know how it got updated, but it did. I wasn't running a custom rom or kernel or anything. It was just a stock a500.
Well now most of my apps force close, can't connect to Xda forums, wallpapers don't work, wifi barely works, etc.
Should I go back to bestbuy and exchange it? I've had it for less than a week. I just want one that works! I love this tablet though.
Fyi, order and chaos is pretty damn fun on our big screens, as is Contract killer zombies I miss playing them lol.
Any helpful advice is welcomed and thanked!
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
First of all, please remove any task killers or "battery savers" you're using. These are pretty terrible for any android OS newer than 2.1. Try to stay away from them. You can get away with "passive" ones like as an example, Watchdog. But nothing that actively shuts down processes and such.
This isn't supposed to be possible, but do you happen to have any apps auto-moving other apps to the microSD card, or are you using any apps to do this manually? By design I don't think that can even be done inside of Honeycomb, but I'm aware that some apps 'force it'. If you do, move any and all apps on the microSD card back to the internal storage of the A500 - then remove the offending 'mover' app.
Stupid question, but have to tried powering the tablet off and back on? If not, let's try that first, shall we?
Second thing - if it's still force closing when it comes back up, try using the reset on the side of the unit. What I want is basically to have the tablet hard reset (the equivalent of removing the battery for a few seconds).
To do this put something in the little reset hole for 10 seconds or so while the unit is on, so you can see it reboot. Once it turns off you can remove the item from the hole.
Still force closing apps? Alrighty then, moving on:
If you are using a completely stock A500 (and yes, I did read that you said you are), then just factory reset it and you should be alright. It won't downgrade to 3.1, but why would you want it to? 3.2 is working great for many of us.
I'd love to get to the bottom of your force closes. But alas, that may be just a bit much to deal with for a new user so go ahead and do the factory reset.
To do a factory reset, go to Settings and then Privacy and the option is in there. I would remove the microSD if you have one inserted (it's not necessary, but just to rule anything out).
Since it's only a week old hopefully you don't have too many apps or settings invested in the tablet.
So to summarize:
1. Uninstall any and all task killers or battery savers
2a. Make sure you don't have any programs automatically moving apps to the microsd. Move any apps you have installed to the microSD back to the internal storage
2b. Remove the microSD card
3. Power cycle the device (then 4 if 3 doesn't work)
4. Hard reset the device (then 5 if 4 doesn't work)
5. Factory reset the device
If you factory reset and STILL get force closes when you're back up then unfortunately there's something wrong with either the core software (maybe a bad update) or the hardware. Return it in that case.
Good Luck. Please let me know how it goes.
I'm not new to Android, just new to this device.
I never use task killers.
No app2sd stuff.
Rebooted multiple times.
I've removed the SD card and even tried a different one.
Hard resets don't do anything for my problem.
Why would I want 3.1? To root it. 3.2 is useless to me without root. Apps like drive mount make this tablet much more useful, but they require root access.
Sent from my SAMSUNG-SGH-I997 using xda premium
I would try to downgrade - http://forum.xda-developers.com/showthread.php?t=1276227
From there you can install your own custom ROM. If it still gives you issues, factory reset (or load a ROM that looks stock) and exchange it
skatin707 said:
I'm not new to Android, just new to this device.
I never use task killers.
No app2sd stuff.
Rebooted multiple times.
I've removed the SD card and even tried a different one.
Hard resets don't do anything for my problem.
Why would I want 3.1? To root it. 3.2 is useless to me without root. Apps like drive mount make this tablet much more useful, but they require root access.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Exactly! Currently there is no root for 3.2 on our device. Hence having to downgrade to 3.1, root, and install a pre-rooted 3.2 ROM. IMHO the stock based 3.2 ROMs are the most stable, and trouble free.
If you're not new to Android you should have no problem following the procedure.
Timmydean did a tut that's a little easier to follow here:
http://forum.xda-developers.com/showthread.php?t=1307539
I'll give it a go. Will I need a pc? I just sent my laptop to dell for warranty repairs /facepalm
I was about to install a custom rom when I found out I lost root anyway lol.
Sent from my A500 using xda premium
skatin707 said:
I'll give it a go. Will I need a pc? I just sent my laptop to dell for warranty repairs /facepalm
I was about to install a custom rom when I found out I lost root anyway lol.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Althought it is easier to do it with a computer (to get the files). You can download them straight to your tab, transfer the files over to your external SD card and away you go! I've installed a few ROMS without the help of my computer. Afterall, that's part of the reason why I got a Honeycomb tab, so I wouldn't have to rely on a computer unlike other "tablets" on the market LOL!
skatin707 said:
I'm not new to Android, just new to this device.
I never use task killers.
No app2sd stuff.
Rebooted multiple times.
I've removed the SD card and even tried a different one.
Hard resets don't do anything for my problem.
Why would I want 3.1? To root it. 3.2 is useless to me without root. Apps like drive mount make this tablet much more useful, but they require root access.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Ah, sorry about that. You said you were running completely stock. Didn't know you had any interest in rooting.
Good luck.
skatin707 said:
I'm not new to Android, just new to this device.
I never use task killers.
No app2sd stuff.
Rebooted multiple times.
I've removed the SD card and even tried a different one.
Hard resets don't do anything for my problem.
Why would I want 3.1? To root it. 3.2 is useless to me without root. Apps like drive mount make this tablet much more useful, but they require root access.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Maybe it would help if you remove all apps that require root access, FCs may be caused by them since you don't have root anymore. Actually you don't need root anymore to mount NTFS hdds - 3.2 took care for that. The one thing I need root now is to map the keys of my USB keyboard to my liking. Probably I'll flash a custom kernel when I feel the need for OC but still it runs everything I throw at it.
Sent from my A500 using XDA Premium App
I uninstalled them, or most of them at least. I'll continue looking for root apps.
I've got my hdd formatted to fat32 but my tablet still doesn't see it. I really wish it could, that's why I want drive mount to work so badly. I'm not sure why it's not working though. It did before, but now that there are files on it won't. If I can fix that, I'm fine waiting for ICS.
Sent from my SAMSUNG-SGH-I997 using xda premium
so are you stuck with the stock bootloader? or can you download CWM and flash an alternate recovery? if you can do that (does that apk require root access??? I honestly do not know???) then there are all the stock and rooted OS's here on XDA somewere? if CWM does then cant you still get one of the older OS's (rename it update.zip) and flash it with the stock recovery image? if any of this is simplistic I appologize just trying to help, I should probably stay out of it and let the experts help...
I'm stuck with the stock bootloader. I never got a chance to flash a recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
Well, after trying to charge my Nexus in the car, it appears the USB has gone kaput and only charges the device now (although it doesn't actually say it's charging, the percentage just increases). Anyway, as it would appear a return is in order, I'd like to remove the unlocked sign on my bootloader to be able to send it back, but without USB, the conventional fastboot/adb method is out the window. Anybody got any suggestions? Thanks.
Bump, per chance?
Use wugfresh toolkit and Hitt the oem lock option
Sent from my Nexus 7 using xda app-developers app
The OP clearly said they are looking for a method that doesn't require USB. So your method suggesting he use wugs toolkit isn't the answer he's looking for. And honestly I don't think there is a way to do it without USB capabilities.
Sent from my Nexus 7 using Tapatalk 2
I don't think you can.
I'm not exactly a pro at this, but as far as I know you need fast boot mode to lock/unlock the bootloader.
I installed twrp last night (got bored with cwm) and noticed it has a command line section. I don't know if you could use this to lock the bootloader. If you look up one of the manual guides to locking/unlocking maybe try whatever it says to type in a terminal there?
The only problem is then you couldn't put back the stock recovery.
Sent from my Nexus 7 using xda app-developers app
You can use this to install the stock ROM and kernel, there is also an option to unroot it. http://forum.xda-developers.com/showthread.php?t=1929270 (install zip in custom recovery)
I don't know how to OEM lock your tablet without a pc..
Hope this helps
Sent from my Nexus 7 using xda app-developers app
I would be really surprised if it is not simply a bad micro USB cable. Try another one, if you have it laying around, or pick one up for cheap. My unofficial cable would charge, but not write for some reason.
i had the same problem after using a car charger.After some days that i charged with original charger only, charging icon started working and also fastboot.But usb otg functions were still dead either in twrp recovery or inside the rom.
After i flashed ota update (i was in stock 4.1.2) for 4.2 it magically started fully working.First i thought that it was 4.2 that made it work,but i went back in 4.1.2 (nandroid restore) and it continue to work ok.Of course i dont use anymore 3rd party chargers.I see now that my bootloader is 4.13 but it work ok with 4.1.2 too,so i will not change it to 3.41
I've tried 4 or 5 different cables and no luck unfortunately. Going from my beloved PA 2.54 to stock 4.2 temporarily to see if it fixes it, fingers crossed!
Update: Unfortunately I've not been so lucky problem persists...
Adb over WiFi?
Sent from my SPH-D710 using xda app-developers app
And now I'm stuck on 4.2 with root not working, my recovery corrupt, and USB still not working :crying:
Looks like I'll be sending it back and hoping they ignore the little opened padlock on my splash screen
DaMan90 said:
Adb over WiFi?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Adb won't do it, it has to be fast boot, and it has to be usb.
Cadabena said:
And now I'm stuck on 4.2 with root not working, my recovery corrupt, and USB still not working :crying:
Looks like I'll be sending it back and hoping they ignore the little opened padlock on my splash screen
Click to expand...
Click to collapse
Hi ! I'm in the same situation and am thinking of returning it. How did it go ? Did they accept it ?
chuck_0 said:
Hi ! I'm in the same situation and am thinking of returning it. How did it go ? Did they accept it ?
Click to expand...
Click to collapse
Accepted it no problem
However, they'd be well within their rights not to so I'm not guaranteeing. Best of luck!
Heya...
On my 16GB Grouper I had installed the stock rooted 4.3 rom. Yesterday a system OTA update message appeared on my screen - 1.7 MB. I let it download and install over night and just went to bed. Came back in the morning to a boot loop where the device got stuck with the four colorful thingies animation. I can access the bootloader, but the recovery seems to be broken. Can't remember if I had anything other than the stock one... Anyways, now I'm strugling to get this thing going again. I am a zero at ADB but willing to learn whatever is necessary to get me started with a working recovery at least. No tool root box will do anything really for me...
Thanks for your help in advance
Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app
hettige677 said:
Hey!
Had a problem just like yours. If your running windows then install this program its called nexus tool kit. I'm a newbie here but if you Google 'nexus toolkit wug fresh' you can find it
All you need to do is plug your device in and open the program, then select flash OTA with the boot loop option and then follow the on screen instructions
That should put you back to normal with a fresh start meaning all you data will be lost. You can also root from there to.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah. It would be dumb to actually learn what you are doing to your device. You should totally use a toolkit.
/s
Sent from my Galaxy Nexus
Honestly, I'm just showing the user one way, I anticipated him of being a newbie. For the record, it shows you all the process's happening.
Sent from my Nexus 7 using xda app-developers app
Thank you guys. You might not believe it, but I'm not a newb to Android or flashing. It's just that I've always been playing around with Samsung devices and there you'd normaly turn to Odin in case something went wrong. Here it's different.
Anyways, with this comprehensive guide I've been able to reflash a recovery image and my old rom. Unfortunately losing all of my data in the process, but there was no way to save it.
http://www.androidupdate.us/recover-bricked-device-fastboot/
In case this happens to anybody else.
Cheers
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!