Related
Just got to know that Pantech has released the much awaited Jelly Bean 4.1 for the Flex through OTA AT&T software update.
Like many others, I'm using the flex outside US, therefore, cannot update my flex.
Would request someone to upload the OTA JB zip file.
Can't wait to see Jelly Bean on the Flex.
PS: Check out the Pantech website for this great news
This is good news. I wish I wasn't rooted with CWMR so I could get this. Tried flashing stock recovery.img and boot.img files but get NOT SUPPORT.
Anyone know a way to get this phone back to complete stock so we can get the Jell Bean goodness?
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Tersanyus said:
I managed to unroot and restore stock recovery.
Got prompted for the update, it downloaded and installed fine!
This little Flex seems quite a bit better with Jelly Bean. Wish it had been 4.2 but 4.1 is fine.
Click to expand...
Click to collapse
Can you upload the update file?
How did you unroot?
Sent from my PantechP8010 using xda app-developers app
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
---------- Post added at 01:09 PM ---------- Previous post was at 12:52 PM ----------
I knew from experience I had to go to stock recovery and unroot to update.
I flashed a stock rooted nandroid backup I had made after rooting initially.
To unroot I think I went into the SuperUser app and choose option to unroot.
Stock recovery file is posted in a thread here somewhere, had recovery.img and boot.img.
Tried flashing those in fastboot but only got NOT SUPPORT mesage.
I took a flashable zip file that had CWM recovery.img file in it and replaced it with the stock recovery.img and flashed it in CWM.
Once stock recovery was on the phone when I tried to use it I only got a little android symbol lying on its back with a red exclamation point.
Phone booted fine and worked ok
Couldn't get it to see the AT&T update until this morning.
Things I have noticed in this new Jelly Bean build for our little Flex:
Of the stock AT&T apps only 3 I could disable (ugh), why no Disable button
good news
Tersanyus said:
Not rooted anymore so probably can't get the update file. It was like 264MB or something.
Not planning to root this phone again.
Interesting that the Pantech diag menu shows still rooted and tampered, it's definitely not rooted.
It should be 100% stock.
If you know of a way to get the file off the phone I can look for it.
Click to expand...
Click to collapse
Basically you will find the update in the /cache folder.
I'm not sure if you you can access this folder without being rooted. You can give it a try using the ES File Explorer.
Let me know if you get the update.
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Oh that's bad!
Actually, there's another way. If you can share your system nandroid backup, maybe that can help.
Try Rooting
Tersanyus said:
ES File Manager did see the cache folder and all the other system folders. It was empty. I'm sorry, I factory reset the phone last night from stock recovery since it was not updating built in apps properly. Never seen stock recovery on this phone before. It has an option for root. I selected it. Downloaded a few root checker apps, not rooted.
I'm sorry if I hadn't reset it last night I might have found the file. I'm sure it will turn up somewhere. This little Flex doesn't have much in the way of development but someone here at XDA will get it sooner or later.
Click to expand...
Click to collapse
Why dont you try to root with this method http://forum.xda-developers.com/showthread.php?t=1886460 ,its the same you used to root 4.0.4 I guess, should work, pull out the update and then unroot the phone as you dont want it rooted.
It happened to me, even rooted I wanst able to see /data content with ES File Blablabla, then tried with root explorer and worked fine.
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Thanks for your help
Tersanyus said:
I'm not going to root this Flex. It's not a primary phone for me (never was). It is used as a spare now and can be used by novice users in my family and friends. Don't want them to have a rooted phone. I'd been wanting to get this phone back to complete stock for a while but hasn't really put much effort into it.
When I saw that Pantech released JB for Flex a few days ago that was my motivation to get it back to stock. Frankly I was surprised I was able to get it back to stock and not brick the phone!
I'm uploading the stock rooted rom I have. Luckily I saved that on my computer. It's uploading to Dropbox now so it will take a while.
Click to expand...
Click to collapse
Well, thanks for the file, I'm outside US and even on stock, update notification doesn't prompt.
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Wait...
kneemeister said:
I got mine back to Stock, but when I hit check for upgrade it says..."Previous session is running. Please Try Later"
I have wiped it several times. any ideas?
Click to expand...
Click to collapse
I can see ATT's software updater sucks, we just can wait for our friend's upload.
Here it is: Link removed, Dropbox suspended it.
That should be a stock but rooted rom. Nothing else done to it at all. At least. I had that on the phone for a while as a backup when I was playing with roms for the flex.
Probably only going to leave this link up for a day. I'd make your own nandroid backup first. You'll probably get an md5 error in CWMR but there are instructions for fixing that around. I think it was ADB commands that had to fix it. I know the instructions for clearing the md5 error are in one of the flex rom threads, not that there were many of those. The standard disclaimer applies, if this nandroid backup bricks your phone, I can't help you.
I got the same previous session message too. Then it said no update after wiping. I think the best thing is just wipe and don't check for updates. Leave phone on, wifi on and wait for the phone to check on it's own. I got the prompt in a few hours.
Hope this helps you.
So, need to flash stock recovery after restoring nandroid correct?
Sent from my PantechP8010 using xda app-developers app
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Still waiting
Tersanyus said:
Likely if you do not flash stock recovery in CWMR the update will fail. I tried to take the update before flashing stock recovery, it failed each time. I had already unrooted though. Pretty much what I have learned from flashing various phones over the years is that if you are not stock completely any OTA updates from the carrier will fail or soft brick your device.
I think the Flex was one where I had just that issue. There was some AT&T update a few months back, I said to apply it and I got stuck in recovery. Every time I rebooted the phone it just booted to recovery. Found out if I went into the diag screen on the Flex and choose reboot from there I could boot normally. Eventually I figured out I had the wrong boot.img on the phone. Once that was fixed the phone booted fine. But the update never worked.
You can try to take the update with CWMR but I doubt it will work and could brick or soft brick. I've learned to never take an OTA update from the carrier if you are not completely stock.
Click to expand...
Click to collapse
Im on stock and I cant update, no root, stock recovery, Ive been waiting for the update and nothing.
I dont know if is because Im outside US
I got mine back to stock and unrooted, but the upgrade still fails at about 25% and reboots. If I clear cache and wipe, it will download again, then fail again. Even after flashing back to stock, recovery still says rooted and so does the software upload screen. But I have confirmed that I am no longer rooted. I am about to give up.
So my Galaxy S4 has been rooted for over 2 months now. I had heard about a move to SD card update on OTA and had to install it, I originally had TWRP recovery installed with custom backups. But when I went back to a stock backup and attempted to take the update it wouldn't allow me to with a 410 error. I flashed a file through Odin replacing TWRP with stock recovery (still couldn't install the OTA updates) And finally installed the updates through my pc on a Verizon software. I had lost root and got it back an hour later, but now I can't get TWRP back to flash a few mods. (Getting rid of annoying Wifi bar, sound boost, Wifi toggle) Any advice? When I try to install TWRP through GooManager it boots into download Odin mode. And I don't even have access to Odin anymore, I tried to flash back through Odin and it keeps saying Auth fail. Any advice would be appreciated. Feeling kinda lost here, Searched all over the threads and came up with nothing. Just feels less safe with my galaxy s4 without anyway to back it up if anything goes wrong.
Model Number SCH-I545
Android Version: 4.2.2
Baseband Version: VRUAME7
Secure boot status: Samsung
Thanks in advance.
DemonSoul1996 said:
So my Galaxy S4 has been rooted for over 2 months now. I had heard about a move to SD card update on OTA and had to install it, I originally had TWRP recovery installed with custom backups. But when I went back to a stock backup and attempted to take the update it wouldn't allow me to with a 410 error. I flashed a file through Odin replacing TWRP with stock recovery (still couldn't install the OTA updates) And finally installed the updates through my pc on a Verizon software. I had lost root and got it back an hour later, but now I can't get TWRP back to flash a few mods. (Getting rid of annoying Wifi bar, sound boost, Wifi toggle) Any advice? When I try to install TWRP through GooManager it boots into download Odin mode. And I don't even have access to Odin anymore, I tried to flash back through Odin and it keeps saying Auth fail. Any advice would be appreciated. Feeling kinda lost here, Searched all over the threads and came up with nothing. Just feels less safe with my galaxy s4 without anyway to back it up if anything goes wrong.
Model Number SCH-I545
Android Version: 4.2.2
Baseband Version: VRUAME7
Secure boot status: Samsung
Thanks in advance.
Click to expand...
Click to collapse
Don't know how you came up with nothing cause its posted all over the place. I hate to say it but you should have read FIRST and updated second. You are now officially screwed. At the present time there is only a root method for me7. You CANNOT install any custom recovery on that firmware. They changed/locked the boot loader with that update. No flashing back to MDK, no nothing. That is why there is a sticky in the general thread called Bounty. There is about $3000 worth of donations ready to go to the first person to crack the boot loader. But ad of now, no solution. Sorry man, always read first before you OTA. Hope you enjoy you apps2sd.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
It's not as though this isn't well documented- it's all over the forum and should be common knowledge at this point. You now have a device on which the loki exploit has been patched. You cannot install a recovery, kernel, or rom at this point.
If there is ever another exploit discovered, I would hope you have learned a lesson about die diligence and blindly flashing updates without having an inkling about what the update entails. Had you done your die diligence, you would have not only known about the patched bootloader, you would have also known how utterly useless the "apps to sd" feature is.
Sent from my SCH-I545 using Tapatalk 4 Beta
Wasn't just the App 2 SD I also wanted to leave hyperdrive to go back to stock. Hyperdrive would constantly crash when I run the OTA app. And S health wouldn't properly count correctly (Not that S healths important) But still a minor bug. I appreciate everyone's response, and will be keeping an eye out for the next exploit (if). Least I won't be spending all day browsing for a way to install a custom recovery. And SQLite Editor helped remove the Wifi annoying notification and added a wifi toggle. (main things I wanted to mod) And I am pretty sure there is a way around the sound increase without flashing. Anyways, sorry I was dumb and wasted 5 minutes of your guys time. And thanks for the advice. Will leave a small 20$ tip to the donations also.. xD
Hi all, I originally rooted my phone using this post several months ag http://forum.xda-developers.com/showthread.php?t=2380325
I'm still fairly new to the dealings of root, and have found that I only used it to have access to a couple of cool apps that required root and at that rate I don't even use any more. That being said, I finally accepted the most recent update being okay that I would likely loose my root access. The update kept failing, I assumed because of the root. I backed up my personal data, and performed a factory reset from the phone. The phone still has superuser from the reset and still fails to update. Could someone help me return my phone to fully stock configuration? Thanks!
zomsoc said:
Hi all, I originally rooted my phone using this post several months ag http://forum.xda-developers.com/showthread.php?t=2380325
I'm still fairly new to the dealings of root, and have found that I only used it to have access to a couple of cool apps that required root and at that rate I don't even use any more. That being said, I finally accepted the most recent update being okay that I would likely loose my root access. The update kept failing, I assumed because of the root. I backed up my personal data, and performed a factory reset from the phone. The phone still has superuser from the reset and still fails to update. Could someone help me return my phone to fully stock configuration? Thanks!
Click to expand...
Click to collapse
Find out what odin is. Then..
Google "odin emergency tar (your build number here)" or something to that effect.
If you don't know your build number then you have some more research to do. Good luck.
I'd recommend using the Verizon update assistant. Much easier, but takes about half an hour to do:
1) Connect phone to PC using USB cord
2) When prompted for what action to take when this device is connected, select Verizon update assistant. Installation will take a few minutes.
3) Start the update assistant and confirm that you want to update the phone. The update will take a few minutes.
When the update is complete, you should have the most current update (MK2), and no root access. Should you need root again, try Saferoot - it's quick and easy:
http://forum.xda-developers.com/showthread.php?t=2565758
Thanks for pointing me in the right direction guys, I'll do some more research into both and report back soon.
Help! I've researched odin, downloaded and attempted to flash the stock image. Odin failed. My phone as of now is stuck in the downloading screen.
zomsoc said:
Help! I've researched odin, downloaded and attempted to flash the stock image. Odin failed. My phone as of now is stuck in the downloading screen.
Click to expand...
Click to collapse
You need to flash the same stock image as what was previously on your phone.
If you don't know what version you were on previously, flash MJ7 or MK2.
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
nuar_y said:
I connect my Galaxy Mega (i9205) to kies and it showed that my phone have new update. Bear in mind that my phone is rooted previously (CWM). Kies updated my phone to I9205XXUCNA3. I update my phone with no problem (it took longer time only) but unfortunately KNOX ruined everything. It keeps on saying that SuperUser is trying to access the system. Furthermore, my Wifi is not working at all. I tried to click on the toggle button but no to avail.
So after searching, I found out how to disable KNOX - By flashing using vcoreroot-v2. Done flashing with this file, and now I can't see my interna; SDCard. I'm doomed and now I don't know what to do to turn back to how it was before.
Anybody that can help me, really appreciate it.
Click to expand...
Click to collapse
I see that so far you have found a way to disable knox AND cripple your Mega...
IMHO the best way to fix this situation is:
1. Download once more your newest firmware I9205XXUCNA3 (e.g. from Sammobile) and flash it by Odin to resolve starting position. Or try to restore your firmware through Kies.
2. Then BEFORE YOU DO SOMETHING read forums to find information how safely root firmware with KNOX. You have to be known so probably your warranty is already void and if not so it will be on the first attempt to root your unit. You are warned... There are some threads about rooting KNOX-ed firmware and even how to come back (partially) to previous build.
BEWARE! Do not attempt to flash older firmware lest you brick your Mega. New bootloader prevent from downgrading and if you try you will have endless bootloop. Upgradindg to newest firmware is one way trip.
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
nuar_y said:
OK I've followed your advise:
1. Re-download I9205XXUCNA3 from Sammobile and flash using odin.
2. Re-apply vcoreroot-v2
and after reboot.... WALLA!! My phone is back to normal again! And same goes to my internal SDCard, back as normal.
I have a problem with messaging where it keeps on crashing at first. But then I boot into recovery, clear cache and apply factory reset.
Now, all back to normal.
Anyhow, thank you so much for the tips. Now I can ease out a bit
Click to expand...
Click to collapse
I am glad you are successful. Sometimes you have to repeat two times, but no more: one for download errors, two for your errors. But if then you are not successful... then you have to look for another solution...
Can I know what rom u are using before updating to stock rom using kies?
Sent from my GT-I9205 using XDA Free mobile app
Hello! Sorry for my panic and sense of urgency, but I'm currently away for school and my lease is ending at the end of the month and I have no way to contact my parents, real estate agents, movers, or anything now. All I have is my phone and computer, and I haven't renewed my internet for the month so it should be shut off any day now as well.
But I was running Lollipop (OC1) and rooted my phone the other day with the terrible KingRoot. I attempted to use this app that was supposed to remove KingRoot and replace it with SuperUser but it only removed KingRoot - nothing else. So I lost root access, but still had all the KingRoot crap on my phone. Today a Verizon update appeared on my phone and I clicked install - I didn't think anything of it because it wasn't a major OS upgrade, just a small patch. Plus I thought it'd help remove KingRoot. Uh oh. I was wrong.
I installed the update, it went into recovery and then attempted to install. next thing I know all I see is a black screen. I tried pulling the battery and rebooting it, but I can't get passed the Samsung logo - it just goes to a black screen (but I believe it's still on, draining battery). If I try to boot into recovery it INSTANTLY starts auto-installing this update, which it of course always fails to do and gives me an error message.
My brother said I need to use 'ADB' but he's busy and can't email me much more information. I'm entirely lost, panicked, and scared! I need my phone working soon. I'm assuming theres no way to 'fix' my phone - so I'm just going to have to suck it up and realize I lost everything (man I wish I saved a lot of people I was texting as contacts *face palm*). What can I do now?
P.S. If I need to install a new ROM or whatnot over this, then can I do so with a pre-rooted Lollipop ROM? That way I don't have to risk using KingRoot ever- ever again. NOTE I NEED ROOT FOR WiFi TETHER! My internet is being shut off very soon, so to get by in the meantime I planned on using my phone and its tether.
No... You need internet access..
BUT... If you backed up everything to the external SD, then you can regain contacts..
Otherwise, Any attempt to fix it won't do anything...
ADB won't work on this phone either...
What you need to do is download a program called Odin, and a OC1 stock tar... That will recover your phone, but you will lose all contacts unless you had the Verizon contact thing...
I had the exact same experience as you yesterday... I had to put my phone in Download mode and start fresh with the Verizon Software Update Assistant. All I really cared about was my pictures, and they were on the external SD card. The other response about using ODIN to go back to OC1 works just as well... Best of luck!
Odin is your friend
Don't panic. You're contacts and other media of a similar nature are usually backed up regularly enough if you don't mess with the default sync settings of your stock rom. We can all agree Kingroot is a terrible way to root because of it's unnecessarily bloated bundle that it installs along with its super user app. To get your phone working you need to 'Odin' back to stock and from there you can root and install a custom rom. However your choices are very finite because of the new SELinux enforcing files on the OC1 build for the Verizon bootloader.
Step 1) Download Odin here ---> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Step 2) Download the stock OC1 Build ROM for the SCH-I545 (Verizon Galaxy S4) here ---> http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-5-0-1-lollipop-oc1-t3174850
Step 3) Once the download has finished (use DownloadThemAll add-on in FireFox to boost download speed) load the tar.md5 file into Odin
using the AP button.
Step 4) Put your phone into download mode and plug it into your computer. Make sure the cables aren't loose and click start in Odin.
Step 5) Wait for the phone to reboot and for the com-slot in Odin to turn green (will say "PASS!!" when complete).
If you use KingRoot to root the phone then I suggest googling how to replace KingRoot with SuperSu and following the tutorial W0lfdroids website here ---> http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html