VRALL4 rolling out now apparently - Verizon Samsung Galaxy Note II

http://www.droid-life.com/2013/01/1...-2-receiving-surprise-update-to-build-vrall4/

Probably exynos patch.

Can someone grab the update.zip file and post it here?

Was just about to ask about this. I just got the update but I'm rooted so it failed, just wanted to see if it's anything worthwhile unrooting for

As long as you have a custom recovery it won't install.
So...someone capture the update URL by doing a logcat
adb shell logcat > logcat.txt, accept update and post it.

omgitswes said:
Was just about to ask about this. I just got the update but I'm rooted so it failed, just wanted to see if it's anything worthwhile unrooting for
Click to expand...
Click to collapse
Too bad you didn't logcat it.
Check your /cache for files.

Freakin website for info about it doesnt work either. verizonwireless.com\galaxynotellsupport is in the update page but cant tell if the "ll" is LL's or II's. Why wouldnt they just put the number 2 to eliminate issues. either site doesnt work. That is just ridiculously stupid web admins.

adrynalyne said:
Too bad you didn't logcat it.
Check your /cache for files.
Click to expand...
Click to collapse
Not sure how to do a logcat. Nothing is in my cache though
vtec2k7 said:
Freakin website for info about it doesnt work either. verizonwireless.com\galaxynotellsupport is in the update page but cant tell if the "ll" is LL's or II's. Why wouldnt they just put the number 2 to eliminate issues. either site doesnt work. That is just ridiculously stupid web admins.
Click to expand...
Click to collapse
yeah I tried all of the combinations none worked.

It just failed on my phone. Unfortunately I can only defer it for 5 days, but by then I figure a workaround will be found.

The update installs Google Wallet.
Kidding.
Sent from my SCH-I605 using Tapatalk 2

SeanPlunk said:
It just failed on my phone. Unfortunately I can only defer it for 5 days, but by then I figure a workaround will be found.
Click to expand...
Click to collapse
Too bad you didn't logcat it either.
Did you check /cache for any files?

adrynalyne said:
As long as you have a custom recovery it won't install.
So...someone capture the update URL by doing a logcat
adb shell logcat > logcat.txt, accept update and post it.
Click to expand...
Click to collapse
Hopefully this is what you need.
Looks like I was able to get the update.zip as well, gimmie a minute and I'll post that too.

ILMF said:
Hopefully this is what you need.
Click to expand...
Click to collapse
Unfortunately, no. It doesn't contain the needed info I need a full logcat.
Thanks for trying!

This was in /cache also the update only allows you to defer for 5 days so hopefully we can figure out what it does

I'm thinking that if, as I did, you gained root via the ExynosAbuse exploit application if you turn off the patch but keep root active (in the application settings) that will allow Verizon to patch the exploit however you'll still have root. I think this is correct but I'm not sure.

Here is the update. The file is downloaded to /cache/fota

ryngds said:
This was in /cache also the update only allows you to defer for 5 days so hopefully we can figure out what it does
Click to expand...
Click to collapse
Thanks!
I will let you know whats in it. The first thing I see, is a new bootloader. We can imagine why.

Ok updated are:
1. Phone
2. MMS
3. SystemUI
4. Settings
5. Modem
6. Bootloader
7. Browser
8. Contacts
9. HiddenMenu (maybe)
10. libbcc.so.sha1
11. kernel
I don't know what the updates are, I am going by patch size.

I'm rooted on stock with a few tweaks - nothing I can't live without. The initial update failed. I saved root using Voodoo, unrooted, and tried the update again. It failed the second time. I'm not inclined to do anything else until I see what the update entails and if we can retain root. I like my root

I used exynos abuse apk to achieve root. Then ota root keeper to protect it. I have many disabled apps and installed the ota with no issue and restored root fine.
I never unrooted either.

Related

Strange Problem with Rooting Vibrant

