Hi.
Some weeks ago I did unlocked the bootloader and got magisk working and also rooted the phone. I have been using Google Pay since that. Today I went into settings and checked phone for new update. But it was the latest update. I pressed the three dots and selected "Download latest package" and the phone restarted in twrp after that but said it failed to update once the phone was restarted. After this I went to buy some food with Google Pay and it was working. Got home and now I got a pop-up window looking like this:
{
"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"
}
I then went into Magisk Manager and it says Magisk is not installed? It has been installed? Super SU says my phone is not rooted? So what strange things has happened?
I tried to install magisk again in magisk manager but it fails doing that.
Any ideas how to solve this? I really need Google Pay to work.
You can try Install Magisk.zip in TWRP again
EDIT:
I installed Magisk using TWRP now (had to flash twrp again using adb). It's strange however that I was not rooted yesterday but Google Pay does not work because it thinks I'm rooted?
So now Magisk Manager says Magisk is installed, and it seems that Google Pay is working again!
Also King Go Root says my phone is rooted now again. (which it was prior to yesterday)
So what really happend then with my phone yesterday? I just want to understand why Magisk was gone, and the phone was unrooted and TWRP gone? Was it because I did try to download and install the package from the phone system update? (which failed anyway, and I did pay with my card after that). This popup just appeared when the phone was picked up before I went to sleep. Any ideas?
Akerhage said:
EDIT:
I installed Magisk using TWRP now (had to flash twrp again using adb). It's strange however that I was not rooted yesterday but Google Pay does not work because it thinks I'm root....
Click to expand...
Click to collapse
I am not sure what happened, but tale a look at this:
https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/
MacGuy2006 said:
I am not sure what happened, but tale a look at this:
https://www.xda-developers.com/magisk-no-longer-hide-bootloader-unlock-status/
Click to expand...
Click to collapse
Wow, thats bad news. Is there any way to lock the bootloader again?
For me, there was no point of unlocking and root the device anyway. (I thought that the Mi Note 10 would have more custom roms without Xiaomi bloat)
And I really need Google Pay to work, because I do not take my pay-card with me. So if a rooted and unlocked phone will cause this to spontaneously fail, it would cause a lot of problems for me.
However, strange that a re-install of magisk made the problem go away? If its a hardware-level key attestation my phone would be blocked even after a re-installation right?
If checking the Safety-Net status right now, Im passed.
Akerhage said:
... However, strange that a re-install of magisk made the problem go away? If its a hardware-level key attestation my phone would be blocked even after a re-installation right?
If checking the Safety-Net status right now, Im passed.
Click to expand...
Click to collapse
Yeah, this is why I am waiting for the OTA. It's good that it's working for you, but it's likely that it will end sometime in the not too distant future.
MacGuy2006 said:
Yeah, this is why I am waiting for the OTA. It's good that it's working for you, but it's likely that it will end sometime in the not too distant future.
Click to expand...
Click to collapse
The same error happend again to me today, so is there any way for me to maybe undo the unlock-thing that makes google pay not working?
Related
just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.
mikeew83 said:
just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.
Click to expand...
Click to collapse
Did you unlock your bootloader?
yep
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.
Had the same issue setting up my bro's galaxy yesterday. I had to flash back to stock via Odin and then I just redid root and unlock boot loader and haven't had issue since. Running the new d2vzw euroskank right now with no issues.
yea
I figured as much i was downloadin the files had to run out so just switched devices real fast while i fix it figure ill just start from scratch once i odin back to stock.
Marcismo55 said:
I wouldn't run the official nightlies for the time being until the data and MMS fixes get approved and merged. CVPS (Austin Dickenson) posted an Alpha 2 on his G+ with those fixes above so you would be better off running those.
Click to expand...
Click to collapse
sent from my unlocked bootloader Verizon Samsung galaxy s III
mikeew83 said:
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.
Click to expand...
Click to collapse
You need to UNLOCK your bootloader not just root. the official CM is a non kexec kernel and you are still running with your locked bootloader
and fixed
just funny to me how far verizon will go to feel like big brother so to speak.
Assuming your bootloader is unlocked. I had the same thing happen the first time. Tried to use CWM, missed the suggestion of flashing TWRP from EZ Recovery. Made all the difference. Watch the video from DroidModd3rX:
Verizon Galaxy S3 Cyanogen Mod 10 Unofficial NONKEXEC Install (I can't post links yet, sorry)
{
"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"
}
Sent from my SCH-I535 using xda app-developers app
is it suitable for daily use??
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.
I had more then just those issues, apparently my phone was sending doubles text messages, also WiFi struggled to keep a solid signal, data also dropped in and out and last but not least screen would flicker. Did a clean install of the nightly build and alpha build and had the same issues.
Sent from my SCH-I535 using xda app-developers app
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I am happy with it. It has rebooted twice on me, once after an hour and a half phone call with Dell tech support, I was tired of talking to the guy anyway . But jelly bean is nice, if you don't need NFC, MMS, or Flash (can't get my side load to work). Guess it is all in the eye of the beholder, if you don't mind some of those issues is suitable.
Sent from my SCH-I535 using xda app-developers app
Mms is working fine as well as flash. What build are you on?
SGS3 production
zxsix said:
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.
Click to expand...
Click to collapse
Not quite stable. It suffers from reboots for some during/after calls..... Me for one. The original alpha build never showed that symptom. Also a lot of people are saying that they are having echo problems on calls.
TAPPED in on my (now unlocked bootloader) Verizon S3
Did the same thing
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.
Nice !
same issue
bluetoast said:
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.
Click to expand...
Click to collapse
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?
rmcneely said:
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?
Click to expand...
Click to collapse
derp....unlock your bootloader!
droidstyle said:
derp....unlock your bootloader!
Click to expand...
Click to collapse
but how?? can't get past this unauthorized software screen
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
It was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Edit: Added img
{
"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"
}
insaneshan3 said:
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
Not sure if this will help anyone or if the boot logo was there to let you know that you can use a custom boot image, but it was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Click to expand...
Click to collapse
While obviously keeping in mind that bad things MAY occur with Triangle Away, of course. Use at own risk.
Could I use ktoonsez kernel with this or?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
insaneshan3 said:
I used Triangle away to reset custom flash counter, both on a stock rooted rom and on goldeneye rom, and both times I was able to get rid of the stupid samsung custom logo with the picture of an unlocked lock.
1. Install triangle away
2. Click reset flash counter (even if it says counter: 0) i think this happens when you have only flashed 1 rom, sometimes under status is shows official but when it boots it says custom.
3. Reboot and enjoy looking at the official S4 logo
4. Profit
Not sure if this will help anyone or if the boot logo was there to let you know that you can use a custom boot image, but it was really bothering me so I found a way to get rid of it, and I thought that I'd share it with you guys.
Click to expand...
Click to collapse
+1 It worked for me after using CASUAL on my S4 (CUAMDL) right out of the box! {removed the "open lock" almost instantly!}
Thanks for the tip!
alternatively, install SuperSU as your su app, let it install binaries, then uninstall whatever other app you were using (it does this automatically), and reboot a few times. Unlocked icon will go away.
No risk of issues from triangle away.
Will this work on non-stock?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
jova33 said:
Will this work on non-stock?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only if the non-stock you are running identifies the device properly. In other words, if you run triangle and it says a different model, do not continue, it will brick, but if it shows the correct device model, go for it.
No dice. I'm on VZW, SCH-I545, it identifies the device properly, says it's going to reboot into Odin mode, reboots, get the blue text at the top that says booting into recovery, then skips to boot animation.
Sent from my SCH-I545 using Tapatalk 4 Beta
cegna09 said:
alternatively, install SuperSU as your su app, let it install binaries, then uninstall whatever other app you were using (it does this automatically), and reboot a few times. Unlocked icon will go away.
No risk of issues from triangle away.
Click to expand...
Click to collapse
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
seanpr123 said:
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
Click to expand...
Click to collapse
I found it through a google search, and it worked perfectly for me. Took about 3-4 reboots, and then the lock icon went away. I'm just running stock rooted software, not sure how it works with other software.
here's the thread
http://forum.xda-developers.com/showthread.php?t=2257058
cegna09 said:
I found it through a google search, and it worked perfectly for me. Took about 3-4 reboots, and then the lock icon went away. I'm just running stock rooted software, not sure how it works with other software.
here's the thread
http://forum.xda-developers.com/showthread.php?t=2257058
Click to expand...
Click to collapse
Ahh ok, do you have a custom recovery?
I'm running TWRP & custom ROM, that must be why.
seanpr123 said:
Tried this and no luck.
How well known and acknowledged is this procedure?
Anything I can do differently?
Click to expand...
Click to collapse
That method seemed to work for some and not for others, with no discernible reason why.
I was stock rooted with stock recovery when I tried it and never did manage to get the custom screen to go away. Thankfully, I realized I could care less about it and went on with my life!
I have a Galaxy s7 930f, it always rebooting every day or second day one time, I made a original firmware install with odin, but it did not help me.
Anybody has a advice.
I tried it with original apps, I did not install any other apps.
It rooted but it is does not matter, it is rebooting with root or without root.
How can I find out what is the problem?
Python_69 said:
I have a Galaxy s7 930f, it always rebooting every day or second day one time, I made a original firmware install with odin, but it did not help me.
Anybody has a advice.
I tried it with original apps, I did not install any other apps.
It rooted but it is does not matter, it is rebooting with root or without root.
How can I find out what is the problem?
Click to expand...
Click to collapse
Hi mate
Maybe something went wrong during rooting , did you reflash your stock firmware again (odin)?
Yes I did it, 4 times, 3 different firmware. I mean tried with btu united kingdom , dbt germany , zto brazil, not helped.
Python_69 said:
Yes I did it, 4 times, 3 different firmware. I mean tried with btu united kingdom , dbt germany , zto brazil, not helped.
Click to expand...
Click to collapse
when that started to happen? from beginning , after rooting....... do you install any apps after flashing with odin? try flashing with odin and not installing anything else and leave it for a day or two to see how it behaves, just to discard if is app related
I did it, I made a clean install with odin, I did not install any apps, but it is rebooting. So I don't know it is rebooting after rooting, or before, because I was rooting immediately when I got it.
Python_69 said:
I did it, I made a clean install with odin, I did not install any apps, but it is rebooting. So I don't know it is rebooting after rooting, or before, because I was rooting immediately when I got it.
Click to expand...
Click to collapse
strange indeed
check this thread , all kind of theories.....sd contact problems , apps , sim.......
http://forum.xda-developers.com/s7-edge/help/getting-random-restarts-reboots-t3327296
Thanks! I try to figure out what is wrong. I hope it is not a hardware problem.
Python_69 said:
Thanks! I try to figure out what is wrong. I hope it is not a hardware problem.
Click to expand...
Click to collapse
Sound like a software issue ...hopefully !
Back in the S3 times were a lots of cases of problems with the power button stuck......check all button just in case one of them is stuck
Let us know
Python_69 said:
I did it, I made a clean install with odin, I did not install any apps, but it is rebooting. So I don't know it is rebooting after rooting, or before, because I was rooting immediately when I got it.
Click to expand...
Click to collapse
Try flashing stock ROM again with Odin, then factory reset from recovery and don't root. See if you still have problems.
EDIT: Sorry, I misread your first post. I would take it back to Samsung, if it happens on a completely stock phone, something hardware-related may be the culprit.
Sent from my SM-G930F using Tapatalk
iridaki said:
Try flashing stock ROM again with Odin, then factory reset from recovery and don't root. See if you still have problems.
EDIT: Sorry, I misread your first post. I would take it back to Samsung, if it happens on a completely stock phone, something hardware-related may be the culprit.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
I did it yesterday, so right now I'm waiting and hope no reboot again.
My stock phone made me mad by rebooting randomly, did a 4-part Odin flash + pit file now. Hope it helps. Before I deleted my accounts from the phone and enabled oem load in developer options. Don't know how to flash a stock Rom any cleaner. Really hoping the damn phone is cured now.
Sent from my SM-G930F using XDA-Developers mobile app
Im experiencing the random reboots and freezes as well but more frequently. Maybe 4 to 8 times a day if phone is used.
On custom, stock, rooted and unrooted. .
Just got the phone 3 days ago ?
Im currently trying out an older firmware but still no luck. Just had another reboot by using android beam.
{
"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"
}
Phone : Samsung s7 G930F
Android: MM 6.0.1
Common triggers ive seen so far
1. Connecting phone to pc and start a file transfer
2. App update or install
3. File transfer from phone to another phone as in the case of Android beam.
But there is still some other random unexplained occurrences.
Phone freezing up I dont know why it does this or what triggers it.
As I was still suffering from those nasty random freezes Samsung changed the Mainboard on warranty.. Now everything is fine. Monday device
Hi XDA,
I flashed a stock ROM on my brand new Galaxy S7, to change CSC code and other country specific changes, because the store sold me the wrong version.
Everything went smooth, and after the flash, I (think) saw an error in recovery. Nevertheless I've heard it's a good idea to wipe data/factory reset + clear cache partition after a flash so I did that, and it went fine.
I then updated OTA to the latest (again, stock) firmware w/o problems.
When booting into recovery, these screens appear. First a "Installing system update" and then a warning screen.
http://i.imgur.com/unFzLNf.jpg http://i.imgur.com/eYDfJdu.jpg
{
"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"
}
When shutting down the phone it prints out messages, writing verifies has diverity (or something) and successfully does that.
Then this error appears:
Code:
[B]E: Failed to mount /data (no such file or directory)[/B]
And no other errors. Everything seem to work fine. What does this error mean, and is it important?
What is the E: drive?
Is it because it did not upgrade the bootloader successfully? Or recovery? Or? Would clearing cache help?
Bonus info: KNOX is not tripped, and the phone isn't rooted
My s7 is also displaying exact the same. But thats normal process i think. My phone isnt rooted or tripped knox also. When entering recovery looks same as above.
V_B said:
My s7 is also displaying exact the same. But thats normal process i think. My phone isnt rooted or tripped knox also. When entering recovery looks same as above.
Click to expand...
Click to collapse
Okay, glad to hear. Are you running stock rom?
AndroidifyIt said:
Okay, glad to hear. Are you running stock rom?
Click to expand...
Click to collapse
Yes completly untouched stock firmware...
V_B said:
Yes completly untouched stock firmware...
Click to expand...
Click to collapse
Hmm, you surely must have flashed a stock rom if you see the warning screen with the dead android. Because it should only appear if the phone has been tampered with externally AFAIK.
AndroidifyIt said:
Hmm, you surely must have flashed a stock rom if you see the warning screen with the dead android. Because it should only appear if the phone has been tampered with externally AFAIK.
Click to expand...
Click to collapse
Nope i only send the phone to samsung cause had some troubles maybe they flashed something. But im pretty sure before it was the same. When entering recovery it Shows installing update and than the dead android and after that im in recovery
So I got an update last night on my J7 2016 with MetroPCS. I wanna update it, but I'm rooted and don't wanna screw anything up. Should I take the update, or hold off? Thanks in advance
{
"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"
}
It is nothing important, as samsung says, overall improvement, what is bothering me is how did you get that update since you are rooted
I also received this update yesterday. I spoke with T-Mobile. They told me it was an update from Google. They also told me that I was one of the few customers out of the thousands to receive it. It was not in their system they had to update it themselves. Still kinda sketchy.
Ragazzza said:
It is nothing important, as samsung says, overall improvement, what is bothering me is how did you get that update since you are rooted
Click to expand...
Click to collapse
I have no clue. The same thing happened twice when I had my LG G Stylo with the same company. It's kinda weird. I guess I'll just hold off on the update until further notice. Thanks though
SuperSancho said:
I also received this update yesterday. I spoke with T-Mobile. They told me it was an update from Google. They also told me that I was one of the few customers out of the thousands to receive it. It was not in their system they had to update it themselves. Still kinda sketchy.
Click to expand...
Click to collapse
It was from one of them though, so I guess I can trust it somewhat, but I don't wanna update it with a risk of screwing this phone up. I guess I can hold off for a bit
Yeah, this update bricked my device. SM-J700T.
Accidentally allowed it when clearing the annoying notification while watching youtube. Failed to flash properly. Somehow flashed a new sboot.img still. Tried to reinitialize with smart switch, but its still only listing apk6, and the update managed to only flash the sboot.img from AQC3, so i cant go back to APK6.
I tried as well with the AP from sammobile, and now have unknown baseband and invalid imei. Well, I'm 6 days away from my jump anyways, but I'd rather stick with this phone a while longer.
Any thoughts or advice? It boots, and it shows apk6 for build.
Hell, If any of you have the update.zip, I might be able to fix it still. I pulled the update from cache I thought, but it seems to be corrupt. Hell, maybe that was the problem? Maybe I can pop the update on sd (if anyone has it and would be willing to share?) and use stock recovery to flash it, and see what happens?
Thanks for any input.
EDIT: I have a friend with the same device, who was unrooted and on the new update. He wanted his rooted anyways, so I installed twrp, and used it to pull a backup of the system image, the radio image, the cache image, and used those to restore my phone. All is good. We're both on the last update, rooted and feelin good.
social.catastrophe said:
Yeah, this update bricked my device. SM-J700T.
Accidentally allowed it when clearing the annoying notification while watching youtube. Failed to flash properly. Somehow flashed a new sboot.img still. Tried to reinitialize with smart switch, but its still only listing apk6, and the update managed to only flash the sboot.img from AQC3, so i cant go back to APK6.
I tried as well with the AP from sammobile, and now have unknown baseband and invalid imei. Well, I'm 6 days away from my jump anyways, but I'd rather stick with this phone a while longer.
Any thoughts or advice? It boots, and it shows apk6 for build.
Hell, If any of you have the update.zip, I might be able to fix it still. I pulled the update from cache I thought, but it seems to be corrupt. Hell, maybe that was the problem? Maybe I can pop the update on sd (if anyone has it and would be willing to share?) and use stock recovery to flash it, and see what happens?
Thanks for any input.
EDIT: I have a friend with the same device, who was unrooted and on the new update. He wanted his rooted anyways, so I installed twrp, and used it to pull a backup of the system image, the radio image, the cache image, and used those to restore my phone. All is good. We're both on the last update, rooted and feelin good.
Click to expand...
Click to collapse
Good to know man. one of my friends almost updated it on accident, i was lucky to pull the battery on time. Thanks for that
Juncojam said:
Good to know man. one of my friends almost updated it on accident, i was lucky to pull the battery on time. Thanks for that
Click to expand...
Click to collapse
Glad to help! Or glad to suffer a problem so you don't have to, maybe?
social.catastrophe said:
Glad to help! Or glad to suffer a problem so you don't have to, maybe?
Click to expand...
Click to collapse
Lol that also works:good: