Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.
Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.
ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.
erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.
help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?
Related
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.
vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?
GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.
vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.
I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.
I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly
The Knox Bootloader is.... Annoying
Anyone know if I could flash the MF9 tar in ODIN and revert back to the 4.2 Bootloader
do not you will even cause bigger problems stay cool untill a tar is released they are working hard to see what they can due the only choice you have no is to go to a ROM that is 4.3 but that I know of it is still un heard of KNOX is a whole new monster that I have a feeling is gonna tick a lot of people off love love love Samsung phones but they need to realize this could hurt them....
NO.
Sent from my SPH-L720 using Tapatalk
jprocket45 said:
do not you will even cause bigger problems stay cool untill a tar is released they are working hard to see what they can due the only choice you have no is to go to a ROM that is 4.3 but that I know of it is still un heard of KNOX is a whole new monster that I have a feeling is gonna tick a lot of people off love love love Samsung phones but they need to realize this could hurt them....
Click to expand...
Click to collapse
Thanks for the reply. If I had known that KNOX was gonna be such a problem I would of held off from upgrading...
Guess I gotta be patient until our beautiful dev community comes up with some way to deal with KNOX
Robin Dhicke said:
Thanks for the reply. If I had known that KNOX was gonna be such a problem I would of held off from upgrading...
Guess I gotta be patient until our beautiful dev community comes up with some way to deal with KNOX
Click to expand...
Click to collapse
so there is no way to go back to MDC then huh? -/-
kalanir said:
so there is no way to go back to MDC then huh? -/-
Click to expand...
Click to collapse
Well not yet.
Sent from my SPH-L720 using xda app-developers app
nope stuck just like the rest of us lol its not fun
Don't worry......it's only a matter of time. If u need a stable rom, I highly recommend sac23's custom 4.3 rom. V3 will be out soon. This rom has made it easier to cope with 4.3, well easier for us who are stuck with the Knox......check out his thread. You'll love it.
Sent from my SPH-L720 using XDA Premium 4 mobile app
I'm not sure what any of you are talking about. I updated to 4.3 a couple of days ago, then wiped and flashed a MDC tar with ODIN and brought it back to MF9 with OTA updates. Everything is fine.
---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------
Robin Dhicke said:
The Knox Bootloader is.... Annoying
Anyone know if I could flash the MF9 tar in ODIN and revert back to the 4.2 Bootloader
Click to expand...
Click to collapse
Yes... You can do this. I did it. See my last post above.
Sleepycloud said:
I'm not sure what any of you are talking about. I updated to 4.3 a couple of days ago, then wiped and flashed a MDC tar with ODIN and brought it back to MF9 with OTA updates. Everything is fine.
---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------
Yes... You can do this. I did it. See my last post above.
Click to expand...
Click to collapse
Hello,
How did you manage to do it?
I tried to do that with Odin 1.85 and 3.07 and nothing. It aborts right away.
edgardch said:
Hello,
How did you manage to do it?
I tried to do that with Odin 1.85 and 3.07 and nothing. It aborts right away.
Click to expand...
Click to collapse
I wiped everything in TWRP, and rebooted into download mode. Then flashed the tar with 3.07 and a PIT file. Uncheck reboot. Check Repartitition, Nand erase, and F. Reset Time. When it reboots it wiil update in recovery with the little andy dude, and then reboot to load up. I pull the battery and factory reset. It works fine. I updated to 4.3 friday morning. and decided to go back to MF9 so that I could use The HotSpot Mod and Reboot Menu. F**k 4.3...it was disapointing.
EDIT-----> READ ALL OF THE FOLLOW-UP POSTS BEFORE YOU TRY THIS.... MY PHONE HAD A UNIQUE SITUATION AND THIS WILL NOT WORK FOR MOST EVERYONE ELSE.
Sleepycloud said:
I wiped everything in TWRP, and rebooted into download mode. Then flashed the tar with 3.07 and a PIT file. Uncheck reboot. Check Repartitition, Nand erase, and F. Reset Time. When it reboots it wiil update in recovery with the little andy dude, and then reboot to load up. I pull the battery and factory reset. It works fine. I updated to 4.3 friday morning. and decided to go back to MF9 so that I could use The HotSpot Mod and Reboot Menu. F**k 4.3...it was disapointing.
Click to expand...
Click to collapse
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
There is one problem. Now it won't update to MJA. Something is different, but I'm not sure what. I don't care if you don't believe me. I did it, and that is how I did it. There was one other issue. It kept redownloading the Sprint Default Configuration over and over and over. Like more than 50 times back to back.I finally deleted the apk to get that to stop. Outside of that, my phone works fine. I believe their are remnants of 4.3 and that is why it says the system is up to date on MF9 and does not prompt me for the 4.3 update. I really don't know, but m phone appears to be working perfectly.
Sleepycloud said:
There is one problem. Now it won't update to MJA. Something is different, but I'm not sure what. I don't care if you don't believe me. I did it, and that is how I did it. There was one other issue. It kept redownloading the Sprint Default Configuration over and over and over. I finally deleted the apk to get that to stop. Outside of that, my phone works fine.
Click to expand...
Click to collapse
As in tkaimg the OTA or trying to flash MJA ROM like Skyrockets or Sacs ?,
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
As in tkaimg the OTA or trying to flash MJA ROM like Skyrockets or Sacs ?,
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
The OTA. It doesn't recognize any update as being available anymore. It went from MDC to MDL to MF9 just fine. Then stopped. It says it's up to date now? I'm not sure what's going on with it, but I rerooted it and it works fine. I even innitialised it on KIES to set it all the way back to stock MF9 but it still won't show any update as being available for 4.3
daniel4653 said:
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I tried it just barely as I want to go back to my mf9 rom with the stock kernel. You get a secure error on pit and also a firmware revision error "fused 4 .... 1" can't remember what the word was where the dots were. It was a no go for me. I tried to odin back to mdc like was mentioned in the previous posts.
:EDIT Definitely don't try this. Caused my data partition to get corrupt. Couldn't format it. Couldn't pit restore it. Philz recovery couldn't mount it. Finally found an option to format data and sdcard. This allowed me to format data and restore. Once again Definitely don't try if you have the mja bootloader. (I'm back up and running and will let other figure this out.)
I just found out why I was able to go back to 4.2.2!!! When I updated to 4.3 via OTA a couple of days ago, I plugged it in to KIES 3 and noticed it said "PDA:MJA, Phone:MF9, CSC:MJA".... notice the phone says MF9! I don't know how that happened, but I didn't question it at the time because it was OTA. I thought it was supposed to be that way. Last night before I went to bed I manually flashed the 4.3 update zip after using KIES to initialise my phone back to complete stock. (It wouldn't load the zip when I was rooted) Anyways.... Well this morning I plugged it in to KIES 3 after flashing the 4.3 update.zip last night and it said MJA on all three. I'm not sure how that happened, but I only got part of the OTA update a couple of days ago it appears, and thus being, it is the reason I was able to revert. Sorry if I got anyones hopes up. I just went back and edited a warning in my first post with instructions.
Bummer!!! lol i was getting all excited.
wilsonwa said:
I tried it just barely as I want to go back to my mf9 rom with the stock kernel. You get a secure error on pit and also a firmware revision error "fused 4 .... 1" can't remember what the word was where the dots were. It was a no go for me. I tried to odin back to mdc like was mentioned in the previous posts.
:EDIT Definitely don't try this. Caused my data partition to get corrupt. Couldn't format it. Couldn't pit restore it. Philz recovery couldn't mount it. Finally found an option to format data and sdcard. This allowed me to format data and restore. Once again Definitely don't try if you have the mja bootloader. (I'm back up and running and will let other figure this out.)
Click to expand...
Click to collapse
I'm having the same issue that you had with the data partition being corrupt. I had stupidly tried to downgrade stock MJA to MF9 before checking with the forums if it was possible. It got stuck in the Firmware error message (can't remember what it exactly said), but got to restore it to a stock MJA. And now its data partition cannot be recognized in any computer. IE: Whenever I plug it into the computer it used to show that it is connected via USB and give me the MTP option. Now it will not even do that and I cannot access its data partition via the computer. Kies won't even recognize it.
How did you get to format data and sdcard?
EDIT: OK, dont know how, (I'm blaming crappy cable) but now I do have access to the phone. In other words it's working normal. But in case that this were to happen again, it would be awesome to know how to format data section, so as it can be recognized by the computer. Thanks in advance.
I downloaded the official OTA update. When I went to install it the phone needed to reboot and now I've been stuck looking at the Green Android screen saying Downloading... Do not turn off target!!! and in very small writing could not do normal boot, Odin mode. I am rooted. Please help
What version is the phone? I'm reading up on things in preparation of updating myself. I'm on MF3 and for what I've read I need to Odin back to stock before updating since I'm rooted. This may not be your case figured I'd toss it out there.
brought to you by my not so sexy GS4 MF3
padgaland said:
I downloaded the official OTA update. When I went to install it the phone needed to reboot and now I've been stuck looking at the Green Android screen saying Downloading... Do not turn off target!!! and in very small writing could not do normal boot, Odin mode. I am rooted. Please help
Click to expand...
Click to collapse
Same with me. I'm stuck at the emergency firmware recovery screen. My phone was at 4.2 and it did the OTA to 4.3.3 and froze. What do I need to do to go back to stock rom?
SGH-I337 16GB.
schreiber37 said:
Same with me. I'm stuck at the emergency firmware recovery screen. My phone was at 4.2 and it did the OTA to 4.3.3 and froze. What do I need to do to go back to stock rom?
SGH-I337 16GB.
Click to expand...
Click to collapse
You i think you should use Kies to go back they actually have a feature for that. Mine won't even be recognized by the computer or anything.
I am rooted and I was running 4.3 GoldenEye v 11 rom BTW awesome ROM and Dev support best I've ever seen on xda. Any way today I installed my nandroid back up of stock ROM 4.2 Att gs4 sgh 1337 let it boot up any settle in 10 min..when I looked at phone I saw the Att redwhite arrows in task bar I quick shut down WiFi and now under settings status it says update continue or something .now my back up is mdb never ota before. so is this update mf3 the one u that is bootlocked or is it the 4.3 update?? I read some were Att was to start with 4.3 update yesterday what u guys think I should do? Thanks in advance ..
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Ok I am going to try to go back to stock by using a firmware DL and Odin v3.07 If it works I will tell everyone. If not I may be screwed.
I'm currently on MF3 and had rooted my device previously and would like to upgrade to the new OTA. Would someone be so kind to link me to ODIN and the stock file,so I may return to stock and apply the OTA.
Thank you,
Did anyone go to recovery and factory reset?
Sent from my Nexus 7 using Tapatalk 4
Andrew149 said:
Did anyone go to recovery and factory reset?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'd recommend it but it's to late for me.
This worked for me to unroot.
To unroot, try this. It worked for me. I'm back to "official". However, I've downloaded 4.3 like 5 times already. I can download 100%, but when it reboots to install it stops at 30% then says update failed.
http://forum.xda-developers.com/showthread.php?p=45301834
Ditto
silrosriv said:
To unroot, try this. It worked for me. I'm back to "official". However, I've downloaded 4.3 like 5 times already. I can download 100%, but when it reboots to install it stops at 30% then says update failed.
http://forum.xda-developers.com/showthread.php?p=45301834
Click to expand...
Click to collapse
Same exact problem!
wading through threads for answer!
Ok I have my phone working again. I am not on 4.3 but its back to where it was before I started, which is better than nothing. After running Odin once and it failing like it always does (I have never seen it work) I was able to get the holding down volume, home and power button option to work and I just said no and to reboot and it worked. I then went into SuperSU app and unrooted. I will try to update to 4.3 at a later time. I am glad I wasn't the only one having issues. I usually pride myself on knowing technology and being able to figure it out.
silrosriv said:
To unroot, try this. It worked for me. I'm back to "official". However, I've downloaded 4.3 like 5 times already. I can download 100%, but when it reboots to install it stops at 30% then says update failed.
http://forum.xda-developers.com/showthread.php?p=45301834
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems.
So if I oden to stock again don't root Then hit the update it should go? Weird thing is I installed my back up today and it a stock backup fresh rich from a oden wipe and it stared DL on its own before I stopped it with killing WiFi. I s this 4.3 update or is it mf3 since I never did that update. ..help. Thanks
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
tried that..didnt work
padgaland said:
Ok I have my phone working again. I am not on 4.3 but its back to where it was before I started, which is better than nothing. After running Odin once and it failing like it always does (I have never seen it work) I was able to get the holding down volume, home and power button option to work and I just said no and to reboot and it worked. I then went into SuperSU app and unrooted. I will try to update to 4.3 at a later time. I am glad I wasn't the only one having issues. I usually pride myself on knowing technology and being able to figure it out.
Click to expand...
Click to collapse
Tried unrooting through SuperSU and managed to still be rooted after reboot, and OTA 4.3 still didnt work
SIGH
Read that u have to oden to stock dint root and the try ota they say this worked gunna oden back to stock and try..
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
thanks
ralphie1267 said:
Read that u have to oden to stock dint root and the try ota they say this worked gunna oden back to stock and try..
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
could you point me in the right direction for that procedure? Im trying to do it on my mac using hiemdall but I think im about to go try odin on a PC.
MasterShakeMan said:
Tried unrooting through SuperSU and managed to still be rooted after reboot, and OTA 4.3 still didnt work
SIGH
Click to expand...
Click to collapse
Take it to Best Buy. "Kies broke your phone" *wink*wink* and they can flash it back to stock without messing up your data. You can do it yourself. Plus they have this mysterious awesome SMART tool. Lol
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
MasterShakeMan said:
could you point me in the right direction for that procedure? Im trying to do it on my mac using hiemdall but I think im about to go try odin on a PC.
Click to expand...
Click to collapse
Use the link in my previous post (post #13). That has the files and procedures for using Odin to get back to stock 4.2.2 and then you can do the OTA upgrade from there.
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
motel6man said:
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
Click to expand...
Click to collapse
Same problem here,
I'm going to try and install a kernel through TWRP. I've tried a fresh root / loki install, same issue.
For me, I remember having to install an AT&T compatibility pack.zip file on previous Hyperdrive releases, like RLS 10.
I tried to install RLS15 and at the very end of install, it says this:
Flashing Kernel
file_getprop: failed to stat"/tmp/aroma/kernel.prop": No such file or
directory
However, for some reason, after trying to install this new release, I was not able to restore data in TWRP from a backup of RLS 10. I was able to restore to a non-rooted backup (i don't know how), and it appears that I am not rooted anymore, and I don't think I have superuser anymore. So, I'm not exactly sure where to start.
Glad to see I'm not the only one this is happening to. Please let me know if you figure it out. I noticed the same thing but thought I seen someone else say that it was nothing.
so i redownloaded all files and nothing. tried loki patch and nothing. tried kt kernel because i seen another post with someone saying it was the only one that worked for them and nothing. im still stuck on splash screen. please if anyone knows how to fix this please let me know im desperate now. i really want to try this rom so any help would be greatly appreciated. thanks
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Click to expand...
Click to collapse
I haven't tried any other roms yet. I haven't really seen any that I liked.
d9vabder said:
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm still on mdl. I'm going to keep looking around for a solution. Please let us know if you found a way to fix it.
Also heres a screen shot of my info
motel6man said:
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
Click to expand...
Click to collapse
Are you using Safe strap?
I was having the same problem after like 4 tries i figured out that every time I would download this it would go into the internal memory when it should have gone into the xd. I had to move folders manually. After that everything has been working correctly.
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I created a new one on the xd card named it roms so I won't forget.
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
d9vabder said:
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
cool im going to go try it in a few mins thanks
i tried mounting both internal and external and still nothing can you go through the steps you did from start to finish maybe im missing something
Okay, so the first thing i did was mount my microSD(external sd) then a full wipe. Even though i was mounted to my sd card, i still had to navigate to my internal memory to select the zips i wanted to flash. I first installed an older release of Hyperdrive Rom, and during installation, i selected Full Wipe option again. i also added my AT&T compatibility pack.zip to be flashed right after the ROM. Also, i dont know if this affected anything, but i tried installing the T-Mobile compatibility pack on a previous attempt. I read somewhere where some1 did this and it worked for them, but it didnt work for me until i did another install of RLS15 and the ATT pack.
Hope this can help you
Sent from my SAMSUNG-SGH-I337 using xda premium
Hello Gents,
Have had my S4 for about a year now and its been awesome (still on MK2, stopped it from updating). It is rooted and safestrap has been installed. I didn't get around to installing a custom ROM though so im still on stock ROM. Been noticing some random issues today and cant pinpoint why. First I am unable to turn on WIFI, was able to yesterday but now it just stays grey. I randomly lose my data connection (well it has a circle with a line through it) and it randomly just pops back on to 4g. I was playing on the phone one time and no SIM error came up but then went away. Power saving mode turned itself on randomly when i have over half battery. Lots of random things happening...
Now i did lose some data and have been trying to recover it this past week using this thread http://forum.xda-developers.com/gal...e-internal-memory-data-recovery-yes-t1994705/
I didn't make it far though because when i try to launch ADB Shell it gives me a permission error.
So that is another thing on the list, it is no longer prompting me to give root access to things. I also noticed that when i power on the phone, it no longer shows Samsung with a lock like it did ever since i rooted it. It now shows Samsung Galaxy S4...I Guess i may have lost root? I downloaded root checker and it says i still have it. Anyway its just so confusing, is it time to blow everything out and go back to stock MK2 and start over? What do you guys think? Thanks!
If you don't mind, I'd say Odin to stock would be your first troubleshooting step.
Don't forget, internal SD gets erased when you Odin to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
guut13 said:
If you don't mind, I'd say Odin to stock would be your first troubleshooting step.
Don't forget, internal SD gets erased when you Odin to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Think so huh? I was thinking so...and yeah i know it erases internal memory, ill pull everything off before that and titanium backup apps and blah blah..
What i'd like to know is does Odin to stock blow EVERYTHING out including root and safe strap to where i would have to do that all over again? and i assume there is an Odin to stock for MK2? because i do not want the new update...
jermo said:
Think so huh? I was thinking so...and yeah i know it erases internal memory, ill pull everything off before that and titanium backup apps and blah blah..
What i'd like to know is does Odin to stock blow EVERYTHING out including root and safe strap to where i would have to do that all over again? and i assume there is an Odin to stock for MK2? because i do not want the new update...
Click to expand...
Click to collapse
I think Odin to stock is easier than troubleshooting every issue that you are having. Especially considering you already tried fixing one of them.
Yes. Odin wipes the slate clean. You'd have to root and install safestrap again. In case you don't have it.
mk2 odin... http://forum.xda-developers.com/showthread.php?t=2621279
root for mk2... http://forum.xda-developers.com/showthread.php?t=2565758
guut13 said:
I think Odin to stock is easier than troubleshooting every issue that you are having. Especially considering you already tried fixing one of them.
Yes. Odin wipes the slate clean. You'd have to root and install safestrap again. In case you don't have it.
mk2 odin... http://forum.xda-developers.com/showthread.php?t=2621279
root for mk2... http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
thanks brother! running through the long ridiculous process now
I see you have started the process... But wouldn't doing a FDR first be a simpler first effort? You would still have to restore root and data and apps, but it would be a bit easier and probably fix the problem. Just a thought. Hope all worked out!