I have a T-Mobile version of Samsung Galaxy S Vibrant.
I followed a guide here:
forum.xda-developers.com/showpost.php?p=7150299&postcount=1
I can get into the recovery menu and I can see the option to reinstall packages. However when I press a power button to reinstall packages it seems like something is happening and it takes about 3 seconds and then the phone reboots.
I tried to use titanium Backup and I get a message it can't get access to root. I am assuming that am still not rooted.
I tried rooting with this method two times and it seems the result is the same.
Anyone has any idea?
thanks
Okay who is going to be the first one to flame him?
Have you tried using Ryan Za's OCLF app in the market?
Sent from my SGH-T959 using XDA App
dmolition said:
Okay who is going to be the first one to flame him?
Click to expand...
Click to collapse
If you can help by replying or guiding me to the right place I would appreciate it.
Have you tried using Ryan Za's OCLF app in the market?
Click to expand...
Click to collapse
I just did and followed the instructions. However when I entered the recovery mode I did not see the package that I have to install.
Orochi77 said:
If you can help by replying or guiding me to the right place I would appreciate it.
Click to expand...
Click to collapse
Q & A section would have been my first guess.
http://forum.xda-developers.com/forumdisplay.php?f=708
Orochi77 said:
I have a T-Mobile version of Samsung Galaxy S Vibrant.
I followed a guide here:
forum.xda-developers.com/showpost.php?p=7150299&postcount=1
I can get into the recovery menu and I can see the option to reinstall packages. However when I press a power button to reinstall packages it seems like something is happening and it takes about 3 seconds and then the phone reboots.
I tried to use titanium Backup and I get a message it can't get access to root. I am assuming that am still not rooted.
I tried rooting with this method two times and it seems the result is the same.
Anyone has any idea?
thanks
Click to expand...
Click to collapse
Ignore some of the idiots above me
But that is normally how long it takes.. It doesn't take long at all for it to work. Just go to apps on your phone, and look for an application called "SuperUser"
If it is there then you are rooted, and for apps that require root, there will be a little box that pops up asking for permission
dmolition said:
Okay who is going to be the first one to flame him?
Click to expand...
Click to collapse
Why are you going to flame him? None of the stickys have been updated with any information regarding root information for JI6.
Some people have issues, while other people do not.
I visit this forum everyday and still haven't found any definitive information about rooting on JI6...just people saying "hey try this" or "try that".
Goofing around without knowing what you're doing is the easiest way to jack up your phone. If he messed it up just following a thread by 'Billy-bob-Joe' then you would probably be the first one to flame him for not asking for help before he tried anything.
Cut the guy some slack.
Master thank you for responding.
Just go to apps on your phone, and look for an application called "SuperUser"
If it is there then you are rooted, and for apps that require root, there will be a little box that pops up asking for permission
Click to expand...
Click to collapse
I had the superuser application even before I was trying any rooting.
I also just tried another tutorial for one click root and another tutorial where a rooting is done from a apk file from within the phone but nothing seems to work.
Some people have the same problem at the one click root thread but there is no answer to that.
Thanks Tarzanman
I am assuming JI6 is a firmware that I have.
As of this post JI6 is the latest firmware for the Samsung Vibrant.
T-mobile is sending it out over their network ("OTA"), but you can also obtain the update via Samsung's (very buggy) Kies or Kies Mini software (assuming you get the software to recognize your phone properly).
It is called JI6 because if you go to Settings|About Phone|Baseband Version
then phones running this firmware will read "T959UVJI6"
Tarzanman thanks for your explanation.
On my phone is actually reads as: T959UVJFD.
Can this firmware be rooted?
Orochi77 said:
Tarzanman thanks for your explanation.
On my phone is actually reads as: T959UVJFD.
Can this firmware be rooted?
Click to expand...
Click to collapse
Yes, JFD is the stock ROM. You might as well get JI6 loaded on to it, as loading it on after will reset your root priviledges anyways.
Best way to check if you have root is to download Terminal Emulator, open it, and type in SU...
I7oobie said:
Yes, JFD is the stock ROM. You might as well get JI6 loaded on to it, as loading it on after will reset your root priviledges anyways.
Best way to check if you have root is to download Terminal Emulator, open it, and type in SU...
Click to expand...
Click to collapse
Thanks
Terminal Emulator gave me a message "Permission Denied"
I am assuming that i am not rooted.
What am i doing wrong then?
you followed the steps on this guide?
http://forum.xda-developers.com/showpost.php?p=7150299&postcount=1
make sure you DL the file on that thread, and follow its steps!
1) make sure you rename the dl'd file "update.zip"
2) make sure you have the file in the internal memory of the phone, not the SD card
Try it again, and let us know!
I have never had a root problem, though I do find it strange that you had "superuser" prior to rooting.
You have a brand new phone? or did you buy it off the internet somewhere? There's no way new phones have "superuser" on it already.
If you've already tried to many methods, i'm guessing one of those ways you tried installed superuser on the phone without granting you root access (which is weird too)
From the General Sticky (and it works regardless of JFD or JI6):
HOW TO ROOT
justadude had a great post on how to root. Please read his post. I have used this method about 10 times and it always works flawlessly and it's just so incredibly easy.
Be sure you are placing the file on the root of your internal memory (sdcard/). This is possibly the easiest phone ever to root.
you followed the steps on this guide?
http://forum.xda-developers.com/show...99&postcount=1
Click to expand...
Click to collapse
I did . I just tried now again and the same thing happened.
It seems like the process went fine. Now I tried to type su in terminal emulator and again it says permission denied.
I have never had a root problem, though I do find it strange that you had "superuser" prior to rooting.
You have a brand new phone? or did you buy it off the internet somewhere? There's no way new phones have "superuser" on it already.
If you've already tried to many methods, i'm guessing one of those ways you tried installed superuser on the phone without granting you root access (which is weird too)
Click to expand...
Click to collapse
The phone was bought from second hands. It was locked to T-Mobile. The guy who i bought it from unlocked it and claimed that he only used it for one week.
The phone came with superuser app. It is part of the phone and not a 3rd party application. I cannot remove it. I thought it was part of the stock apps that come with the phone.
s15274n, yep did that at least three times now with no luck.
Just to confirm. I am putting the update.zip file on the root of the drive that has internal memory of the phone, not the SD card. I am guessing if I was putting it elsewhere then the recovery menu will not see it as install packages option.
I am lost. Perhaps the dude that sold me the phone messed something up somehow and now because of that I can't root.
Thank you for helping me guys.
s15274n
Can you tell me something?
When you select install packages how long does the process take before the phone reboots?
For me it takes about three seconds.
It really does not take long at all.... several seconds sounds about right.
Are you renaming the file on your phone, or the pc?
My concern is you are renaming it update.zip.zip (because your pc is hiding the file extension).
s15274n said:
It really does not take long at all.... several seconds sounds about right.
Are you renaming the file on your phone, or the pc?
My concern is you are renaming it update.zip.zip (because your pc is hiding the file extension).
Click to expand...
Click to collapse
I am renaming the file on the PC via total commander.
I am pretty sure it is not zip.zip issue.
Download the file to your phone directly from the thread I linked.
On your phone, go to the filed (sdcard/download).
Long press and rename it using Astro or Root Explorer, etc.
just start to the left of update.zip and delete the name so it's now just update.zip
long press and move this file to sdcard/
go to stock recovery and flash it.
Do all of these steps and tell me it doesn't work....
Moved to Q&A and closed

