Related
Hi there,
After checking several tutorials and howtos I still have an unanswered question about unlocking and upgrading a Samsung Galaxy Spica i5700.
I’ve just got a Spica locked by Orange with firmware 1.5. I’m planning to first unlock and then flash it with Eclair and if possible with Gingerbread.
Unlock:
According to this guide: forum(dot)samdroid(dot)net/f28/how-spica-i5700-sim-unlock-free-4886
It seems that the Spica can be unlocked without the need of paying for an unlocking code. However, following this process requires the Spica to be rooted, so the /efs/nv_data.bin can be edited.
Rooting:
Some of the most complete guides I’ve found follow:
www(dot)addictivetips.com/mobile/root-samsung-galaxy-spica-i5700-with-leshaks-kernel
pomzung(dot)wordpress.com/2010/12/22/rooting-samsung-spica-i5700/
One of the prerequisites is that the Spica has at least the firmware 2.1. Since my version is the 1.5, I guess I need to upgrade to 2.1 before rooting, so I can minimize bricking risks.
Upgrade to 2.1:
Very good information on that can be found here:
www(dot)sammobile.com/forum/showthread.php?t=11
However one of the prerequisites is that the cell phone is unlocked.
So here is my problem, according to the prerequisites listed above I should not root because my Spica is locked, and I should not unlock because my Spica is not rooted….
My intention is to flash the device with the firmware 2.1 regardless of the locked status, then root and then unlock. However, I couldn’t find any post telling whether that will brick the device. Does anybody know if it is safe to proceed as I have described?
Thanks,
Caste
rooting, sim lock
caste said:
Hi there,
After checking several tutorials and howtos I still have an unanswered question about unlocking and upgrading a Samsung Galaxy Spica i5700.
I’ve just got a Spica locked by Orange with firmware 1.5. I’m planning to first unlock and then flash it with Eclair and if possible with Gingerbread.
Unlock:
According to this guide: forum(dot)samdroid(dot)net/f28/how-spica-i5700-sim-unlock-free-4886
It seems that the Spica can be unlocked without the need of paying for an unlocking code. However, following this process requires the Spica to be rooted, so the /efs/nv_data.bin can be edited.
Rooting:
Some of the most complete guides I’ve found follow:
www(dot)addictivetips.com/mobile/root-samsung-galaxy-spica-i5700-with-leshaks-kernel
pomzung(dot)wordpress.com/2010/12/22/rooting-samsung-spica-i5700/
One of the prerequisites is that the Spica has at least the firmware 2.1. Since my version is the 1.5, I guess I need to upgrade to 2.1 before rooting, so I can minimize bricking risks.
Upgrade to 2.1:
Very good information on that can be found here:
www(dot)sammobile.com/forum/showthread.php?t=11
However one of the prerequisites is that the cell phone is unlocked.
So here is my problem, according to the prerequisites listed above I should not root because my Spica is locked, and I should not unlock because my Spica is not rooted….
My intention is to flash the device with the firmware 2.1 regardless of the locked status, then root and then unlock. However, I couldn’t find any post telling whether that will brick the device. Does anybody know if it is safe to proceed as I have described?
Thanks,
Caste
Click to expand...
Click to collapse
i have the same problem, and i would like to know if anybody figure this out!?!?
thanks
zarko.janjetovic said:
i have the same problem, and i would like to know if anybody figure this out!?!?
thanks
Click to expand...
Click to collapse
I'll be honest - I'm new to all this rooting and ROM flashing malarky but I have worked out a few things that may help you both.
Firstly, truely bricking your device is quite hard to do, I have not bricked a single device of mine although I have messed it up and ended up with a useless phone. In all of these cases I was, in worst case scenario's, able to reflash a stock ROM via Odin. This is annoying but only in the aspect of you having to start EVERYTHING again but to be quite honest, thats what I found fun and more educational than it all going swimmingly. THE GOLDEN RULE of rooting, flashing etc. is that if you mess it up, its your responsibility and your responsibility to sort it out!!!!!!!!!!!!!!!!!!!! Read these forums fully and 99% of the time there is an answer that will cure your problem.
Now to answer your query to the best of my inexperienced ability..........your starting block IS rooting your phone. Without a rooted device you are not going to flash a new ROM with any Android version! In my opinion before you even root your device, read up on how to reinstall a stock ROM, then download it along with Odin. This is your ultimate back up should you go wrong. But rooting your device is paramount to flashing a custom ROM which will use Gingerbread etc. There are plenty of great custom ROMs out there that only require root and a zip file installed on you SD - Once confident, it really is as simple as that!
Network/Sim unlocking your device is TOTALLY seperate to rooting and alot of people get them confused from what I see, rooting your device DOES NOT sim unlock your handset. A Sim unlock is possible on the i5700 with root but to be honest its easier just to get a code from a vendor on eBay for £1. If you want to do it yourself then again read up on it.
Bottom line to your question is root your device first if you want to do it all yourself.
RE: Downgrade Galaxy S3 I747 from 4.3(knox) to 4.1.2???
Hi guys,
I've been searching online and no luck finding a good answers. I have a Galaxy S3 I747M(Canadian) that was handed to me.... Sad part is, most average users, whenever they see an update for the phone, they freaking update without research the pros or cons.
Anyhows, I was fiddling with my Galaxy Note 2 and came across on how disable KNOX to achieve Rooting and I thought***** Light Bulb*
Here's my idea, not sure if this will work but, I will root my Galaxy S3 and use the same idea by disabling KNOX using Dr Ketan multitool to rename Knox.*apk files then inject busy box and root. (By the way, I have rooted my S3 this way and it achieve rooting no problem).
Now the question is, since KNOX is disabled, would I be able to downgrade to 4.1.2? Just wondering if other people out there has ever done this route by disabling KNOX and then do downgrade....
What do you guys think?
amilayajr said:
Hi guys,
I've been searching online and no luck finding a good answers. I have a Galaxy S3 I747M(Canadian) that was handed to me.... Sad part is, most average users, whenever they see an update for the phone, they freaking update without research the pros or cons.
Anyhows, I was fiddling with my Galaxy Note 2 and came across on how disable KNOX to achieve Rooting and I thought***** Light Bulb*
Here's my idea, not sure if this will work but, I will root my Galaxy S3 and use the same idea by disabling KNOX using Dr Ketan multitool to rename Knox.*apk files then inject busy box and root. (By the way, I have rooted my S3 this way and it achieve rooting no problem).
Now the question is, since KNOX is disabled, would I be able to downgrade to 4.1.2? Just wondering if other people out there has ever done this route by disabling KNOX and then do downgrade....
What do you guys think?
Click to expand...
Click to collapse
Dont do it. You will BRICK your phone. For the moment on android 4.3 Samsung galaxy i747M (same as mine on Rogers) therse no way to downgrade. Yon wont be able to downgrade anyway because you have the new bootloader and with the new one, you CANT downgrade, or if you try, you will Soft-Brick your phone.
(In the past, i got an HTC EVO 3D and Soft-Bricked my phone by flashing a wrong Kernel.... so i made some research on the web and i found the a JTAG may be able to unbrick my phone and flash back the good Kernel the good ROM and the good bootloader.... So I sent it to a store who was repairing smrtphones. Tey tell me that they knew what my problem is so they should be able ot fix it but... the next day when i came to get my HTC they told me that finnally EVEN with the JTAG they wasnt able to repair it...)
* All of that to tell you : dont trust JTAG sometimes it may not work...
amilayajr said:
Hi guys,
I've been searching online and no luck finding a good answers. I have a Galaxy S3 I747M(Canadian) that was handed to me.... Sad part is, most average users, whenever they see an update for the phone, they freaking update without research the pros or cons.
Anyhows, I was fiddling with my Galaxy Note 2 and came across on how disable KNOX to achieve Rooting and I thought***** Light Bulb*
Here's my idea, not sure if this will work but, I will root my Galaxy S3 and use the same idea by disabling KNOX using Dr Ketan multitool to rename Knox.*apk files then inject busy box and root. (By the way, I have rooted my S3 this way and it achieve rooting no problem).
Now the question is, since KNOX is disabled, would I be able to downgrade to 4.1.2? Just wondering if other people out there has ever done this route by disabling KNOX and then do downgrade....
What do you guys think?
Click to expand...
Click to collapse
I have the i747 canadian model too and althpugh you can't downgrade to stock 4.1.2, you can definetly flash a custom 4.1.2 rom which DOES NOT include a bootloader. Im currently running hyperdrive rls 16 which is 4.1.2 based and before that i was rooted on stock 4.3.
Sent from my SGH-I747 using Tapatalk
I have a question along the same lines, is it possible to restore a nandroid of 4.1.1 or 4.1.2 after updating the bootloader? Does restoring a nandroid affect the bootloader?
I actually haven't don't the official update yet, specifically because I don't like that it's one way. I flashed stock 4.3 without updating the bootloader and I like the improvements.
Sent from my SGH-I747M using xda app-developers app
gc84245 said:
I have a question along the same lines, is it possible to restore a nandroid of 4.1.1 or 4.1.2 after updating the bootloader? Does restoring a nandroid affect the bootloader?
I actually haven't don't the official update yet, specifically because I don't like that it's one way. I flashed stock 4.3 without updating the bootloader and I like the improvements.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
No by restauring your phone whit nandroid if you are on 4.3 with the new bootloader you will brick your device...
Code:
[ro.bootloader]: [I747MVLUEMK5]
[ro.build.id]: [JZO54K]
[ro.build.hidden_ver]: [I747MVLDMF1]
I'm able to get 4.1.* running but none of the modems seem to work.
Am I screwed if I need to network/sim unlock this?
EDIT: Just found out about EFSv1 vs. EFSv2. Looks like I'm boned for a free unlock.
weedy2887 said:
Code:
[ro.bootloader]: [I747MVLUEMK5]
[ro.build.id]: [JZO54K]
[ro.build.hidden_ver]: [I747MVLDMF1]
I'm able to get 4.1.* running but none of the modems seem to work.
Am I screwed if I need to network/sim unlock this?
EDIT: Just found out about EFSv1 vs. EFSv2. Looks like I'm boned for a free unlock.
Click to expand...
Click to collapse
You cannot use the free method to sim unlock the phone unless you are running a completely stock ROM, inclduing the bootloader. There were a couple of users that downgraded everything to 4.1.1 from 4.3 except the bootloader and the required unlock menu options were not available.
Because the 4.3 upgrade changes to format of the EFS partition.
Nope, its all because of the modem. You never had to flash a 4.1.1 rom, only the modem. The problem is that once you've updated to 4.3, older modems no longer function.
There is little more than factoryapp, s/n, and drm related data on the EFS partition of these devices. They are not like many others where a lot of NV data was stored there.
This is also why backing up the EFS, while not a bad idea, does not protect against many of the things people think it will, such as IMEI loss.
Hi, I need your help!
i have I747 AT&T with 4.1.1 PDA: I747UCDLK3
My main concern what will brick my device if i try downgrade from 4.3 coustm rom?!
Can anyone give my a full list of BT+MO+Ke ? what I found in XDA is short list.
4.3+ bootloader - YES! (I747UCUEMJB and Up will brick )
I being told that I747UCUEMJ2 is the higher i can get downgrade without porblems
I rellay don't know which Modems & Kernals are belong to 4.1.1 VS 4.3+
Modems - ? (will loss IMEI) can I use old modem like:I747UCDMG2/UCDLK3 on 4.3+ ?
Kernels - ?
http://forum.xda-developers.com/galaxy-s3-att/help/bootloaders-kernaels-modems-list-t2851857
-
http://forum.xda-developers.com/showthread.php?t=2321310&page=41#post54912358
Once on 4.3 or above you cannot flash older firmware. Only the modem belonging to each build will work.
You can flash older roms, but thats it.
Hello,
I bought this tablet (P600 - WiFi edition) just 2 days ago and I love it, however I'm kind of missing root functionality.
I've read a lot of threads and posts and I'm not sure if I can actually root my device without tripping KNOX.
I've looked at Root de la Vega (http://forum.xda-developers.com/showthread.php?t=2498850) which supposedly doesn't trip KNOX.
There are some versions mentioned in the thread, but I'm new to Samsung devices and this is the output I got:
Bootloader version: MJ6
PDA Version: MJ6
CSC Version: MJ2
Build Number: MJ6
I'm not sure which value the RDLV thread is mentioning, so I would appreciate some insight.
There are really a lot of threads and posts each suggesting another thing, so I'm not sure which one is correct.
As a side question, I want to know if the tripped KNOX counter affects warranty in case there are actual hardware problems (screen, battery, ...) or does warranty get denied even if it had nothing to do with KNOX/rooting/software side of things ? Does anyone have any experience with this?
Thanks!
shiinkotheone said:
Hello,
I bought this tablet (P600 - WiFi edition) just 2 days ago and I love it, however I'm kind of missing root functionality.
I've read a lot of threads and posts and I'm not sure if I can actually root my device without tripping KNOX.
I've looked at Root de la Vega (http://forum.xda-developers.com/showthread.php?t=2498850) which supposedly doesn't trip KNOX.
There are some versions mentioned in the thread, but I'm new to Samsung devices and this is the output I got:
Bootloader version: MJ6
PDA Version: MJ6
CSC Version: MJ2
Build Number: MJ6
I'm not sure which value the RDLV thread is mentioning, so I would appreciate some insight.
There are really a lot of threads and posts each suggesting another thing, so I'm not sure which one is correct.
As a side question, I want to know if the tripped KNOX counter affects warranty in case there are actual hardware problems (screen, battery, ...) or does warranty get denied even if it had nothing to do with KNOX/rooting/software side of things ? Does anyone have any experience with this?
Thanks!
Click to expand...
Click to collapse
Unfortunately, there's currently no way of rooting the P60x without tripping KNOX. The URDLV method worked without tripping KNOX only for the very first firmware. Moreover, you would be stuck on that firmware, if you wanted to keep 0x0 and root.
Concerning the warranty, there are varied anecdotal stories on the web. It seems that it depends on the people handling the warranty claim. In short: luck.
The bottom line is: Samsung sucks!
no.0ne said:
Unfortunately, there's currently no way of rooting the P60x without tripping KNOX. The URDLV method worked without tripping KNOX only for the very first firmware. Moreover, you would be stuck on that firmware, if you wanted to keep 0x0 and root.
Concerning the warranty, there are varied anecdotal stories on the web. It seems that it depends on the people handling the warranty claim. In short: luck.
The bottom line is: Samsung sucks!
Click to expand...
Click to collapse
Okay, thanks. Are there any other reasons suggesting I shouldn't root the device apart from warranty?
I guess I will proceed with rooting since I can't even execute ping command from within terminal.
Althought it seems funny how I got a feeling, that we looked up to Samsung in terms of updates and software from LG P880 forums here on XDA :laugh:
Declining warranty for broken battery because phone was rooted seems a bit absurd.
You can ping without rooting.
I'm using LandDroid from playstore to do that.
lightman33 said:
You can ping without rooting.
I'm using LandDroid from playstore to do that.
Click to expand...
Click to collapse
I know, I was just using that as an example. What I meant is you don't really have access to most commands in terminal without root :laugh:
Hi!
I'm sorry if this has been asked before but I just can't find a definitive answer to this and I've been trying to search for an answer for nearly a week now.
My boss received a used Samsung Galaxy S3 from a friend of his in the states. It is a locked AT&T phone (SGH-I747) and it is on 4.3.
I managed to root the phone using CF-Auto-Root, which disabled Knox (whatever that is) and also installed CWM and was planning to flash 4.1.1 so I can unlock the phone using the *#NUM# method.
After reading a bit I've seen many people saying that you can't "downgrade" from 4.3 to anything else because it will brick your phone. Hence, I did not try and flash any other rom on the phone.
So I guess I'm just trying to get a definitive answer here because I can't find anything but rumors on this subject. I mean it's weird, I'd expect if you couldn't downgrade from 4.3 than it would be a bit more documented.
Has anybody tackled this problem with success?
Thank you
The normal method for the end user to conduct software updates and upgrades is via OTA or Kies. Using Kies or OTA doesn't require the end user to know about download mode, fastboot, or recovery mode. Samsung probably did not want non-technical users to brick their phones using download mode and Odin. It would be too easy for a non-techie to use the wrong firmware, tick the wrong options in Odin, etc.
I'm sure the fact that you cannot downgrade the bootloader has been well document by Samsung and its service centres. Based on the contents of my first paragraph, there would be no need for Samsung to advertise to the end user that the bootloader cannot be downgraded.
rikonor said:
Hi!
I'm sorry if this has been asked before but I just can't find a definitive answer to this and I've been trying to search for an answer for nearly a week now.
My boss received a used Samsung Galaxy S3 from a friend of his in the states. It is a locked AT&T phone (SGH-I747) and it is on 4.3.
I managed to root the phone using CF-Auto-Root, which disabled Knox (whatever that is) and also installed CWM and was planning to flash 4.1.1 so I can unlock the phone using the *#NUM# method.
After reading a bit I've seen many people saying that you can't "downgrade" from 4.3 to anything else because it will brick your phone. Hence, I did not try and flash any other rom on the phone.
So I guess I'm just trying to get a definitive answer here because I can't find anything but rumors on this subject. I mean it's weird, I'd expect if you couldn't downgrade from 4.3 than it would be a bit more documented.
Has anybody tackled this problem with success?
Thank you
Click to expand...
Click to collapse
Right now there is no free way to unlock your phone if it's on 4.3.(you can downgrade to older stock android, but the 4.3 bootloader remains and messes up your phones IMEI until you go back to stock 4.3)
Anyhow, the reason you can't downgrade the bootloader is because there is no method discovered to do this yet. I ended up using gsmliberty to unlock, and they have a deal that you get a free unlock if you take a video when you unlock and upload it to vimeo/youtube using the format they request.
I did that and they re-funded me very quickly. So IMO this is the best "free" method until we can downgrade from 4.3 bootloader and do the 4.1.1 free unlock.
I was in the same situation, and I had to pay for an unlock code.
If you want to see me unlock it, here is the video: http://vimeo.com/96549806
rikonor said:
Hi!
I'm sorry if this has been asked before but I just can't find a definitive answer to this and I've been trying to search for an answer for nearly a week now.
My boss received a used Samsung Galaxy S3 from a friend of his in the states. It is a locked AT&T phone (SGH-I747) and it is on 4.3.
I managed to root the phone using CF-Auto-Root, which disabled Knox (whatever that is) and also installed CWM and was planning to flash 4.1.1 so I can unlock the phone using the *#NUM# method.
After reading a bit I've seen many people saying that you can't "downgrade" from 4.3 to anything else because it will brick your phone. Hence, I did not try and flash any other rom on the phone.
So I guess I'm just trying to get a definitive answer here because I can't find anything but rumors on this subject. I mean it's weird, I'd expect if you couldn't downgrade from 4.3 than it would be a bit more documented.
Has anybody tackled this problem with success?
Thank you
Click to expand...
Click to collapse
What everyone else has said here is correct. You can't safely downgrade from 4.3 to free unlock - or free unlock by any other means for that matter once you are on 4.3. Your boss' friend would have unlocked prior to shipping the phone down but perhaps this was omitted. Your only options now would be to buy an unlock code online or perhaps the friend can contact AT&T to request the unlock code. If the device was off contract and is eligible for the unlock code, they would oblige the request. Otherwise, the code could cost between $18 - $30 online.
Thank you everybody.
I will use the service posted above.
I think it would be a good idea to make a sticky in this forum explaining that it is not possible at this point to downgrade from 4.3 (or is that just the boot loader).
Thanks again.
rikonor said:
Thank you everybody.
I will use the service posted above.
I think it would be a good idea to make a sticky in this forum explaining that it is not possible at this point to downgrade from 4.3 (or is that just the boot loader).
Thanks again.
Click to expand...
Click to collapse
It is just the bootloader that cannot be downgraded, not the ROM.
I'm interested to know if anyone is working on rooting the most current firmware?
I'm new to the scene and have read that things got tricky (possibility to brick?) a few releases back, is that correct?
I hope people are working on this device and that people who are without root get the opportunity.
Since now there is only a hardware root method available if you are on the latest firmware. You can find the specific thread in this forum. If you read something about a blown efuse, don't misunderstand this with rooting. This just means you can no more downgrade to an earlier firmware. Still, rooting via hardware is possible (but with somehow great risk of bricking your device if you don't know what you are doing).