I have decided to root and I have configured all the necessities such as the adb. I was informed that the newest upgrade(ending in .6) could not be rooted, therefore I searched the thread about the downgrade and it appears as though the author claimed the method of downgrading obsolete and I can root the phone without downgrading. I'm at a loss here and would appreciate further information.
Bump... Someone help?
I'm running the .6 version and I rooted just fine. You do not need to downgrade. Just make sure in the future your do not download unedited updates from sprint because that might mess up your root.
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.
This might come as late issue, since everybody already moved to 4.3 or 4.4.2, but the thing is I got stuck from my own insecurity to install a Custom Rom, and standing behind is starting to hurt my device.
Since it's rooted, I cannot update automatically trought Kies, but I just don't get to understand all the variables implied on flashing or installing a Custom Rom, from bootloaders, Knox, constantly appearing new versions of required software, hipertextual installation guides whose requirements link you to either obsolete utilities, or utilities for which my device became obsolete, and seas of prerrequisites whose end I cannot manage to find.
So, I would like to know if there's any short way for getting out 4.1.2. Would TriangleAway help me?
Well after reading a lot of information on how to unlock my n7100 (which i mysteriusly bought unlocked) i found out about the methods that involved having 4.1.1 version in order for them to function and as i have 4.3 installed i considered downgrading my phone but after a long time of reading and looking up for different and efficient methods to do it ( so i didnt bricked my phone which concerned me a lot) i came up with things like knox blocking the phone and voiding its warranty which would lead to it being ending up bricked, and also read something about the 4.3 mk4 not being downgradable.
So... The reason why i created this thread is because most of these posts are closed/ old or the creator has litlle or none knowledge about technical troubleshooting so my question is, is it there a way to downgrade such version without coming across knox? also is there a reason why my phone locked it self?
The model number is GT-N7100
Baseband version :N7100UBUEMJ4
Build number: JSS15J.N7100UBUEMK4
Thanks in advance, i hope to have provided sufficient information .
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt