Related
Hey fellows.
So I wanted to try a custom ROM for my SNS, so I rooted it with this guide: http://www.youtube.com/watch?v=xwe4sWH67dk
And since I'm completly green in all this root thing, I didnt manage to get a custom ROM on my device. So I just stayed with stock android and a launcher, and to be fair, I dont need any more than that.
Then the 2.3.6 OTA update came and I wanted to install that, so I hit "Install" and my phone rebooted. Come to the Google logo with the padlock on the button... and frooze (have to remove battery to restart my phone). Nothing I have done can help it, I tryed factory reset, nothing (get stuck on the same screen again)!
So I looked around the SNS topics in here, and frankly, I can't fix it! I read that locking the bootloader would probably help it. So I installed drivers for my device on my computer, and tryed to use this guide http://forum.xda-developers.com/showthread.php?t=875630 since it seemed fairly easy. But I cant make it work.
My phone version number is GRJ22 and my phone lock state is unlocked.
WHAT DO I DO? Remember, I'm completly green, so cut it into small pieces would be nice!
Hope that there is some helpfull sole out there that can help
arNooold said:
Hey fellows.
So I wanted to try a custom ROM for my SNS, so I rooted it with this guide: http://www.youtube.com/watch?v=xwe4sWH67dk
And since I'm completly green in all this root thing, I didnt manage to get a custom ROM on my device. So I just stayed with stock android and a launcher, and to be fair, I dont need any more than that.
Then the 2.3.6 OTA update came and I wanted to install that, so I hit "Install" and my phone rebooted. Come to the Google logo with the padlock on the button... and frooze (have to remove battery to restart my phone). Nothing I have done can help it, I tryed factory reset, nothing (get stuck on the same screen again)!
So I looked around the SNS topics in here, and frankly, I can't fix it! I read that locking the bootloader would probably help it. So I installed drivers for my device on my computer, and tryed to use this guide http://forum.xda-developers.com/showthread.php?t=875630 since it seemed fairly easy. But I cant make it work.
My phone version number is GRJ22 and my phone lock state is unlocked.
WHAT DO I DO? Remember, I'm completly green, so cut it into small pieces would be nice!
Hope that there is some helpfull sole out there that can help
Click to expand...
Click to collapse
I had a similar issue some time ago and I think I can help you. In my case, I had removed some system apps. I removed books and talk, and it couldn't update because the recovery didn't find these apps to update them. Also, if you don't have the stock recovery, but clockwork instead I think it will not work. You can find in the General section of this Nexus S forum links with the official updates zips. Download one of these and then flash it in recovery(stock or clockwork). Copy the zip to the USB storage and in recovery select 'flash update from usb storage' and select the downloaded zip. Personally, I downloaded the GRJ22 and flashed it, so I can have a clean and upgradeable GRJ22. Then I updated using the incorporated update tool from google OTA to GRK39F. It is better to do a factory reset before you flash the zip with the rom. Sorry for the messy explanation hope this helps. GL
Hmm, I downloaded the GRJ22 fitting me device from http://forum.xda-developers.com/showthread.php?t=1063664, placed it on the SDcard and tryed to go to recovery in fastboot, then the same thing happend again :/ (If that was what you meant)
I installed ClockworkMod Recovery through ROM Manager, then I installed the downloaded file on my device. Now I'm running 2.3.6 :O Thanks for the help dude!
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
misteral1970 said:
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
Click to expand...
Click to collapse
Mate, it doesn't sound good.
What I would do, at this point, is Fastboot the 4.1 image again.. And stay the heck out of CWM. If you Fastbooted the 4.0.4 image, and you still have it showing 4.1, then you have a serious issue. So boot to fastboot, and try it again. Clearly, whatever you did with CWM, didn't work,
Installing a rom from CWM, requires certain things to be done, either in the install script, or via CWM.
Most notably, Formatting User data, cache, dalvik, system, and data. If any of these do not get done, chances are, the rom install will not go good. The basic install script, generally only formats System and Flexrom. This is because Acer distributes a full rom with the understanding there is nothing on it. Most rom modders know this, which is why they give extra instructions via cwm.
The big thing, is when you boot your tablet, is if it says which bootloader you are on. So you have to look,. You want to be on the JB bootloader.
MD
Thanks for the response MD,
A tiny bit unsure how to proceed. I understand everything that you said (well, I think I understood correctly!)
I have in fact tried to fastboot the 4.1.1 image again, and again I am stuck on the language and location screen (did this last night before giving up for the day)
I have read and understood "Stay away from CWM" (and I know that it is in this case only - have used CWM on my Gnex without issue)
Please forgive me if what I am about to write is ridiculous - this is kind of where we'll see whether I understood correctly or not.
I'm thinking that if the various areas were not wiped, and that could be the reason for the snafu, then it would be worth going into CWM (which I have been warned to stay away from, and which I would stay away from except for this one thing) and formatting the user data, system, dalvik etc, then applying either the 4.1 or 4.0.4 to result in a working tablet.
Or possibly flashing the bootloader to make sure it is JB
Or going back to the weird 4.0.4/4.1.1 hybrid which works but doesn't allow Play Store and finding a way around that issue.
Mate, I'm not sure which way to go at this point!
Fastbooting 4.1 is a dead end at the moment (but could that be a bootloader issue....)
Fastbooting 4.0.4 gives me the hybrid (though I can check this again tonight)
BTW, the only CWM Rom work I have tried to do has been with the patched update (second downloadable file I think) - everything else has been done via ADB
So.....CWM to wipe/format caches? (I'm thinking 'NO! DID YOU NOT HEAR WHAT I SAID ABOUT STAYING AWAY FROM CWM????' but I'm asking anyway!)
Flash a new bootloader on? If so, any idea where I would find it (will obviously search here and Google)
Thanks anyway, and thanks in advance if you have any more advice. I really do appreciate the support!
Al
Well Al,
This is perplexing to say the least. Clearly fastbooting the 411 results in frozen at the wizard. My question, when you have the unlocked bootloader, does it say JBxxxxxxxx unlock mode when you boot the tab? Because it should. If it doesn't, then you're still on ICS bootloader. And will have to do the CWM thing to get JB installed. The 411 image flash, is to get a rooted version.
And this is the point. Personally, I do not trust the CWM's at this point. That's just me (already bricked 1 tab 3 months ago with a faulty CWM) I know the folks with ICS are using Pawitp's CWM, and haven't reported issues. But I don't know if they are doing wipes or not.
As with the 404 image, well, why playstore doesn't work is perplexing. You could try reinstalling the playstore via manual method (root required). Which is to delete the vending.apk, install a new vending.apk (making sure permissions are the same as the other files), then reboot. Go to settings, wipe the playstore cache's. Then try Playstore again. This was an old method we used with market issues in HC.
Personally, I feel the issue is with the wipes before running the patch. But I would hate you do the wipes and formats, then discover the emmc chip bricked. So it's 50/50.
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
Wish I could give you a definitive answer, but these processes are too new.
MD
Keep warranty
Moscow Desire said:
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
MD
Click to expand...
Click to collapse
Can you make a short tut how to replace the old unlocked Bootloader?
My Tab has some Problems with the Display so it need a service ...
witch cwm to use?
witch update.zip?
remove cwm and su if necessary
Android Version: 4.0.4
Baseband: 11.810.922.00
Kernal:2.6.39.4+
Image:ACER_AV043_A701_RV08RC02_EMEA_DE
Build: ACER_AV043_A701_1.017.00_EMEA_DE
Hi MD,
Thanks for such a speedy and useful response!
Warranty: nope! I'm in China, bought the tablet in Shanghai (now way down south in Shenzhen) and it was a dodgy deal to say the least. I suspect they were being lifted from the factory. No complaints from me about this, or about any difficulties caused by rooting/flashing/CWM. My choice of action all the way along and I am aware of the risks
Just flashed 404 again and it is fine so far, again very nice and smooth. Going to look at the Play Store and see how it behaves, see what I can do as far as vending.apk is concerned (although I'm lost when it comes to permissions. Obviously I know what permissions are in tech terms, but no idea where they would be set, how to change them, what to use as a reference) I figure this is the path of least resistance for right now.
Then I'm going to see if I can apply the standard A701 update to JB (which I won't be able to because of rooting/unlocking but I will fiddle around) and see if I have any joy.
Got my keen eyed gf to check the message on boot, you were right that with the 411 image applied it still had an ICS bootloader, so that's good to know if I want to try going back to the flashed JB image. However, I have no idea how to flash the JB bootloader/kernel, and the CWM process for the patched update fails each time (despite editing the first line of the necessary file in META-INF/Google/Android)
So, I will keep you up to date with progress. Fingers crossed!!!
Al
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
misteral1970 said:
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
Click to expand...
Click to collapse
Well, seems like Nova is the culprit. I assume you are talking about nova launcher? Or nova the game?
Hi MD
Yes, Nova launcher but no, it's not the culprit. At least I don't think so.
The play store stopped as soon as I ticked 'Install from unknown sources', before I installed Nova.
Very odd.
Quick questions:
1) Any advice/links/downloads for changing to JB bootloader if I apply the 4.1.1 again? Given that I cannot run the patched update/flash from CWM, I am guessing I would need to directly install/flash the bootloader from ADB...
2) Don't kill me for asking this. I know to stay away from CWM, I have seen you post it a good few times here, I heed the warning....BUT.....
Given that I have CWM installed and it's working ok (apart from failing to apply updates) - I have 6.0.1.4 - many of the guides to updating the 701 say it needs 6.0.1.1. Would the slightly more recent version of CWM make a difference in terms of success or failure of the update? Update is failing with a 'set_perm:some changes failed' very early in the update.
Seriously, I am being extremely wary of CWM, it's just that currently I have a slightly disabled tablet and it would be great to get this sorted.
Thanks, once again, for all your help,
Al
Update again, put 404 back on (after issue with play store and unknown sources)
Opened play store, downloaded Apex launcher - all good.
Ran Apex, all good....then suddenly Play Store stops, Apex stops, never to return.
With 404 img on, About Tablet still says 4.1.1
The saga continues!!
Aaaand that's the end of that!
Put 4.1.1 back on, pushed the boot.img from the official update.
Now no CWM, so it seems no recovery mode....if I try to get there by volume down and power on, it goes into update mode.
And of course neither the official update nor the 'patched' one will apply.
Can boot to the first start screen (language/location) but can't get any further.
Maybe I can find a service center here in Shenzhen who can sort it out.....as I said before, no harm no foul, I knew the risks!
Thanks one more time MD for all your support and advice )
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
misteral1970 said:
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
Click to expand...
Click to collapse
HA HA, you found the User Data wipe.... Yeah, a little known secret from the 500 forums.
MD
It's so strange....so now I'm back to having flashed 404 but the tablet thinks it's 411.
Play store was fine for about 40 minutes, I quickly got chrome, currents and BBC news.
I turned off the Acer ring and play store died...
But here I am, typing to you on the tablet and it's fine. And what a change in performance. It's most noticeable in currents..the increase in speed and smoothness when scrolling between pages makes it at least ten times better than before.
But the last flash was 404....weird....
I'll leave it like this for now. No market but at least it's not semi bricked!
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
misteral1970 said:
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
Click to expand...
Click to collapse
Well, good news then. I think it's an interesting set-up. Hybrid. Still not sure though, why it pulls 411 from the build.prop as it should have been changed when you flashed the 404image. But honestly, after reading the OP's steps, I believe he references going back to 404 via CWM, and not fastboot. This of course would mean installing a full 404 original rom. I'll have to look over my JB system dump and see where the other prop would be. Maybe something changed in JB.
So if you can live with it, it's probably better to leave it be till we come up with something more definitive.
MD
"So if you can live with it, it's probably better to leave it be till we come up with something more definitive"
Yeah, totally agree.
Mate, seriously, thanks for the support and advice on this. It makes a big difference. Even as I sat there last night with what seemed to be an unusable tablet, being able to chat to you about it meant that at least I didn't feel completely adrift!
Big big thanks
Something very strange happened yesterday.
I got the latest OTA and installed it, after this the touch screen is not responding at all.
I managed to control the tablet with an usb mouse, so I have been able to do a factory reset, but to no avail.
Just now I'm clueless on what to do.
I actually did on more thing in the same process; the initial reason for why I took up the tablet yesterday, was to put on a screen protector film.
So while it was updating I put on the screen protector, after all this was done the touch screen was not responding. I don't think this issue has nothing to do with the screen protector, and I have also now removed the film. But still the screen does not react to touch.
But what to do from here?
Is it possible to revert to a previous version of the firmware?
I doubt reversion is the best option.
If this was common this forum would be flooded with complaints.
It might have been something to do with putting on the screen protector DURING an update.
Factory reset may help. Did you try the pinhole reset switch?
Sent from my HTC One X using Tapatalk 2
I can use the tablet with a usb mouse, and have been able to do a factory reset. But this did not difference.
I have also tried the pinhole reset, no luck...
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
imtheyoyo said:
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
Click to expand...
Click to collapse
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
owangen said:
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
Click to expand...
Click to collapse
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
My touch screen work again.
I back to ICS stock rom (Acer_AV043_A700_RV07RC06_EMEA_FR), then I apply the update (Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR).
Now I'm on JB (Acer_A700_AV043.RV23RC04_AV051.RV10RC01_EMEA_FR). All Work fine.
jacksonkuo said:
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
Click to expand...
Click to collapse
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
owangen said:
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
Click to expand...
Click to collapse
Seems the touch FW is incorrect.Maybe you can download the OS upgrade image from Acer website and reflash OS. I checked the image and it should packed touch FW. If still failed, maybe contact Acer service is good way to solve your problem.
Good luck.
I had the same problem this week, bought the Tablet on monday, made the OTA Update and boom, no Touch input.
I resolved it by unlock my device, flash CWM and then flashed a older full rom.
After that i made the OTA Update again and this time it worked well.
I can upload the ROM i used for this if it's needed.
MfG Frank
via Acer Iconia Tab A700 mit Tapatalk 2.0
Thanks. I have fixed my tablet now.
I managed to reflash an older rom, taken from Acer site. And then upgraded via ota to the latest version.
I did not need to use cwm. Just started the tablet the power + volume - combination
Sent from my A700 using Tapatalk 2
Problem: Screen touches are bugged..
Hi,
I need some urgent help..
I upgraded my A700 (was shipped with 4.0.4) to JB but the screen touches are completely off track. I did the following:
1) unlocked the bootloader
2) flashed CWM Rom 6.0.1.5
3) installed cm-10
Don't know what to do next..
I have an Acer A700 and I'm having the same problem as others here.
Once I upgarded my ROM, the A700 touch-screen did not work.
I found a post that explained a fix. Here's what I did:
* Flashed the non-touch CWM v6.0.1.5
* Wiped everything (system, data, cache, dalvik)
* Installed the IconiaN ROM (by Vorbeth) and choose the option to have IconiaN upgrade my "Touch Firmware"
* The A700 is now booting with version JB-653b3d3 (Unlocked)
* The ROM loads just fine
However, in the ROM, the touchscreen does not work. Clicking in one place on the screen will trigger a click in an entirely different area of the screen.
I then tried installing one of the stock Acer ROMs from their website through CWM. None of them would load, not sure why?
Other people here seem to have solved the problem by flashing an "older ROM" from Acer. I could not find any trace of this older ROM.
I'm running an American version (PA1_CUS) if that makes any difference? I've also tried installing CM 10.1 with the same problems in the touchscreen.
Thank you in advance for any suggestions!
RKM
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
pyrochance said:
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
Click to expand...
Click to collapse
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Moscow Desire said:
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Click to expand...
Click to collapse
Thank you for the detailed help!
after many google searches i finally found the update files on the acer website!
i managed to go back to ics then re update to jb
and for a while my screen had no issues but they came back again. Im begining to think that its a hardware related issue because it comes and goes. I am going to see if my warranty with square trade will get it fixed.
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.
First; I hate to be a double poster, but I'm on the back page of How to Upgrade to 5.0.1 and Keep Root. My apologies. I've spent several days trying to solve this and have no answers.
I did the 5.0.1 "Keep Root" when it first came out, but it acted buggy and unpredictable. I just got a Note 4, and hate that I can't root it, so I decided to try to resolve the problems with my S4. I re-did the process, as stated and it seemed to work fine. I downgraded, rooted, and upgraded to 5.0.1. Then the trouble started. I installed the "Stock" Kernel, Modem, and Recovery. When I rebooted; it gave me a nasty message like: "AT&T has discovered unauthorized software on your phone." and froze up. I booted back into download mode, re-flashed the NB1 file, and it seemed to work, except for no Wi-Fi. When I tried to re-flash the OC4 with Flashfire, it acted like it was going to do it, but only booted into the recovery screen. I've tried close to a hundred different combinations, but no joy.
It allows me to root the NB1 and install Flashfire, but cant get it above 4.3. I installed a terminal emulator APK file and checked my bootloader status and it shows OC4. If my understanding is correct; I'm screwed. Is there any way to get past this and upgrade to ANY working ROM that will allow Wi-Fi and be fairly stable?
BTW; I'm on AT&T.
Thanks in advance!
As far as I'm concerned, ODIN just puts back your phone to its original state. Have you tried following the guide on how to install a custom Lollipop ROM? You gotta flash a rootable NB1 firmware and then continue with the process explained in the thread.
Here, take a look and tell me how it goes http://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
Crash and Burn
Crash and burn. NB1 wouldn't think of loading with Odin. Fails almost immediately.
Thanks for the help, though. Any other ideas?
Here's a screenshot of my phone parameters.
http://dl-1.va.us.xda-developers.co....png?key=Hy1bNEcEPo2F55Cm_pjqYg&ts=1450058617
Guess it won't upload my photo...