[Q] New Nook Tablet users (as of 21/12)

So, I think my question is useful to a lot of us, even myself, so I hope someone could help me out. It goes a little something like this:
I have a Nook Tablet, wrapped under my xmas tree. Going straight to the point: what is the best way to get it rooted, under the light of this new software update? On the 25th December, should I turn it on, register it, quickly disable wifi, and start to root it, along with the titanium backup solution? Shoud this work? Or do you have another (and better) solution?
Thanks in advance to all who can help us!
Just got mine today and root couldn't have been easier using this thread -> [Update 12/10/11] Full root for Nook Tablet. [11/20/11] [Permanent root!]
I never saw anything come up on the tablet about an update. Side loaded apps work fine also, just installed all 3 angry birds.
Thanks! A bunch, really! You made my day!
Just got mine today as well. Prepare to root after reading the thread here.
SteelH said:
Just got mine today and root couldn't have been easier using this thread -> [Update 12/10/11] Full root for Nook Tablet. [11/20/11] [Permanent root!]
I never saw anything come up on the tablet about an update. Side loaded apps work fine also, just installed all 3 angry birds.
Click to expand...
Click to collapse
Hi, would like to know if you have the Wi-Fi ON all the way during the process? Thanks!
keidgeibef said:
So, I think my question is useful to a lot of us, even myself, so I hope someone could help me out. It goes a little something like this:
I have a Nook Tablet, wrapped under my xmas tree. Going straight to the point: what is the best way to get it rooted, under the light of this new software update? On the 25th December, should I turn it on, register it, quickly disable wifi, and start to root it, along with the titanium backup solution? Shoud this work? Or do you have another (and better) solution?
Thanks in advance to all who can help us!
Click to expand...
Click to collapse
Just to be safe, first thing I would do after turning on and registering is go straight to root thread and download tgps app. then disable wifi. then after rooted, enable wifi and download titanium backup, then freeze devicemanager.apk. this will block verification of software version.There are other methods of blocking OTA.
Also, there is still a question on if they are even pushing OTA, some of us never got one and have left our devices on for the past couple of days...
albertwertz said:
Just to be safe, first thing I would do after turning on and registering is go straight to root thread and download tgps app. then disable wifi. then after rooted, enable wifi and download titanium backup, then freeze devicemanager.apk. this will block verification of software version.There are other methods of blocking OTA.
Also, there is still a question on if they are even pushing OTA, some of us never got one and have left our devices on for the past couple of days...
Click to expand...
Click to collapse
Do I need to download tgps app directly on the nook, can't I push it through my sd card?
Yes, comptonsoft.com/test and select the top left link.
So it looks like we can still root if ee have one sitting under the tree waiting for us huh? I had been debating between this and the acer a100 and chose this for the battery life and ease of root/use factors. Hmm. Thanks for the info
Sent from my LG-P925 using Tapatalk
you can root anyway, just might have to sideload stock rom of 1.4.0 through sdcard restore
---------- Post added at 10:36 AM ---------- Previous post was at 10:36 AM ----------
keidgeibef said:
Do I need to download tgps app directly on the nook, can't I push it through my sd card?
Click to expand...
Click to collapse
yes, can be done through sdcard as well
Thanks, albertwertz
I just wish someone could post a really simple guide (n00b alert) on how people who don't have their NT yet could root it and bypass this software update as soon as possible...
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
In theory if this is all true; we should be ok even after the weekend.
I will do mine tonight but I need to do my wife's after she opens it; I'm not letting B&N spoil the surprise
radtechy said:
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
In theory if this is all true; we should be ok even after the weekend.
I will do mine tonight but I need to do my wife's after she opens it; I'm not letting B&N spoil the surprise
Click to expand...
Click to collapse
Thanks I'm filled with relief... Happy xmas, everyone!!!
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
You just made my day.....
Root and don't worry thanks a bunch albert.
Are you are the guy who made the you tube tutorial?
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
Looks like I WON'T be sending my Nook back after all! Thanks so much!
radtechy said:
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
Click to expand...
Click to collapse
Assuming your modem is not also your wifi router, just unplug the modem before you register the device and if you like, you can still use wifi to load files from a local file server. No need to worry about how quickly you disable wifi if there is no line to the outside world.
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
How did you confirm?
Not saying your lying, but I don't know how you would be able to confirm it blocks OTA updates.
radtechy said:
You just made my day.....
Root and don't worry thanks a bunch albert.
Are you are the guy who made the you tube tutorial?
Click to expand...
Click to collapse
yes, the link in my signature should direct you there. I make a bunch of other stuff too
---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------
xdahgary said:
How did you confirm?
Not saying your lying, but I don't know how you would be able to confirm it blocks OTA updates.
Click to expand...
Click to collapse
we talk through gtalk and irc. He said that the GAPPS part removes OTA and he just added those comments to his root thread.
albertwertz said:
yes, the link in my signature should direct you there. I make a bunch of other stuff too
---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------
we talk through gtalk and irc. He said that the GAPPS part removes OTA and he just added those comments to his root thread.
Click to expand...
Click to collapse
Is there a default location to get these GAPPS from beforehand? As well as any other needed software for root/applications etc.

