Related
Hey guys
I have a lgp500 phone and i am thinking of rooting my phone, as i hate the touchscreen bug that makes the cpu go 100%, soo laggy
anyways i have a few questions that i would like to know about rooting before i attempt it.
firstly ill start by listing my phone software etc
Android version - 2.2.1
Kernal Version - 2.6.32.9
Build Number - FRG83
Software Version - V10b-DEC-13-2010
and now my questions
1. Well the most obvious question. Is it possible to root my phone?
2. My main ques - What are the chances of bricking my phone? as in to a point that would leave my phone completely useless.
3.At what steps of the rooting process can the phone be bricked?
4. How does rooting work? - basically i just want to learn about everything so i know how the system works and how kernal etc work - so that i wont do anything stupid when im rooting
for now thats all, but ill probly have a alot more once i get answers to these
please help
thanks
first of all u will need to downgrade to android 2.2.then u can root it and enjoy!
Ramis93 said:
1. Well the most obvious question. Is it possible to root my phone?
Click to expand...
Click to collapse
Not yet. Android 2.2.1 is not rootable at the moment. A downgrade to v2.2 is necessary, as upendra_p said.
Ramis93 said:
2. My main ques - What are the chances of bricking my phone? as in to a point that would leave my phone completely useless.
Click to expand...
Click to collapse
Chances are very small, but there are.
Ramis93 said:
3.At what steps of the rooting process can the phone be bricked?
Click to expand...
Click to collapse
At the downgrade, when you have to flash the phone with a different Android version using an application that sometimes fails. But that's rare.
Ramis93 said:
4. How does rooting work? - basically i just want to learn about everything so i know how the system works and how kernal etc work - so that i wont do anything stupid when im rooting
Click to expand...
Click to collapse
"Rooting" simply gives various applications wider system rights, so that they are able to perform actions otherwise forbidden, such as messing with system settings and allowing critical system files to be modified or deleted. It also is an important step needed if you decide to install a custom ROM -- a modified and (usually) improved version of Android.
Rooting is not for the faint of the heart
However, keep in mind that you can find all the help you need on this forums...
masteryx said:
Not yet. Android 2.2.1 is not rootable at the moment. A downgrade to v2.2 is necessary, as upendra_p said.
Chances are very small, but there are.
At the downgrade, when you have to flash the phone with a different Android version using an application that sometimes fails. But that's rare.
"Rooting" simply gives various applications wider system rights, so that they are able to perform actions otherwise forbidden, such as messing with system settings and allowing critical system files to be modified or deleted. It also is an important step needed if you decide to install a custom ROM -- a modified and (usually) improved version of Android.
Click to expand...
Click to collapse
about the chances on bricking my phone, i understand they are small
but approximately how small? like a number?
i understand its different for each phone, so how much would it be for my phone?
Well it depends on how well you read and follow the instructions.
I have installed Custom ROMs on a total of 3 phones with 100% success.
And in short Rooting is like being Administrator in Windows, you can do anything you feel like doing, even if that means bricking your device.
Ramis93 said:
about the chances on bricking my phone, i understand they are small
but approximately how small? like a number?
i understand its different for each phone, so how much would it be for my phone?
Click to expand...
Click to collapse
It's not the phone it's usually the user. You should never attempt to mess with something unless you know what you're doing. Take that from someone who actually bricked his phone by not knowing enough.
Best advice against bricking is never try to flash something that's not meant for your specific device.
And if you wanna put a number on it post your IQ.
Ahmmm... i just used z4root and in just one click, im already rooted. Very easy XD. The part where you should be cautious about is flashing back to android 2.2 that is where a lot of p500 get brick. Just read the forums more.
Sent from my LG-P500 using XDA App
@OP, just take note of the important steps & thing you should check before proceeding like turning LG modem off in device manager. though my friends have downgraded even without checking that option, its always better to follow the instruction to be safe.
& also after rooting, take your time when installing custom recovery. it is also responsible for bricking quite a few mobiles. i'll advice copy paste the commands to avoid any typo.
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
Here's my problem, I bought a Samsung Galaxy S2 I9100 from a friend like 4 months ago, which means I don't really know if it's a factory unlocked device or international unlocked device or unlocked using some kind of methods that I don't really know anything about them...
Anyway, I rooted it probably a month after buying it, and I installed two or three custom roms her and there. (I think I installed the X-TremE CM10 1.5 Pure, 1.6 Pure and others roms from other developpers...)
Finally I found the perfect custom rom that I used all the time until now, it was the SuperNexus rom from Faryaab.
Everything went fine until today, I decided to try a new rom, the Omega v16.2 from ::indie:: (I can't post the link sorry but it's very easy to find).
Factory/Data Wipe, Wiped the cache and the Dalvik Cache and installed from zip, everything went fine.
The problem here is that all this time I was using my default modem which I found with the phone, the XXLPX (not a quite loved and famous modem from what I've seen), but the rom I installed was "equiped" with the XXLSJ modem (I don't know if we can say so, i'm not really a professional), so my Baseband version actually changer to I9100XXLS6 (it was I9100XXLPX as said above) and know I have in my hands a SIM Locked device...
I tried the Galaxy S2 SIM Unlock application from Chainfire and the Galaxy_S Unlock from HELROZ and none of the two have worked.
I switched back to the SuperNexus rom, redownloaded the XXLPX modem and reflashed it through the CWM Recovery menu and my phone is still SIM Locked.
So my question here is, does the fact that the rom have changed my modem version locked my phone, or did I do something wrong when installing ?
And is there anyway I could reunlock my phone using any method (probably not, but I ask anyway, who knows) ?
Thanks in advance.
You tried those apps with busybox right? sometimes you need to install another busybox installer version to getting it unlocked.
Have you tried Galaxy S2 SIM Unlock?
if you have a tendency to switch ROMs too often, you might want an app that keep that locking nightmare away.
if all apps fail, look into what these guys did (do not replace the bin file posted there, it's a diffrent method):
http://forum.xda-developers.com/showthread.php?p=35934314#post35934314
Thanks alot for this ! it's gonna be really useful next time i'm gonna have a problem like that ! But I've already reunlocked it so I can't really try :c. I took it to some "specialist" guy that did it. I still don't know what's the method he used though...
As I've said I'm not a professional my self so it would be kind from you if you explain me two or three things.
First, what do you mean with busybox ? I'm not quite sure if the rom I was using (the Omega) while testing the two unlocking applications listed above was "equiped" with that.
Second thing, you didn't really answered my question which I'm gonna reformulate now:
Can I actually change the version of the Baseband of my phone ? If yes, do I lose the SIM Unlock ? And if I can change the Baseband version and lose the actual SIM Unlock, can I reunlock it and keep that version of the Baseband or do I need to get back to the old version by reflashing it, then reunlock it ?
And finally, the efs folder that I need to backup every time before flashing a new rom (I didn't knew that), what does he contain ? From what I've seen he contains the nv_data.bin file which I think contains the unlock, and that folder also contains some IMEI informations and other stuff. If I actually back it up before installing a new rom, and if that rom changes the baseband version which will probably lock my phone, is it safe to put back that backed up efs folder while keeping the same rom and the same baseband version that came with it ? Does it reunlock the phone ? And do I just put it back using a root explorer and just overwrite it the existing ones ?
Yeah I know, too many questions a man can handle, but I really need to be informed of all those things so I can be aware of what I'm doing.
And thanks in advance for your patience.
Best regards.
fury1337 said:
Thanks alot for this ! it's gonna be really useful next time i'm gonna have a problem like that ! But I've already reunlocked it so I can't really try :c. I took it to some "specialist" guy that did it. I still don't know what's the method he used though...
As I've said I'm not a professional my self so it would be kind from you if you explain me two or three things.
First, what do you mean with busybox ? I'm not quite sure if the rom I was using (the Omega) while testing the two unlocking applications listed above was "equiped" with that.
Second thing, you didn't really answered my question which I'm gonna reformulate now:
Can I actually change the version of the Baseband of my phone ? If yes, do I lose the SIM Unlock ? And if I can change the Baseband version and lose the actual SIM Unlock, can I reunlock it and keep that version of the Baseband or do I need to get back to the old version by reflashing it, then reunlock it ?
And finally, the efs folder that I need to backup every time before flashing a new rom (I didn't knew that), what does he contain ? From what I've seen he contains the nv_data.bin file which I think contains the unlock, and that folder also contains some IMEI informations and other stuff. If I actually back it up before installing a new rom, and if that rom changes the baseband version which will probably lock my phone, is it safe to put back that backed up efs folder while keeping the same rom and the same baseband version that came with it ? Does it reunlock the phone ? And do I just put it back using a root explorer and just overwrite it the existing ones ?
Yeah I know, too many questions a man can handle, but I really need to be informed of all those things so I can be aware of what I'm doing.
And thanks in advance for your patience.
Best regards.
Click to expand...
Click to collapse
okay, here we go,
1) There are a lot o people that become some sort of experts on devices thanks to this forums. It takes houndreds - if not thousends - of hours reading posts and executing some things you learn here.
2) busybox is an app. It's Linux based and to tell you the truth, not too many people know exactely what it does, It's very difficult to pinpoint every single thing that this "busy" app performs; Just think of it like a an app that does a lot of things for other app(s) to perform better or to perform at all. You can download it directly from Playstore; bare in mind that sometimes the unlocking app will work with different versions of busybox, so you'll have to try and see. I'm now using "Busybox Free 8.9.7" & "Busybox Installer 4.1"
3) You can always change your MODEM, Baseband it's some sort of radio version that cell phones use to get service, some basbands work on many countries, regions, some don't, still...you always can "odin it" and change the modem (Always read about flashing modem with odin before you do anything).
4) Some ROMs will re-Networkl-lock your device, hell, happened to me every time I went up from Gingerbread - Ice Cream Sandwich - Jelly Bean Leak. The only thing you have to do is get the right tools so you can always unlock it without the drama.
These unlocking apps let you LOCK & UNCLOCK as pleased.
5) the EFS folder indeed contents your network information, IMEI and stuff, it's always good to back it up as it is an important folder for your device to function. I use HC-kTool to back it up whenever i need to.
There is an unlocking method that makes you modify the .bin file. Never done it before but some guys here do it all the time and actually works.
Some other member could enlighten you in this matter; makes sense that flashing a new modem would lock your phone but i wouldn's know. Still, as I've got all these wonderfull apps to unlock....I really don't give a damn
Open for corrections, I've just used common sense.
gastonw said:
okay, here we go,
1) There are a lot o people that become some sort of experts on devices thanks to this forums. It takes houndreds - if not thousends - of hours reading posts and executing some things you learn here.
2) busybox is an app. It's Linux based and to tell you the truth, not too many people know exactely what it does, It's very difficult to pinpoint every single thing that this "busy" app performs; Just think of it like a an app that does a lot of things for other app(s) to perform better or to perform at all. You can download it directly from Playstore; bare in mind that sometimes the unlocking app will work with different versions of busybox, so you'll have to try and see. I'm now using "Busybox Free 8.9.7" & "Busybox Installer 4.1"
3) You can always change your MODEM, Baseband it's some sort of radio version that cell phones use to get service, some basbands work on many countries, regions, some don't, still...you always can "odin it" and change the modem (Always read about flashing modem with odin before you do anything).
4) Some ROMs will re-Networkl-lock your device, hell, happened to me every time I went up from Gingerbread - Ice Cream Sandwich - Jelly Bean Leak. The only thing you have to do is get the right tools so you can always unlock it without the drama.
These unlocking apps let you LOCK & UNCLOCK as pleased.
5) the EFS folder indeed contents your network information, IMEI and stuff, it's always good to back it up as it is an important folder for your device to function. I use HC-kTool to back it up whenever i need to.
There is an unlocking method that makes you modify the .bin file. Never done it before but some guys here do it all the time and actually works.
Some other member could enlighten you in this matter; makes sense that flashing a new modem would lock your phone but i wouldn's know. Still, as I've got all these wonderfull apps to unlock....I really don't give a damn
Open for corrections, I've just used common sense.
Click to expand...
Click to collapse
So what are the tools I need? I already tried 2 different sim unlocking apps on the play store and I got someone to try changing the upload ur nv_data.bin and it still doesn't unlock
RacecarBMW said:
So what are the tools I need? I already tried 2 different sim unlocking apps on the play store and I got someone to try changing the upload ur nv_data.bin and it still doesn't unlock
Click to expand...
Click to collapse
galaxysim unlock
galaxy s unlock
galaxy s2 sim unlock
Read First Threads:
http://forum.xda-developers.com/showthread.php?t=1360174
http://forum.xda-developers.com/showthread.php?t=1092451
http://forum.xda-developers.com/showthread.php?t=1289395
http://forum.xda-developers.com/showthread.php?t=2070375
http://forum.xda-developers.com/showthread.php?t=2069517
and don't forget busybox!
gastonw said:
okay, here we go,
1) There are a lot o people that become some sort of experts on devices thanks to this forums. It takes houndreds - if not thousends - of hours reading posts and executing some things you learn here.
2) busybox is an app. It's Linux based and to tell you the truth, not too many people know exactely what it does, It's very difficult to pinpoint every single thing that this "busy" app performs; Just think of it like a an app that does a lot of things for other app(s) to perform better or to perform at all. You can download it directly from Playstore; bare in mind that sometimes the unlocking app will work with different versions of busybox, so you'll have to try and see. I'm now using "Busybox Free 8.9.7" & "Busybox Installer 4.1"
3) You can always change your MODEM, Baseband it's some sort of radio version that cell phones use to get service, some basbands work on many countries, regions, some don't, still...you always can "odin it" and change the modem (Always read about flashing modem with odin before you do anything).
4) Some ROMs will re-Networkl-lock your device, hell, happened to me every time I went up from Gingerbread - Ice Cream Sandwich - Jelly Bean Leak. The only thing you have to do is get the right tools so you can always unlock it without the drama.
These unlocking apps let you LOCK & UNCLOCK as pleased.
5) the EFS folder indeed contents your network information, IMEI and stuff, it's always good to back it up as it is an important folder for your device to function. I use HC-kTool to back it up whenever i need to.
There is an unlocking method that makes you modify the .bin file. Never done it before but some guys here do it all the time and actually works.
Some other member could enlighten you in this matter; makes sense that flashing a new modem would lock your phone but i wouldn's know. Still, as I've got all these wonderfull apps to unlock....I really don't give a damn
Open for corrections, I've just used common sense.
Click to expand...
Click to collapse
Thanks alot for those "enligthments".
I don't know which method the guy I brough my phone to used to unlock it, but I reflashed the Omega custom rom yesterday and it actually didn't relock my phone ! But from now on I'm gonna be alot more cautious when flashing a new custom rom. Recovery backup from the CWM recovery mode, efs backup and maybe some Titanium backup too, even though I prefere having a clean "new phone" and install the apps by myself rather than referring to a backup. Yeah I know it's stupid but I like it that way.
Anyway, thanks again for your help and your patience, much appreciated c: .
Cheers.
salut.
btw, you might wanna add mobile odin yo that list. Hell of an app.
from sii xda-ded
Hi XDA. I'm an user of a veteran Xperia Play, so now I have some experience with custom roms, kernels, recoverys and such, but not with unlocking bootloaders. I unlocked my XP with the services of this page http://unlock-bootloader.com/, which is paid.
Anyway, the reason for this thread is that my girlfriend has had a Xperia Mini Pro SK17a for like one year. Until now it was fine but it suddenly started to lag and had random reboots, so she asked me to fix it. The idea is to install some rom, but the thing is: which is the most convenient method to unlock the bootloader so I can flash custom kernels on it?
The service menu says "bootloader unlock allowed = yes", so it can be done with:
1. The official method of sony page but DRM get lost and some Sony apps stop working, or
2. Through testpoint with s1tool o setool but then flashing kernels in the original formats .sin and .img is not possible anymore
As I unlocked my xplay with paid method there are none of these problems, but I'm not willing to pay for unlocking another phone that will only be flashed once or twice, so I have some questions about the other methods in order to make a desicion on what to choose :
- With the DRM certificates missing, which apps will no longer work?
- With the method of the sony page, can I flash kernels in .img and .sin format..?
- If I unlock with testpoint with no paid method, the only way to flash kernels is in .ftf format?
- The phone is no more on warranty period. If ever damaged, can I send it to a technician with no problem? (I say this because testpoints are used for repairing as well, and there may be some problem after unlocking by these methods, I suppose)
- Will it be better if I leave the BL locked and just flash a GB rom with stock kernel? My gf is looking for the best possible battery life and stability, so she doesn't care much about performance in games
Finally, what rom and kernel would you recommend me for daily use?? lol (I'm not asking for the "best rom/kernel", it's just that I don't have enough time to properly test battery life on various roms, spending a few days on each, so I'm asking you to please recommend me SOME GOOD ROM, NOT THE BEST ROM).
Sorry for so many questions and thank you all in advance
Anyone here??? Please respond or just answer the poll....
Sent from my SK17a using xda app-developers app
If I were you I'd try the stock gingerbread rom first and if she likes it it's all right
If not, unlock it using the official method. Maybe TrackID won't work any longer, but I guess apps like shazam doing the same work should still be working!
And if you unlock like that you can flash kernels in .img .elf .sin and .ftf (I guess these are the formats), but the same formats should be supported when you unlock using the testpoint method too
To find a good rom, just tell your girlfriend to look through the development threads and if she likes the design of a rom (check screenshots) she can tell you or check the bug list herself, then you flash it and she should be happy :good:
Sent from my Nexus 4 running Android 4.4
Thanks for your answer @mihahn
All this mess was just cause she's on .62 firmware. Since it can't be rooted (I even tried some chinese app called Eroot that is claimed to work on .62 but it didn't) I couldn't install CWM or titanium in order to backup her apps and things before flashing any rom.... and the ovbious solution was to flash a custom kernel and therefore unlocking BL....
She's not a tech fan, but after a lot of explaining and after she saw your answer, she finally decided to check out the devs section ( she's doing it right now ) and hopefully choose a good rom, not just a good-looking one
And again thanks for your answer, it was all she needed
Sent from my R800a using xda app-developers app
julian280 said:
Thanks for your answer @mihahn
All this mess was just cause she's on .62 firmware. Since it can't be rooted (I even tried some chinese app called Eroot that is claimed to work on .62 but it didn't) I couldn't install CWM or titanium in order to backup her apps and things before flashing any rom.... and the ovbious solution was to flash a custom kernel and therefore unlocking BL....
She's not a tech fan, but after a lot of explaining and after she saw your answer, she finally decided to check out the devs section ( she's doing it right now ) and hopefully choose a good rom, not just a good-looking one
And again thanks for your answer, it was all she needed
Sent from my R800a using xda app-developers app
Click to expand...
Click to collapse
Well e-root does work on .62 fw. You might not have follow the steps. Try again with proper steps
Cheers,
AJ
Abhinav2 said:
Well e-root does work on .62 fw. You might not have follow the steps. Try again with proper steps
Cheers,
AJ
Click to expand...
Click to collapse
Well, I tried several times even with various versions of eroot. I think there were the 1.0 and 1.2 but none work.
I dont have here the tutorials I followed but the steps are like this:
1. Open eroot
2. Connect the phone on with mass storage mode on, USB debugging on and unknown sources on.
3. Click on root button
4. Wait for it. It shows its making 4 steps
5. It says its rooted, so you just have to unplug, reboot and enjoy.
But all those is just assumptions of what it says cause I don't speak chinese.... and the text can't be selected in order to copy and translate with google. I also remember sometimes it shows an error-like screen with some red colored "x" marks but I didn't understand either what was that about.
Thanks anyways
Sent from my R800a using xda app-developers app
julian280 said:
Well, I tried several times even with various versions of eroot. I think there were the 1.0 and 1.2 but none work.
I dont have here the tutorials I followed but the steps are like this:
1. Open eroot
2. Connect the phone on with mass storage mode on, USB debugging on and unknown sources on.
3. Click on root button
4. Wait for it. It shows its making 4 steps
5. It says its rooted, so you just have to unplug, reboot and enjoy.
But all those is just assumptions of what it says cause I don't speak chinese.... and the text can't be selected in order to copy and translate with google. I also remember sometimes it shows an error-like screen with some red colored "x" marks but I didn't understand either what was that about.
Thanks anyways
Sent from my R800a using xda app-developers app
Click to expand...
Click to collapse
You can try rooting using the cydia impactor or even the other methods mentioned in my rooting guide for the build number .62. This should help you to gain root access
Sent from my Nexus 4 running Android 4.4
Just to advise - unlocking bootloader removes all user data, so leave it as a last resort after you have backed up your data.