New android user here coming over from RIP WebOs.
I rooted my phone several months ago and all was well. rooted stock.
I tried to unroot to get the new update and it failed and soft bricked my phone. I used Odin.
I had to run twrp recovery and that brought the phone back.
Now I am stuck. Don't know what to try next.
SPH-L900
version 4.1.2
baseband L900VPALJ1
I would try flashing this and start from scratch.
http://forum.xda-developers.com/showthread.php?t=2086769
Related
I previously rooted using auto-script method (EG30). I flashed a couple ROMs, lost some ****, had some issues, just couldn't get everything figured out like on my OG EVO. Anyways, I un-rooted using auto-script but didn't realize CWM was still installed so when I got the OTA update (EK02) today, it failed. If I re-root, and get the stock recovery back, then un-root, will the update be pushed again?
Or is my only option to flash a rooted version of EK02?
I just don't feel like messing with rooting and rom'ing at this point, just want to be stock and have the OTA pushed/installed via the stock recovery if possible.
I'm not sure if I should test the water but... Having had an Evo as well, everytime I had went back to a stock setup Sprint pused the updates, even so just do a check to the updates. Once Sprint/Google have pushed 100% progress out any phone after that should have no problem updating. Basically if you don't care to flash right now go back to stock out of the box and in any case your gonna get the update. That answer almost seemed to easy, hope it helps.
I suggest reading over FAQ #E12 in the auto root sticky:
e12) I told it to install the EK02 update, but something went wrong, now it won't prompt me again, how do I install EK02?
I have searched countless threads for assistance. I have been able to root every phone I've had. I am finally having an issue with my GS4 from AT&T. I bought it back in May, but had to go out of the country for work before I could root it and I just got back this last week. It had received the updates from the server so it is now running the I337UCUAMF3 build. I ran Motochopper, but it said failed and no SU. I have tried utilizing Odin to revert back to the original firmware so that I can try running Motochopper, but when I try it shows fail when in the middle of running the program. I tried factory reset from within android and the stock recovery, but it just reverts back to the latest firmware. I tried going through Kies, but it won't do a recovery and says that it is only through the phone server. I have downloaded 10's of gigs of firmwares, motochoppers, loki flashes, etc.... I am officially lost and would love any assistance someone could offer, cause I would really like to get a better ROM installed like on my other phones.
Thank you
Read the gs4 forum. The info is there. You cant revert back to a later firmware. You can't use Loki or motochopper. All you can do now is root mf3 firmware and that process just became available a few days ago. Stop what your doing and read read and read.
Sent from my SAMSUNG-SGH-I337 using xda premium
venomoussniper said:
I have searched countless threads for assistance. I have been able to root every phone I've had. I am finally having an issue with my GS4 from AT&T. I bought it back in May, but had to go out of the country for work before I could root it and I just got back this last week. It had received the updates from the server so it is now running the I337UCUAMF3 build. I ran Motochopper, but it said failed and no SU. I have tried utilizing Odin to revert back to the original firmware so that I can try running Motochopper, but when I try it shows fail when in the middle of running the program. I tried factory reset from within android and the stock recovery, but it just reverts back to the latest firmware. I tried going through Kies, but it won't do a recovery and says that it is only through the phone server. I have downloaded 10's of gigs of firmwares, motochoppers, loki flashes, etc.... I am officially lost and would love any assistance someone could offer, cause I would really like to get a better ROM installed like on my other phones.
Thank you
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=44165374#post44165374
You are on MF3 build which means this is only root method that will work, but be careful what you do after rooting, currently there is no custom recovery available for the MF3 build due to locked bootloader and loki being patched and there is not any Odin images to restore stock firmware if need be yet. Once you upgrade to MF3 from MDL, there is no way to go back either.
Hope this helps!
Thank you so much for your help!! Much appreciation to all the techs out there for making all these sweet ROMs and roots!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Two days ago i bought Samsung Galaxy Note 2 N7100 (international). It had android 4.1.2 but i saw there is available update. After update to official android 4.3 my phone lost signal and started showing me "Not registered on network". 1 day passed since i am searching how to fix this thing. Tried custom rom (4.4.2) and still the same. I went back to official 4.3 for UK O2 , successfully rooted it, passed knox, installed busybox, installed ARIZA Patch. Still the same. Tried to flash MJ5 bootloader via ODIN but it shows me FAIL. And after every FAIL my phone is bricked so i am flashing all over again official ROM. I have NO backups of my EFS (in my search i saw that i need some EFS to repair this thing). I got no issue with WI-FI but only with network. If i revert back to stock android 4.1.2 will i be able to call somebody? If the answer is "YES", would somebody tell me how? I saw in some threads that with new 4.3 ROM note 2 got knox locked bootloader which is impossible to be downgraded. Please, give me guide step by step what to do to repair my phone by myself. Thank you in advance.
I would suggest you to take an efs backup on 4.1. Then flash 4.3 and if you aren't getting network try restoring your efs backup. That might solve your problem.
I'm on virgin mobile. Yesterday I applied an OTA update. I was running stock 4.4.2. The update was 94mb, so It probably wasn't a big update. But it failed, and now I get stuck on the pulsating samsung logo. Tried a factory reset, but that didn't fix it. I brought it to the nearest samsung dealer and his special software wouldn't fix it either. Not under warranty. But I can get to the odin screen, and I need help getting this thing back to life. I read that I can't just download any random image for it because the bootloader was locked down with other updates that I applied a while ago. Is there any image that I can flash onto here, or will that just brick it even more?
Thanks.
I found two odin files. Need advise on whether they will work or not:
ND8 full restore. Worried it won't work because it's for sprint, not virgin mobile.
http://www.rwilco12.com/forum/showthread.php?tid=716
Cyanogenmod for SPH-L710 . supposedly works for virgin. Worried it won't work because I had stock 4.4.? before, so I probably had knox.
http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-unofficial-cm12-lollipop-t2953040
are any of these viable options?
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!