[GUIDE] How to prevent the OTA if you can root with RazorClaw

Ok folks,
If you're lucky enough to get a TP that's rootable with RazorClaw, you're gonna wanna keep it. Problem is that Asus keeps trying to ram a firmware update down our throats that kills root. We can't have that.
Problem with the OTA is that it keeps spamming you to update, and also in theory at least, you can only postpone it 3 times before it forces you too. Hitting back works somewhat, but you're still gonna get spammed.
The TP also immediately looks for the update as soon as it attaches to wireless.
SwiftKS provided me with the idea of freezing it with TiBu. While it could work in theory, I couldn't get it work as TiBu will only freeze the app with Pro version. I have the pro version, but it wouldn't recognize my key without connecting to market. Which, as you guessed, also lets the TP go out and grab the OTA.
Thanks to some the folks over in the "For any chance of root on TP..." thread in General, I found something else that works.
As always on here, I'm not responsible for anything going wrong or you bricking your device. You assume all risk. If you have your apps backed up, I suggest moving them to your PC to copy back later.
1. Root with RazorClaw if you haven't already.
2. Download Voodoo OTA Root keeper from Market
3. Run Voodoo OTA Rootkeeper and have it protect root
4. Once it says it's protected, download and install the OTA
5. After the OTA is applied, go back into Voodoo OTA Rootkeeper and have it restore superuser.
6. Enjoy!
Thanks to SwiftKS for planting the idea, and the guys in the mentioned thread above for their idea.
Have a great holiday folks!
Hmm, also, you could probably use File Explorer and go in to system/app and rename Update Launcher.apk
Possibly. Didn't try that as I thought it might still try to do its thing even with a different name.
Hehe, Android isn't THAT smart. But, if they're paranoid they could always remove the file from the system/app folder and drop it onto an SD card for safe keeping.
****.
After a few hours, it pulled it down. Must be another process at work.
Mods, feel free to close/delete the thread. Or if anyone else has any ideas, they're welcome to post.
I tried.
could probably just move the. Apk to somewhere else completely or rename it to ****update.apk.bak (don't have one ATM.) Should have one tomorrow so I'll look more into it.
di11igaf said:
could probably just move the. Apk to somewhere else completely or rename it to ****update.apk.bak (don't have one ATM.) Should have one tomorrow so I'll look more into it.
Click to expand...
Click to collapse
That's what I've been thinking. Seemed to work for everything I didn't want to run in the past. My experience is limited to DInc and GB but there's no reason why it shouldn't work here. Assuming it's the only apk thats responsible for the upgrade process. Alternatively, you could block asus servers from the host file perhaps?
The update makes things so much better though ::-(
Sent from my Transformer Prime TF201 using xda premium
You could always get the update(assuming someone can grab it somehow), see what is does/replaces, then just push the updated system/framework files to the old firmware then have the best of both worlds.
Remember with root you can manually push anything in /system you want just can't flash kernels and the like yet u til we have a recovery working or a way to rite a new kernel.
When I get the tp hopefully it won't be updated. We should be able to grab the update via adb and pre root it (maybe) if that is possible ill post my results
sent from my Atrix via XDA premium
What does it improve?
I can try renaming the apk and awe what happens. I'm not sure what it'll do though as it still says the process isn't running.
I'd prefer to keep root so unless someone has tried rooting then updating, I'm hesitant to try it.
I did find done files that look like they were downloaded last night in the /d directory. Didn't muck with them though without a recovery.
Sent from my Galaxy Nexus using XDA App
when it downloads the update does it reboot into recovery?
if there is a way to get between that with adb we could pull the update and check it out, possibly add root to it and see if the update will continue.
Can you please add in your post what is Prime firmware version!
Thanks
marko! said:
when it downloads the update does it reboot into recovery?
if there is a way to get between that with adb we could pull the update and check it out, possibly add root to it and see if the update will continue.
Click to expand...
Click to collapse
I held off on updating for 3 days but then ******* friend didn't know what to do and hit to update it. I thought about what you said. It does boot into recovery. I was trying to find where the OTA was being stored those 3 days that it was downloaded to my prime, but I couldn't find it. Of course I only checked the system folder and forgot to check the data folder. I'll look to see if it's there now but I have a feeling it's been deleted since the update has been done already.
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
ka911 said:
Can you please add in your post what is Prime firmware version!
Thanks
Click to expand...
Click to collapse
The prime version that is rootable is 8.8.3.23 build
Gamestop retails come out with 8.8.3.27 build (not rootable)
The OTA build makes it 8.8.3.29 (not rootable)
Superguy had a best buy model that had the 8.8.3.23 build.
unknown_owner said:
I held off on updating for 3 days but then ******* friend didn't know what to do and hit to update it. I thought about what you said. It does boot into recovery. I was trying to find where the OTA was being stored those 3 days that it was downloaded to my prime, but I couldn't find it. Of course I only checked the system folder and forgot to check the data folder. I'll look to see if it's there now but I have a feeling it's been deleted since the update has been done already.
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
The prime version that is rootable is 8.8.3.23 build
Gamestop retails come out with 8.8.3.27 build (not rootable)
The OTA build makes it 8.8.3.29 (not rootable)
Superguy had a best buy model that had the 8.8.3.23 build.
Click to expand...
Click to collapse
Most likely it gets downloaded to the cache!
if anyone who is rooted can get into adb after DL the update just try
Code:
adb root
adb pull /cache
has anyone tried any of the other root methods or just the one included with razorclaw?
Find where the download comes from, and block it using the hosts file. Look in the resources/data for the update app for the ip.
marko! said:
has anyone tried any of the other root methods or just the one included with razorclaw?
Click to expand...
Click to collapse
I tried a lot of the methods out there but no luck of course on any of them even the tried the other root method from the original TF.
TONS of people should be getting the TF from Best Buy tomorrow or Wednesday. So hopefully we can get some people to try some things! I'm gonna be searching all over the place for that update!
dsmitty166 said:
TONS of people should be getting the TF from Best Buy tomorrow or Wednesday. So hopefully we can get some people to try some things! I'm gonna be searching all over the place for that update!
Click to expand...
Click to collapse
A zip of the OTA can be found here
unknown_owner said:
A zip of the OTA can be found here
Click to expand...
Click to collapse
Now, to see if we can add root to the update...

"EternityProject EasyRootICS" failed on 4.0.4, 6.16.211.XT912.Verizon.en.US

I'm trying to root my Droid Razr using the "EternityProject EasyRootICS" tool but I am having problems. I would just post in that thread, but I don't have 10 posts yet and am not allowed.
What I've done:
1) Restored the phone to factory defaults
2) Followed all the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1710871
3) Batch file reports success, but upon going into the "SuperSU" application for the first time, it wants to update itself. I allow this, then it fails.
4) I downloaded "Root Checker" from the Android marketplace and it reports that my phone is not rooted.
What troubleshooting steps should I take? If you guys need more info I can provide it. Thanks in advance.
Zamiell said:
I'm trying to root my Droid Razr using the "EternityProject EasyRootICS" tool but I am having problems. I would just post in that thread, but I don't have 10 posts yet and am not allowed.
What I've done:
1) Restored the phone to factory defaults
2) Followed all the steps from this thread: http://forum.xda-developers.com/showthread.php?t=1710871
3) Batch file reports success, but upon going into the "SuperSU" application for the first time, it wants to update itself. I allow this, then it fails.
4) I downloaded "Root Checker" from the Android marketplace and it reports that my phone is not rooted.
What troubleshooting steps should I take? If you guys need more info I can provide it. Thanks in advance.
Click to expand...
Click to collapse
Hi!
Delete all the @cls in the .bat file and run it again. Get the log and send me a PM.
It's a windows batch script and will run all over even if get an error message. So, let me know witch error you got.
Cheers
pedrotorresfilho said:
Hi!
Delete all the @cls in the .bat file and run it again. Get the log and send me a PM.
It's a windows batch script and will run all over even if get an error message. So, let me know witch error you got.
Cheers
Click to expand...
Click to collapse
I got it working now! I needed to run the "EPRJ_EasyRootICS_MultiOS_v1.1" that you mentioned in the OP even though I had already restored my device to factory defaults and wiped my SD card clean.
You might want to make a note of that in the OP of the thread for noobs like me. Thanks so much for your help!
Zamiell said:
I got it working now! I needed to run the "EPRJ_EasyRootICS_MultiOS_v1.1" that you mentioned in the OP even though I had already restored my device to factory defaults and wiped my SD card clean.
You might want to make a note of that in the OP of the thread for noobs like me. Thanks so much for your help!
Click to expand...
Click to collapse
Most of the problems getting root is due a previous root method attempt (which is fixed the way you followed) or by a not working adb connection.
Glad to hear you figure out.
Cheers

