I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.
If you repeat three times "owaa tagoo siam" it might magically appear.
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless
So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app
You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:
add myself to the thread for future fixes...
Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.
Thank you! I knew that little bit of advice would help somebody one day.
Related
I rooted my Epic 4G with the new Epic Experience Rom recently. I am going to return the phone, but they won't take it back rooted. I couldn't find anything in search. Does anyone know how to erase any trace of my phone being rooted?
Thanks everyone.
Edit: nm read his post wrong.
RootTheWorld said:
I rooted my Epic 4G with the new Epic Experience Rom recently. I am going to return the phone, but they won't take it back rooted. I couldn't find anything in search. Does anyone know how to erase any trace of my phone being rooted?
Thanks everyone.
Click to expand...
Click to collapse
ODIN, and an official release, not Froyo.. Use the DI18 Package..
Also remember to wipe your SD card too which will not be touched during install. ODIN will flash over EVERYTHING making it brand new.
Why would you want to return your Epic? I hope not to get an EVO.. The EVO is a good phone and I wanted it when it first came out, my gut kept telling me to wait and the EPIC really is a good phone.
brian_hoffman said:
ODIN, and an official release, not Froyo.. Use the DI18 Package..
Also remember to wipe your SD card too which will not be touched during install. ODIN will flash over EVERYTHING making it brand new.
Why would you want to return your Epic? I hope not to get an EVO.. The EVO is a good phone and I wanted it when it first came out, my gut kept telling me to wait and the EPIC really is a good phone.
Click to expand...
Click to collapse
Last time I had to take my phone into a sprint store, I ODIN'ed back to DI18 and thought that it removes root as I've read in multiple posts but apparently it doesn't because the technician said the phone is rooted and although they will service the phone this time, root voids warranty and they put a note on my account to check if phone is rooted if i ever take it back again. My speaker just died, so I ODIN'd and used this to remove root.
http://forum.sdx-developers.com/epi...ecovery-1-13-for-windows-intel-mac-and-linux/
When I took it in, they didn't mention anything about root. So either they didn't check or they saw phone wasn't rooted.
For you those going back to stock or are stock and u flashed 2.2 and want to downgrade or resort back to stock use this method.
Rooted/clockwork users skip the first step...
1. Do the one click root/clockwork/etc Here
2. Flash the d118 modem Here
3. Then Flash the zip file Here
4. Then flash the get rid of clockwork zip Here
5. Your are back to stock without using odin yay!!!
Now all links work!!! and added a step use this method to return to stock with out odin.
viper786 said:
Last time I had to take my phone into a sprint store, I ODIN'ed back to DI18 and thought that it removes root as I've read in multiple posts but apparently it doesn't because the technician said the phone is rooted and although they will service the phone this time, root voids warranty and they put a note on my account to check if phone is rooted if i ever take it back again. My speaker just died, so I ODIN'd and used this to remove root.
http://forum.sdx-developers.com/epi...ecovery-1-13-for-windows-intel-mac-and-linux/
When I took it in, they didn't mention anything about root. So either they didn't check or they saw phone wasn't rooted.
Click to expand...
Click to collapse
Perhaps,
If you ODIN to an offical "virgin" Rom you will lose root.. Period. If you dont believe me do it then try and run any app that requires root "like wifi tether" it will not work. There are roms that work with odin that are pre rooted.
What I got from the other thread was Sprint can tell by some method what OS version and build you have been using while connected to thier network... so if this is true they may be able to tell your running an "Epic Experience" build and put 2&2 together that you have rooted.
The fact of the matter is, if you are running software not designed for the phone or not ready to be released and things do not work then they waste countless man hours trying to figure our why things force close on a product that is no longer thiers.
So, it is not hard to see why they do not like people rooting thier devices.
If you ODIN back and still have the speaker problem then it is SAFE to assume its a hardware rather than a software problem regardless of your past programs that have run on the phone.
brian_hoffman said:
Perhaps,
If you ODIN to an offical "virgin" Rom you will lose root.. Period. If you dont believe me do it then try and run any app that requires root "like wifi tether" it will not work. There are roms that work with odin that are pre rooted.
What I got from the other thread was Sprint can tell by some method what OS version and build you have been using while connected to thier network... so if this is true they may be able to tell your running an "Epic Experience" build and put 2&2 together that you have rooted.
The fact of the matter is, if you are running software not designed for the phone or not ready to be released and things do not work then they waste countless man hours trying to figure our why things force close on a product that is no longer thiers.
So, it is not hard to see why they do not like people rooting thier devices.
If you ODIN back and still have the speaker problem then it is SAFE to assume its a hardware rather than a software problem regardless of your past programs that have run on the phone.
Click to expand...
Click to collapse
I was not aware that they can see what OS i've been using. Anyway, they are replacing the phone and said i should receive the replacement at my house tomorrow. Normally all replacements are sent to them this is the first time i'm getting a replacement sent to my house instead of the store.
Are you sure you searched? One of the very first threads in the development forum...
Sent from my SPH-D700 using Tapatalk
updated instructions to goto stock without odin, see post 5.
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Not at the moment. There is a root method, but no factory image to flash back to.
http://forum.xda-developers.com/showthread.php?p=43890414 check here for recovery updates.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
sheek360 said:
and its on mf3, i really wanted to flash a gpe rom too.....
is there any way to flash it at all? i understand mf3 doesnt have a working recovery
Click to expand...
Click to collapse
We all just have to be patient! It's not the end of the world, rooting it allows you to remove some bloatware, then you can install themes and launchers to make it a little better!~
You can still tweak the device so it's enjoyable!
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
jd1639 said:
Think hard before you root it. There is currently no way to unroot. There also is no odin flashable firmware should you get into trouble and need to recover from it. Read a lot in this forum before you attempt to root. Everyday there are multiple users who run into trouble and end up with a crippled phone at best.
Click to expand...
Click to collapse
You get around alot, have you seen any update to the MF3 bootloader issue?
TheAxman said:
You get around alot, have you seen any update to the MF3 bootloader issue?
Click to expand...
Click to collapse
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Tons and tons of uninformed people are messing up their phones. You're right, it's sad.
It will be great when people can comfortably root their device knowing there is a way back when all is said and done.
In the mean time, to the OP, playing the waiting game will not kill anyone in this situation.
jd1639 said:
Unfortunately, no! Seen a lot of people messing up their phones though. Which is sad to see.
Click to expand...
Click to collapse
Agreed, if most would have read just a little, they would not be having this issue. For me, I always wait until a dev gets a hold of an update and does their thing, and then I update to the newest...I have NEVER updated direct on the phone, even with all the phones I have ever owned.
Not happening OP, do a search on MF3 in the search bar you will find all kinds of things related to it.
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
ThePerson98 said:
I just want to say, if you root your MF3 phone, do NOT modify anything in the system partition, which means files that require root to edit. If you happen to do some sort of mod that borks your system, it will be very difficult and perhaps impossible to recover. Don't do anything that can't be undone with a factory restore done in recovery.
I'm fairly certain that it is possible to unroot once rooted, however, your phone and system partition must be in full working order and unmodified in order to be at complete stock. If you are new to rooting and customizing the phone in that matter, you are probably best not rooting at the moment, since you will likely mess something up on accident while learning. I think most every single one of us has borked our OS while tinkering with root stuff and had to use some sort of recovery method. At the time, no recovery method is possible, so I repeat, don't root if you don't know what you're doing.
Click to expand...
Click to collapse
I just wanna plus 1 that for the OP
Sent from miPhone using XDA Premium HD app
As long as you're a smart cookie and don't go around attempting to mod your twframework and other important inner system files, I wouldn't get too disheartened and held back from touching the partition. Simply be intuitive and anything you intended on replacing, rename instead to the file with a *.temp extension. Wouldn't be that hard to roll back then (as long as you can still boot). Rooting itself mods the system, so people have already jumped ship in that regard.
Just don't go around trying to enable verbose boot or flash a recovery from some kind of mobile ODIN or GooManager.
BE SMART, not eccentric and living by the standards of yolo.
I have an SGH-I337 with Android version 4.4. I have the Knox bootloader (sadface). I attempted to root this phone previously using Saferoot but this caused problems (relevant thread).
I can connect to the data network but I can't get the wifi to work. It won't even turn on. As soon as I tap the switch it goes back off.
Please help.
You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app
DeadlySin9 said:
You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.
goose90proof said:
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.
Click to expand...
Click to collapse
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).
DeadlySin9 said:
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).
Click to expand...
Click to collapse
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:
WiFi issues with OTA firmware too
Just thought I'd add that the OFW has WiFi issues as well, at least for a few if us. When I updated OTA to 4.4 the WiFi worked for a couple of weeks then stopped working (reboot will allow it to work for a while until the unit sleeps, then it won't toggle). I tried the Odin tar.md5 image and the same thing crops up. This thread is relevant: [Q] OFW 4.4.2 WiFi Not Turning On. I like KitKat, hopefully we can figure out what the problem is.
goose90proof said:
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:
Click to expand...
Click to collapse
You likely overwrote the stock recovery. Here is the NB! stock recovery. Flash in PDA slot in Odin:https://mega.co.nz/#!M9EQBT5A!ri4QeMYpgi-JjmUGZ3FY2gtogDBWPEL7zRCjASIcVe8
If you need the NB1 stock modem here it is. Also flash in PDA slot in odin: https://mega.co.nz/#!sstkFRiJ!d9zTRte0KcVFv7o-bjKFuFMM1Q9ivzDlqJKy2OlP_7o
Excellent thank you.
goose90proof said:
Excellent thank you.
Click to expand...
Click to collapse
did it work for you?
I haven't gotten around to trying it. The phone is working now so I'm a bit reluctant to do anything to it until future developments bear fruit.
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
I don't think so if you had android 4.4.2 before flash the custom ROM. You will have to buy a unlock code.
How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!
intacto said:
How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!
Click to expand...
Click to collapse
I don't know if is legal or no. All depends of the little letter of the contract. Did you read the contract when you signed it?
intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.
intacto said:
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.
Click to expand...
Click to collapse
I hope he explain you too the PROS and CONS about that process :highfive:
I know the pross, what are the cons?
The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.
Strephon Alkhalikoi said:
The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.
Click to expand...
Click to collapse
Well I have tried that service menu trick while on kitkat, but that didnt go pass step 2, it didnt even show me the menu, but I am fine with downgrading to 4.2.2 and giving it a try....I also tried ragionaway app 2 days ago, that was a no-go
Because the exploits that allowed both to work were patched in versions later than 4.2.2. Downgrading the modem at minimum is a requirement for either to work.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
Well it didnt go well with this 4.2.2 rom i must said, i got this in Odin:
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
I then tried to do the stock of 4.4.2, that resorted fine but it wiped my IMEI and now phone doesnt connect to mobile network...help...:crying:
What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.
Strephon Alkhalikoi said:
What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.
Click to expand...
Click to collapse
I have managed to revert back to lollipop from hte backup and it works fine but I am still in the square one. I do use the original cable, direct to my PC drivers are there, kies isnt running. It did a proper flashing to 4.4.2 but it refuses to have that 4.2.2, is there anyway to downgrade the modem only from 4.4.2 to see if that will work for me? also my phone is i9505xxugni2, the rome u gave me the link to has a different PDA, would that prevent the flashing of my handset?
Cheers!
Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.
Strephon Alkhalikoi said:
Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.
Click to expand...
Click to collapse
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:
intacto said:
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:
Click to expand...
Click to collapse
:good:
RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.
Strephon Alkhalikoi said:
RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.
Click to expand...
Click to collapse
Yes region away always ask for root so I have to re-do it every time after the flash. But seriously EE is the worst provider and one of the most hated companies in UK. I would rather pay someone on the street with z3x box than them
in our country we can get unlock code for free, but only till one month from end of contract. later they ask money.
i hate them too for asking money, but on other hand: why they should do anything for free if phone is yours and not their.
I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app
I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.
JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.
joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf