I just got a regular S6 through T-Mobile and for some reason, the initial update is failing. It will download (177 mb), reboot to install, get to 25%, fail, and reboot. The phone is working perfectly other than that. Any idea what I can do to fix it? Thanks.
Since you just got it, why not do a factory reset, then see if the update takes.
roger1955 said:
Since you just got it, why not do a factory reset, then see if the update takes.
Click to expand...
Click to collapse
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
BTow1105 said:
I just did a factory reset and it still fails repeatedly.
I get the error "dm verity verification failed".
Also keep in mind that it was doing this out of the box before I even installed any apps.
Click to expand...
Click to collapse
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Alarand said:
What firmware is listed under build number in settings?
The only things off the top of my head I can think of that would be causing this out of the box are Samsung's own phone security or a buggy phone. When trying to root some people got stuck in a boot loop, not cause of a bootloader lock, but because of some part samsung's anti malware security of whatever it is that can be disabled in settings. It was apparently turned on without them knowing. Not sure if this could happen with an official OTA but it's something you can check.
Other than calling samsung or T-mobile considering this is a bug that happened without root, you could try flashing the stock firmware with odin. Although, I can't say whether you'll still have access to the OTA or not, which is why I asked what firmware version you're on.
If it's G920TUVU1AOCG then it's the same as the stock anyway and potentially that could mean it's a bug with the update that was pushed to you seen as it's new. If it's not G920TUVU1AOCG then chances are G920TUVU1AOCG is newer and you can just flash it via odin to update.
edit: you could also try booting into recovery and clearing cache then try the ota again.
Click to expand...
Click to collapse
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mikeyinid said:
When me and my girlfriend got our S6's, hers wouldn't take the update either. It said she had a custom system....The only way I got it to take it was to odin the firmware. That's probably what you'll have to do. Out of curiosity is yours white?
Click to expand...
Click to collapse
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
BTow1105 said:
Here is the info you're looking for. It doesn't look to be exactly the same as either version you mentioned.
I tried to use Odin and it seemed like the phone froze on the blue "Downloading..." screen after I tried to send it the stock firmware.
Its a white 32gb regular S6.
Click to expand...
Click to collapse
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
mikeyinid said:
Weird. Same as hers. Do you have all the drivers installed? Is odin seeing your device?
Click to expand...
Click to collapse
The drivers are installed, Odin recognizes the device, but it just seemed frozen on the blue screen. Odin did a few things and said "started" or something and it said that for about 20 minutes before I decided that couldn't be right. Rebooted it and it went right back to normal.
Have another computer to try, just to cancel out that computer being the problem?
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
BTow1105 said:
So its fixed now. I went to Best Buy and they have a Samsung rep there. I talked to him about it and he decided to plug it into his laptop and put the stock firmware on it (which I tried to do but it also didnt work). The build number changed slightly and now it says the phone is up to date. Here is the old and new build info:
Click to expand...
Click to collapse
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
5.1 the dream
mikeyinid said:
That was very cool of him, I'm pretty sure they're not suppose to do that. To bad he didn't flash some super secret unreleased test software on it lol.
Click to expand...
Click to collapse
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
altimax98 said:
They actually are setup to do it. The Bestbuy Samsung experience shops can install firmware on any Samsung device as long as it has not been modified. They cannot reset Knox.
Click to expand...
Click to collapse
Well , to be honest, they should be doing all warranty work and claims and things right there as well. They have such ****ttty customer service that I'd much rather go somewhere so that I could actually discuss things in person. Kinda like......... APPLE!! That's really the only reason I keep these Crapple devices around, because they will swap out anything 4 me on a dime and it can be done in less than an hour. No 2-3-4 weeks without a phone. It seems like being 2015, Samsung should be able to compete in that sense. Oh well, Sorry, I am just daydreaming over here. :cyclops:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
PS4AndroidHacker said:
Anybody have a tar file that we can flash in Odin for the 5.1.1 update? I just got my phone today and it wont take the update from T-Mobile. It downloaded all the files and started installing in recovery,then it rebooted and stated the update failed. My phone is bone stock factory and has never been modified in any way. Any help is greatly appreciated!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62486197
Related
Good evening,
A few months ago I tried to root my S3 I9305, unfortunately it didn't really worked out. I had it rooted, installed some kind of clockwork app, but stopped right here, as I had no idea what I was exactly doing, and I did not want to take the risk to brick my phone. So I unrooted it, got rid of the supersu and the clockwork custom app.
Now the problem is, whenever I want to see if there is an update for my phone, it says I cannot do this, as my device is modified... So here is my question, how do I REALLY get completly rid of the root, because root checkers say im not rooted anymore, but for some reason my device says it is still rooted...
I've read that factory resets wont help, but flashing the stock rom with odin does ... Can someone explain to me what exactly I can do to just get completly rid of root?
Greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see in the picture above, it says my apparaatstatus (Status device) is aangepast (modified)
I suppose that before rooting your phone, you were on stock rom 4.3? In that case you have installed knox automatically. Knox will let Samsung update know that you modified your phone.
Flashing firmware with pc and Odin should fix it but i never tried this myself. I'm happy with a rooted phone and modified recovery
zertyx said:
I suppose that before rooting your phone, you were on stock rom 4.3? In that case you have installed knox automatically. Knox will let Samsung update know that you modified your phone.
Flashing firmware with pc and Odin should fix it but i never tried this myself. I'm happy with a rooted phone and modified recovery
Click to expand...
Click to collapse
Thank you for your answer, so as I thought, flashing to stock ROM with ODIN is the best solution..? Altough I have absolutely no idea what that consists of...
The thing is, I really wanted root as well, as we all know 4.3 is a big failure on the S3 (Battery drain, slow, wake up lag, ...) But the problems were 1st of all, I didn't really find a clear guide on how to do it, so I was just doing things without knowing what exactly I was doing.
2nd of all, I have some apps I use on a regularly base who do not run when rooted, for example to watch TV or my bank application ... So I couldn't really root because of all this.
Would be appreciated if someone could link me how to flash my device, I9305 from Belgium, with proximus providor.
palmenmichiel said:
Would be appreciated if someone could link me how to flash my device, I9305 from Belgium, with proximus providor.
Click to expand...
Click to collapse
Go here, read it, then read it again before you do it...
http://forum.xda-developers.com/galaxy-s3/help-i9305/compiled-guide-rooting-gt-i9305-s3-lte-t2287234
Raistlin1158 said:
Go here, read it, then read it again before you do it...
http://forum.xda-developers.com/galaxy-s3/help-i9305/compiled-guide-rooting-gt-i9305-s3-lte-t2287234
Click to expand...
Click to collapse
Thank you for answering, but that is a methode to flash root with odin, what I want to do is flash stock rom so my phone is just as new WITHOUT root.
I think with a little bit of research I can figure out how to work with Odin myself, but I can't see to find a firmware the same as my phone.
Since you have Knox, I guess your device status will stay on "modified" until there is a way to reset the Knox counter.
If you only want to get rid of root to use apps which require an unrooted phone, I suggest you try root with SuperSU. There you have an option to (temporarily) deactivate root. On my i9305 phone, I can watch TV like this (in Belgium). This method however doesn't seem to work on my older HTC phone with CM 11 (although it used to in the past with an older version of the TV-app).
zertyx said:
Since you have Knox, I guess your device status will stay on "modified" until there is a way to reset the Knox counter.
If you only want to get rid of root to use apps which require an unrooted phone, I suggest you try root with SuperSU. There you have an option to (temporarily) deactivate root. On my i9305 phone, I can watch TV like this (in Belgium). This method however doesn't seem to work on my older HTC phone with CM 11 (although it used to in the past with an older version of the TV-app).
Click to expand...
Click to collapse
So even flashing a stock rom wont get rid of my root status, therefor I'll never be able to download following android updates via kies or OTa again... My god never ever a samsung device for me again, next one will be a nexus..
palmenmichiel said:
So even flashing a stock rom wont get rid of my root status, therefor I'll never be able to download following android updates via kies or OTa again... My god never ever a samsung device for me again, next one will be a nexus..
Click to expand...
Click to collapse
I'm not sure; I think you can do updates (maybe not OTA) and your phone will be completely unrooted, but Knox counter will say that in the past, you modified your phone (voiding warranty).
zertyx said:
I'm not sure; I think you can do updates (maybe not OTA) and your phone will be completely unrooted, but Knox counter will say that in the past, you modified your phone (voiding warranty).
Click to expand...
Click to collapse
Oh well if its only about warrenty, I don't really care about that, device isn't under warrenty anymore anyways so!
then what's the problem? updates? if you got the 4.3 you are on the latest version...s3 is not nexus to receive updates every week/month...
the next update that is important is 4.4...and should get out soon...just go to samfirmware.com and get it(when it will roll)..
spiderman07 said:
then what's the problem? updates? if you got the 4.3 you are on the latest version...s3 is not nexus to receive updates every week/month...
the next update that is important is 4.4...and should get out soon...just go to samfirmware.com and get it(when it will roll)..
Click to expand...
Click to collapse
What you're saying is my problem , I cant just update with kies/OTA anymore because my device says its modified. Now what I've already learned now is that once it comes out, I can just flash it with odin, just as I can flash my stock rom with odin now. But the problem is that my PDA number is nowhere to be found on that site with firmwares, and I don't want to ruin my phone by flashing a wrong firmware..
hermmm why do you root your device when you don't even know what is root and why u need it? You understand that you are taking risk when you are rooting/flashing custom recovery on your device right? And one thing u will have to understand is that, literally speaking, there's no way you can brick you phone if you didn't modify anything after rooting, so you won't brick your phone "again(?)" if you now leave your phone as it is. Another thing is that rooting will not affect the functionality of other apps, instead it allows you to access more apps, so it is impossible that you can't run an app that you previously can after rooting, but the story will be different if you made other modification besides rooting and installing custom recovery. I think you might want to check out triangle away. I'm not sure whether this app can save you or is what you need, since I never use this app, but I know it can reset flash counter. But again, it needs root.
nikctsh said:
hermmm why do you root your device when you don't even know what is root and why u need it? You understand that you are taking risk when you are rooting/flashing custom recovery on your device right? And one thing u will have to understand is that, literally speaking, there's no way you can brick you phone if you didn't modify anything after rooting, so you won't brick your phone "again(?)" if you now leave your phone as it is. Another thing is that rooting will not affect the functionality of other apps, instead it allows you to access more apps, so it is impossible that you can't run an app that you previously can after rooting, but the story will be different if you made other modification besides rooting and installing custom recovery. I think you might want to check out triangle away. I'm not sure whether this app can save you or is what you need, since I never use this app, but I know it can reset flash counter. But again, it needs root.
Click to expand...
Click to collapse
I do know what root is, I just found no clear guide on how to root and install custom roms from scratch on these forums. I wanted a new rom because 4.3 on an S3 is ridiculously bad, battery drain etc ... I never bricked my phone before or anything like that, I just stated that I do not want to flash the wrong firmware causing my device to go broken.
Sadly, some applications do NOT work after you rooted. An example is a TV app called 'TV overal' or a banking application 'Bancontact mobile'. Now that I removed my root, together with supersu, my tv app works again, but my banking app still doesn't work as it says my device is modified. To what I've learned on this thread, it's because of the Knox app that still thinks my device is rooted...
I guess the only thing I can do is wait for the 4.4 firmware to come online and flash it with odin, however I need to do that ...
palmenmichiel said:
I do know what root is, I just found no clear guide on how to root and install custom roms from scratch on these forums. I wanted a new rom because 4.3 on an S3 is ridiculously bad, battery drain etc ... I never bricked my phone before or anything like that, I just stated that I do not want to flash the wrong firmware causing my device to go broken.
Sadly, some applications do NOT work after you rooted. An example is a TV app called 'TV overal' or a banking application 'Bancontact mobile'. Now that I removed my root, together with supersu, my tv app works again, but my banking app still doesn't work as it says my device is modified. To what I've learned on this thread, it's because of the Knox app that still thinks my device is rooted...
I guess the only thing I can do is wait for the 4.4 firmware to come online and flash it with odin, however I need to do that ...
Click to expand...
Click to collapse
Yes you are right, knox did that, from what I know, there's no way a regular app can find out the status of your device without asking for SU permission, so that's why I say "rooting will not affect the functionality of other apps", but since knox is there, then...
Anyway, I'm not sure whether I'm right, but I think the 4.4 firmware is ald up since the device is ald updated for quite some time. You can try to grab it from sammobile.
nikctsh said:
Yes you are right, knox did that, from what I know, there's no way a regular app can find out the status of your device without asking for SU permission, so that's why I say "rooting will not affect the functionality of other apps", but since knox is there, then...
Anyway, I'm not sure whether I'm right, but I think the 4.4 firmware is ald up since the device is ald updated for quite some time. You can try to grab it from sammobile.
Click to expand...
Click to collapse
Mh, as far as I can see, my CSC number (Which I think is the guideline to make sure you're downloading the right firmware?) I9305LUXEMK1, 4.3 is the latest, no such thing as 4.4 for it yet.
palmenmichiel said:
What you're saying is my problem , I cant just update with kies/OTA anymore because my device says its modified. Now what I've already learned now is that once it comes out, I can just flash it with odin, just as I can flash my stock rom with odin now. But the problem is that my PDA number is nowhere to be found on that site with firmwares, and I don't want to ruin my phone by flashing a wrong firmware..
Click to expand...
Click to collapse
then don't update via OTA or kies....just go to samfirmware.com and get firmware for the country you live on.... or any firmware from any country.
For example: i live in Romania and i got firmware from Netherlands(cause it was latest in samfirmware)...and it's working perfect...no battery drain no nothing....
As long as you are flashing firmware for your device it won't get bricked....
One small tip: after you flash firmware and got the the point where it says upgrading apps.....i manually enter recovery mode(stock one) and do a full wipe to make sure it works perfect.
nikctsh said:
Yes you are right, knox did that, from what I know, there's no way a regular app can find out the status of your device without asking for SU
Click to expand...
Click to collapse
Well, in Belgium they can
Me too, I have an app called Yelo tv, to watch some of the channels that the cable provider offers. It doesn't try to ask for root access and nevertheless it knows when the phone has root.
I don't have Knox.
Flash a stock rom with odin , the only solution i see there , then retry a root , it'd be okay then
So I'm back to trying to fix this... I found out that apperantly I have clockwordmod recovery still installed, when i use the key combo volume up + power+home button, and I have a backup on my SD card ... When I reboot from this menu, it says that I do not have root, so I chose yes there (to root it) , once it rebooted, went to play store to get supersu/root checker and both said I wasn't rooted ...
So what should I do to just get rid of it all and have a stock phone again? Because you've got all kinds of options in clockwordmod (Wipe data/factory reset, wipe cache partition, ... )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
someone could tell me if I should give this update..?
just come to my active 5...
hdelvalle009 said:
someone could tell me if I should give this update..?
just come to my active 5...
Click to expand...
Click to collapse
I did the update, not sure how big it is or whats different. Still 4.4.2
The question is what well happen to the root if installed.
I'm rooted and the update failed for me. I don't know if it was root that caused it to fail or the fact that I changed my build.prop to reflect SM-G900A. Either way, doesn't seem a big enough deal to me to "fix" it for the update.
I'm using the KoolKit Active variant as my rom (http://forum.xda-developers.com/att...m-koolkit-s5-koolactive-v1-0-0b01-07-t2809957)
I take it trying to perform this update would be a bad idea.
Just updated. New Baseband Version G870AUCU1ANG. Kernel is 3.4.0-2304514. Build Number: KOT49H.G870AUCU1ANG3. Android Version 4.4.2.
I thought this might be 4.4.4. By the way, I lost ROOT when I did this. Will have to see what is needed to restore it.
---------- Post added at 12:18 PM ---------- Previous post was at 12:02 PM ----------
Just tried to re-install Towelroot. No Dice. It says the device isn't supported.....darn.
dbodom said:
Just updated. New Baseband Version G870AUCU1ANG. Kernel is 3.4.0-2304514. Build Number: KOT49H.G870AUCU1ANG3. Android Version 4.4.2.
I thought this might be 4.4.4. By the way, I lost ROOT when I did this. Will have to see what is needed to restore it.
---------- Post added at 12:18 PM ---------- Previous post was at 12:02 PM ----------
Just tried to re-install Towelroot. No Dice. It says the device isn't supported.....darn.
Click to expand...
Click to collapse
the exploit that geohot used for towelroot has now been patched, so if you apply this update you will no longer be able to root your device. unfortunately this was bound to happen, there are a couple of apks to look for the main one to freeze or delete is the localFota.apk (i think thats the correct name) this should prevent the ota from being recieved by your device. if you are running a a custom rom (either mine or nickoftyme's) the OTA should not apply. Technically it shouldnt apply at all if you are rooted in any fashion but apparently AT&T in their infinite wisdom found away to screw with us once again.
Geohot did say that they were going to patch...and now it's happened...
Block those OTA's people...
We may never see root again...so thanks for nothing AT$T....
rotten azzhats...g
So if I turn on wifi will it update automatically? Its been asking since this morning.
The update installed on mine, I lost root as well even though OTA Survival Mode was turned on.
On the brightside Visual Voicemail is fixed but I want my root back.
Slowb00st said:
So if I turn on wifi will it update automatically? Its been asking since this morning.
Click to expand...
Click to collapse
Most likely yes....unless you freeze the "ATT UPDATES" apk by using titanium backup...
You may want to freeze the following as well...
Local fota
Security policy updates
Samsung push service
With those 4 frozen...you should not see an update prompt again...g
UGH... sux.
I was hoping to root my phone tonight. I downloaded Towelroot and can open it but "Install" is not clickable.
I received the ATT update on Friday.
I don't know about anyone else but my update came down the other day and now my wifi sucks. It connects fine, has good strength, but is slower than dirt and loading content (browser and apps) and we have @ a 65Mbps connection.
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Like a fool, I allowed the AT&T OTA update in my Galaxy S5 Active. I lost root and towelroot would no longer work as the device was no longer supported. However, I was able to use ODIN to downgrade back to ANE4. Towelroot worked again to root my device and I was able to re-install all of my Xposed modules and most importantly Titanium Backup to freeze the OTA updates.
I did have to do a factory reset after downgrading because my stock email app repeatedly crashed afterward. But all is well with the world once again.
Ocires said:
Like a fool, I allowed the AT&T OTA update in my Galaxy S5 Active. I lost root and towelroot would no longer work as the device was no longer supported. However, I was able to use ODIN to downgrade back to ANE4. Towelroot worked again to root my device and I was able to re-install all of my Xposed modules and most importantly Titanium Backup to freeze the OTA updates.
I did have to do a factory reset after downgrading because my stock email app repeatedly crashed afterward. But all is well with the world once again.
Click to expand...
Click to collapse
Where did you download the ANE4 rom?
Edit: found it! http://rootzwiki.com/topic/202682-how-to-restore-your-att-s5-active/
Ha! I nixed that in the bud before it began. Damned ATT.
first off I'll admit I'm as new as new can be to Android. I got an s5, rooted it in hopes of getting WiFi tethering again (after years of a jailbroke Iphone) and to get rid of the emergency number I kept butt calling. . neither of these worked for me so I went ahead and updated. it said the installation failed twice but my software is now up to date. still rooted. . not sure what is going on. I'll check for the software update again tomorrow
gregsarg said:
Most likely yes....unless you freeze the "ATT UPDATES" apk by using titanium backup...
You may want to freeze the following as well...
Local fota
Security policy updates
Samsung push service
With those 4 frozen...you should not see an update prompt again...g
Click to expand...
Click to collapse
Thanks. I'm thankful I checked here before taking the update.
BuLLitz said:
UGH... sux.
I was hoping to root my phone tonight. I downloaded Towelroot and can open it but "Install" is not clickable.
I received the ATT update on Friday.
Click to expand...
Click to collapse
Late to the party on this reply...but we have a fix...by pushing the stock firmware via Odin....(see above )..
That'll get you to the rootable image and allow you to freeze the update...g
gregsarg said:
Late to the party on this reply...but we have a fix...by pushing the stock firmware via Odin....(see above )..
That'll get you to the rootable image and allow you to freeze the update...g
Click to expand...
Click to collapse
Worked beautifully!
My S5 Active is now not an Active and I am able to access all the apps on Gear Manager.
Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse
lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse
OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse
lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse
and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.
Here we go for those interested in sideloading
https://developers.google.com/android/ota
johnny8910 said:
Here we go for those interested in sideloading
https://developers.google.com/android/ota
Click to expand...
Click to collapse
thanks
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
sn0warmy said:
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
Click to expand...
Click to collapse
A week after updating, and still fine for me.
sn0warmy said:
Anyone else finding face unlock is now broken after the January update?
What's odd is that for 2 days after flashing the update, everything was just fine. But yesterday I got a notification that I needed to re-enroll my face for face unlock to work. I did that and now no matter what I do, I can't get face unlock to work. I've reflashed the update and the issue persists. Extremely annoying.
Click to expand...
Click to collapse
Hasn't happened for me but if you're having issues go back to December update with a clean flash. Then take the January update before you root. Once it's downloaded and installed then root.
Spookymyo said:
Hasn't happened for me but if you're having issues go back to December update with a clean flash. Then take the January update before you root. Once it's downloaded and installed then root.
Click to expand...
Click to collapse
I've tried all sorts of things to get it fixed, including what you mentioned. But it remains broken.
I've tried...
1) Clean flashing the January image again
2) Clean flashing the December image (which previously worked perfectly)
3) Clean flash December and let it auto-update to the January update before attempting to set up face Unlock
None of the above have solved the issue and now, no matter what image I clean flash, I get an error telling me a new face can't be added because there is old face data already uploaded. It gives me no way to remove the old face data in any clean flash I install. This has truly become a serious problem, at least in my case.
My only hope at this point is for Google to roll out an update/fix to correct it. Otherwise, the only other option I can think of is to RMA, which would suck because the phone has been flawless until now. Extremely annoying.
sn0warmy said:
I've tried all sorts of things to get it fixed, including what you mentioned. But it remains broken.
I've tried...
1) Clean flashing the January image again
2) Clean flashing the December image (which previously worked perfectly)
3) Clean flash December and let it auto-update to the January update before attempting to set up face Unlock
None of the above have solved the issue and now, no matter what image I clean flash, I get an error telling me a new face can't be added because there is old face data already uploaded. It gives me no way to remove the old face data in any clean flash I install. This has truly become a serious problem, at least in my case.
My only hope at this point is for Google to roll out an update/fix to correct it. Otherwise, the only other option I can think of is to RMA, which would suck because the phone has been flawless until now. Extremely annoying.
Click to expand...
Click to collapse
Are you making sure you're using the right build number? Mess ups like yours can be a result of flashing the wrong build.
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
Spookymyo said:
Are you making sure you're using the right build number? Mess ups like yours can be a result of flashing the wrong build.
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
Click to expand...
Click to collapse
I have a carrier unlocked US Pixel 4 and used the top factory image in this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, the December image I tried re-flashing was the proper image that had face unlock working perfectly up until moving to the January image.
It would be amazing if I simply flashed the wrong January image. However, even going back to the previously working December image (which was saved on my PC) didn't solve it. So I'm not confident that this is the case.
Also, I want to reiterate that face unlock WAS working for the first few days after flashing the top January image in the above screenshot. It only stopped working a few days after flashing when I got a random notification to re-enroll my face. After that, it was broken and there is seemingly no fix. I also haven't rooted my Pixel 4. Looks like I need to contact google.
Possible hardware fail?
gpvecchi said:
Possible hardware fail?
Click to expand...
Click to collapse
That's my main concern. I'm thinking about just testing one of the other January factory images to see if I can get lucky. I really have nothing to lose, at this point.
regardless, it does look like this issue is a bit more wide spread than just me...
https://www.androidpolice.com/2020/...ken-for-some-may-be-caused-by-recent-patches/
https://www.androidcentral.com/pixel-4s-face-unlock-inexplicably-broken-some
https://bgr.com/2020/01/10/pixel-4-face-unlock-not-working-authentication-failure-and-fixes/
https://9to5google.com/2020/01/09/pixel-4-face-not-available/
Can someone explain what "NTT DOCOMO" means in the bottom factory image from my above screenshot? I'm thinking about giving that a try. I know the "TW & JP" version is "Taiwan and Japan", so I'm not going to bother with that one.
On another note... when did Google start resorting to confusing factory image labels? I've had all the Pixel phones since the Pixel 1 and I have to say, the naming conventions Google is now using for factory images is the most confusing I've ever seen. They aren't even consistent, month to month.
---------- Post added at 12:35 PM ---------- Previous post was at 11:57 AM ----------
UPDATE: Face Unlock fixed!! :highfive:
Spookymyo said:
Also try going back to stock unrooted with the bootloader relocked. Then try again. Other than that you may have to contact Google.
Click to expand...
Click to collapse
I should have paid this more mind. I was digging around and saw someone on the Google support forum report that simply relocking and unlocking the bootloader solved the problem as relocking and/or unlocking the bootloader is the only way to do a 100% true wipe, which erases previously stored face data.
So I relocked the bootloader, immediately unlocked it again before even booting up. Then booted, went back through setup an VOILA! Face unlock working again. Extremely relieved right now.
sn0warmy said:
I have a carrier unlocked US Pixel 4 and used the top factory image in this screenshot:
Also, the December image I tried re-flashing was the proper image that had face unlock working perfectly up until moving to the January image.
It would be amazing if I simply flashed the wrong January image. However, even going back to the previously working December image (which was saved on my PC) didn't solve it. So I'm not confident that this is the case.
Also, I want to reiterate that face unlock WAS working for the first few days after flashing the top January image in the above screenshot. It only stopped working a few days after flashing when I got a random notification to re-enroll my face. After that, it was broken and there is seemingly no fix. I also haven't rooted my Pixel 4. Looks like I need to contact google.
Click to expand...
Click to collapse
QQ1B is the correct build.
You may have hardware failure.
---------- Post added at 05:34 AM ---------- Previous post was at 05:32 AM ----------
sn0warmy said:
That's my main concern. I'm thinking about just testing one of the other January factory images to see if I can get lucky. I really have nothing to lose, at this point.
regardless, it does look like this issue is a bit more wide spread than just me...
https://www.androidpolice.com/2020/...ken-for-some-may-be-caused-by-recent-patches/
https://www.androidcentral.com/pixel-4s-face-unlock-inexplicably-broken-some
https://bgr.com/2020/01/10/pixel-4-face-unlock-not-working-authentication-failure-and-fixes/
https://9to5google.com/2020/01/09/pixel-4-face-not-available/
Can someone explain what "NTT DOCOMO" means in the bottom factory image from my above screenshot? I'm thinking about giving that a try. I know the "TW & JP" version is "Taiwan and Japan", so I'm not going to bother with that one.
On another note... when did Google start resorting to confusing factory image labels? I've had all the Pixel phones since the Pixel 1 and I have to say, the naming conventions Google is now using for factory images is the most confusing I've ever seen. They aren't even consistent, month to month.
---------- Post added at 12:35 PM ---------- Previous post was at 11:57 AM ----------
UPDATE: Face Unlock fixed!! :highfive:
I should have paid this more mind. I was digging around and saw someone on the Google support forum report that simply relocking and unlocking the bootloader solved the problem as relocking and/or unlocking the bootloader is the only way to do a 100% true wipe, which erases previously stored face data.
So I relocked the bootloader, immediately unlocked it again before even booting up. Then booted, went back through setup an VOILA! Face unlock working again. Extremely relieved right now.
Click to expand...
Click to collapse
That's why I was thinking it was hardware failure. Because if relocking the bootloader didn't fix it then it had to be hardware related. Because without twrp to do a full wipe the only way to completely wipe the phone is by relocking the bootloader.
Glad it's fixed!
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
View attachment 5253543
View attachment 5253545
Click to expand...
Click to collapse
Are you rooted? Did you ever enable usb debugging in developer settings?
Tulsadiver said:
Are you rooted? Did you ever enable usb debugging in developer settings?
Click to expand...
Click to collapse
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
ChrisH78 said:
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
Click to expand...
Click to collapse
Yes, you have to unlock the bootloader and that wipes the data. Your phone would have to be able to boot up for that to happen. Just wondering if you flashed something that didn't agree with your phone. Without usb debugging enabled, I don't know a way to pull anything off.
ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
Click to expand...
Click to collapse
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
v12xke said:
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
Click to expand...
Click to collapse
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
v12xke said:
Wishing you a successful recovery.
Click to expand...
Click to collapse
Would the mount /system option be of any use to me?
ChrisH78 said:
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
Click to expand...
Click to collapse
You would use fastboot to dirty flash a full image, removing the wipe flag (-w) from the flash-all script beforehand. This wipes and replaces the boot partition but leaves your data intact.
ChrisH78 said:
Would the mount /system option be of any use to me?
Click to expand...
Click to collapse
No. Even unlocked and rooted we cannot write to the system partition anymore. Any luck on getting your phone working again?