Too many pattern attempts

Hey guys, I got the tablet yesterday to get rid of that "too many pattern attempts" screen. The owner of course doesn't remember the credentials to his google account, so he gave it to me to get rid of the lock, without hard-resetting if possible.
I have no idea what the Android version is; I can't get past the log in screen. I can't root it/delete that one small file responsible for all of this since ADB isn't enabled. The Android recovery seems to be the only option, but of course, I can't use unsigned zips like AROMA File Manager... or can I?
I'd like to know if I have any options besides resetting to factory settings from the recovery screen. And what does it delete? Only apps, their data and system settings or pretty much everything?
Spaqin said:
Hey guys, I got the tablet yesterday to get rid of that "too many pattern attempts" screen. The owner of course doesn't remember the credentials to his google account, so he gave it to me to get rid of the lock, without hard-resetting if possible.
I have no idea what the Android version is; I can't get past the log in screen. I can't root it/delete that one small file responsible for all of this since ADB isn't enabled. The Android recovery seems to be the only option, but of course, I can't use unsigned zips like AROMA File Manager... or can I?
I'd like to know if I have any options besides resetting to factory settings from the recovery screen. And what does it delete? Only apps, their data and system settings or pretty much everything?
Click to expand...
Click to collapse
Try an update as it may removed the lock (although I think it will stay in place) Have a look at my stickied FAQ for how to and look at my signature for update zips.
Stifilz
Knowing how Android works, I would expect the update to either delete all the data or keep everything. I thought more of running something from the recovery, but I see how it may not be possible.
Spaqin said:
Knowing how Android works, I would expect the update to either delete all the data or keep everything. I thought more of running something from the recovery, but I see how it may not be possible.
Click to expand...
Click to collapse
The update will keep all the files. You can ONLY install Sony signed zips anyway so this is the only hope. Or a recovery of the password for Google... Which you stated is a no go...
stifilz said:
The update will keep all the files. You can ONLY install Sony signed zips anyway so this is the only hope. Or a recovery of the password for Google... Which you stated is a no go...
Click to expand...
Click to collapse
Downloaded the update from your thread (Polish version) and I can't seem to be able to open the zip... is it supposed to be like that? I'd see if I could modify it by any chance to delete/overwrite that one file.
Spaqin said:
Downloaded the update from your thread (Polish version) and I can't seem to be able to open the zip... is it supposed to be like that? I'd see if I could modify it by any chance to delete/overwrite that one file.
Click to expand...
Click to collapse
It is encrypted and signed by Sony. You can decrypt it, modify it and re-sign it but IT WILL NOT WORK. We do not have SONY'S private key for sigining... Otherwise we could ad SU etc, this is not the case.
stifilz said:
It is encrypted and signed by Sony. You can decrypt it, modify it and re-sign it but IT WILL NOT WORK. We do not have SONY'S private key for sigining... Otherwise we could ad SU etc, this is not the case.
Click to expand...
Click to collapse
Okay, thanks for that... Gotta try it, not many options left.
[edit]
"Prohibit update as a result of checking version or base sku" when trying to update, is there anything I can do with it now?
Spaqin said:
Okay, thanks for that... Gotta try it, not many options left.
[edit]
"Prohibit update as a result of checking version or base sku" when trying to update, is there anything I can do with it now?
Click to expand...
Click to collapse
Use adb pull /tmp/recovery.log after the update fails. USB debugging is always enabled in recovery
stifilz said:
Use adb pull /tmp/recovery.log after the update fails. USB debugging is always enabled in recovery
Click to expand...
Click to collapse
Weird, the device wasn't visible through adb devices...
Anyway, it doesn't matter much now since I tried updating to an older update (revision 1a? Sth like that) and it didn't fix the problem, so in the end I had to wipe data. I could probably experiment a bit if I didn't have to give back the tablet yesterday.
Just wipe the device via recovery, the key files are in /data/system so unless you have root and ADB then a wipe will have to do.
A wipe via recovery will not wipe the emulated internal or just external storage such as SD and USB.
Sent from my Nexus 4 using Tapatalk

Categories

Resources