Figured I would be a lurker forever, but I guess my hand was forced.
Well, I was annoyed by the sound on my Note 3 and some applications with no equalizer, so I tried a couple out with very limited success. Lots of people suggested Viper4Android as working better than the random ones you could find on Google Play. So I tried going to what looks to be the official thread. The installation seemed simple, aside from modifying a build.prop file(still simple but possible to mess up).
Long story short, I restarted the phone when the application told me to and was greeted with a permanent white 'Samsung Note 3' text-logo. I never get to see the Samsung or Sprint carrier video-logo. Holding down power merely reboots the phone after a few seconds. Seemingly the Power/VolDn/Home combo still works for download mode... but at the moment I don't know what to do with that access.
I would try posting on the official thread, but being a lurker, I don't have the required 10 posts.
Searching the Viper4Android thread, I only see happy Note3 people... and no one at all having the extremely bad luck that I have had. I don't even see any particular warnings about this being possible. The only thing I can think of is the driver that it installs and the build.prop file. If something seriously went wrong there with the audio, it could possibly prevent the videos from playing and the boot process wouldn't continue.
I'm at a temporary loss and thought I would post somewhere to get my options rolling as I think. Primarily, given that Viper4Android was the last thing that I did before this happened... is there something different I should be looking for rather than a generic method of undoing a soft-brick?
jljtgr said:
Figured I would be a lurker forever, but I guess my hand was forced.
Well, I was annoyed by the sound on my Note 3 and some applications with no equalizer, so I tried a couple out with very limited success. Lots of people suggested Viper4Android as working better than the random ones you could find on Google Play. So I tried going to what looks to be the official thread. The installation seemed simple, aside from modifying a build.prop file(still simple but possible to mess up).
Long story short, I restarted the phone when the application told me to and was greeted with a permanent white 'Samsung Note 3' text-logo. I never get to see the Samsung or Sprint carrier video-logo. Holding down power merely reboots the phone after a few seconds. Seemingly the Power/VolDn/Home combo still works for download mode... but at the moment I don't know what to do with that access.
I would try posting on the official thread, but being a lurker, I don't have the required 10 posts.
Searching the Viper4Android thread, I only see happy Note3 people... and no one at all having the extremely bad luck that I have had. I don't even see any particular warnings about this being possible. The only thing I can think of is the driver that it installs and the build.prop file. If something seriously went wrong there with the audio, it could possibly prevent the videos from playing and the boot process wouldn't continue.
I'm at a temporary loss and thought I would post somewhere to get my options rolling as I think. Primarily, given that Viper4Android was the last thing that I did before this happened... is there something different I should be looking for rather than a generic method of undoing a soft-brick?
Click to expand...
Click to collapse
looks like a factory reset ,volume up, power home, factory reset
Did you choose the correct driver to install?
jaythenut said:
looks like a factory reset ,volume up, power home, factory reset
Click to expand...
Click to collapse
Even losing absolutely everything doesn't really bother me. Only hard-bricking does.
munnarg said:
Did you choose the correct driver to install?
Click to expand...
Click to collapse
I had very few choices. I used the ViPER4Android_4.x_2313.apk since I have Android 4.3; a no brainer. Once installed and open, the changelog popped up, SuperSU asked to authorize, then V4A asked to install the driver. By this point I had already done the build.prop modification so I clicked Yes. It told me that it would automatically detect my CPU type which matches what the official thread says. It then prompted me to select the driver profile(?) with the options of Battery Saving, High Quality Mode and Super Audio Quality. Since the thread didn't give any suggestions, I went with the middle-ground of High Quality Mode. After the selection was made, it told me to reboot. I closed the application, held the Power button and selected Restart(then OK). And was stuck there.
Looking at some other various threads, it seems that improper modification of build.prop can indeed cause the type of bricking that I am seeing. I'll have to try V4A without that one step since it looks like it was added in after the fact... and in some cases optional if the lines to modify don't exist.
Don't think you had to mess with the build.prop at all. I sure didn't do it.
SwiftKey Flowed from my tiny Galaxy Note 3
munnarg said:
Don't think you had to mess with the build.prop at all. I sure didn't do it.
SwiftKey Flowed from my tiny Galaxy Note 3
Click to expand...
Click to collapse
I would have not done so if it had not asked me to.
http://forum.xda-developers.com/showpost.php?p=39156718&postcount=2
1. ROOT your device.
2. Install busybox if doesn’t come with root.
3. Modify build.prop (Thanks [email protected])
a. Open up /system/build.prop in text editor using any file explorer with root access.
b. Change the line (If you can’t find these lines, skip this step.)
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Click to expand...
Click to collapse
As a side note, factory resetting doesn't seem to affect this. Doing so says that it's wiping out /data and /cache. Where as what I modified was in /system. Some of my other reading proposed that re-rooting will undo those sorts of changes. Looks like I'll have to go down that research path.
I guess it should be unsurprising to me, but I never encounter only small problems.
Factory resetting in recovery mode and re-rooting in download mode, while successful, do not allow the device to boot past the first screen.
jljtgr said:
I guess it should be unsurprising to me, but I never encounter only small problems.
Factory resetting in recovery mode and re-rooting in download mode, while successful, do not allow the device to boot past the first screen.
Click to expand...
Click to collapse
if its still not working download your firmware from www.sammobile.com and flash with odin
jaythenut said:
if its still not working download your firmware from ----sammobile---- and flash with odin
Click to expand...
Click to collapse
I'm willing to try... but will that really replace more than what the CF-Auto-Root image has? Nevermind... just looked at the file size. That certainly changes a lot more than the CF-Auto-Root image. It'll take me a while to get it off of their free file hosting, probably.
Well, I have a blank but working device now... and that's what really matters.
Reading around... if I were to make a wager that I can't collect on, I would say that I ran into a bug with ES File Explorer. I read someone else bricking their device in the same way editing the same file. ES-FE makes a backup by renaming the file, then fails to save the new file. I swear I saw it do this once before on a less critical file and I was annoyed to have to do the cp through terminal. I didn't hit refresh to make sure it did it correctly... I just assumed when it said it saved, it saved.
Thanks for the responses. Back to lurking!
Just for info, V4A is running flawlessly on my N3. All I did was install the APK, open it, install driver as prompted and restart!
Related
if your have issues with the update not finishing 100% this will work
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
download the zip using heimdall flash like normal
factoryfs-factoryfs.rfs
zimage-zimage
param.lfs-param.lfs
cache-cache.rfs
recovery-zimage
ignore the rest of the files
then before first boot wipe data and cache reboot
manually use update.zip or just let it download itself
install update and your done
you can verify by going to "about device" build number will be SCH-I800.EC02
use superoneclick for root z4mod not working keep getting f/c's
it seems like anybody who used z4mod to root or flashed recovery "back to stock" is having problems a 100% fix is just download the files from my post and flash like normal then use superoneclick for root
***for it to work you must download the recovery files from my post***
the files in my post are created using a temp. root so the files are a pure clone of unrooted rom 100% stock that is why you have to use superoneclick to root I tried everything and have done this to 6 tabs with no errors
EC02 stock ota update.zip download
http://www.4shared.com/file/qIHEta11/update.html
Thanks, I noticed you posted this on the other thread too. I have never used Heimdall so I was REALLY trying to avoid this but I guess I will have to take the plunge and figure it out.......
this works
I have tried every which way and this way has worked every time for me
Finally worked
works 100% just followed the steps and no problems finally updated!!!!!
It works, 100% Thank you so much for this
This does work, 100%, but please note that it DOES NOT WIPE THE DEVICE. It will boot up with all your stuff. This is not neccessarily practical, but it will probably be fine. If you have any root dependent mods, such as set cpu or lcd density, they wont work and it may operate funny/slow until you reroot and set them back up.
stock restore files download
http://dl.dropbox.com/u/21215221/Verizon-GTab-Stock.zip
or
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
Download Mode (Volume down and power)
Download Heimdall from Here:
http://www.glassechidna.com.au/products/heimdall/
Also just below version 1.1.0 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Launch download mode on your tab that is already connected to your PC.
unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device or might say it other ways
Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end leaving Tab plugged in and in download mode
Unzip the stock files.
the zImage goes in both the Kernel AND Recovery slot.
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs make sure you use param.ifs not param.rfs
and the cache.rfs goes in the cache slot.
ignore the rest of the files in the zip and just use these
After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
After this runs you will more then likely have to Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
then let update download install it and you can use superoneclick if you want root back
This worked!
Thank you lexriley! That seemed to work. I forgot to wipe data/cache before i applied the update.zip, it still worked anyway. I should probably have wiped the data/cache.
Thank you !!!!!! Great Work!
Thanks so much. I rooted using Z4 and the update failed. I used your instructions and got up and running again! You saved my Tab!
I'm happy its working for everyone like it worked for me
100% fully working!!!!!!!
thank you lexriley your guide is easy to follow and do your the man!!!!!!
This should be a sticky!!!!
Sent from my ADR6300 using Tapatalk
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
oldmacnut said:
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
Click to expand...
Click to collapse
Well let me tell you what I have noitced with the upgrade
1) Stock browser speed is faster, but I dont use the stock so that wasnt much help
2)There is now a item in the top of settings for you to activate your device through verizon (like you would using *228 or whatever it is from your phone)
3)The wifi searching thing. I often forget to turn wifi off so when I drive it drains battery searching, the drain is significantly less now.
4) BLUETOOTH HID SUPPORT! Sorry for the caps but I have been wanting this one for quite some time now. First thing I did was try my MX5500 at home and it paired up and worked perfectly.
5)Hyperlinks in emails issue. Constantly many hyperlinks were cut off and I wasnt able to click them, this has now been resolved.
If none of these things are appealing to you then by all means you have no need to upgrade. But I found that most of this was a welcomed change. The tab seems faster, but I believe that is just due to the fact that I do not have LCD density changing the density, which I find slows down many things on the tab.
lexriley said:
I'm happy its working for everyone like it worked for me
Click to expand...
Click to collapse
At first it didn't work for me. I got "failed to access device. Error: -12". But that was my fault. I had forgotten to load the zagdig drivers for Heimdall. So I did that following the instructions in this thread and tried again. First try, I simply got a "fail", second try worked like a charm. When finished the Tab rebooted on its own.
As soon as it rebooted, I got the message that an update was waiting to be installed (EC02). Since I had already wiped the cashe (twice) on earlier attempts, I just went ahead and let the update install. Worked like a charm and now I've got EC02 update.
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Now to begin the task of re-rooting, installing ADW, and putting my Tab back into shape the way I had it.
BIG THANKS goes out to lexriley!! (And by all means, make this thread a sticky.)
Robin
Excellent work! This worked perfectly.
Got it, installed the newest Keis for drivers.
i hate to be that guy but is it possible to get odin files too? i can never get heimdall to work but odin works just fine
Robin M said:
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Click to expand...
Click to collapse
So if I just restore the vcast stuff then I should be able to update without doing all the recovery stuff? I just renamed them all with a .bak at the end instead of deleting just incase I needed them again so I still have them all.
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
shiltz said:
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
Click to expand...
Click to collapse
You're welcome. ...Isn't it great when you answer your own questions? I find myself doing that more frequently now, as I learn more about Android and my Tab - mostly from this forum.
PS... Now that you've successfully updated, take a look at the recovery.log file in your /cashe/log folder. I was amazed at the number and the variety of files this upgrade patched.
After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic.
Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.
Many thanks in advance for any suggestions/fixes!
Phillip
Its not bricked if it boots...
That is strange though. May have to reflash stock images.
Try bringing everything back to stock?
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Gr3yghost said:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Click to expand...
Click to collapse
No push the images using adb
I figured it could be done. Could you please point me to a thread explaining how to push images using adb?
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).
Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.
[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
djsaad1 said:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
Click to expand...
Click to collapse
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!
Sent it back
Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Borman18 said:
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full nandroid backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
Are you using Iconia Root to root and unroot? Let's start there?
Off to bed, I'm sure one of the other "late nighters" will be able to help you.
My only question is that you stated you installed CWM, if so, why didn't you create a full backup with it instead of nandroid?
Yes, I used Iconia Root to do the deed, which has worked since I got the unit a week ago until today.
And thats what I mean in terms of backing up, my apologies (im just use to calling it Nandroid for whatever reason).
I have no idea how the recovery got wiped though.
Borman18 said:
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
I STRONGLY recommend you read the following thread.
http://forum.xda-developers.com/showthread.php?t=1129873
Looks like you flashed something and didn't run "itsmagic".
Ive tried that, and no go. As far as I can remember, I havent flashed anything in days, since updating to the latest update a few days ago. And its been fine since then, until today. I started downloading google music stuff, went to the bathroom, came back and my tablet was off. I can give it another go though.
If it wasn't clear, I can definitely boot, its just with all those errors
But you get a checksum error, right? Have you gone through the steps in that thread that detail how to fix the checksum error?
If so, I suggest you contact sc2k.
Correct, if I hold the volume - and power, it gives that error. Just ran through the steps for the "<CASE 1> SOS checksum error" again to be safe, and its the same. I PM'ed him earlier (maybe twice..), but I can only assume he's sleeping, so I was just trying to see if anyone has any ideas.
Edit: from my ADB Shell session, just to show that it seems to want to work anyway? But of course, the same old..
# /data/local/itsmagic
Some magic trick by @sc2k on xda
it tricks the bootloader to run any kernel you want.
Thx @Acer for making this so easy.. why did you say the BL is locked if it isn't?
USE AT YOUR OWN RISK!
Done. Have fun!
# exit
Your best option is to wait until sc2k gets back to you, then. Don't worry. He's a fairly nice guy and has helped plenty of folks sort out similar issues on their tabs. Just remember to beer him afterwards!
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Borman18 said:
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Click to expand...
Click to collapse
AH, y'see, now you know what caused it in the first place! You tempted the fates! Never tempt the fates, for they are mean and sadistic beings that just LOVE to screw with folks right before they go camping.
I hope sc2k is able to help you out.
I have searched around and can't seem to find a similar problem with a solution that I can understand. I used superoneclick to root my Verizon Galaxy 7" tablet. Everything seemed to go fine, but I really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so I should have just left it alone. Instead I tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using Hemdall and loading new cache, param, system & zImage files. Now I am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple FCs until the setup wizard itself FC. Then it powers down and starts all over again. "Wipe data/factory reset" produces no change to the problem.
At this point I just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me. I have downloaded Odin, but am uncertain which ROM I need to use. I really don't care which method you recommend as long as it is detailed (ie. written for a complete idiot to follow).
Thanks for any help.
2 things. Are you talking about a regular 7" galaxy or the 7.7? And this will most likely be moved because its a question and questions go in the general section.
mmcounts said:
i have searched around and can't seem to find a similar problem with a solution that i can understand. I used superoneclick to root my verizon galaxy 7" tablet. Everything seemed to go fine, but i really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so i should have just left it alone. Instead i tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using hemdall and loading new cache, param, system & zimage files. Now i am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple fcs until the setup wizard itself fc. Then it powers down and starts all over again. "wipe data/factory reset" produces no change to the problem.
At this point i just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me. I have downloaded odin, but am uncertain which rom i need to use. I really don't care which method you recommend as long as it is detailed (ie. Written for a complete idiot to follow).
Thanks for any help.
Click to expand...
Click to collapse
wrong section...please post in q&a section...........
Moving?
Should I repost in the Q&A section or will the post be moved automatically? I don't see an option to move the post myself.
Moved To General
Please Post all questions in the General section
7 or 7.7
Regarding the 7 or 7.7 question: I don't know which it is because I can't get it to boot up long enough to go into settings. According to the label it is an SCH-i800. It was purchased from Verizon in March 2011. I am pretty sure that it is a 7. Is there any way to tell just by looking at it?
Just determined it is a 7.0 per the Samsung webpage.
I guess I am in the wrong forum again. I am going to post in the General Galaxy Tablet forum.
Googled your model # you listed and stock rom and found this tutorial. Hope this helps you.
Thanks. I have tried that one a couple of times. It is close, but no cigar. I appreciate you thinking of me.
Some boot loop problems can be solved by letting the battery go flat overnight to get out of the loop, recharging then booting normally and doing a factory reset. If that doesn't work then re-flashing using Odin followed by a factory reset is worth trying.
You can get the firmware for flashing here:
http://www.samfirmware.com/
and a guide how to do the flashing here:
http://forum.xda-developers.com/showthread.php?t=1469635
I hope this helps and good luck
mmcounts said:
Regarding the 7 or 7.7 question: I don't know which it is because I can't get it to boot up long enough to go into settings. According to the label it is an SCH-i800. It was purchased from Verizon in March 2011. I am pretty sure that it is a 7. Is there any way to tell just by looking at it?
Just determined it is a 7.0 per the Samsung webpage.
I guess I am in the wrong forum again. I am going to post in the General Galaxy Tablet forum.
Click to expand...
Click to collapse
Verizon only sells the silver version of the 7.7, for which the model number is SCH-I815. If you have a plastic back, it's the 7, and an aluminum back is the 7.7. Of course, since posted your model I can tell you for sure it's the 7, so you might have better luck posting in the appropriate forum.
Depending on how SuperOneClick works for the tab (I have no idea personally), you might just be best taking it to Verizon and asking for a replacement. I find it unlikely that they'd be able to detect that it has been rooted if it's totally fubar'd.
I have an Acer 500a I just bought off carigslist. Initially I thought it would be fine but then I realized I was inheriting someone elses problems. I hope someone may be able to help.
Within the first few hours I was noticing google Play crashed a number of times and struggled to update from Market. Somehow the update went through but now there is a system update that won't go through. I'm able to down load it and when i restart the computer to complete installation the screen goes black and says: booting recovery kernel in the corner. I then see a picture of an android and a load bar which after 2-4 seconds the android is on his back and an exclaimation mark is coming out of his belly.
My android version is 3.2
Kernel version
2.6.36.3+
Build number
Acer_a500_7.006.01_COM_GEN2
I'm pretty sure its rooted and i think that might be why its not playing nice with google market and system updates. I called the old owner and explained the problem and he just said he had it rooted and he thought he unrooted it. There is an ap called superuser in aps. (although if it were rooted would'nt I be able to uninstal some of thecrap software it comes with like GOLF HD? -- it won't let me).
The system update is for Acer_a500_7.014.01_COM_GEN2 8.88mb
My problem is all of the force closes I'm getting and the inability to update the system. Any thoughts? I don't have a usb cord to connect it to a desktop either =(
I am a bit out of practice, but...
Should be pretty simple to fix. From what I am seeing, you are running a stock rom. Just because the superuser.apk is installed on the system does not mean it is rooted, but it probably is.
Hit the market, grab "Root Checker" - simple tiny program to let you know for sure if your tab is rooted or not.
https://play.google.com/store/apps/details?id=burrows.apps.rootchecker&hl=en
From what I understand - automatic system updates will fail when trying to apply them to a rooted or modded system. Probably why you cannot auto-update.
My advice at this point would be to:
1) Since you just bought it, just do a factory wipe on it. That will remove all the stuff the prior owner had running on it and will result in a unrooted tab that should be able to get auto updates without a problem.
2) Un-Root it. Once the tablet is unrooted, the system should update without any issue.
As for your Play Store issues - I have never heard of or personally seen any issues caused with installing apps from the store on a rooted device. I have seen a few apps that will refuse to run on a rooted device - but that does not sound like your problem.
I would go with option 1 - just factory wipe the thing. Prior owner may have made tons of changes to the OS that we will never know about, and may have handed you a unstable system. Start fresh. Wipe it out.
Hope this helps you out! Let me know if I can answer any questions.
k thank you so much for the quick reply! I downloaded the root checker and it Is rooted. I did a factory wipe as found in the settings privacy tab when I bought it. That factory reset did not unroot and only cleaned out some of the aps on the device. Is there a better or more surefire way to unroot it? If I reset with the volume down key will it hard reset it?
Thank you for you help!
Draight
Okay.
I am about a year out of practice with my a500 - but from what I am think, if a factory reset still results in a rooted device - the prior user installed a stock ROM that comes pre-rooted.
I highly doubt being rooted is causing the issues you are running into.
At this point if you just want to get back to stock you can probably just install the Acer Recovery Manager from the market and use it to reflash a stock unrooted ROM. Or I see a few guides about how to manually restore back to stock over in the dev section for the a500.
Others will correct me if I am wrong, but I think Acer Recovery Manager should take care of your problem.
Hope this helps!
(Edit: Or you can just download the official stock 4.x rom (ICS) from the dev section and flash that. 3.2 is pretty slow and wonky in my experience, you should be able to just download a 4.x ROM and flash, since you are rooted. Again, I am way out of practice. Don't do anything before reading up!)
(Edit again: I think I was making this harder then needs be. Just flash any stock 3.2 unrooted ROM, done. After you do that the automatic on the air update should kick in for you and update you to ICS)
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
draight said:
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
Click to expand...
Click to collapse
Hmmm..
Try the thread I linked two in my second edit of my last post. You just need to grab the stock and unrooted 3.2 - put it on a MicroSD card as update.zip - then reboot with vol rocker and power switch to get the system to flash the update.
That *should* work just fine.
(Edit: Forgot the link! http://forum.xda-developers.com/showthread.php?t=1839313 - there you go)
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
draight said:
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
Click to expand...
Click to collapse
Nope. Just snag the stock unrooted 3.2 ROM - place it in the root of the MicroSD card as update.zip
Power down.
Power up with VOL + and POWER key held at the same time (you can let the vol rocker go when you see text appear in the upper left corner)
Should be all you need to do. Worst case; it does not work and returns you back to where you are now. Worth a shot.
If that does not work, let me know so I can do a few mins of homework and help you further. Been a long time since I have changed ROMS or had any issues with my a500.
I have bricked it twice by not following directions all the way or just making simple mistakes, but from what I have found there is always a way to recover.
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
draight said:
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
Click to expand...
Click to collapse
Hmmm. Odd.
Like I said, I am rather out of practice.
Someone more experienced them me: please help me point Draight in the right direction here?
Thanks for trying to help. =(
I wish that my tablet wasn't having such issues. I;m going to try to scramble around the forums and see if I can find some advice...If anyone has a suggestion please let me know.
Thanks again entropy,
Draight
Update:
So I've been tinkering around with it a bit more and I found a usb cord that plugs it into my computer. I keep finding boken links on this site so Im struggling to find an update I can use to flash to. I downloaded a different super user program which allowed me to temporarily unroot my device. I then restarted it and no root checker says its no rooted and I cannot find the superuser program. I think I have somewhat unrooted it -- but I think the real issue now is the recovery tool. I keep reseting it - hard reset, or factory reset and it wipes everything away but when i try to update it gets about 1/3 of the way up the bar then it stops with an '!' Mark above the droid. Im kind of annoyed at this point and hoping for some new links or some ideas on how to repair the recovery piece.
Draight
Go to the Dev section, and grad a couple of the ICS Update roms. You will see them listed for the a500. Make sure they are the FULL update roms. Should be about 3-400mb. These contain a FULL ICS Update Rom, and not a patch file.
http://forum.xda-developers.com/showthread.php?t=1816560
Then, go to the Themes and apps forum. You'll see a sticky that has the Acer Update Decrypter.
http://forum.xda-developers.com/showthread.php?t=1869505
Now, unpack the decrypter, and select one of the ICS Updates. Then hit Start. Take a couple minutes, but you will have a duplicate file with the word "decrypted" added to it.
Wait, you are not done yet.
Using a program like 7zip, or even Winzip, open the decrypted file. DO NOT EXTRACT, just open it and pull the update.zip to your PC's desktop.
Copy that update.zip file to your Ext SD Card of the tablet. Don't be putting it in any folder, just copy it to the root of the card.
Now, you still ain't done.
With the tablet off. Press and hold Vol+ and then PWR. Hold them both untill you start to see text about installing blah blah blah, then release the buttons.
If it completes, and you can reboot into ICS, then you are good to go.
If something fails during installation, then decrypt the other update Rom file you downloaded, and do the same procedure. Usually one of the 2 or three should work for you.
Note these are for the a500, and not the a501.
One more thing. It's advisable you get your UID number before doing these things. You probably won't need it, but it's nice to have written down in case you need it in the future. Inf to get it is at;
http://forum.xda-developers.com/showthread.php?t=1624645
MD
Thanks! I am downloading a few of the FULL ICS roms:
*Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy
Acer_A500_1.031.00_PA_CUS1: http://d-h.st/idO
Acer_A500_1.041.00_WW_CUS1: http://d-h.st/Yt5
*Acer_AV041_1.054.00_WW_GEN1: http://www.theandroidcollective.org/...00_WW_GEN1.zip
*Acer_A500_7.014.16_041.206.01_COM_GEN1: https://docs.google.com/file/d/0B_bk...hVc1RVcHc/edit
The I downloaded the ones ending with Gen1. Once they are downloaded I will continue with the instructions. Thank you so much for your help! I will post how it goes later tonight.
Draight
I just decrypted both:
*Acer_AV041_1.054.00_WW_GEN1:
*Acer_A500_1.031.00_WW_GEN1
Both get get to the third bullet quickly and the bottom says DONE! It takes like 4 seconds. I don't think the Decryption key of $12 is working
[*] Opening file: Acer_A500_1.031.00_WW_GEN1.zip
[*] Decrypting using key $12
[*] Writing decrypted file: Acer_A500_1.031.00_WW_GEN1_decrypted.zip
I try to extract something from the decrypted file and it says the file was not downloaded properly and I should try redownload it...it says its not a proper archive
wahoo!
So that worked! I down loaded the file Acer_AV041_A500_1.033.00_PA_CUS1 and extracted the update. I palced the update on the sd card and booted with the power and sound volume pressed down. it went through the installation procedure and restarted twice before saying it was upgrading my aps and BOOM its got ICS and everything looks great. Thank you so much for your help and I hope that this paper trail is able to help someone in the future
My problem is that I'm on ICS and I'm rooted, but I just can't download a custom recovery. I've tried, and I haven't gotten anywhere
Sent from my SPH-L710 using Tapatalk 2